Convert Standard Bank PDF bank statement to CSV/Excel

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

Statement formats provided by Standard Bank

Ways to create CSV/Excel from a Standard Bank 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.

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

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

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

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.

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 Standard Bank 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.