PDF statements

Extract transactions from a PDF statement, with the arithmetic checked against the statement's own printed totals.

Last updated: August 6, 2026

When you have a PDF statement and no OFX download is available, PennyBolt can extract the transactions from it. It reads the transaction list, then verifies its own arithmetic against the totals printed on the statement. If the parsed transactions don’t add up to what the bank printed, PennyBolt refuses the import and tells you what’s off — so you don’t end up with silent errors that compound over months.

Supported statements

PennyBolt reads PDF statements from three institutions:

Synchrony Bank — credit card statements
Bank of America — checking and savings statements
First Tech Federal Credit Union — credit card statements, and checking and savings statements

PennyBolt identifies the statement by looking for text patterns particular to each issuer. There is no generic PDF reader: if your statement isn’t from one of the institutions above, PennyBolt says so rather than guessing and producing plausible-looking wrong numbers.

If your bank isn’t listed, check Which format should I use? — many banks offer OFX downloads even when a PDF is what you have in hand, and OFX is the better source when you can get it.

Import a PDF statement

Drag the .pdf file onto the PennyBolt window, or open Import from the sidebar and choose the file. PennyBolt detects that the file is a PDF, identifies which institution it came from, and opens a preview.

The arithmetic check

Before the preview opens, PennyBolt extracts the account summary from the PDF — the printed previous balance, the per-category totals, and the new balance. Then it sums every transaction it parsed and compares the two.

If the sums match, the import proceeds: the math agrees, so the transactions in the preview are the same set the statement describes.

If the sums don’t match, PennyBolt refuses the import and shows the specific discrepancy — for example, “Statement says Payments = $29.00, parsed transactions sum to $0.00 (diff −$29.00).”

The check is not optional and cannot be turned off. Refusing a doubtful import is better than quietly absorbing wrong data into your books.

Read the preview anyway

The arithmetic check catches missing and miscounted transactions. It does not catch everything, so it’s worth a look before you commit:

The statement period looks right. PennyBolt shows the detected date range in the preview header. Confirm it matches your PDF.
Merchant names are readable. Odd characters or truncation won’t affect your balances, but cleaning them up now saves work later. See Payees .
The transaction count matches. Your statement usually prints one.

What can go wrong

The arithmetic check fails. PennyBolt extracted transactions but they don’t add up to the statement’s printed totals. The message names which category is off and by how much. Email a sanitized copy of the PDF to support — the parser needs an update for that layout.

Bundled multi-statement PDFs. If your PDF contains several monthly statements bound together — a “January–June” file, say — PennyBolt reads it as a single statement and the arithmetic check will fail. Split the PDF into individual monthly statements and import them one at a time.

Extraction found zero transactions. The PDF may be a scanned image rather than a machine-readable file. PennyBolt can only read PDFs with embedded text; scanned images aren’t supported.

The statement is from an institution PennyBolt doesn’t read. PennyBolt tells you it can’t identify the statement rather than attempting it. Check whether your bank offers OFX — most banks that issue PDFs also offer a “Download transactions” option.