Bank statement to QBO converter

Convert a bank statement PDF to QBO free — upload the statement, get a .qbo file you upload straight into QuickBooks Online — free for your first statement.

Convert to QBO — Free

See the difference

From messy PDF to clean QBO

Before
Original bank statement PDF

bankstatement.pdf

After
<STMTTRN>
  <TRNTYPE>DEBIT</TRNTYPE>
  <DTPOSTED>20251015</DTPOSTED>
  <TRNAMT>-67.42</TRNAMT>
  <NAME>WHOLEFDS MKT #10247</NAME>
</STMTTRN>
<STMTTRN>
  <TRNTYPE>DEBIT</TRNTYPE>
  <DTPOSTED>20251015</DTPOSTED>
  <TRNAMT>-4.75</TRNAMT>
  <NAME>STARBUCKS #8291</NAME>
</STMTTRN>
<STMTTRN>
  <TRNTYPE>DEBIT</TRNTYPE>
  <DTPOSTED>20251014</DTPOSTED>
  <TRNAMT>-1850.00</TRNAMT>
  <NAME>ZELLE TO LANDLORD</NAME>
</STMTTRN>
<STMTTRN>
  <TRNTYPE>CREDIT</TRNTYPE>
  <DTPOSTED>20251014</DTPOSTED>
  <TRNAMT>2847.63</TRNAMT>
  <NAME>PAYROLL - ACME CORP</NAME>
</STMTTRN>

bankstatement.qbo

Works withChaseBarclaysHSBCWells FargoBank of AmericaCitiTD BankPNC& 10,000+ more

How it works

Three steps to a clean QBO file

1.Upload your PDF

Drag and drop your bank statement — downloaded from your bank or scanned from paper. Both work.

2.AI extracts every transaction

Our AI reads each row, identifies dates, merchants, and amounts, then classifies spending into 19 categories.

3.Download QBO & import into QuickBooks

Export .qbo and upload it in QuickBooks Online under Banking → Upload transactions. On QuickBooks Desktop export IIF instead and use File → Utilities → Import → IIF Files.

Why us

Not just a PDF extractor — a bank statement QBO exporter

Generic PDF tool
Dumps raw text — no OFX structure
No FITID, so imports collide
Dates left in the bank's format
Amounts keep commas and symbols
QuickBooks rejects the file
This converter
Valid OFX 2.x structure in a .qbo file
A unique FITID derived per transaction
DTPOSTED normalized to YYYYMMDD
TRNAMT written as a plain signed number
Real DTSTART / DTEND statement range

Preview

What the QBO export looks like

A structured Web Connect file — every transaction carries a type, a date, an amount, and its own id.

bankstatement.qbo
<BANKTRANLIST>
  <DTSTART>20251001</DTSTART>
  <DTEND>20251031</DTEND>
  <STMTTRN>
    <TRNTYPE>DEBIT</TRNTYPE>
    <DTPOSTED>20251015</DTPOSTED>
    <TRNAMT>-67.42</TRNAMT>
    <FITID>K7QX2M1</FITID>
    <NAME>WHOLEFDS MKT #10247</NAME>
    <MEMO>Groceries</MEMO>
  </STMTTRN>
  <STMTTRN>
    <TRNTYPE>DEBIT</TRNTYPE>
    <DTPOSTED>20251015</DTPOSTED>
    <TRNAMT>-4.75</TRNAMT>
    <FITID>3PD9WZ4</FITID>
    <NAME>STARBUCKS #8291</NAME>
    <MEMO>Dining Out</MEMO>
  </STMTTRN>
  <STMTTRN>
    <TRNTYPE>CREDIT</TRNTYPE>
    <DTPOSTED>20251014</DTPOSTED>
    <TRNAMT>2847.63</TRNAMT>
    <FITID>B5HN0TC</FITID>
    <NAME>PAYROLL - ACME CORP</NAME>
    <MEMO>Income</MEMO>
  </STMTTRN>
</BANKTRANLIST>
Each transaction is an <STMTTRN> block: TRNTYPE = debit or credit, DTPOSTED = the date in YYYYMMDD, TRNAMT = the signed amount, FITID = the unique id QuickBooks uses to spot transactions it has already imported, NAME = the payee. This is the structure a Web Connect import expects.

The problem

Why you need a PDF to QBO converter

The bank feed won't connect
Not every bank is supported by QuickBooks bank feeds, and connections break. Converting the PDF statement to QBO is the fallback that always works.
Bank feeds only go back 90 days
Older transactions have to come from statements. Convert each PDF to QBO and backfill the months the feed never delivered.
Client hands you a PDF
Bookkeepers rarely get bank access — they get a PDF by email. This turns that PDF into a file QuickBooks can take in one import.
Manual entry eats the margin
Re-keying a quarter of transactions takes hours and introduces typos. Extraction takes seconds and keeps the amounts exact.
Catch-up bookkeeping
A year of neglected books means a stack of PDF statements. Convert each one to QBO and import them in date order.
Several banks, one company file
Each bank formats its PDF differently. Convert every statement to the same QBO structure and import them into one QuickBooks file.

PDF to QBO: get your bank transactions into QuickBooks

Converting a bank statement PDF to QBO is the shortest route to getting transactions into QuickBooks when the bank feed is unavailable, broken, or simply does not reach far enough back. The .qbo Web Connect file carries the same fields QuickBooks would have received from the feed itself — transaction type, posted date, amount, payee and a unique id — so nothing has to be mapped by hand after the import.

The part that most often goes wrong in a PDF-to-QuickBooks conversion is the date. Banks write dates differently around the world: MM/DD/YYYY in the US, DD/MM/YYYY across the UK and Europe, YYYY-MM-DD in parts of Asia. The converter detects the convention your statement actually uses and rewrites every date into the YYYYMMDD form the OFX specification requires, which is what stops the silent day/month swap that turns a March transaction into a December one.

Amounts and transaction types are handled with the same care. Debits are written as negative values in TRNAMT and credits as positive ones, with currency symbols and thousands separators stripped, because importers reject anything else. Every transaction is given a FITID derived from its own date, amount, and description, so re-importing an overlapping period does not duplicate rows — QuickBooks recognises ids it has already seen and skips them.

Whether the PDF came from your bank's website or was scanned from a paper statement, extraction works the same way: digitally generated PDFs and scanned documents both go through the same pipeline, with OCR applied where the page holds no text layer. Multi-page statements are handled in one pass — upload a quarterly statement and every transaction across every page lands in a single .qbo file, ready to import.

Statement analyzer pricing

Pro

$19/ month

For heavy files and repeat work

  • 200 PDF pages per billing cycle
  • Unlimited visible transactions per report
  • Subscription and recurring charge detection
  • Priority support
Most popular

Business

$49/ month

For lenders, accountants, and teams processing at volume

  • 500 PDF pages per billing cycle, then $0.08/page
  • REST API access with your own keys
  • Unlimited visible transactions per report
  • Priority support
Your file stays privateSecure checkoutCancel subscriptions anytime

FAQ

Bank statement to QBO FAQ

What is a .QBO file?+−
A .qbo file is Intuit's Web Connect flavour of OFX — the contents follow the OFX specification, and only the extension differs. Each transaction is an <STMTTRN> block holding a type (DEBIT or CREDIT), a DTPOSTED date in YYYYMMDD form, a TRNAMT amount, a unique FITID, and a NAME payee. Unlike a CSV, there are no columns to map on import: QuickBooks reads the fields by name. Unlike a plain .ofx, the .qbo extension is what QuickBooks expects for a Web Connect import.
How do I import the file into QuickBooks?+−
QuickBooks Online: Banking (or Transactions) → Upload transactions, pick the .qbo, map it to the right account and review the transactions before you accept them. That is the path this converter is built for. QuickBooks Desktop is different: its Web Connect import checks the file against Intuit's own list of financial institutions, which no third-party file can satisfy, so export IIF instead and use File → Utilities → Import → IIF Files. Both exports come from the same upload — you only choose a different format on the way out.
Why does QuickBooks reject my .qbo file?+−
Four causes account for nearly all rejections: missing or duplicated FITIDs, which make QuickBooks silently skip transactions it thinks it has already seen; a DTPOSTED that is not in YYYYMMDD format; a TRNAMT carrying a currency symbol or thousands separator; and a header that declares one OFX version while the body is written in the other serialisation. A fifth is specific to QuickBooks Desktop and is not a defect in the file: Web Connect matches an INTU.BID bank identifier against Intuit's own list of financial institutions, and Intuit issues those identifiers to banks. We do not put one in, because it would mean the file claimed to come from an institution it did not. So on Desktop, use the IIF export instead — it is Intuit's own desktop import format and needs no identifier. QuickBooks Online performs no such check and takes the .qbo directly. To see exactly which of these your file trips, run it through our free QBO / OFX validator — it names the failing line.
Is it really free?+−
Yes — no account needed to try it. You get one free upload total, ever, and an unpaid upload analyzes up to 10 PDF pages. Pro ($19/mo) includes 200 pages per billing cycle and Business ($49/mo) includes 500 pages per billing cycle.
Which banks are supported?+−
Any bank worldwide that provides PDF statements: Chase, Barclays, HSBC, Deutsche Bank, BNP Paribas, ING, Santander, HDFC Bank, and 10,000+ banks worldwide.
Will importing create duplicate transactions?+−
Every transaction gets a FITID derived from its own date, amount, and description, so the same transaction produces the same id every time. If two statements overlap by a few days, QuickBooks sees matching ids and skips the repeats instead of booking them twice.
Is my PDF secure?+−
Your PDF is processed in memory and immediately discarded — never stored on disk, never shared. Only the structured transaction data is saved temporarily to generate your .qbo download.

Convert your PDF to QBO — free

No account required. Get a .qbo file ready for QuickBooks in under 30 seconds.

Upload PDF & Convert to QBO

Already have a CSV, QIF or OFX file? Convert it directly — no PDF step needed.

Not using QuickBooks? Quicken, GnuCash and Moneydance read OFX and QIF.