PDF to QBO: Get Statements Into QuickBooks Without Retyping
QuickBooks will happily import a QBO or OFX file. The problem is getting one out of a PDF statement, with every transaction signed the way QuickBooks expects and the balances still adding up.
Convert one file free — see the table land in Excel
Free daily conversions · running-balance verification · QBO, OFX, and CSV export.
Why QuickBooks imports go wrong
Signs reversed
A debit imported as a credit doubles the account balance in the register instead of correcting it.
Duplicate transactions
Re-importing a period you already loaded creates a second copy of every row. QuickBooks does not deduplicate for you.
Description fields that break the parser
Line breaks, quotes, and ampersands in merchant names break badly formed QBO files.
No running balance to check
A plain CSV import gives no arithmetic check — errors only surface when the reconciliation does not tie.
Credit cards treated like bank accounts
Card statements have the opposite sign convention. Using the bank path flips every purchase.
Multi-account PDFs
One file containing two accounts must be split before import, or the transactions land in the wrong register.
The three file formats, briefly
- QBO — the QuickBooks Web Connect format. Bundles transactions for one account; the safest choice for a single statement.
- OFX — the more general Open Financial Exchange format, accepted by QuickBooks and most other accounting tools.
- CSV — flexible but dumb: you map columns yourself and QuickBooks trusts whatever signs you supply.
Import routine that avoids duplicates
Convert and reconcile first
Confirm the opening balance plus credits minus debits equals the closing balance before importing anything. An unreconciled import is a future cleanup job.
Check the date range
Compare the converted range with what is already in the register. Overlap is the source of duplicates.
Import one account at a time
Web Connect files carry the account they belong to. Splitting multi-account PDFs is not optional.
Match, then accept
Use QuickBooks’ matching screen rather than bulk-accepting. It is the last cheap chance to catch a sign error.
If the statement is a scan
Scanned statements convert the same way, with OCR in front. The reconciliation check is what makes this safe: a misread digit will break the running balance, and the mismatch points you at the exact row to inspect against the page image.
Without that check, a scanned statement import is a guess dressed as data. With it, you have a file whose arithmetic you have already verified.
Frequently asked questions
Can QuickBooks import a PDF directly?+
No. QuickBooks imports CSV, QBO, and OFX files. A PDF has to be converted first, and the conversion is where the structure and signs are decided.
Will importing create duplicates?+
Only if the period overlaps what is already in the register. Check the existing date range before importing, and use the matching screen rather than bulk accept.
Does it work for credit card accounts?+
Yes — card statements need the opposite sign convention from bank accounts. Converting them through the card path keeps purchases as outflows.
What if the statement is scanned?+
OCR runs first, then reconciliation. Check any row the reconciliation flags against the page image before importing.
Is the QBO file specific to one account?+
Yes. A Web Connect file describes a single account, so split multi-account PDFs before generating the export.
Keep reading
Done reading? Convert a document and check the output yourself.
Convert a statement to QBO