The ledger is not a downstream system
In most cores, accounting is a nightly batch that reads what the product did and tries to agree with it. Here the double-entry fact is written in the same transaction as the movement, so agreement is structural rather than achieved.
Six mechanisms, not six adjectives
The ledger is inside the product, not downstream of it
Every rand movement writes its double-entry fact in the SAME database transaction that moves the money. There is no nightly accounting run to reconcile against, because there is nothing to reconcile.
Facts are recorded, not reconstructed
Balances and exposures are the fold of an append-only event stream. Where a subsystem once derived a figure from mutable state it was rewritten to record it — that is why a restructure cannot double-bill a month and a reversal cannot lose capitalised interest.
Walk-back is a query, not a project
Any financial-statement line resolves to its postings, and each posting to the origin event, the workflow step, the identity that authorised it and the mandate it moved under.
The chain makes tampering visible
Postings are hash-chained per tenant. Editing history breaks the chain at the exact record touched, and the verifier reports a fork as a blocking alarm rather than a warning.
IFRS 9 and Basel 3.1 consume the same facts
Staging, expected credit loss and capital consumption read the ledger the statements read. A capital number and a disclosure number cannot drift apart because they are computed from one source.
Money is never floating-point
Amounts are bigint minor units from the database column to the rendered page. There is no float money anywhere in the codebase, and a gate enforces it.
Six frameworks, one fact set
A reporting framework here is a projection over the same origin facts. That is why your IFRS statements, your SARB return and your management pack cannot tell three different stories about the same month.
| Framework | What it produces |
|---|---|
| IFRS (full) | Primary statements, notes, IFRS 9 ECL staging |
| IFRS for SMEs | Reduced-disclosure variant off the same facts |
| SA GAAP-legacy comparatives | Restatement bridge for historical series |
| SARB BA returns | BA 100/120/125/200/900 mappings |
| Tax (SA income tax + VAT) | Permanent and temporary difference tracking |
| Management (internal) | Segment and product-line P&L |
The walk-back
This is the query an auditor asks for and rarely gets. Any line in a financial statement resolves, in one hop each, all the way to the human decision behind it.
- A statement line resolves to the postings that composed it.
- Each posting resolves to its accounting fact and the fact's chain position.
- The fact resolves to the origin event — the disbursement, the purchase, the settlement.
- The event resolves to the workflow step, the identity that authorised it and the mandate it moved under.
- Every hop is verifiable: recomputing the chain from origin either reproduces the recorded hashes or names the record where it stopped agreeing.
Period close
- A closed period is frozen: a posting dated into it is refused with the reason named, not silently re-dated into the open one.
- Re-opening a period is a two-eyes, audited action with a bounded future date, because an unbounded close date is how a book gets quietly rewritten.
- The close head is signed, so a restated set of accounts is distinguishable from the original rather than replacing it.
- Multi-entity consolidation eliminates intercompany positions from the same facts, in the same chain.
Wynk Systems is a bank-grade core-banking platform. Registered in South Africa.
This site is informational: nothing on it constitutes an offer, a quotation, or credit advice.