Why Bookkeepers Shouldn't Upload Client Bank Statements to the Cloud

For client bank statements, start with an agreed collection and delivery procedure. Confirm the purpose, account and period, who may access the file and where the checked output belongs. Avoid an unnecessary upload when a local workflow meets the task; approve any external processing through your organisation’s procedure.

LocalExtract desktop capabilities: Export one selected PDF at a time as CSV with date, description and amount columns. Open the CSV in Excel and save an XLSX there if needed. The app has no batch queue, JSON/QBO/OFX export or accounting sync. PDF parsing and OCR run locally; internet is needed for account, subscription and update services, including periodic Pro verification. Test your statement and review every row: a supported language or bank guide does not guarantee compatibility with every format.

Agree the collection scope

Ask which account, currency and period are needed for the engagement. A personal account, company account and credit card can have different statement cycles. Confirm whether the request is for an original issued statement, transaction rows or both. Do not collect the client’s online-banking password or authentication code; ask them to download the authorised documents themselves.

Receive files through an approved channel

Use the collection channel approved for your engagement. Confirm the intended recipient and access permissions before sending financial records. If a document contains accounts outside the agreed scope, ask the client for the appropriate separate record where available. Keep the original unchanged rather than making an edited document look bank-issued.

Keep a traceable working copy

Record the source filename, account identifier in the permitted form and statement period. Store an unchanged original and a separate working copy. Avoid putting account numbers into public links or broadly visible filenames. Check whether desktop or document folders are automatically synchronised before assuming that a locally saved PDF stays only on that device.

Compare the handling steps

A practical file-handling checklist

1. Check the document’s account, currency and cycle dates against the client’s request. Note missing periods rather than treating an empty activity export as an issued statement.
2. Extract one account section at a time. Keep source filename and page references in the working sheet so an unexplained amount can be traced back.
3. Compare all exported rows against the PDF. Check fees, interest, wrapped descriptions, repeated transactions and debit/credit signs before any accounting import.
4. Reconcile the period and list unresolved differences for the client. Keep credit-card liability conventions distinct from deposit-account balances.
5. Deliver only the agreed output through the approved channel. Record retention and deletion decisions for working files, exports and backups.

Check the requirements that apply

Coverage depends on your activities and jurisdiction. Use the FTC’s official coverage guide and IRS Publication 4557 where relevant. Check applicable duties with a qualified adviser. Local processing is not itself a compliance certification and does not remove security, recordkeeping or incident obligations.

How LocalExtract fits

LocalExtract processes one selected PDF at a time on Mac or Windows, using on-device parsing and OCR. It exports CSV with date, description and amount. For XLSX, open the CSV in Excel, check the import and save a workbook there. It has no PDF batch queue, native QBO/OFX/JSON export or automatic accounting sync.

Sign-in, subscription services, updates and periodic Pro verification need the internet. Do not plan permanently offline paid access. Its free evaluation covers a cumulative 10 pages; Pro is USD 10/month or USD 60/year. A bank guide or supported language does not prove compatibility with your statement.

FAQ

Should I ask a client for online-banking credentials? No. Ask the client to obtain their own authorised statement and transmit it through the agreed channel. A conversion task does not require their password or authentication code.

Should I delete the original after exporting CSV? Follow the engagement’s retention procedure. A CSV does not preserve the issued document’s layout or authenticity. Keep the original where required for reconciliation or supporting records.

How should I handle missing or unclear amounts? Record the unresolved row and request a clearer or complete source. Do not guess values or insert an unexplained adjustment merely to make totals match.

Can I send a CSV instead of an issued statement? Confirm the recipient’s requirement. Use CSV for agreed transaction analysis; provide the authorised original when the request is for the bank’s issued document.

Evaluate with your own document

Download LocalExtract and use the 10-page evaluation to test one statement. Verify the output and the file-handling procedure before using it for client work.