Convert FNB PDF bank statement to Xero

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.

Xero import settings

Xero imports bank transactions through Accounting, Bank accounts, Import a Statement (also reached as Manage Account, Import a Statement). The file goes into the bank account's reconcile list, where Xero matches each line to invoices, bills and bank rules, or creates a spend or receive money transaction.

• OFX is the format to aim for. It carries the date, the amount, a payee, a description, a reference, a check number and a unique transaction ID. Xero uses the ID to skip lines it already has, so re-importing a period does not double it.
• QBO and QFX are OFX with extra header fields for QuickBooks and Quicken. Xero reads them as OFX, either directly or after renaming the extension to .ofx. If a QBO, QFX or OFX file downloaded from a bank is rejected, the file usually has a header, encoding or date format Xero does not accept; converting it to a plain OFX fixes that.
• CSV works when the columns match what Xero expects. A CSV downloaded from a bank often needs mapping on import and sometimes fails on the date or amount format. A CSV written for Xero carries the column names Xero maps on its own: Date, Amount, Payee, Description, Reference, Check Number.
• PDF must be converted first, to OFX or to a Xero CSV.

Settings that matter:

• Account: the Xero bank account is chosen before the upload. The account number inside the file is not used to pick the account, but keep it stable per account so the file is recognized on the review screen.
• Account type: bank or credit card. Xero keeps the statement's sign convention for credit cards, so a card purchase stays a debit; the converter should not flip signs for Xero the way it does for some other targets.
• Dates: four-digit years. In CSV, use one order for the whole file and confirm it on the import screen; day-month and month-day are both accepted but Xero must be told which one.
• Amounts: one signed Amount column, or separate Debit and Credit columns, in a CSV. No currency symbols or thousands separators. Money out is negative in the single-column layout.
• Payee and description: Xero shows Payee as the contact and Description as the transaction text, and bank rules match on either. Put the merchant name in Payee and the bank's transaction text in Description. Reference is a free field that other targets do not have; use it for the bank's reference number.
• Transaction IDs: unique per line and stable per transaction, so a second import of the same statement skips what is already there instead of duplicating it.
• Balances: Xero does not read an opening or closing balance from the file. Check the statement balance in Xero against the printed closing balance after import.

Xero questions

Should I import OFX or CSV into Xero?

OFX. It carries the payee, description, reference and check number in separate fields and gives Xero a transaction ID for duplicate checks. CSV is fine when the file was written for Xero with the right column names; a bank's own CSV usually needs mapping and cleanup.

Xero says my OFX, QFX or QBO file is invalid. What is wrong?

Most often the file has a header Xero does not read, non-UTF-8 text, dates in a format it does not accept, or a missing transaction ID. Convert the file to plain OFX and import that. Renaming QBO or QFX to .ofx helps only when the content is already clean.

Why did Xero import only some of the transactions?

Xero skips lines whose transaction ID it already has, and for CSV it skips lines it reads as duplicates by date, amount and description. Two genuine identical lines on the same day can be dropped from a CSV. Use OFX with unique IDs for those.

Why are the dates wrong after a CSV import?

The date order was misread. A file with 03/04/2026 can be read as 3 April or 4 March. Set the order on the import screen, or export dates as YYYY-MM-DD, which Xero reads without asking.

How do I undo an import?

Open the bank account, go to the statement lines or Bank Statements tab, select the imported statement and delete it. The lines disappear from reconcile and the file can be imported again.

Can I import older periods into Xero?

Yes. There is no date limit on file imports. Import periods in order and do not overlap them, so the balance in Xero follows the statements.

Does Xero read the opening balance from the file?

No. The statement balance in Xero is computed from the imported lines. Compare it to the printed closing balance after each import. If they differ, a line is missing, doubled, or has the wrong sign.