What is here
- Provision views — the ledger arranged so a tax provision can be prepared from it.
- Audit preparation — the schedules an auditor asks for first, assembled from posted data.
- Data governance — where figures come from and which are provisional.
- Documents — a place to keep the supporting material together.
Audit preparation
Year to 31 March 2026
What is not here
There is no tax engine. Nothing computes a statutory liability under any jurisdiction's rules, applies allowances or reliefs, or submits a return to any authority. What the module provides is your own posted data arranged so that the person who does compute your tax has less work to do. Treat any figure here as management information, not as a tax computation.
This page is marked In progress because the preparation views are useful and incomplete — they cover the schedules most commonly asked for and not the full set an auditor may want.
Making an audit easier
- Reconcile monthly, not annually. Twelve reconciled months is the single biggest determinant of how long an audit takes.
- Write real descriptions on journal entries. "Adjustment" costs an hour each when somebody has to ask.
- Lock periods. An auditor who can see that a period was closed and not reopened asks fewer questions about it.
- Keep support with the entry. An attachment on the journal entry is found; a file in a folder is asked for.
- Do not reopen a closed period without a reason you can state. See Close.
What this does not do
No jurisdiction rules, allowances or reliefs.
Nothing is submitted anywhere.
Tax is recorded in the ledger; returns are prepared elsewhere.
The common ones, not the full set.
An auditor is a member with module access, or works from exports.
Questions
Can our auditor have access?
Invite them and remove every module except what they need. See Module access.
Does it handle VAT?
The ledger records it. The return is prepared outside.
Is the provision view reliable?
It is your own posted data, arranged. The provision itself is your adviser's work.