Replaces Sage and Xero
IronLedger
One immutable journal. Seven reports that are only ever views of it.
IronLedger is double-entry accounting for South African businesses. Nothing posted is ever edited or deleted — corrections are reversals, and every report is a projection of the same journal, so the statements cannot disagree with each other.
Running on staging with the core ledger and all seven statutory reports built. Not yet released for production books.
- Written for
- IFRS for SMEs, the VAT Act and the Income Tax Act
- Journal
- Immutable, balance enforced by the database
- Reports
- Trial balance, income statement, balance sheet, general ledger, VAT, debtors and creditors age analysis
- Banking
- Statement import and reconciliation
- Capture
- Photograph a slip, with VAT input tax identified
- Migration
- Imports from Pastel
The books cannot go out of balance
Every journal entry must sum to zero, and that is checked by the database itself rather than by the application. An unbalanced entry cannot be written, so it cannot be found later.
Corrections leave a trail
A posted entry is never updated or deleted. Fixing something means posting a reversal, which means the history of what was thought to be true, and when, survives the correction.
Seven reports, one source
Every statutory report is a read-only projection of the same journal. The trial balance and the balance sheet cannot disagree, because neither is stored — both are derived.
Separation of duties is built in
Capturing and posting are different permissions, as are importing and approving. The controls an auditor expects to see are in the software rather than in a policy document.
Bank statements reconcile against the ledger
Import a statement and match it to what is already posted, so the cash book reflects the bank rather than someone's memory of it.
Slips become entries
Photograph an expense slip and IronLedger reads it, proposes the entry and identifies the VAT input tax, leaving you to approve rather than retype.
Listed so you can decide with the whole picture rather than discover it after signing.
- Production release, once the staging books have run a full cycle
- The public API and API keys, built and tested but not yet deployed