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.
Full name: First National Bank (South Africa)
Countries: South Africa
Supported statement formats: PDF
Supported destinations: QuickBooks Online, Xero, Sage Pastel, CSV/Excel, Microsoft Money, Wave, MYOB, FreeAgent, Kashoo, AccountEdge Pro, Banktivity
QuickBooks Online can read a PDF statement itself: Banking, Upload transactions, choose the PDF. Try it first. Use ProperConvert when QuickBooks flags the statement for review, stops before the last page, or the account is not in QuickBooks Online.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Online, and save the converted file on your computer.
Business profiles on Online Banking Enterprise can also export transactions as CSV, OFX, QIF and Pastel files from the Statements download page; the PDF statement is the one every profile has.
Steps follow the bank's own help pages. Menu names change from time to time; if they differ, follow the bank's page.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
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.
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.Cr, attached to the amount in the transaction table.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.
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.
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.
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.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
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.
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.
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.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
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.
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 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.
Since 2026 the same upload screen also takes a PDF or an image of a statement (JPG, PNG, HEIC). Intuit's AI reads the pages, and a statement it cannot read with confidence is held for a manual review by Intuit staff. If the account is in QuickBooks Online and the statement is a clean PDF, try that first; it costs nothing. A converted file is the better route when the upload flags the statement or stops before the last page, when there are many statements to catch up, when the bookkeeper wants to see and fix every row before it enters the books, or when a client's statement should not be uploaded to a third party.
Settings that matter:
MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.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.
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.
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.
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.
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.
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.
For one clean statement of an account that is already in QuickBooks Online, the built-in upload is the shortest path, and this page says so. A converter earns its place when the upload flags the statement for review, when a scanned or multi-year statement does not go through, when the account is in QuickBooks Desktop, Quicken, Xero or Sage instead, or when the statement must stay on your computer. The converted file goes through the same Upload transactions screen as a QBO file, with a transaction ID per row, so re-uploading a period does not double it.