Audit-ready books
Books where every entry traces to a document, every change is on the record and closed periods stay closed.
The problem
Audits are painful when numbers cannot be traced. An entry with no document behind it, an invoice edited after it was sent, a prior month changed after the accounts were shared: each one becomes a question, and each question costs days.
How it runs in Sundial
1. Ledger entries come from documents. A sales invoice, purchase invoice, payment, stock entry or journal entry posts to the general ledger, and every ledger line links back to the document that created it.
2. Submitted documents cannot be edited. To correct one, you cancel it, which reverses its postings, and amend it into a new version that keeps a link to the original.
3. Every change to a record is kept in its version history: what changed, from what to what, who did it and when.
4. Closed accounting periods are locked against new postings, and accounts can be frozen up to a date so only authorized roles can post before it.
5. Roles and permissions decide who can create, submit, cancel or view each type of document, down to the company.
What the team sees
Auditors start from the trial balance and drill into the general ledger, then into the source document, then into its history, without asking anyone for a file. Finance answers questions by sharing a link. Owners know that what they signed off has not changed since.
Sample for Kestrel Workspace: FY 2025–26 locked, 14 cancelled and amended invoices each linked to their original, no postings into closed periods.
With AI (coming to Sundial)
Sundial is built for an agent to run pre-audit checks, such as entries without attachments, unusual manual journals or round-sum payments, and hand the list to the accountant. That is on the roadmap; the controls above are in the product today.

