Source type
State whether the route covers digital PDFs, scans, or both.
Local statement formats
Built around the bank PDFs
South African teams receive.
Start with the original digital statement, review every extracted row, and use a clean CSV in the workflow that follows.
Launch routes: FNB · Standard Bank · Absa · Nedbank · Capitec
01Choose a bank
One conversion flow. Bank-specific review guidance.
Each bank page explains the strongest source file, what to check in the extracted rows, and how to move the CSV into a controlled next step.
02
Standard Bank statement to CSV
Digital PDF route · keep the statement period visible
Open bank guideAnother South African bank?
Investec, Discovery Bank, TymeBank, African Bank, and Bank Zero should be added only after layout testing.
Request a bank02What “supported” should mean
A tested layout, not just a bank logo.
A credible support claim needs a known statement type, a tested date, a visible output, and documented exceptions. When a bank changes its layout, the page should change with it.
Tested date
Record when the layout and sample output were last checked.
Review points
Explain the dates, signs, balances, and headers a user should verify.
Known limits
Publish unsupported layouts and failures instead of hiding them.
03After conversion
The bank tells us the source. Your workflow tells us the destination.
Once the rows are clean, use destination-specific guidance for Sage or Pastel, Xero, QuickBooks, or Excel. A generic CSV should never be described as a guaranteed direct import.
10 pages / free trial
Choose the bank. Then test a real statement.
Start with the original PDF and review the extracted rows before deciding whether the route works for your workflow.