Bookkeeping workflow
How to Prepare Bank Statements for Accountant Handoff
Give an accountant complete source statements, traceable Excel or CSV files, and a concise exception log instead of an unexplained folder of exports.
- For
- Business owners and bookkeepers sending converted statements to an accountant
- Read
- 7 min
- Updated
TL;DR
- Ask the accountant which periods, accounts, output formats, and supporting documents they need.
- Deliver original statements, unchanged conversion output, a reviewed working file, and an exception log.
- Use secure transfer, mask operational filenames, and avoid implying that conversion equals reconciliation.
Confirm the request before converting
The fastest handoff is the one that matches the accountant’s workflow the first time. Confirm entity, account list, statement periods, fiscal year, currency, preferred output, and whether source PDFs must accompany the table. Use Excel for a review-oriented workbook or CSV for portable rows, unless the accountant specifies another format.
Build a package that can be audited backward
- 1
Inventory the source statements
List entity, masked account, period, filename, and any missing month.
- 2
Convert one logical batch
Keep unrelated entities and currencies in separate jobs.
- 3
Preserve raw results
Store unchanged Excel or CSV output beside the source PDFs.
- 4
Create a reviewed working copy
Add corrections or notes without overwriting extracted values silently.
- 5
Write the exception summary
List failed files, missing periods, unsupported layouts, ambiguous rows, and manual changes.
- 6
Transfer securely
Use the channel agreed with the accountant and send access details separately when appropriate.
When preparing many months, start with the multi-month statement inventory. It makes a missing month visible before delivery instead of leaving the accountant to discover it during close.
Use a predictable folder structure
| Folder or file | Contents | Rule |
|---|---|---|
| 01-source-statements | Original native PDFs | Do not alter or overwrite |
| 02-raw-conversion | First Excel or CSV downloads | Keep read-only |
| 03-reviewed | Working files and correction notes | Every change remains traceable |
| 04-exceptions | Missing, failed, and unresolved items | Nothing disappears silently |
| README | Entity, coverage, accounts, format, reviewer, date | One-page orientation for the recipient |
If statement results need to be consolidated, use the merge versus separate decision guide and retain source filename, page, account, currency, and period columns.
State what has and has not been reviewed
- Number of expected, converted, reviewed, failed, and missing files.
- Whether transaction dates, amount signs, page coverage, and printed balances were checked.
- Which rows were corrected manually and where their source evidence is located.
- Whether categorization, import, or reconciliation was intentionally left to the accountant.
- Any deadline or decision that depends on an unresolved statement.
Handle the files as financial records
Agree on access, retention, and deletion with the recipient. Avoid full account numbers in email subjects or filenames. Before uploading, review the converter’s security and file-handling disclosures and ensure they fit the obligations that apply to the engagement.
Limitations to keep visible
- This checklist does not define an accountant’s professional requirements or replace their instructions.
- Conversion does not perform reconciliation, categorization, tax work, or accounting review.
- The workflow covers native PDF statements, not scanned or image-only documents.
Put the workflow into practice
Convert the complete native PDF set, then package it with the checklist below.
Prepare statement files for handoff