For bookkeepers
Bank statement converter for bookkeepers
Catch-up work, new-client onboarding and the account the feed never connected: all of it starts with a stack of PDF statements. Convert them in a batch and spend your time on the rows that need it.
- Batch upload for digital statements
- Review only the rows that fail a check
- A different export per client, same conversion
- Re-imports do not duplicate
The short answer
How bookkeepers turn PDF statements into client books
A bank statement converter for bookkeepers takes the PDF statements a client hands over and produces an import file for that client’s software, checked against the statement’s own balances. For catch-up work, that means uploading a year of digital statements in one batch, clearing the handful of rows that do not reconcile, and downloading QBO, IIF, a Xero CSV or Excel per client.
Bookkeeping from PDFs goes wrong in predictable ways. Bank feeds only reach back a limited period, so older months exist only as statements. Copying out of a PDF splits wrapped descriptions into separate rows and drags in page headers. Dates with no year on them get the wrong year when the statement crosses December. And when fourteen statements are converted in an afternoon, nobody is checking each one by hand.
VouchRow is built for that volume. Every statement is checked the same way regardless of how many came before it, and the review screen shows only what failed, with a link to the line on the page.
The job
Several clients, each on different software, each handing over statements in whatever form their bank produced. The work is repetitive and priced as though it were quick, so anything that turns a two-hour statement into a ten-minute one changes the economics of the engagement rather than merely being convenient.
Why catch-up work goes wrong
Volume hides errors. Converting one statement, you would notice a missing transaction; converting fourteen in an afternoon, you will not. And the errors that survive are the quiet ones — a row lost at a page break, a carried-forward balance counted as a transaction, a date read the wrong way round in a month where every day falls below the twelfth. They surface at the year end, in a reconciliation that is out by an amount nobody can trace.
Step by step
A catch-up job, start to finish
The routine for onboarding a client or catching up missed months.
- 1Gather the statements per accountAsk the client to download PDFs from online banking where possible, one folder per account. Downloaded statements have a text layer and convert in a batch. Password-protected PDFs are set aside from a batch and converted one at a time, where you type each password.
- 2Upload the account’s months togetherDrop all the digital statements for one account in at once. Each is converted and checked on its own. Scanned statements, if the client only has paper, go through OCR one at a time.
- 3Clear the flagged rowsMost statements reconcile cleanly. Where one does not, the row that breaks the balance chain is marked. Open it at the source line, correct it if the read was wrong, and move on.
- 4Check continuity between monthsEach month’s opening balance should equal the previous month’s closing balance. A gap here usually means a statement is missing from what the client sent, which is worth asking about before you import anything.
- 5Export in the client’s format and import oldest firstQBO or QuickBooks CSV for QuickBooks Online, IIF for Desktop, the Xero preset for Xero, Tally XML for Tally. Deterministic transaction IDs mean that re-importing a corrected file does not create duplicates where the software matches on IDs.
What helps
What this does about it
Volume does not weaken the checking
The same five arithmetic checks run on the fourteenth statement of the afternoon as on the first, and they do not get tired. A dropped page-boundary row breaks the running balance at exactly the row where it should have been, whether or not anyone is looking closely.
A year of statements in one run
Drop a client’s twelve monthly PDFs in together. Each is converted, reconciled and saved to that client’s project, and a file that fails — a password-protected one, a scan among the downloads — is reported and skipped rather than ending the run. What survives is a list you work through, not fourteen rounds of the same four clicks.
One conversion, every client’s format
The client on QuickBooks Online gets QBO, the one on QuickBooks Desktop gets IIF, the one on Xero gets a Xero-preset CSV. Same conversion, different download, no second tool and no second subscription.
Statements stay organised by client
Converted statements are saved into projects, so a client’s history is in one place rather than in a downloads folder named by the bank’s file naming scheme.
A cost that scales with the work
Metered in pages, and only pages carrying transactions count. A catch-up month costs more than a quiet one, which is the right shape for work that arrives in bursts.
Why it works
What changes in a bookkeeper’s week
Review time goes to exceptions
Instead of scanning 400 rows for a problem, you look at the three that failed a check. The rest have been tied to the bank’s printed balances.
Batch upload for catch-up
A year of digital statements for one account goes in together. A file that fails is reported without stopping the others.
Every client’s format
QBO, IIF, Xero and QuickBooks CSV presets, OFX, QIF, QFX, Tally XML and Excel from one conversion.
No duplicates on re-import
Transaction IDs are generated the same way every time, so importing an overlapping or corrected file does not double transactions in software that checks IDs.
Statements kept by client
Projects keep each client’s saved statements together on paid plans, with retention you choose: 24 hours, 7 days, 30 days or none.
Bulk labelling when you want it
Select rows and label them in one action, for example owner transfers or a loan account, before export. Nothing is categorised automatically.
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.
Onboarding and catch-up
Client onboarding and catch-up bookkeeping from PDFs
New clients rarely arrive with clean books. Some have not reconciled since the last tax return, some changed software mid-year, some have a card account that was never linked to a bank feed. The months that matter are usually older than the feed can reach, so they come from PDF statements.
The order that avoids rework: convert every statement for an account before importing any of it, confirm each one reconciles, confirm the months chain together, then import oldest first. Doing it this way surfaces a missing month or a misread page while it is still a question for the client, not a mystery in the reconciliation screen.
For a client changing software, the same converted statements can be exported again in the new format. The conversion does not have to be redone, and the checks stay with it.
- One folder per account, statements named by month
- Convert all, check all, then import
- Opening balance of each month equals the previous closing balance
- Import oldest first so the software builds the running balance in order
Multi-format
One process, many client ledgers
A bookkeeper with a dozen clients may touch five ledger systems in a week. The conversion step should not change with them. In VouchRow it does not: the statement is read and checked the same way, and the format is a choice at download.
Each receiving system has its own expectations, and they are worth knowing before the import fails. QuickBooks Online accepts QBO files when the bank’s INTU.BID is present, or the three-column CSV. QuickBooks Desktop takes IIF, which avoids the Web Connect version limits some older installs hit. Xero’s CSV import wants its own columns and a date order that matches the organisation’s region. Wave, Zoho Books, FreshBooks and MYOB each have a page here with the format and steps.
| Client set-up | Export | Watch for |
|---|---|---|
| QuickBooks Online, feed gap | QBO | Bank’s INTU.BID; IDs prevent overlap duplicates |
| QuickBooks Desktop | IIF | Professional plan and above |
| Xero | CSV, Xero preset | Region date format |
| Wave or FreshBooks | CSV | Column mapping on import |
| Tally | Tally XML | Ledgers created in Tally first; Professional plan and above |
| Client wants a spreadsheet | Excel | Reconciliation sheet included |
Review speed
Reviewing hundreds of rows without reading them all
The checks are what make volume safe. The strongest is the running balance: for every pair of rows, the previous balance plus this amount must equal this balance. A row lost at a page break, or a credit read as a debit, breaks that chain at the exact row. Page subtotals, opening plus movement against closing, the printed debit and credit totals and the transaction count add further checks where the statement prints them.
When a statement has no running balance column, which is common on credit card statements, the converter falls back to the totals the statement does print and says so. That is still a meaningful check, though less precise about where an error sits.
Two limits are worth keeping in mind. The checks are arithmetic, so a wrong date or a garbled description passes; and two errors that cancel out would pass too. For anything you are unsure of, the source link opens the PDF at the highlighted line.
Recurring problems
The errors catch-up work keeps producing
Most bookkeepers have met each of these at least once, usually at year end.
- A carried-forward balance imported as a transaction, doubling the opening position. VouchRow recognises brought-forward lines and excludes them.
- A description wrapped over two lines becoming two transactions, one with no amount. Wrapped descriptions are merged into their row.
- Rows dropped where a table continues onto the next page. The running balance breaks at that point and the row is flagged.
- Overlapping statements and bank feed creating duplicates. Deterministic IDs let software that matches on IDs skip what it already has.
- Statements imported out of order, so the running balance in the software jumps. Date order is preserved per statement; import the oldest statement first.
Pricing for practices
A cost that follows the work
Plans are metered by pages that contain transactions; cover pages, terms and blank pages do not count. Starter is $15 a month for 300 pages, Professional $39 for 900 pages and adds IIF and Tally XML, and Business $99 for 2,500 pages. Annual billing charges ten months for twelve.
Catch-up work arrives in bursts, so a heavy month can be topped up with a page pack from $0.06 a page instead of a bigger plan. Pack pages never expire, so a pack bought for one client’s backlog is still there for the next.
Every plan includes seats, so the whole practice can work in one workspace, each person with a role you choose and, if needed, access to only their own clients.
It will not learn your categories
Side by side
Catch-up options compared
| Retyping | Bank CSV export | Generic PDF converter | VouchRow | |
|---|---|---|---|---|
| Reaches older months | Yes | Often limited history | Yes | Yes |
| Checked against bank balances | No | No | No | Every statement |
| Wrapped descriptions | By hand | Usually fine | Often split | Merged |
| Ledger formats | n/a | Whatever the bank offers | Excel or CSV | QBO, IIF, Xero CSV, Tally XML and more |
| Scanned statements | Yes, slowly | No | Sometimes | Yes, via OCR |
| Source line per row | No | No | No | Yes |
Who uses it
Typical bookkeeping jobs
Eighteen months behind
A new client has not touched the books since the last return. Batch-convert each account’s statements, chain the months, and import into QuickBooks Online as QBO.
The credit card nobody linked
A business card has never been connected to the feed. Convert its statements, where the totals check stands in for the missing running balance, and export to the client’s ledger.
Switching a client to Xero
Re-export the client’s converted statements with the Xero CSV preset rather than reconverting, and import the history into the new organisation.
A client with paper statements only
Scan them, convert one at a time through OCR, and rely on the checks to show which rows the scan made uncertain.
FAQ
For bookkeepers: questions
How do I import old bank statements into QuickBooks?
Convert the PDFs to QBO (or the QuickBooks CSV for Online, or IIF for Desktop) and import them oldest first. The bank feed only reaches back a limited period, so older months have to come from statements.
Can I convert a year of statements at once?
Yes for digital statements, which upload in batches. Scanned statements are converted one at a time through OCR.
Will the statements duplicate what the bank feed already imported?
Transaction IDs are deterministic, so software that de-duplicates on IDs will recognise rows it already has from a previous import of the same file. Where the feed and the statement overlap, review the date range in the software before accepting.
Can one account handle several clients?
Yes. Projects keep each client’s saved statements together, and team members can be limited to the clients they work on.
Does it categorise transactions?
No. You can label selected rows in bulk before export, but categorisation is left to the client’s software, where your bank rules and chart of accounts are.
What if a statement does not reconcile?
The failing check and the row that breaks it are shown, with the source line on the page. Nothing is adjusted to force a balance. Often the cause is a misread digit on a scan or a missing page in what the client sent.
Do password-protected statements work?
Yes. Upload the locked statement and enter its password when asked. It unlocks the file in your browser and is never sent to us or stored. In a batch, locked files are set aside to convert one at a time.
Which plan do bookkeepers usually need?
It depends on page volume. Starter covers 300 transaction pages a month; Professional covers 900 and adds IIF for QuickBooks Desktop and Tally XML. Page packs from $0.06 a page cover busy months.
Keep going
Related guides and converters
Client software
Guides for catch-up work
Clear your next catch-up faster
Create an account, batch-convert a client’s statements and review only the rows that fail a check. Plans start at $15 a month.