Home › Blog › Security & Privacy › Handling Client Bank Statements Securely
A practical security standard for bookkeepers handling client bank statements: secure transfer, tight storage, limited access, retention, and deletion.
By StatementVerified Editorial · November 2, 2026 · 6 min read · Filed under Security & Privacy
A bank statement is one of the most sensitive documents in a small business. It shows balances, income patterns, every payee, account numbers, and enough transaction detail to reconstruct a person financial life or impersonate an account holder convincingly. When clients hand statements to a bookkeeper, they are extending serious trust, and the bookkeeper handling standard should be worthy of it: deliberate about how files arrive, where they live, who can see them, how long they stay, and how they are destroyed.
Many practices handle statements on habit rather than on standard, in email inboxes, downloads folders, and shared drives with forgotten permissions. This guide sets out a workable standard for a small practice: secure transfer in, organized and access-controlled storage, careful day-to-day handling including any conversion tools used, defined retention, and real deletion at the end. None of it requires enterprise infrastructure. All of it requires deciding once and then actually following the decision.
Set one approved route for clients to send statements and put it in the engagement paperwork and the intake request: a secure upload link, a client portal, or an encrypted file-sharing folder you control. Discourage regular email attachments, which persist in multiple inboxes and sent folders indefinitely, and decline photographs of statements sent through messaging apps, which combine poor quality with uncontrolled copies on personal devices. When a client does send by email despite guidance, move the file into proper storage promptly and delete the message copy where your systems allow.
On your side, download and file statements in one sitting rather than letting them accumulate in a downloads folder synced to unknown places. Confirm receipt to the client with the accounts and months listed, which both reassures them and creates the completeness record the engagement needs. If you use any online conversion or processing tool as part of the workflow, its handling of uploaded files is part of your transfer standard, and the retention questions in the later sections of this guide apply to it exactly as they apply to your own storage.
Give client statements one defined home: a single folder structure per client inside storage that is encrypted in transit and at rest, backed up, and protected by strong unique passwords and multi-factor authentication on the accounts that reach it. Organize by client, account, and period so that access can be granted and audited sensibly. The test of your storage is a simple question you should be able to answer instantly: if a client asked where their statements are and who can open them, could you answer completely and truthfully in one minute?
Access follows need. Only the people actively working on that client should be able to open that client financial files, and access should be removed when staff change roles or leave, the same week, as a checklist item rather than an intention. Avoid local copies on laptops outside the controlled storage, avoid personal cloud accounts entirely for client material, and treat a lost device as a security incident to respond to, not an inconvenience, when it may hold client financial data.
Most exposure happens in ordinary moments rather than dramatic breaches. A statement left open on a screen in a shared space, a printout for a meeting that never gets shredded, a file shared with a collaborator through a link set to anyone can open, a converted spreadsheet emailed onward with full account numbers in a header row. Build small habits against each: lock screens, print rarely and shred promptly, share with named people rather than open links, and check what a file actually contains before forwarding it, including its metadata and its extra tabs.
Be equally deliberate about the tools in the chain. A conversion tool, a spreadsheet add-in, or a storage sync client each becomes a place your client data lives. Before adopting one, learn where files are processed, how long they are retained, and how deletion works there, and record the answer in your vendor notes. Your standard is only as strong as the least examined tool in the workflow, and clients reasonably hold you responsible for the whole chain, not just the parts with your name on them.
Retention should be a policy, not an accumulation. Define how long you keep client statements and working files after an engagement ends or a period is filed, taking account of your professional obligations, the client ability to obtain statements from their bank, and any legal or contractual requirements that apply to your practice. State the retention period in the engagement terms so the client hears it from you first. Indefinite retention feels safe and is not: every retained file is exposure carried forever, and most old statements can be re-obtained from the bank if a genuine need ever arises.
Distinguish the records of your work from the bulk data. Reconciliation reports, final statements relied on for filed periods, and correspondence about judgments may deserve longer retention as your professional record, while duplicate downloads, superseded conversions, and working copies generally do not. A retention pass once or twice a year, client by client, keeps the archive aligned with the policy instead of with everyone forgetfulness, and produces a log of what was destroyed and when.
Deletion means the file is removed from live storage, from shared locations, and in due course from backups under your backup rotation, not merely moved to a folder called old. When an engagement ends, follow an offboarding list: return or confirm the client own copies of key records, remove their material from any tool accounts used along the way, revoke collaborator access, and delete your copies on the schedule your terms promised, confirming completion to the client in writing. That confirmation is a trust asset; clients remember being told their data was properly destroyed long after they forget the bookkeeping.
Finally, write the whole standard down in a page or two and keep it where your team can find it. A standard that exists only as the senior person habits dies with their holiday. Reviewed annually, tightened when a tool changes, and actually followed, it becomes part of what your practice sells: not just accurate books, but custody of sensitive documents that a client never has to worry about. In a profession built on trust, that is not overhead. It is the product.
It is the common route and the weakest one, because copies persist in inboxes and sent folders on both sides. Provide a secure upload route in your intake request, move any emailed files into controlled storage promptly, and delete the email copies where your systems allow.
For a period defined in your engagement terms, reflecting your professional obligations and any applicable requirements, rather than indefinitely. Records of the work itself may be kept longer than duplicate downloads and working copies, which should be cleared on a regular retention pass.
Where files are processed, how long the service retains them, whether deletion is automatic and verifiable, and how you remove your client data if you stop using it. Record the answers; the tool becomes part of your handling chain and your responsibility.
Security & Privacy · November 5, 2026
For landlords, property managers, and lenders: check statement arithmetic, test whether running balances walk, watch layout tells, and verify with the bank.
Security & Privacy · November 4, 2026
How to evaluate any bank statement tool retention behaviour: what auto-delete should mean, where copies hide, and the questions to ask before uploading.
Security & Privacy · November 3, 2026
When to redact account numbers on bank statements before sharing, what reviewers actually need to see, and what to never redact, including balances.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.