QuickBooks Web Connect from a PDF
PDF to QBO converter for bank statements
Turn a PDF bank or credit card statement into a .qbo file that QuickBooks imports through Web Connect. You supply your bank's Intuit ID; we build the rest of the file and the transaction IDs that stop duplicates.
- QuickBooks Online and Desktop
- Your own Intuit bank ID, never a guessed one
- Deterministic FITIDs, so re-imports don't duplicate
- Checked against the statement before export
<INTU.BID>10898<STMTTRN> <TRNTYPE>CREDIT <DTPOSTED>20260302 <TRNAMT>4210.00 <FITID>a3f9c2e81b07 <NAME>ACH DEPOSIT STRIPE PAYOUT</STMTTRN><STMTTRN> <TRNTYPE>CHECK <DTPOSTED>20260305 <TRNAMT>-1250.00 <FITID>5d10e7b4c9a2 <CHECKNUM>1042</STMTTRN><LEDGERBAL><BALAMT>15354.12
The short answer
How to convert a PDF to QBO
To convert a PDF bank statement to QBO, a PDF to QBO converter has to extract the transactions, write them as an OFX 1.0.2 document with Intuit's QuickBooks tags, and give each transaction a unique FITID. The file must also carry your bank's Intuit bank ID (INTU.BID). VouchRow does all of that from your statement: you upload the PDF, enter your bank's ID once, and download a .qbo that QuickBooks Online and QuickBooks Desktop import through Web Connect.
The bank ID is where most PDF-to-QBO attempts fail. QuickBooks checks INTU.BID against its own list of Web Connect institutions and rejects the file if it doesn't match, with an error (OL-301, OL-249, "unsupported financial institution") that describes a connection problem rather than the tag that caused it. Tools that fill in a default ID make every file claim to come from a bank it didn't come from. We ask for yours.
In exchange, QBO gives you something CSV can't: the file enters through QuickBooks' bank feed, where transactions are matched against what's already in the books and repeats are recognised by ID.
Step by step
Converting a PDF statement to QBO and importing it
- 1Find your bank's Intuit bank IDIf your bank has ever given you a .qbo file, open it in a text editor and copy the number after <INTU.BID>. It's a short number and it's the same for every account at that bank. Don't borrow another bank's number.
- 2Upload and review the statementSign in, upload the PDF, and check any row the running-balance check flags. Each row links to its highlighted line on the PDF page.
- 3Export QBOChoose QBO and enter the bank ID. The file is built with the bank or credit card account structure as appropriate, a FITID per transaction and the closing balance.
- 4Import into QuickBooks OnlineTransactions → Bank transactions → Link account → Upload from file. Select the .qbo, choose the QuickBooks account it belongs to, and the transactions appear in the For review tab to match or add.
- 5Or import into QuickBooks DesktopFile → Utilities → Import → Web Connect Files. Select the .qbo, link it to an existing account (or create one), then add the downloaded transactions from the Bank Feeds Center.
Why it works
Why this QBO file imports cleanly
Stable FITIDs
Each transaction ID is derived from the account, date, amount and description, with a counter for genuine repeats. Re-converting the same statement gives identical IDs.
Your bank ID, not a placeholder
The file carries the INTU.BID you supply, so QuickBooks sees your own institution, not one borrowed from somewhere else.
Card statements done right
Credit card statements are written with the OFX credit card structure, so charges and payments land the right way round in a QuickBooks card account.
Full descriptions kept
QuickBooks truncates the NAME field at 32 characters. The full description is also written to MEMO, so nothing is lost.
Checked before it's built
The running balance, totals and transaction count are verified before the file is written, so what QuickBooks receives ties to the statement.
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.
Inside the file
What's inside a QBO file
A .qbo file is a plain-text OFX 1.0.2 document. It's SGML rather than XML, so leaf elements like <TRNAMT> are not closed, which is the most common reason a hand-built file is rejected. These are the parts QuickBooks reads:
| Field | What it holds | Why it matters |
|---|---|---|
| OFXHEADER, VERSION:102, CHARSET:1252 | The plain-text header block before the document | QuickBooks expects OFX 1.0.2 SGML with a Windows-1252 body |
| <FI> ORG / FID | The institution's name and ID | Shown in QuickBooks as the source |
| <INTU.BID> | Intuit's ID for your bank | Checked against the Web Connect list; a mismatch means OL-301 or OL-249 |
| <BANKACCTFROM> or <CCACCTFROM> | Account number and type (checking, savings or credit card) | Lets QuickBooks link the file to the same account each time |
| <DTSTART> / <DTEND> | Statement period, as YYYYMMDD | Unambiguous dates, unlike CSV |
| <STMTTRN> TRNTYPE, DTPOSTED, TRNAMT | Each transaction's type, date and signed amount | The transaction itself |
| <FITID> | A unique ID per transaction | QuickBooks' duplicate key |
| <NAME> and <MEMO> | Description (NAME up to 32 characters, MEMO up to 255) | The full text survives QuickBooks' truncation |
| <LEDGERBAL> | Closing balance and its date | Gives QuickBooks the statement balance |
INTU.BID
The bank ID, and what to do if you don't have one
INTU.BID is a number Intuit assigns to each institution enrolled in Web Connect. It isn't secret and it isn't your account number. Your bank's is printed inside any .qbo file the bank has issued you, on the line beginning <INTU.BID>.
If your bank isn't enrolled in Web Connect, it has no valid ID, and no QBO file will import for it however it's made. Using another bank's ID can get the file past the check, but it makes the import claim an origin it doesn't have, and it can tangle the account's online banking settings in QuickBooks. The honest alternatives work just as well: QuickBooks Online accepts the three-column CSV and OFX through the same Upload from file screen, and QuickBooks Desktop users can import IIF.
Troubleshooting
Common PDF to QBO import errors and fixes
Almost every QBO import failure has one of a few causes.
| Error or symptom | Cause | Fix |
|---|---|---|
| OL-301, OL-249, "unable to verify financial institution" | INTU.BID missing, mistyped or not a Web Connect institution | Use the ID from a .qbo your bank issued; otherwise use CSV, OFX or IIF |
| "Unsupported financial institution" | Same cause: QuickBooks doesn't recognise the ID | As above |
| Transactions imported twice | The period overlaps transactions already pulled in by the bank feed, which carry the bank's own IDs | Import only the dates the feed doesn't cover, or match in For review |
| QuickBooks Desktop won't accept the file at all | Intuit switches off online banking services, Web Connect included, for Desktop versions past their support date | Use IIF, which imports through a file utility rather than the bank feed |
| Wrong account shown or account missing in Desktop | The account is already linked to a different bank's online services | Deactivate the account's online services in its bank feed settings, then import again |
| Descriptions cut short | QuickBooks shows NAME, capped at 32 characters | The full text is in MEMO |
Duplicates
Why re-importing the same statement is safe
QuickBooks uses each transaction's FITID to recognise one it has already seen. Many converters generate IDs from timestamps or random values, so converting the same statement twice produces two sets of IDs and QuickBooks treats every row as new.
Here, the FITID is built from the transaction itself (account, date, amount and description), with an occurrence counter so two identical coffees on the same day still get different IDs. Convert the statement today and again next month and the IDs are identical, so a second import is recognised. Transactions brought in by a live bank feed carry the bank's IDs, not ours, so overlapping a feed period is still worth avoiding.
Context
QuickBooks now reads PDFs. When do you still need QBO?
QuickBooks Online can now read some PDF bank statements directly. For a recent digital statement in QuickBooks Online, that may be enough, and it's worth trying.
A PDF to QBO conversion still makes sense when you're on QuickBooks Desktop (which has no native PDF import), when statements are scanned, when you're importing a year or more of history, or when you want to see that every row reconciles before anything reaches the bank feed. The QBO file is also something you can keep and re-import with the same IDs.
Side by side
QBO, CSV or IIF for QuickBooks?
| QBO (Web Connect) | CSV | IIF | |
|---|---|---|---|
| QuickBooks Online | Yes | Yes | No |
| QuickBooks Desktop | Yes, while the version is supported | Not through Web Connect | Yes |
| Needs a bank ID | Yes (INTU.BID) | No | No |
| Duplicate detection | Yes, by FITID | No | No, writes straight to the register |
| Goes through the bank feed for review | Yes | Yes (Online) | No |
| Plan needed here | Starter and up | Starter and up | Professional and up |
Who uses it
When QBO is the right output
Filling a gap in the bank feed
The feed broke for two months, or only reaches back 90 days. Convert the missing statements to QBO and import them into the same account, then match in For review.
QuickBooks Desktop catch-up
Desktop has no native PDF import. A year of PDF statements becomes twelve .qbo files that import through Web Connect.
Accountants working across many clients
Convert client statements, check them, and import into each client's file knowing a second import won't double anything.
FAQ
PDF to QBO converter for bank statements: questions
How do I convert a PDF to QBO?
Upload the PDF statement, review the extracted rows, choose QBO and enter your bank's Intuit bank ID. The download is a QuickBooks Web Connect file ready for QuickBooks Online (Upload from file) or Desktop (File → Utilities → Import → Web Connect Files).
What is INTU.BID and why do you ask for it?
It's the Intuit Bank ID. QuickBooks matches it against its list of Web Connect institutions and refuses the file if it doesn't match, which is what errors OL-301 and OL-249 mean. We ask for yours instead of shipping a default, because a hard-coded ID would make every file claim to come from an institution it didn't come from. If your bank has ever sent you a .qbo file, the number is inside it after <INTU.BID>.
I don't have a bank ID. What can I use instead?
OFX and QIF carry the same transactions and need no bank ID. QuickBooks Online also imports CSV directly, and QuickBooks Desktop imports IIF. All of these are available here.
Will re-importing create duplicates?
Not from our files. Every transaction gets a FITID derived from the account, date, amount and description, so converting the same statement twice produces identical IDs and QuickBooks recognises the repeats. Overlapping a period your live bank feed already covers can still duplicate, because those rows carry the bank's IDs.
Does this work with QuickBooks Desktop as well as Online?
Both. Online: Transactions → Bank transactions → Link account → Upload from file. Desktop: File → Utilities → Import → Web Connect Files. Desktop versions past Intuit's support date lose Web Connect; use IIF on those.
Can I convert a credit card statement to QBO?
Yes. Card statements are written with the OFX credit card structure, so they import into a QuickBooks credit card account with charges and payments on the right side. The card issuer's Intuit bank ID is needed, as for a bank.
How do I open a QBO file to check it?
It's plain text. Open it in Notepad or any text editor to see the header, the INTU.BID line and each <STMTTRN> block. Don't save it from a word processor, which can change the encoding.
Which plan includes QBO?
Every paid plan: Starter ($15 a month, 300 pages), Professional ($39, 900 pages) and Business ($99, 2,500 pages). Only pages that contain transactions count.
Keep going
Related guides and converters
Related formats
QuickBooks guides
Build a QBO file QuickBooks will accept
Create an account, upload a PDF statement, enter your bank's Intuit ID and download a Web Connect file with stable transaction IDs. QBO is included from Starter at $15 a month.