Controls that guide you, and an audit trail that never forgets
Ganana keeps four safeguards fixed: every entry balances, posted entries are reversed rather than edited, the audit trail records everything, and tax invoices are numbered without gaps. Every other control can be set to Off, Warn or Require, and most default to Warn, so you can proceed in one click while the exception is recorded for your accountant.
- Approved bill BL-2207UI14 Nov 14:02 · S. Perera
- Matched line 118 to INV-1042 (0.97)AI14 Nov 13:58 · AI · Claude
- Changed supplier bank detailsHeld 24h14 Nov 11:20 · N. Fernando
- Locked October (sales)UI13 Nov 18:40 · K. Silva
- Integrity safeguards, audit trail and period locks on every plan
- Tamper-evident, hash-chained ledger
- Read-only auditor workspace
Which safeguards can't be switched off?
| Fixed safeguard | Why |
|---|---|
| Every entry balances (debits = credits) | Without it there are no valid accounts |
| Posted entries are changed by reversal, not edited | Keeps every report reproducible |
| The audit trail records everything | Lets anything be done flexibly, because it stays visible |
| Gapless numbering of issued tax invoices | IRD requirement |
How do Off, Warn and Require work?
- Off: no check.
- Warn (the default for most): you see the issue, can proceed in one click and add an optional note. The item appears in the relevant exception report.
- Require: the action waits for the condition, such as an approval or an attachment. A user with override permission can still proceed by giving a reason.
This applies to WHT and tax suggestions, approval routes, required attachments, segregation-of-duties rules, duplicate checks, credit limits, budget checks and payroll recalculation checks.
How do periods and locks work?
- The financial year defaults to 1 April to 31 March, matching the Sri Lankan year of assessment; any start month is allowed.
- Periods move from Open to Soft-closed (only accountants post, each entry needs a reason) to Locked to Archived. Period 13 is reserved for audit adjustments.
- One global lock date plus optional per-module lock dates for sales, purchases, bank, inventory and payroll.
- Reopening a locked period needs two approvers (one an accountant), a written reason and re-authentication, and every entry posted while reopened appears in the "changes after lock" report.
Who can do what?
| Control | How it works | Plan |
|---|---|---|
| Roles | Owner, Admin, Accountant, Bookkeeper, Clerk, Auditor (read-only), Approver | All (custom roles on Business) |
| Value limits | For example, "approve bills up to LKR 500,000"; higher values route to the next approver | Growth, Business |
| Approval workflows | Bills, payments, journals, credit notes, POs and supplier changes; multi-level by amount on Business | Growth, Business |
| Segregation of duties | Flags conflicting pairs, such as the creator of a payment approving it | Business |
| Step-up authentication | Re-authentication for changing bank details, unlocking periods, adding admins, changing AI keys and bulk exports | All |
| Supplier bank detail changes | Need a second approver; the supplier's existing contact is notified and payments are held for 24 hours | Growth, Business |
| Access review | A quarterly user-access report signed off by the owner; unused accounts flagged after 90 days | Business |
What does the audit trail record?
- Every create, change, approval, post, reversal, void, export, login, permission change, setting change and period action.
- Who, when, where (IP and device), the source (screen, API, import, rule or AI), before and after values, and any reason given.
- For AI actions: the provider, model, prompt version, confidence, inputs and the person who approved them.
- It is stored append-only, separately from the books, and no one in your organisation, including the owner, can edit it. It is kept for at least 7 years (configurable to 10).
- Each organisation's posted entries are hash-chained, and the chain is verified every night.
Which exceptions are reported?
| Report | Flags |
|---|---|
| Changes after lock | Entries posted to a period after it was soft-closed or reopened |
| Journal review | Manual journals at weekends or after hours, round amounts, unusual account pairs, journals to control accounts |
| Duplicates | Same supplier and bill number, or same amount and date within 3 days |
| Master-data changes | New suppliers, bank detail changes, credit limit increases, tax code changes |
| Unusual payments | First payment to a new supplier above a threshold, payments to changed bank details, splits just under an approval limit |
| Tax overrides | Every manual change to a calculated tax amount, with its reason |
| AI exceptions | Low-confidence AI postings that were approved, and AI suggestions people overrode |
Frequently asked questions
Can my auditor log in?
Yes. Auditors get a read-only workspace scoped to the periods you choose, with sample selection, drill-down to source documents and comments. Access can be time-limited and ends automatically.
Can I delete a posted invoice?
No. Posted records are corrected with a credit note or reversal, never deleted, so every report can be reproduced. Drafts can be deleted, and the deletion is logged.
Last reviewed:
Let the books do themselves.
Start on the Free plan. No card needed.