QBOKit

How to convert a PDF bank statement to QBO

Your bank gives you a PDF. QuickBooks wants a .QBO file, or at least a tidy CSV. The usual way to bridge that gap is to hand your statement to an online service that uploads it to their servers and charges by the page. QBOKit does the conversion inside your browser instead: the PDF is opened by code running on your own machine and is never sent anywhere.

🔒 Convert your PDF statement now — free, no account, nothing uploaded.

The steps

  1. Download the statement PDF from your online banking as normal.
  2. Drop it on the converter. The page fetches its PDF reader at that moment and reads the text out of the file locally.
  3. Check the table it found. This is the step that matters with PDFs, and there is more on why below.
  4. Pick your output — .QBO for QuickBooks Desktop, a cleaned CSV for QuickBooks Online, or OFX or QIF for other software.
  5. Import it in QuickBooks.

Why "nothing uploaded" is not a small detail

A bank statement is about as sensitive as a document gets: account numbers, salary, every payee you have. If you are a bookkeeper, it is not even your own data — it is your client's, and you are the one responsible for where it ends up.

Conversion services that run on a server need a copy of that file. That may be perfectly fine and they may delete it afterwards, but it is a copy you cannot see and a promise you cannot verify. Because QBOKit converts in the browser, there is nothing to promise: the file never leaves the machine you are sitting at. You can confirm it yourself — open your browser's network tab while converting, and you will see the PDF reader being downloaded to you and no statement going back.

To be straight about what you will see there: one small request to our own server recording that a conversion happened, carrying counts only — how many rows, whether the columns were detected, nothing from inside the file. No cell value, no account number, no file name. That is how we learn which bank layouts defeat the converter, and it is the only thing this page ever sends.

What works, and what does not

This needs a PDF that contains real text. Statements downloaded from online banking almost always do, because they are generated as documents. A scan or a phone photo of a paper statement is a picture of text, with nothing to extract — reading those needs OCR, which this tool does not do. If you drop one in, the converter tells you so plainly rather than handing you an empty file.

PDF reading here is new. Statements vary enormously in layout, and a converter that reads one bank's PDF perfectly can make a mess of another's. So the preview is not decoration: look at it before you download, and check a couple of rows against the statement itself. The preview writes dates as YYYY-MM-DD precisely so you can tell at a glance that the day and month have not been swapped.

If your statement comes out wrong, the honest fallback is to ask your bank for a CSV export, which most now offer, and convert that instead.

📮 And please tell us it failed — hello@qbokit.com. Which bank, and what the preview got wrong, is enough; do not send the statement itself, we neither want nor need your transactions. Layouts are the whole difficulty with PDFs, and knowing which one broke is how this gets better.

What it does with the table

There are no columns in a PDF. There is only text at positions on a page, so the table has to be reconstructed: text sharing a baseline becomes a row, text sharing a left edge becomes a column. From there a PDF statement is treated exactly like a CSV, which means it inherits the repairs that were already there:

Which output do you want?

UsingPick
QuickBooks Desktop.QBO, imported via File → Utilities → Import → Web Connect Files. See the QBO guide.
QuickBooks OnlineClean CSV — QBO Web Connect import is a Desktop feature. See the CSV format rules.
XeroOFX or a clean CSV. See the OFX guide.
Older finance softwareQIF, with the caveat in the QIF guide.

Convert my PDF statement — free

Related