Mersal Audit Preparation in One Afternoon
What an auditor actually samples
An audit is not a reading of every entry. It is a set of targeted tests against a small number of controls. Understand the tests and the preparation stops being a project.
Four things draw the sampler's attention. First, serial continuity: are the invoice numbers unbroken and non-repeating. A gap invites a question about a suppressed sale. A duplicate invites a question about a fabricated one. Second, tax treatment at the line: was value-added tax applied correctly to each item, with exempt services and disbursements separated from taxable work. Third, cash: does every receipt trace to a settled payment, and does every settlement produce exactly one receipt. Fourth, the corrections trail: when a figure changed, what was the prior figure, who changed it, and when.
Everything else follows from these four. If they hold, the sample passes.
Structure removes the search
The work of an unprepared firm is reconstruction. Someone opens a spreadsheet, reconciles it against a folder of PDFs, and hopes the two agree. The auditor's questions then become an investigation into your own records.
Structure removes the search. Serial continuity should be a property of the books, not something you check after the fact: separate serial books for taxable, exempt and proforma statements, each advancing on its own unbroken sequence, make a gap impossible to create by accident. Mersal keeps exactly these three books, and value-added tax is ruled per line, so one statement can carry taxable services, exempt items and disbursements without confusing their treatment.
Corrections deserve the same discipline. An invoice that can be quietly overwritten is a control the auditor cannot trust. An invoice that freezes at issue, and is corrected only by a reissue that leaves the original on the record, answers the question before it is asked.
Receipts, settlements and the append-only ledger
The tightest test is cash. Consider a settlement of 4,000 against an issued invoice. The auditor wants a receipt for that exact amount, tied to that invoice, that no one could have edited afterward.
This is a matter of sequence and permanence. A receipt written the moment a payment settles, carrying its own independent serial and sealed against edit or deletion for every role including the administrator, cannot drift from the payment it records. A payments ledger that only appends, never overwrites, cannot lose the history of how a balance was reached. In Mersal both properties are enforced at the database, not asked of the user, and the operational audit ledger rejects modification through triggers that fire before any update or delete.
When the tests are structural, the evidence is already assembled. The export is the deliverable.
The firm that dreads its audit is usually the firm whose controls live in habit rather than in the system. When continuity is guaranteed by separate serial books, when tax is decided at the line, when every receipt is sealed to its settlement, and when no correction erases what came before, there is nothing left to assemble under pressure. You are not building an audit file. You are pressing export on one that has been building itself all year. A structured book is its own best witness.
Matters, conflicts, VAT billing, sealed receipts and the docket, in one defensible system.