QBO to PDF Converter

A QBO file becomes a document you can read, print and keep, drawn in this tab from the file's own period, balance and rows.

Convert your QBO file
A statement worth printing comes out in this tab.

Read here, kept here. Nothing is uploaded.

How to Convert QBO to PDF

A QBO to PDF conversion is one job: a QBO file goes in, and what comes out is a statement a person can read on paper exactly as it reads on screen. The file is opened in this tab, the records it carries become rows, and the PDF reaches your downloads without any copy of it existing anywhere else. Nothing about the flow involves an upload, an account, or a per-file charge.

  1. 1
    Choose the .qbo file; its period, currency and closing balance are read up front.
  2. 2
    Let the statement build: one row per transaction record, listed oldest first so the balance chain reads correctly.
  3. 3
    Download the PDF and keep it for printing and filing; the header names the account and period as the file did.

The header's closing-balance line appears only when the file carried one, and a statement holds one row per transaction record, seven columns, plus a balance column when the file states a balance. A PDF cannot sort, filter or sum, and a QBO to PDF conversion must not pretend otherwise; the spreadsheets on the other pages are where that work happens, and the links in the FAQ take you there.

What a QBO to PDF Conversion Is For

QBO is QuickBooks' Web Connect dialect of OFX: a statement written as tagged records, one block per transaction, wrapped in a header that says which account and which period the records belong to. Turning one into a spreadsheet answers a different question than turning one into a document. A spreadsheet is for working: sorting, filtering, summing, matching rows against a ledger. A document is for reading and keeping: the thing you print, staple, hand to an accountant, or drop into an archive folder, with the statement reading the same on paper as it does on screen. This page does the document: it draws the header from the file's own wrapper, one row per transaction record, and nothing the file did not state.

Portability across whatever is reading it is the whole point of the format, and the standard behind it says so directly: ISO 32000-1, which defines PDF, describes it as a digital form for representing electronic documents so they can be exchanged and viewed independent of the environment they were created in or viewed in.

What the PDF Keeps, and What It Cannot Do

The statement is built from three kinds of facts, and the differences between them are exactly where a QBO to PDF conversion behaves differently from the other downloads on this site. The rows come from the transaction records: date, type, amount, payee, memo, reference and account, lumped into nothing and dropped from nothing. The header facts come from the statement wrapper, which is the only place a period or a closing balance lives. And the drawing itself is done by the fonts built into every PDF reader, which is where the one real limit of this conversion sits. None of that limit touches the QBO to XLSX page, which writes the same rows as typed spreadsheet cells.

One row per record
Every transaction record becomes a row, in reading order, whether the amount is negative, positive, zero, or written as something the reader cannot parse. A record the reader trips on keeps its text rather than vanishing from the page.
The wrapper's own facts
Period, currency and closing balance are read from the statement wrapper the file carries. A file that omits a fact produces a PDF that omits it; nothing is reconstructed to fill the space.
The running balance, computed
When the file states a closing balance, the statement opens with it and walks it back through every row, so the balance beside each line is the sum of what actually happened. It ends, if everything can be read, on the number the bank said it ends on.
The base-14 font limit
The drawing uses the fonts every PDF reader is required to have, which cover Latin-1: accented European letters print as written. Names in anything wider degenerate to question marks, and the page says so rather than pretending otherwise.

What Each Column of the Statement Holds

The statement draws eight columns when the file names an account and a closing balance, fewer when it does not. The labels are the ones every download on this site writes, so a PDF can sit beside the spreadsheet twin of the same file and read the same way.

ColumnWhat it holds
DateYYYY-MM-DD, normalized from the stamp in the record, listed oldest first.
TypeThe transaction type as the record carries it: a debit is money that left, a credit is money that arrived, and a check is a cheque the file saw drawn.
AmountAs the record wrote it: decimals keep their point, and anything unparseable stays as its original text instead of a number.
NameThe payee, from the NAME record, or PAYEE where the file writes that instead.
MemoThe record's memo line, when the file has one to give.
Transaction IDThe FITID or check number, which is what makes a row traceable back to the file it came from.
AccountThe statement's own account, from the file's account identifier. The column disappears when no record names one.
Running balanceThe computed column: the wrapper's closing balance walked back over every row. It appears only when the wrapper states a balance, and any row whose amount is not a number leaves the chain blank from there on.

When the Statement Looks Wrong

Most surprises with a QBO to PDF conversion are the format being honest rather than the conversion misbehaving. Each of these is something the PDF does on purpose when the file does not cooperate.

A payee shows as question marks
The record wrote that name in characters the built-in fonts cannot draw, so the drawing replaced them rather than guess. The spreadsheet exports keep the name whole, and they are a conversion away if the name matters.
There is no balance column
The statement wrapper named no closing balance, so there is nothing for a chain to land on. The rows are all on the page; the column is not drawn rather than drawn with an invented starting point.
The header carries no account line
Some files state which account they describe and some do not. The PDF writes the account only when the file does, so a missing line means the file said nothing, not that rows were lost.
The count on the success line does not match the bank
The count is every transaction record the file carries, including any with a zero amount. Compare it against the bank's listed transactions rather than against a memory of the balance, and against the statement's own last row before asking for a recount.

Where a Statement Beats a Spreadsheet

The rows in this PDF and the rows in that spreadsheet are the same rows. The difference is who the file is for when it lands: these are the situations that call for a QBO to PDF conversion rather than a workbook.

  • Hand your accountant a month of activity they can open in anything, with no application besides a PDF reader involved at their end.
  • Archive a closing period in a folder you can print as-is, where the balance chain on the right of the table shows the period adding up without any recomputation.
  • Attach to an email, a submission packet or a dispute a document whose reading does not depend on the software installed at the other end.
  • Print the register for a binder. Rows arrive oldest first, so the paper reads like a bank statement, not like a download log.
  • Keep a copy around that no formula can break. A spreadsheet opened in the wrong locale rearranges itself; a PDF reads the same in every reader and every year.

Questions About QBO to PDF

No. The statement is drawn in this tab: the browser reads the file and builds the PDF, and there is no server in the flow for the file to land on.

No. A PDF page is a document, not a spreadsheet: nothing here sorts, sums or filters, because a PDF has no cells to compute with. The same rows as a working table are one conversion away.the QBO to CSV converter writes them as a table you can use.

The ones the built-in fonts can draw: Latin-1, which covers accented European names. A payee written in anything wider, such as Chinese, arrives in the PDF as a question mark. That is the format's stated limit, not this site's error, and the CSV and XLSX exports keep every character.

From the statement's own wrapper records, not from anywhere else. A QBO file names its period and, when the bank supplied one, a closing balance; the converter reads those and computes a running balance row by row. A file that carries no closing balance produces a PDF with no balance line at all.

A running balance only reads correctly oldest first. The statement lists rows by date, oldest to newest, whichever order the file happened to write them in, and ties keep the file's own order.

No. The conversion is free, the statement carries no watermark, and no account exists anywhere in the flow.

Turn your QBO file into a statement

Free, drawn in this tab, and the row count is the file's own.