Statements
A statement is the holder’s record of one account over one period. It opens with the balance brought forward, lists every transaction with its running balance, and closes with the balance carried out.
A statement is a snapshot, not a live view. Once issued, its figures never change. Reprinting one two years later reproduces the document you sent.
You work with statements on the Statements panel of the account screen.
What every statement shows
| Section | What it holds |
|---|---|
| Letterhead | The issuing operating entity’s name, its registration number, and its footer address and contact |
| Addressee | The holder’s name and postal address, as they stood when the statement was issued |
| Statement details | Account number, statement number, the period covered, and the currency |
| Transactions | One row per transaction: date, description, amount, and running balance |
| Opening and closing balance | The balance brought forward, and the balance carried out |
| Arrears | A further column, shown only when the account or a line carries arrears |
| Tax | Net, tax and gross columns, shown only when a line carries tax |
For what an individual row means, see reading the transaction list.
The panel lists one row per statement, with its number, its period, how it was raised, and its status.
What a regulated credit statement adds
Each credit agreement is classified when it is booked, as regulated or as outside the regime. That classification decides the shape of the statement.
An account under the regulated credit regime gets these further sections. An account outside the regime gets none of them, and its statement is unchanged.
| Section | What it holds |
|---|---|
| Regulator registration | The credit provider’s registration number with the credit regulator |
| Statement date | The day the statement was issued, which is not the day the period closed |
| Credit agreement | Principal debt at origination, the nominal annual interest rate, and the instalment amount and its frequency |
| Cost of credit | One total per category for the period — payments, interest, fees, insurance, collection costs, default administration charges, legal costs |
| Payment details | The bank, account number and branch code to pay into, and the reference to quote |
| Default charge ceiling | Shown only while the account is in default: the ceiling, what has been charged against it, and what remains |
The standards register row National Credit Act 34 of 2005 (South Africa) §§108–110 / Reg 35 — statements of account records what the platform claims here and what it does not. The platform prints the content the regulation prescribes. It does not reproduce the layout of the prescribed form.
The reference a holder quotes when paying is their own account number. See payment references.
When a statement is produced
| How it is raised | When it happens | Origin on the panel |
|---|---|---|
| The account’s statement cycle | At end of day, when the transaction that marks the cycle lands — typically the instalment or the capitalisation | Scheduled |
| The statutory sweep | At end of day, once an account has gone longer than its account type’s maximum interval without one | Scheduled |
| You, by hand | When you choose a period and select Generate | AdHoc |
The statutory sweep
Statute sets a maximum gap between statements. Cycle-driven issuing normally keeps you well inside it. It stops when the account’s schedule stops — which is exactly when the account is in default or in litigation.
The sweep closes that gap. At end of day it checks every account whose account type carries a maximum interval. Once an account passes that interval, the sweep issues a statement running from the day after the last statement to the current trading date.
The sweep deliberately includes suspended accounts. A suspended account still owes its holder a statement. It skips only accounts with no live agreement to report on: a draft, a discarded application, or a closed account.
Running end of day again issues nothing further. One period gets one statement.
An account with no holder — an internal account of your own — gets no statement, because there is nobody to address one to.
Generating a statement by hand
- Open the account and select the Statements panel.
- Select Generate.
- Enter the Period Start.
- Enter the Period End. It must fall on or after the start.
- Select Generate.
The statement covers exactly the dates you chose. Asking for the same account and the same period twice returns the statement you already have, rather than a second one.
A statement you raise by hand does not move the cycle. The next scheduled statement still begins where the last scheduled one ended.
Generating a statement is eligible for countersign, so a second pair of eyes can be required on it.
What happens after it is issued
Issuing fixes the figures. The document is then produced and sent without anything further from you.
stateDiagram-v2
[*] --> Issued: Statement raised
Issued --> Rendered: Document produced
Rendered --> Emailed: Emailed to the holder
Rendered --> EmailFailed: Email rejected| Status | What it means | What you do next |
|---|---|---|
| Issued | The figures are fixed, the document is being produced | Nothing — wait |
| Rendered | The document is ready | Open the statement, or open the PDF |
| Emailed | Sent to the holder, with the despatch recorded | Nothing |
| EmailFailed | The email was not accepted | Open the document and send it yourself, and check the address on file |
The panel gives you two ways to read a statement. One action opens it as a web page you can print. The other opens the PDF, once that exists.
The statement is emailed only to a holder who has an email address on file and has opted in to receiving documents by email. Otherwise it stays at Rendered: open it from the panel and send it your own way.
Proving despatch
When the email is accepted, the platform records the channel, the address it went to, and the moment it was sent. That is the same proof the default-notice path keeps, and it stays with the statement for as long as the statement does.
Only the email channel exists. There is no registered-mail channel, so a statement you print and post carries no proof inside the platform. This is why the register row above reads Partial, and it is worth knowing before you rely on a statement in a dispute.
The panel shows the status. It does not show the address or the despatch date, so proving a particular despatch is an audit question rather than a panel one.
Worked example
Alex holds a regulated personal loan with Woodgrove Bank. All figures are in ZAR. The agreement’s principal debt at origination is 50,000.00, the nominal annual interest rate is 18.50%, and the instalment is 1,250.44 monthly.
Three items land in May 2026:
- Interest of 120.00 on 5 May.
- A service fee of 60.00 on 6 May.
- Interest of 30.00 on 20 May.
Sam generates the statement for 1 May to 31 May 2026, on a trading date of 1 June 2026.
- The statement opens at 0.00 and closes at 210.00.
- The cost-of-credit summary reads 150.00 interest and 60.00 fees.
- Those two totals add to 210.00, which is the three transactions added up.
- The statement date reads 1 June 2026 — the day Sam raised it, not the day the period closed.
- The agreement block reads 50,000.00 principal, 18.50%, and 1,250.44 monthly.
The sweep, on an account whose schedule has stopped
Jordan’s account opens on 1 January 2026, and its account type carries a maximum interval of one month. No statement has been issued.
End of day on 15 March 2026 issues one statement, covering 1 January to 15 March 2026. Running end of day again on the same date issues nothing.
The machine-readable export
Alongside the printed statement, the platform can produce an end-of-day statement in the ISO 20022 camt.053 format, for a system that consumes statements rather than a person who reads them.
- The export is keyed by booking day: one statement for each day the account moved.
- Opening balance plus that day’s entries equals the closing balance.
- A back-dated posting appears under the day it was booked, carrying its original value date. See value dating.
- A day with no visible movement produces no statement at all.
- Each entry carries the standard classification code of its transaction type. See transaction types.
- An account type with no classification family set produces a clear error rather than a partial export.
The standards register row ISO 20022 — Bank Transaction Codes (BTC) + camt.053 records this, and it is marked as a deviation. The published code list has no family for demand or call deposits, so call deposits are exported under the notice deposits family. The reason is recorded against the row.
The export is not an action on this panel. It is requested for one account and one date range by a system you connect.
What your organisation configures
- Which accounts get a statement cycle. Each account type names the schedule whose transaction closes a statement period. An account type that names none produces no scheduled statements.
- The maximum interval per account type. Set it to the statutory maximum for that class of agreement. An account type with no interval set is never swept.
- Which classification each charge falls under. On a regulated credit account type every charge carries a cost-of-credit category. An uncategorised charge would vanish from the statement summary, so it is refused.
- The stationery. The issuing operating entity’s name, logo, registration number, regulator registration number, footer address and contact all print from the entity.
- Where the holder pays. The statement prints the entity’s own bank account nominated for incoming credit transfers, in the statement’s currency. Where no account is nominated, the block is left off and the statement still issues.
- Whether the holder is emailed. The email address and the email opt-in are properties of the counterparty. A holder who has not opted in is never emailed, and their statement waits at Rendered for you.
- The classification codes the machine-readable export uses, on the account type and on each transaction type.
- Whether the capability is licensed at all. A tenant without statements does not see the panel. See switching features on and off.
Onboarding a product with a different statement cycle, or a different statutory interval, is configuration rather than a release.