AutoBankConvertAutoBankConvert home

Encrypted Email for Bookkeepers: Sending Statements

By AutoBankConvertPublished March 26, 2026Updated March 26, 2026

Encrypted email for bookkeepers protects the message itself, so a bank statement, payroll report or tax ID can only be read by the person it was sent to. Use it whenever a file shows full account numbers or identity details, choose a method the client can open from a normal inbox, and never send its password alongside it.

When is plain email not enough for client statements?

Plain email is not enough when the attachment would hurt the client if a stranger read it: full account numbers, Social Security or tax ID numbers, payroll details, or a year of statements in one file. Ordinary email may be protected between servers, but it sits readable in both mailboxes and in every forward and backup after that.

The risk is less about someone intercepting the message on its way and more about where it lives afterwards. A statement sent as a plain attachment stays in your sent folder, the client's inbox, their phone, and the inbox of anyone they forward it to. If any of those accounts is taken over later, the file goes with it.

A quick test helps decide. If the client would be upset to see the attachment posted on a notice board, it needs more than plain email. A one-page monthly profit and loss summary may pass. A statement with the full account number does not, and neither does an onboarding form with a tax ID. If you only need the last four digits of an account visible, redact the rest before sending and the question gets easier.

Encrypted email options a bookkeeping client can open

The encrypted email options that work best for clients are the ones that open from a normal inbox with no new software: provider message encryption, where the client gets a link and a one-time code, and password-protected attachments, where the password travels separately. Certificate-based email is secure but rarely practical for small business owners.

The table below shows which method suits which file. The rows are examples.

File Recipient Example method
Monthly report, no account numbers Client owner Plain email is usually fine
Bank statement with full account number Client owner Encrypted message or portal link
Year of statements for a tax return Client's CPA Shared folder link to a named person
Payroll register with staff IDs Client payroll contact Encrypted message, expiry set
Onboarding form with tax ID Practice inbox Upload to a portal, not email

Message encryption built into your email provider is the easiest place to start. The client receives a notice, clicks through, and confirms who they are with a code. Nothing is installed on their side, and some providers let you revoke the message later.

Password-protected files, such as an encrypted PDF or ZIP, work with any email account. They protect the file wherever it is saved, which plain message encryption may not. Their weakness is the password, which the next sections deal with.

Whatever method you pick, check that the vendor behind it has had its controls examined. The post on reading a SOC 2 report for bookkeeping software explains what to look for.

Do confidential or private email modes count as encryption?

Confidential or private email modes are not the same as encryption, and they should not be treated as a substitute. They mainly control what the recipient can do with a message, such as forwarding or printing it, and they set an expiry date. They do little to protect a file that has already been opened.

Gmail's own help page on confidential mode describes features such as an expiry date, revoking access, and turning off forward, copy, print and download. It also warns that recipients can still take screenshots or photos, and that a recipient with malicious software may still copy or download the message. The page does not describe the mode as encryption.

Confidential mode is still useful for one thing: making a message expire, so a statement does not sit in a client's inbox for years. Pair it with a protected attachment or a link if the content itself needs protection.

Passwords sent in the same encrypted email thread

The most common mistake with protected attachments is sending the password in the same email thread, or in a second email a minute later. Anyone who reaches the client's inbox then gets both the file and the key. Send it by text or phone, or agree it once at onboarding.

A few related habits undo the protection just as quickly:

  • Using the same password for every client, so one leak opens every file.
  • Using an obvious password such as the client's business name or zip code.
  • Writing the password in the email subject so the client can find it later.
  • Attaching both a protected copy and an unprotected copy by accident.

A misdirected email is still the most likely leak, whatever the encryption. Check the recipient field before every send, and turn off address autocomplete for clients with similar names. If an error does happen, the post on errors and omissions insurance for bookkeepers covers how a professional mistake like this may be treated.

A portal or shared-folder link is usually better than encrypted email for statements, because the file stays in one place you control and the link can expire or be revoked. Encrypted email suits one-off messages to people outside your systems. For monthly statement traffic in both directions, a portal is easier to audit and easier to clean up.

Statements usually flow in from the client more than out. Asking clients to upload into a portal, or to forward statements to one dedicated address, keeps those files out of personal inboxes. AutoBankConvert accepts statements uploaded or forwarded for each client and encrypts them in transit and at rest, so inbound statements stop piling up in staff mailboxes.

For outbound files, put the method in your security checklist and apply it to every client. The bookkeeping data security checklist has a sharing section where it fits. When cleanup engagements send you years of old statements by plain email, decide the method before the first upload and allow for the time it takes; the post on bookkeeping cleanup pricing covers how to price that setup work.

All posts in Security and trust