Absa provides statements for personal and business cheque, savings and credit card accounts in South African rand, with card statements issued in English or Afrikaans. The reviewed statements include a Classic Business Account, a Growing Business Account and an Afrikaans credit card statement from 2026.
Countries: South Africa
Supported statement formats: PDF
Supported destinations: QuickBooks Online, Xero, Sage Pastel, CSV/Excel
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.
Credit card statements have their own Statements tab with a file format choice. eStatements also arrive by email as a password-protected PDF; the cover email says which password to use, and the file must be unlocked before a converter can read it.
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 Absa statements from 2026: two business cheque account statements, a Classic Business Account and a Growing Business Account, and one credit card statement issued in Afrikaans. All are South African rand. Absa prints its cheque statements in English and its card statements in the language the customer chose, so the same converter has to read "Cheque account statement" and "Kredietkaartstaat" as the same kind of page.
D/MM/YYYY with no zero padding on the day, 1/02/2026 and 12/02/2026, and the period is printed as "31 Jan 2026 to 28 Feb 2026" under the title. Card rows carry two dates, transaction and processing, as two separate elements each, 5 and Feb then 7 and Feb, with the year only in the period line "4 Feb 2026 tot 4 Mar 2026 (29 dae)". Some cheque rows add (Effective 31/05/2026) on a line below when the effective date differs from the posting date.92 387,26 and 213 288,06- with a trailing minus, while the transaction rows use a point, 92 387.26 and 13 484.40. Card statements use a comma throughout, 9 546,56, and mark credits with a Kt suffix, 36 000,00 Kt, sometimes glued to the number, 5 799,39Kt. Cheque rows are unsigned; the column decides the sign.4550-1900-5301-3038.Absa cheque statements have four amount columns: Charge, Debit Amount, Credit Amount and Balance. The Charge column shows the fee that a transaction will attract, 10.00 next to a Digital Payment Dt row or 1.25 next to a Proof Of Pmt Email row, followed by a one-letter code, T, A or *. That fee is not taken from the account on that row; the balance moves only by the Debit or Credit amount, and the charges are collected later as Monthly Acc Fee, Transaction Charge and Admin Charge rows on the first of the month, which do sit in the Debit column. A converter that adds the Charge column to the debit doubles every fee and the running balance stops matching. A row with a Charge and no Debit or Credit, such as Archive Stmt Enq 14.00 A, is a fee notice with no money movement and should not become a transaction.
The dated row holds the transaction type and the channel, Digital Payment Dt and Settlement, or Acb Credit and Settlement. The payee or payer is on the next line, indented, Absa Bank Merch Order, Yoco Qjfxv 310126, Outsurance Ot93196730 958474. Card purchases add Card No. 9659 Volpes Weskus Mall Vre Vrede on the second line and sometimes (Effective 31/05/2026) on a third. A converter that keeps only the first line calls every payment Digital Payment Dt; one that joins the lines gets a usable payee, and the effective-date line has to be dropped or moved to a memo, not read as a new row.
The Account Summary at the top of a cheque statement prints Sundry Debits 213 288,06- with a comma and a trailing minus, and the transactions below print 213 288.06 style amounts with a point. A converter set to South African comma decimals reads the transaction rows as thousands; one set to point decimals reads the summary wrong. The summary is the check for the parse, so both formats have to be read, each in its own section. Card statements are consistent, comma decimals throughout, but add the Kt suffix for credits and sometimes glue it to the number.
The card statement was issued in Afrikaans: "Kredietkaartstaat vir die periode", "Saldo van vorige staat" for the opening balance, "Transaksies", "Oorplasing na kontrolerekening", "Betalings/krediete", "Bankkostes" and "Rente bereken" as section headings, "Tran datum" and "Verwerk datum" as the date columns, "Bedrag R" as the amount, and "(Subtotaal)" under each section. Merchant names stay as the merchant printed them. A converter that looks for English headings finds no transactions. Column positions and row shapes are the same as the English version, so a converter that finds the table by the two date columns and the amount column works on both, and the section subtotals give the checks: purchases, transfers, payments, fees and interest each add up separately.
A card purchase in another currency prints a second line, Geldeenheid USD Buitelandse bedrag 9,00, under the row. The rand amount is on the dated row; the foreign amount is not a transaction. Two-letter country codes, ZA, US, IE, sit in their own column after the merchant city, and a converter that joins everything after the reference number gets a payee that ends in a country code.
The "Bankkostes" section lists each fee with its VAT portion and its total, Internasionale transaksiefooi 4,15 31,79, and the Account Summary on page one repeats the total as "Bankkoste 113,79". The fee rows are real transactions and belong in the export; the summary line does not. A converter that reads the two-column fee rows has to take the total, not the VAT figure.
Every card row carries a 23-digit reference, 74548586035122520035208, in its own column between the dates and the merchant. On cheque statements the reference is shorter and lives on the payee line, Yoco Qjfxv 310126, where the last six digits are the date the merchant batched the sales. Neither is an amount, but both are long strings of digits that a loose amount pattern can catch.
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.