Convert Standard Bank PDF bank statement to Xero

Standard Bank of South Africa provides statements for personal and business accounts in South African rand. The reviewed statements include printed business current account statements, an online banking transaction history and a branch-printed copy, each with its own layout and number format.

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

Standard Bank PDF statement details

The following details were checked against Standard Bank of South Africa statements from 2019 to 2026: printed business current account statements, a transaction history exported from online banking, and a branch-printed "Computer Generated Copy" that arrived as a photo. Standard Bank uses three different layouts with three different number formats, so identify the layout first and always reconcile the converted transactions to the running balance.

Three layouts, three number formats

• Printed statement (Business Current Account, BizLaunch and similar). Columns are Details, Service Fee, Debits, Credits, Date and Balance. Numbers use a point for thousands and a comma for decimals, with a trailing minus on debits: 2.741,39-. Credits have no sign. Dates are month and day only, 02 22, with the year in the "Statement from 22 February 2019 to 20 March 2019" line.
• Online banking transaction history. Columns are Date, Reference, In (R), Out (R), Bank fees (R) and Balance (R). Numbers use a space for thousands and a comma for decimals, with a leading sign on every amount: -47 899,03, +4 645,00. Dates are full, 11 Mar 2026. Rows run newest first.
• Computer Generated Copy printed at a branch. Columns are Details, Service Fee, Debit, Credit, Date and Balance. Numbers use a comma for thousands and a point for decimals, with a leading minus on debits: -18,000.00. Dates are 20260401, year, month and day with no separators. Every amount column is printed on every row, so a debit row also shows 0.00 under Credit and Service Fee.

A converter that assumes one number format reads the other two as garbage. The safe rule is to detect the decimal mark from the balance column of the same statement, because the balance always has exactly two decimals.

Settings for a Standard Bank PDF statement

• Date: printed statements show MM DD, month first, even though South Africa writes dates day first everywhere else. Take the year from the statement period line. Online history shows full dates. Branch copies show YYYYMMDD. A statement period such as 15 October to 14 November crosses a month boundary on every statement and crosses the year in December.
• Amount: one of the three formats above. Debit and credit sit in separate columns on printed and branch statements, and the sign is repeated as a trailing or leading minus. Online history puts money in and money out in separate columns with an explicit sign on each.
• Balance: a negative balance is printed with the same trailing minus, 5.062,15-. Treat it as a sign, not as a formatting mark.
• Account number: printed statements show it with spaces, 28 072 181 1. Online history shows it with leading zeros, 0000010155497063. Strip the spaces and keep the zeros, or a file for the same account will not match a previous import.
• Account type and currency: "BUSINESS CURRENT ACCOUNT" or "Current Account" is checking. Amounts are rand; the R appears only on summary lines such as Month-end Balance R54.041,96.

The fee column is not part of the transaction

Printed statements carry a Service Fee column next to each transaction: 7,95 beside an internet banking payment, 4,20 beside a card purchase. That fee is not deducted on that row. The balance moves by the debit alone, and the fees are charged later as one line, for example "BUSINESS ELECT BANK CHARGES". A converter that adds the fee to the debit, or writes it as a second transaction, breaks the running balance on every row and doubles the fees at month end.

The same column also shows ## on rows that are themselves fees ("DEBIT CARD PURCHASE FEE", "FEE-UNPAID ITEM"). ## is a footnote marker meaning "These fees include VAT", printed at the bottom of the page. It is not an amount.

Every transaction takes two lines

The first line holds the bank's transaction type and a reference number, CHEQUE CARD PURCHASE 9111, and carries the amounts, the date and the balance. The second line holds the part a bookkeeper actually wants, WIMPY BEACON B4278193441714771 or KTM BAILEY RENT, and carries nothing else. A converter must attach the second line to the row above it, and should prefer it as the payee, because the first line is the same text for hundreds of rows.

The second line often has a card number or terminal reference glued to the merchant name, PNP CRP SAVANN4278193342568656, and a time stamp glued to it as well, ENGEN BEACON H13H52, NANDOS CAVENDI20H05. Those need to be split off before the payee is usable for matching.

On the online banking layout the reference wraps differently: one part is printed above the row that holds the date and amount, one part on that row, and the rest below it. Grouping strictly by vertical position assigns the top part to the previous transaction. The row with the date and amount is the anchor, and the reference lines above and below it belong to it.

Amounts hidden inside descriptions

Descriptions carry amounts that are not transactions. A declined card row reads 032310749 22/10 11H51 695,00, where 695,00 is the amount that was declined. An immediate payment fee reads 032310749 17H34 R 25039.80#122, with the paid amount in yet another format. A foreign transaction reads INTGBP2.05at21.7339, the currency amount and the exchange rate. None of these are in the amount columns, and a converter that scans text for numbers picks them up as transactions.

Rows that are not transactions

• BALANCE BROUGHT FORWARD opens every page with a balance and, on the first page, a date. It is the opening balance, not a transaction.
• Month-end Balance on the first page is a summary figure and does not match the balance brought forward.
• OUTSTANDING CARD AUTHORISATION rows on the online history are pending card holds. They are included in the available balance shown there but have not posted. Including them means the file will not reconcile to the next month's opening balance.
• RTD-NOT PROVIDED FOR rows are returned debit orders that reverse an earlier row. Both rows are real and must both be kept.
• The page header repeats the branch address block twice, the customer address, the statement period and "Page 1 of 10" on every page, and the footer repeats the bank's registration text. Detect them by position, not by content.

Order and reconciliation

Printed and branch statements run oldest first. The online history runs newest first, so the balance column reads backwards down the page and a converter must reverse the rows before writing a file that other software expects in date order.

The running balance is on every row in all three layouts. Check that each debit or credit moves the previous balance to the printed one. That check catches a missed trailing minus, a fee wrongly added to a debit, and every OCR error on a scanned or photographed copy.

Scanned and photographed copies

Branch copies and older statements often arrive as photos. OCR splits a balance such as 571,999.44 into two elements, 571 and ,999.44, reads the Debit header as noise, and shifts columns on a skewed page. The explicit 0.00 in unused amount columns on branch copies helps here: a row with three amount cells is complete, a row with two has lost one. Reconcile every row against the balance before trusting a scan.

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.