Never edit a posted document: cancel and amend it. Lock closed periods. Then the system's own history answers most auditor questions without a spreadsheet.
What a useful audit trail records
An audit trail answers four questions about any number in the books: who changed it, when, what it was before, and why. Systems that only record the current state of a document cannot answer the last three, which is why auditors working with them end up asking for email threads and spreadsheets.
A useful trail captures field-level changes on master data and transactions, the user who made each change, a timestamp, and the document's status changes: created, submitted, cancelled, amended. It also has to be hard to tamper with. If a user with enough access can quietly delete the history, it is a log, not a trail.
Submit, cancel, amend: never overwrite
The ERPNext engine underneath Sundial separates draft documents from submitted ones. A draft invoice can be edited freely. Once submitted, it posts to the ledgers and becomes read-only. If it is wrong, you cancel it, which reverses its ledger entries, and create an amendment: a new document linked to the original, with its own number derived from the first.
This is slower than editing in place, and some teams find it frustrating at first. It is also exactly what makes the books trustworthy. Every posted figure has a document behind it, and every correction has a visible chain back to the mistake it fixed.
Version history on the records that matter
Beyond posting, many records change over time: a customer's credit limit, a supplier's bank details, an item's valuation method, a price list rate. Turn on change tracking for these. The system then keeps a version entry showing the old and new values and who made the change.
Supplier bank details deserve special attention. A changed bank account just before a large payment is a classic sign of fraud. Make sure changes to it are tracked, reviewed by a second person, and confirmed with the supplier through a channel other than the email that requested the change.
Lock the periods you have closed
Once a month is closed and reported, nobody should be able to post into it without a deliberate, recorded decision. The engine supports a frozen-accounts date, before which only a named role can post, and period closing vouchers that carry the year's profit or loss to the balance sheet.
Set the frozen date as part of each month-end close. If a late entry is genuinely needed, a finance lead unlocks, posts with a clear remark, and locks again. The audit trail will show all three steps.
Do the same for stock. Back-dated stock entries change valuation for every later transaction of that item, which can quietly alter the cost of goods sold in a month you have already reported. Restrict back-dating to a small group, and review any stock entry posted with a date earlier than the day it was created.
What auditors ask, and how to answer quickly
Most audit requests fall into a few patterns: show me the documents behind this balance, show me changes to these masters during the year, show me entries posted after the period closed, and show me who can approve payments. If your system can produce each of those as a filtered report rather than a reconstruction, the audit gets shorter and cheaper.
Prepare a short pack before the auditors arrive: the trial balance, subledger reconciliations, the list of users and roles, the frozen-accounts date for each month, and a report of entries posted after each period closed. Most of the first week of questions is answered before it is asked.
External auditors, lenders and investors increasingly expect the system itself to show who changed what and when, and to prove that closed periods stayed closed. If you are preparing for a financial statement audit or SOX-style internal controls, ask your auditor which change-history and access reports they will want, and walk through them together before year end rather than during the audit. A full record helps, but control design is still your team's and your auditor's call.
Habits that keep the trail clean
- Write a short remark on every journal entry explaining why it exists.
- Attach the source document, such as the supplier invoice or bank advice, to the record.
- Use named accounts for everyone; never share a login.
- Keep the number of people with administrator access very small.
- Review cancelled and amended documents each month; a rising number usually points to a process problem upstream.




