Review / article
Bank statement conversion for bookkeepers: protect the handoff
Separate each client’s evidence, verify the drafted transactions against the PDF, then map and review the approved export in the destination system.
A worked example
Keep the question with the handoff
Fictional client scenario
Complete page range. Review and prepare its approved output.
The page numbering skips page 3. Request the complete PDF.
Please send the complete March statement PDF for Account B, including page 3.
Keep the unresolved question with Account B. A handoff should identify the account and period, the approved file, and anything still requiring the client's attention.
Define the client boundary before collecting PDFs
Confirm who is allowed to provide a client’s statements, who will review extracted rows, and who may receive the final export. Keep an independent record of the client, account, and statement period for every PDF; a file name alone may not be enough to distinguish similar monthly statements.
Use authorized access for uploads and downloads, and send exports only to the intended client workflow. Fulla’s source and export access is private and authorized, but that does not decide your firm’s permissions or create a cross-client delegation process for you. Do not share a workspace API key with clients as a substitute for access control.
Reconcile the draft with the actual statement
Conversion begins with a draft, not a finished ledger. Open source-linked evidence for questionable rows and confirm the period, page coverage, amounts, debit and credit signs, and any opening, running, or closing balances supplied by the bank. A missing page or duplicated transaction can leave an otherwise tidy spreadsheet wrong.
Correct descriptions and amounts where the PDF supports a correction; split or merge rows when source lines require it. Record unresolved ambiguity for the client rather than guessing a merchant, category, or tax treatment from the extraction. Approve the exact revision only after the transaction set has been checked against the source.
Map exports to the destination, then inspect the import
Choose approved CSV for a tabular import, XLSX for workbook-based review, or JSON for an application you control. Decide how the destination represents dates, signed amounts versus debit and credit columns, currency, and optional balances before you map fields. Source page references can help trace a disputed transaction back to its PDF.
Preview the mapped file and the destination’s import results before accepting records into the books. Check row counts against the approved statement, account and period selection, duplicate handling, and the effect of debit or credit sign conventions. Fulla produces the approved export; it does not directly sync or post transactions to an accounting platform.
Close the handoff while evidence is available
Source PDFs and derived financial content expire 24 hours after presign; reviewing or exporting does not extend the deadline. Allow time for client questions, source verification, approval, export download, and import review within that window. If more investigation is needed after expiry, arrange an authorized new submission rather than assuming an old download link will remain valid.
Keep your own client-approved records and retention practices separate from Fulla’s short content lifetime. When handing over a final file, identify the client, account, period, and reviewed revision in your own workpapers so a later question can be traced without treating an unapproved draft as the final deliverable.
Questions about this article
Will conversion post transactions to my accounting platform?
No. Fulla creates an approved JSON, CSV, or XLSX export. Map and review that output in your destination workflow before any accounting entries are posted.
Can I treat a clean-looking spreadsheet as reviewed?
No. Compare the rows and balances with the source statement, resolve discrepancies, and approve the exact revision before using an export.
Will the statement remain available if a client replies next week?
No. Private financial content expires 24 hours after presign, and approval or export does not extend that deadline. Plan the review and download accordingly.