For accountants and CPA firms
Bank statement converter for accountants
Client statements arrive as PDFs. You need them in the client’s ledger, reconciled, and defensible when someone asks where a figure came from. That is what this converter is built around.
- Five arithmetic checks on every statement
- Every row opens its source line on the PDF
- QBO, IIF, Xero CSV, Tally XML, Excel and more
- Reconciliation sheet for the file
The short answer
How accountants get client bank statements into the ledger
A bank statement converter for accountants turns a client’s PDF statements into transaction data the client’s accounting software can import, and shows you whether that data agrees with the statement before it gets there. Upload the PDFs, review anything flagged, and download the file the client’s ledger takes: QBO for QuickBooks Online, IIF for QuickBooks Desktop, a Xero-preset CSV, Tally XML, or Excel for your own schedules.
The usual alternatives each fail in a particular way. Retyping is slow and nobody checks it twice. Copying from the PDF splits descriptions across rows and turns amounts into text. Generic PDF-to-Excel tools give you a table that looks finished whether or not a row was lost at a page break. The bank feed, where there is one, only reaches back so far, which is exactly the period a year-end catch-up needs.
What goes wrong is rarely visible in the output. A dropped row, a debit read as a credit or a brought-forward balance counted as a transaction all produce a tidy spreadsheet. You find out at the bank reconciliation, weeks later, with a difference nobody can explain. VouchRow checks the arithmetic at conversion time instead, using the balances the bank printed, and points at the row that breaks.
The job
A client sends a year of statements as PDFs, usually after you have asked twice. Those transactions have to reach the ledger accurately enough that you will put your name to the accounts built on them, and quickly enough that the engagement is still profitable.
Why this is harder than it should be
Extraction tools are confident by default. A spreadsheet of 400 rows looks finished whether or not a page-boundary row was dropped, a debit was read as a credit, or a digit was misread on a scan — and none of those announce themselves. The checking, which is the part your professional judgement is actually for, gets pushed onto you with no tooling to do it with. So it gets done properly on the first client and by eye after that.
Step by step
The accountant’s workflow, statement to ledger
The same five steps for every client, whichever software they use. Each step leaves something you can keep on file.
- 1Collect the client’s PDFsAsk for the statements as downloaded from online banking where you can; those have a text layer and are read in your browser. Paper statements the client scanned are fine too and go through OCR. Password-protected PDFs are fine: you enter the password when asked, and it unlocks the file in your browser without being sent to us.
- 2Convert them in one goDigital statements upload as a batch, so a client’s twelve months go in together. Scanned statements are converted one at a time. Each statement is read, rows are rebuilt (wrapped descriptions merged, brought-forward balances recognised) and the checks run immediately.
- 3Review the flagged rowsWhere the running balance, page subtotal or closing balance does not agree, the row responsible is flagged. Click it and the PDF opens with the printed line highlighted, so you compare the extracted figure with the source in seconds instead of hunting through pages.
- 4Export in the client’s ledger formatPick the format for that client: QBO, IIF, Xero or QuickBooks CSV, OFX, QIF, Tally XML or Excel. Transaction IDs are deterministic, so if you re-import a corrected file, software that de-duplicates on the ID does not double the rows.
- 5Keep the reconciliation on fileThe Excel export carries a Reconciliation sheet showing which checks ran and whether they passed, and paid-plan exports include a reconciliation note. File it with the working papers as the record of how the transactions were produced.
What helps
What this does about it
The arithmetic is checked before you see it
Five checks run on every conversion, strongest first: row-by-row running balance, page subtotals, statement balance, printed credit and debit totals, and transaction count. Anything that does not agree is flagged at the row rather than as a total, and the result says which checks ran and which the statement did not carry the data for.
Every row points back at the page it came from
Click a flagged row and the original statement opens with that line highlighted. Checking an exception costs seconds rather than a trip to a PDF viewer, which is the difference between checking them all and checking the first three.
Whatever your client’s software takes
Eight formats, so a client on QuickBooks Desktop needing IIF and one on Xero needing CSV are the same conversion with a different download. Client statements do not have to be routed to different tools.
Retention you set, including none
Client financial records under your control means retention is your decision, not ours. It runs from storing nothing at all — transactions never written to the database — through to a year, and expired data is deleted daily along with the stored PDF.
Why it works
Why accountants use a checking converter rather than a plain extractor
Errors found at the row, not at year end
A balance chain that breaks at row 212 tells you to look at row 212. That is a different job from a ledger that is out by an unexplained amount after the period is closed.
A source reference for every figure
Each transaction links to the highlighted line on the statement page it came from. When a reviewer or the client queries an entry, the evidence is one click away.
One tool for every client’s software
QuickBooks Online, QuickBooks Desktop, Xero, Sage, Tally, Quicken or a spreadsheet: the conversion is the same, only the download differs.
Scanned statements handled
Older statements and client printouts are read with OCR and then put through the same checks, which is what makes a scan safe to post from.
Retention set per your policy
Keep converted statements for 24 hours, 7 days or 30 days, or store nothing at all. Digital statements are read in the browser; scanned pages are discarded after the request.
Priced by the page
Only pages with transactions count. For busy season, slide your plan up or add a page pack from $0.06 a page; pack pages never expire, so a quiet month does not waste them.
Checked before export
A misread digit is caught on its own row
Every conversion is tested against the statement: the running balance on every row, page subtotals, opening plus movement against closing, the printed credit and debit totals, and the transaction count. When a number does not add up, VouchRow names the row and highlights the line it came from on the PDF.
Arithmetic only: it verifies amounts, balances and totals, not descriptions or dates, and two errors that cancel out would pass. The source-line link covers the rest.
How the checks workRunning balance check
- POS AMAZON MKTPLACE−86.4316,604.12
- CHECK #1042−1,250.0015,354.12
- ZELLE FROM J MORALES+640.0015,994.12
Every row agrees with the balance printed beside it.
Catch-up and year-end
Month-end and year-end catch-up for clients
Most statement conversion in a practice is catch-up: the client who brings a shoebox of PDFs in March, the new engagement where the previous bookkeeper stopped in June, the account the bank feed was never connected to, or the card that only shows up on statements. The bank feed in QuickBooks or Xero typically reaches back a limited window, so anything older has to come from the PDFs.
For a catch-up, convert every statement for the account, check that each one reconciles on its own, then confirm that each statement’s opening balance matches the previous statement’s closing balance. VouchRow checks the first part on every conversion; the second is a quick look down the Reconciliation sheets in Excel, and a mismatch there usually means a missing month rather than a misread row.
Month-end work is the same at smaller scale. A client whose feed has dropped out for a few weeks sends the PDF, you convert it, and the IDs on the export keep the overlap with the feed from duplicating when the software matches on them. Where the feed and the statement disagree, the statement is the document of record and the source link shows exactly what it says.
- Convert all statements for one account before importing any of them
- Check each statement’s opening balance against the previous closing balance
- Import oldest first so the ledger’s running balance builds in order
- Keep the Excel export with its Reconciliation sheet for each period
Multi-client formats
Every client’s software, from the same conversion
A practice rarely has one ledger system. One client is on QuickBooks Online, another still runs QuickBooks Desktop, a third moved to Xero, and the firm’s own analysis lives in Excel. Running a different tool per client means a different set of quirks per client. With VouchRow the conversion and the checks are identical; you choose the output at download.
Some formats come with conditions set by the receiving software, not by us. QBO files need the bank’s INTU.BID identifier so QuickBooks will accept them. Recent QuickBooks Desktop versions are often easier to feed with IIF. Xero’s CSV import expects its own column layout and a date format that matches the organisation’s region. Tally needs its ledgers to exist before vouchers are imported.
| Client software | Usual export | Note |
|---|---|---|
| QuickBooks Online | QBO or QuickBooks three-column CSV | QBO needs the bank’s INTU.BID |
| QuickBooks Desktop | IIF (Professional plan and above) or QBO | IIF avoids Web Connect version limits |
| Xero | CSV with the Xero preset, or OFX | Match the date format to the organisation’s region |
| Sage | Generic CSV or OFX | Map columns once in Sage’s import screen |
| Tally | Tally XML (Professional plan and above) | Create the ledgers in Tally first |
| Quicken | QFX | Quicken expects QFX rather than plain OFX |
| Working papers | Excel (.xlsx) | Transactions and Reconciliation sheets |
Defensibility
An audit trail you can put your name to
When you sign off on accounts, the question is not whether the transactions look plausible but whether they match the bank’s record. Five checks run on every conversion, strongest first: the running balance row by row, page subtotals, opening balance plus movement against the closing balance, the printed credit and debit totals, and the transaction count. Where a statement prints no running balance, the converter falls back to the totals it does print, and the result says which checks ran.
It is worth being precise about what that proves. The checks are arithmetic. They confirm that the extracted amounts add up the way the bank says they should; they cannot confirm a description or a date, and two errors that cancel each other out would pass. That is why the source link matters as much as the checks: anything you want to test beyond the arithmetic, you can see on the page.
Nothing is silently adjusted. A statement that will not reconcile stays flagged, no balancing line is invented, and the export records what did and did not agree. That is the version you want in a file someone may review later.
Working papers
Using the Excel export as a working paper
The Excel export is two sheets. Transactions holds the rows with dates normalised, amounts signed consistently and descriptions joined back together where the bank wrapped them across lines. Reconciliation holds the checks: the balances used, the totals compared, and the result of each.
That makes it a reasonable starting schedule for a bank lead sheet, a proof of cash, or a review of a client’s own bookkeeping. You can label selected rows in bulk before export, for example marking owner drawings or transfers between the client’s accounts, so the schedule arrives already grouped the way you want to test it. Labelling is deliberate and manual; the converter does not guess at categories.
- Tie the Reconciliation sheet’s closing balance to the bank confirmation or the next statement
- Filter Transactions for large or unusual items and open each at its source line
- Label selected rows (for example, intercompany transfers) before exporting
- Store the file alongside the PDFs in your practice’s document system
Client data
Handling client statements responsibly
A statement downloaded from online banking has a text layer, and VouchRow reads it in your browser. Scanned statements need OCR, so their pages are sent to the processing layer for that one request and discarded afterwards. Statements are never used to train models.
What stays in your account is up to you. Retention can be 24 hours, 7 days, 30 days or nothing at all, and conversion history and projects (saved statements grouped by client) are available on paid plans. The security page sets out the detail for any review your firm needs to do.
This is not bookkeeping software
Side by side
Ways a practice gets statements into the books
Each route below ends with transactions in a ledger. The difference is how much of the checking is left to you.
| Manual entry | Generic PDF-to-Excel | VouchRow | |
|---|---|---|---|
| Time per statement | Long, scales with rows | Short, then clean-up | Short, review flagged rows only |
| Wrapped descriptions | Typed by hand | Often split into extra rows | Merged into one row |
| Brought-forward balances | Skipped by eye | Often imported as a transaction | Recognised and excluded |
| Checks against bank balances | Only if you do them | None | Running balance, subtotals, totals, count |
| Link back to the PDF line | No | No | Every row |
| Ledger-ready formats | n/a | Usually Excel or CSV only | QBO, QFX, OFX, QIF, IIF, CSV presets, Tally XML, Excel |
| Re-import safety | n/a | Duplicates likely | Deterministic transaction IDs |
Who uses it
Where accountants use it
Year-end for a client with no feed
Twelve PDFs for a business account the client never connected. Convert as a batch, clear the two flagged rows against the source lines, export QBO and import oldest first.
Taking over from a previous bookkeeper
The ledger stops in June. Convert July to December, check each opening balance against the previous close, and import the gap in the client’s software format.
A client on QuickBooks Desktop
The client’s Desktop version no longer takes Web Connect files. Export IIF instead and import through the Desktop utilities menu.
Review engagement support
Convert the statements independently of the client’s books and compare the Excel export with their ledger. Differences point at specific rows you can open on the page.
FAQ
For accountants: questions
What is the best bank statement converter for accountants?
The one that tells you when its output is wrong. For accounts you sign, look for checks against the statement’s own balances, a link from each row back to the PDF, and exports in the formats your clients’ software accepts. VouchRow is built on those three; the comparison page covers other tools.
Can I convert a client’s bank statement PDF to QuickBooks?
Yes. Export QBO for QuickBooks Online or Desktop versions that accept Web Connect (the file needs the bank’s INTU.BID), IIF for QuickBooks Desktop on the Professional plan and above, or the QuickBooks three-column CSV.
Does it work with Xero, Sage and Tally?
Yes. Xero takes the Xero-preset CSV or OFX, Sage takes a generic CSV or OFX, and Tally takes Tally XML on the Professional plan and above. Each software page explains the import steps.
How do I know nothing was missed?
Every conversion checks the running balance row by row, page subtotals, opening plus movement against closing, printed debit and credit totals, and the transaction count. A missing row breaks the arithmetic at the point it should have been. The checks are arithmetic only: they cannot verify descriptions or dates, and two cancelling errors would pass.
Can I convert scanned client statements?
Yes, through OCR, one statement at a time. Scans get the same checks as digital statements, which matters more because OCR is less certain than a text layer.
Can I convert a whole year at once?
Digital statements upload in batches, so a year of monthly PDFs for one account can go in together. Scanned statements are converted individually.
Will re-importing a corrected file create duplicates?
Transaction IDs are deterministic, so the same row produces the same ID every time. Software that de-duplicates on the ID, such as QuickBooks with QBO files, will not double the rows.
Does it categorise transactions to the chart of accounts?
No, by design. You can label selected rows in bulk before export, but coding to accounts belongs in the client’s ledger, where the chart of accounts and the bank rules already live.
Which plan suits an accounting practice?
Plans are metered by pages with transactions: Starter $15 a month for 300 pages, Professional $39 for 900 pages (adds IIF and Tally XML), Business $99 for 2,500 pages. Each plan slides to more pages, annual billing charges ten months for twelve, and page packs add more from $0.06 a page.
Keep going
Related guides and converters
Formats your clients’ software takes
How the checking works
Related professions
Also relevant
Put checked client statements on file
Create an account, convert a client’s statements, and keep the Reconciliation sheet with your working papers. Plans start at $15 a month.