Convert FNB PDF bank statement to CSV/Excel

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

Statement formats provided by FNB

Ways to create CSV/Excel from a FNB statement

Check for a direct export

Check online banking first for a direct CSV/Excel export covering the required account and period. If it is not available, use the statement.

Enter transactions manually

For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.

Convert with ProperConvert

Open the PDF statement, review the extracted transactions, choose CSV/Excel, and save the converted file on your computer.

What to check on every bank-statement conversion

Date

Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.

Amount

Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.

Memo

Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.

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

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.

Frequently asked questions

How do I check that every transaction was converted?

Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.

Can I convert an older FNB statement?

Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.

Should pending transactions be included?

No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.

Can the result be imported directly into CSV/Excel?

Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.

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.

CSV/Excel output settings

CSV is useful for review in a spreadsheet and for imports that accept a simple transaction table. A general-purpose layout uses Date, Memo, and Amount. Some destinations instead require separate Debit and Credit columns, so choose the column arrangement before saving.

Keep amounts numeric: do not place a currency symbol inside the amount cell. Use explicit signs in a single Amount column, or unsigned values in separate Debit and Credit columns. Save account name, currency, and statement notes outside the transaction table unless the destination explicitly requests them.

CSV/Excel questions

Can I set the output date format?

Yes. Choose the date order required by the destination, such as MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD. Use four-digit years so spreadsheet software does not infer the wrong century or year.

Can I set the decimal separator?

Yes. Use a point or comma according to the destination and regional settings. The field delimiter must remain unambiguous; a comma-decimal CSV commonly uses a semicolon as its delimiter.

Does the CSV open in Microsoft Excel?

Yes. Excel opens CSV files directly. Confirm that Excel interpreted dates and decimal marks correctly before saving, because spreadsheet auto-formatting can change them.

Does the CSV work with Google Sheets?

Yes. Import the CSV into Google Sheets and select the locale and separator that match the file. Review dates and amounts after import before sharing or exporting it again.

Should debit and credit be one column or two?

Use one signed Amount column for a compact, general-purpose file. Use separate Debit and Credit columns when the accounting application or existing spreadsheet template requires them.