How to import a PDF bank statement into GnuCash

Check your online banking first: if it still offers a download of that period in OFX or QIF, use it — it comes from the bank's own system and is exact. Conversion is for everything else: statements older than the download window, closed accounts, PDFs a client or tenant sent you, paper statements you have scanned.

The bank statement converter here reads text PDFs, scans and phone photos, and writes OFX, QIF and CSV. Two details matter for GnuCash:

• Every OFX transaction gets a stable ID derived from the transaction itself, so importing the same file twice does not duplicate anything — GnuCash recognises the IDs the second time.
• Card statements are written as credit card accounts in both OFX and QIF, so charges increase the liability and payments reduce it, as GnuCash expects.

Before downloading, the converter checks the statement's own arithmetic: opening balance plus money in minus money out must equal the printed closing balance, to the cent. A file that fails that check will import without complaint and leave your books wrong, so it is worth knowing before you import rather than during reconciliation.

1. Go to File → Import → Import OFX/QFX… and choose the file.
2. The first time GnuCash sees the account in the file, it asks which GnuCash account it belongs to. Pick the existing account (for example Assets:Current Assets:Checking Account, or Liabilities:Credit Card), or create one. GnuCash remembers the choice.
3. The import matcher opens, listing every transaction. For each one GnuCash proposes an action — add it as new, or match it to a transaction already in the account — and a destination (the other side of the transaction, such as Expenses:Groceries).
4. Review, assign destinations where GnuCash has none, and press OK.

Transactions GnuCash cannot assign go to an Imbalance account. That is not an error; it is a to-do list. Open Imbalance after the import and move each line to its proper account.

The matcher is the reason importing gets faster over time. It learns from your choices: once you have assigned "TESCO STORES 2231" to Expenses:Groceries a few times, it starts proposing that account for similar descriptions on its own. The first statement from a bank takes the longest; by the third or fourth, most lines arrive already assigned.

It also looks for transactions you entered by hand. If the account already contains a transaction with a matching amount and a nearby date, the matcher proposes to match rather than add, so you do not end up with the same payment twice. Check those proposals: two different payments of the same amount a few days apart can be matched wrongly.

Descriptions from a converted PDF are the same text the bank printed, so the matcher treats them like any bank download.

QIF. Use File → Import → Import QIF…. The assistant loads the file, asks which account the transactions belong to when the file does not name one, and asks about the date format if it is ambiguous. It then offers to find duplicates of transactions already in your books before importing. Take the time on the date question: a wrong day/month order produces a register that looks fine and is wrong for every day after the 12th.

CSV. Use File → Import → Import Transactions from CSV…. Choose the separator, tell GnuCash which row the data starts on, assign each column (Date, Description, Deposit, Withdrawal — or a single signed Amount), set the date format and the account, and continue into the same matcher as OFX. You can save the column settings, which helps if every statement has the same layout.

Importing is not finished until the account reconciles. In the account register, choose Actions → Reconcile…, enter the statement's closing date and ending balance, and tick off the imported transactions. The difference at the bottom should reach zero.

If it does not:

• The difference equals one transaction. It is missing (dropped in conversion, or matched to a manual entry it should not have matched) or doubled.
• The difference is twice one transaction. A payment was recorded with the wrong sign — look at credit card payments and refunds first.
• The difference is small and odd, like 0.09 or 90. A digit was misread, most often on a scanned statement.

A converted file that passed the balance check before import rules out the first and third causes, which leaves only mistakes made inside GnuCash — usually a wrong match in the matcher.

The loop is the same for every statement: convert, import, clear Imbalance, reconcile. It is the right way to enter history, but twelve months across three accounts is thirty-six rounds of it. If you would rather have the files arrive ready to import, a batch can be converted for you, every statement reconciled to the cent before it is sent. For the spreadsheet side of the job, see how to convert a bank statement PDF to Excel.