Convert FNB PDF bank statement to QuickBooks Online

FNB provides bank statements for South African personal and business accounts. The reviewed Enterprise Business Account statement reports transactions in South African rand and identifies the account as DDA, or checking.

Countries: South Africa
Supported statement formats: PDF
Supported destinations: QuickBooks Online, Xero, Sage Pastel, CSV/Excel

FNB PDF statement details

The following details were checked against an FNB Enterprise Business Account statement. Other FNB account types or statement revisions may use a different layout, so always reconcile the converted transactions to the statement totals.

Settings for an FNB PDF statement

• Date: transaction rows can show only day and month, such as 01 Sep. Take the year from the Statement Period line or the dated footer. When a statement crosses January, advance the year as the transaction month moves from December to January.
• Amount: the reviewed statement uses a comma for thousands and a point for decimals. Debits have no suffix; credits carry Cr, attached to the amount in the transaction table.
• Memo: prefer the customer's reference when it identifies the payee more clearly than the truncated bank-generated transaction text.
• Currency and account: the statement identifies ZAR under “Transactions in RAND (ZAR)” and DDA as the account type. DDA corresponds to checking when a destination asks for an account type.

The useful description is split across fields

The Description area contains bank-generated transaction text and a separate customer reference. The bank text can be truncated, as in FNB OB Pmt FNB OB 000000007 Cam, while the customer reference contains a clearer memo such as Cameron - Salary or Rent - Unit 13. A converter should preserve the useful reference instead of keeping only the truncated bank text. A # at the start of a description identifies a bank charge and can also help with categorization.

Debit and credit signs must be proved by the balance

Debits have no sign while credits carry Cr. That suffix can be lost during extraction, and “Bank Cr” describes the bank's side rather than the customer's bookkeeping entry. Check each amount against the running balance: the transaction must move the previous balance to the next printed balance.

The Turnover box provides a second checksum. It reports the number and total of debit and credit transactions. Matching those counts and totals, and reaching the printed closing balance, is strong evidence that every posted row was included exactly once.

Summary tables can be mistaken for transactions

Statement Balances, Bank Charges, and Interest Rate tables use typography and columns similar to the transaction table. A Service Fees total may repeat an amount already present as a dated transaction, so reading both creates a duplicate. Closing Balance and Total Authorised are totals rather than transactions.

The footer repeats branch number, account number, and a date on every page. The account number may also be printed vertically along the page edge and appear as a stray extracted string. These elements must be separated from the transaction rows.

Statement dates do not all mean the same thing

The reviewed statement period starts on 31 August while its first transaction is dated 01 September; the earlier date belongs to the opening balance. A Future Dated Transactions table also shows a post date such as Sep 30 beside a value date such as 16 Oct. Those entries are pending, not posted. Including them prevents the transactions from reconciling to the closing balance.

PDF input challenges

A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.

Page breaks

A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.

OCR

On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.

PDF questions

Can I convert a scanned bank statement?

Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.

Why does copying and pasting a PDF into Excel fail?

PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.

How do I know whether the PDF contains searchable text?

Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.

QuickBooks Online import settings

QuickBooks Online imports bank transactions from a file through Banking, Upload transactions. It accepts QBO, QFX and OFX files, which share the OFX structure, and CSV files. Uploaded rows land in the For Review list, where QuickBooks matches them to existing entries and the user adds or excludes them.

• OFX, QFX and QBO carry the date, the amount, a payee, a memo, an optional check number and a unique transaction ID. QuickBooks Online uses the payee as the Description and the transaction ID to skip rows it has already imported.
• CSV carries less. QuickBooks Online reads a date, a description and an amount, in a three-column layout with one signed amount or a four-column layout with separate debit and credit columns. Only one description column is imported; a payee and a memo cannot both be kept.

Settings that matter:

• Account: the user picks the QuickBooks account during upload, so the account ID in the file matters less than in QuickBooks Desktop. It still helps to keep the same ID per account so the file is recognized on the review screen.
• Account type: checking or credit card. A credit card file into a checking account flips every sign.
• Dates: MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.
• Amounts: digits and one decimal separator. No currency symbols, no thousands separators in CSV.
• File size: QuickBooks Online limits a CSV upload to about 350 KB. Split a long statement into several files.
• Transaction IDs: unique per row and stable per transaction, so re-uploading a period does not double it.

QuickBooks Online questions

Should I use CSV or OFX?

Use OFX, QFX or QBO when the file can be made in that format. It carries the payee, the memo and the check number and gives QuickBooks a transaction ID for duplicate checks. Use CSV when a spreadsheet is the only source and a single description is enough.

Why does QuickBooks Online reject my CSV?

The usual causes are a date column QuickBooks cannot read, an amount with a currency symbol or thousands separator, more columns than the three- or four-column layout, or a file over the size limit. Save the file with dates as digits, amounts as plain numbers, and only the needed columns.

Why did transactions import into the wrong account?

The account was chosen during upload. QuickBooks Online does not read the account name from the file. Exclude the rows, delete them from Excluded, and upload again with the right account selected.

How do I undo an import?

In For Review, select the rows, choose Batch actions, Exclude Selected. Open Excluded, select them again, Batch actions, Delete. The rows are gone and the file can be uploaded again.

Why are some rows missing after upload?

QuickBooks Online skips rows whose transaction ID it has already seen and, for CSV, rows it reads as duplicates by date, amount and description. Two genuine identical rows on the same day can be dropped from a CSV. Use an OFX-type file with unique IDs for those.

Can I import transactions older than 90 days?

Yes. The 90-day limit applies to a live bank connection, not to a file upload. Any date range can be uploaded from a file.