Module
Books an auditor will accept
Multi-level accounts, cost centres, intercompany entries with eliminations, cheque cycles, budgets and fiscal-year closing. Every multi-leg journal is one transaction, so a failure cannot leave half an entry behind — and a closed period refuses a posting rather than accepting it quietly.
What it does
A chart of accounts you control
Multi-level accounts you define rather than inherit. Posting accounts must be leaf nodes with a branch set, which is checked before a transaction opens rather than discovered halfway through one.
Journals that cannot land half-written
Every multi-leg entry is one database transaction. If a leg fails, none of it posts — so you never find a journal with a debit and no credit, which is the kind of thing nobody notices until a reconciliation.
Cost centres and intercompany
Post to a cost centre alongside the account, and raise entries between related companies with the eliminations handled rather than left for a spreadsheet at year end.
Cash, banks and cheques
Cash boxes and bank accounts per branch, with the full cheque cycle — issued, due, collected, returned — each stage posting where it should rather than being tracked in a notebook.
A fiscal close that actually closes
A closed period refuses a posting rather than accepting it quietly and surprising you in the audit. Reopening is a deliberate, recorded act.
Statements that reconcile
Customer and supplier statements aged by due date, trial balance, and a general ledger you can drill from a figure back to the document that produced it.
Why teams choose it
What your business gains:
No half-posted journals: every multi-leg entry posts in full or not at all, so your trial balance always balances.
Closed periods stay closed. A late posting is refused, not slipped in, so the figures you signed off stay signed off.
Drill from any figure in the general ledger to the document behind it, and answer your auditor on the spot.
Run cost centres, intercompany eliminations and the full cheque cycle inside the books, not in side spreadsheets.
Questions about this
Do you handle e-invoicing?
Yes, for Egypt (ETA) and Saudi Arabia (ZATCA Phase 2), from one set of screens.
The part worth asking about is what happens when the authority is unreachable. Signing and numbering are local and ordered; submission is separate and networked. So an outage queues documents instead of stopping a till, and a rejected document never consumes a number from your sequence.
Does it handle VAT correctly?
Yes, with per-line tax amounts and taxable amounts rather than a tax total bolted on at the end, which is what the authorities require.
One setting is worth knowing about: a whole-invoice discount can be applied before or after tax. Applied after, it does not reduce the taxable base — which overstates VAT and is incompatible with ZATCA. New workspaces on the Saudi regime are set to pre-tax for that reason.
Can an auditor see who changed what?
Yes, from the Professional plan: an audit trail on every change, with the user, the time, and the before and after values. A posted document is corrected with a correcting entry rather than edited in place, which is the distinction an auditor is actually asking about.
See it with your own data
Start a free trial, or talk to us and we will show you the module running on your own workflow.