Correcting digital accounting entries should preserve who changed the record, when and why. Use reversals or the software’s controlled correction process where appropriate, and assess whether the change affects a closed period or submitted tax return.
Restrict changes to reconciled periods and retain supporting explanations. Silent edits make later comparisons and professional review harder even when the final balance appears correct.
Identify what the correction changes
Record the original transaction, affected field, reason for the correction and supporting evidence. Distinguish a wrong account code, duplicate entry, incorrect amount and change in tax treatment. Each can have different consequences for reconciliations and reports. A note stating only 'amended' does not help a later reviewer understand whether the change was clerical or altered a submitted tax figure.
VAT record requirements make it important to retain an understandable link between transactions, adjustments and reported totals. Review whether the correction affects an open period or information already submitted. The software's ability to edit an entry does not establish that editing alone is the correct reporting response. Keep the bookkeeping action and any required return correction connected but separately identified. [1]
Use the supported method for the record type
Check whether the system expects an edit, reversal, credit note, unmatching or another controlled action. An issued invoice, reconciled payment and draft journal may need different treatment. Preserve the original commercial document where required and avoid deleting history simply because a reversal leaves more lines in the ledger. The objective is a clear record of what happened, including the correction, rather than the shortest possible transaction list.
Where a manual journal is appropriate, use a meaningful description and attach or reference the calculation. Identify the period and accounts affected and obtain approval for material adjustments. Do not use a suspense or miscellaneous account as a permanent destination for a difference nobody understands. A journal can make totals agree while leaving the underlying customer, supplier or VAT record incorrect.
Preserve who approved and applied the change
Use named accounts and retain the system's audit history. Record the person authorising the correction separately from the operator applying it where those roles differ. A manager's email approving a commercial refund may support the business decision, while the accountant's review determines the VAT or accounting entry. Keep both instructions connected without assuming either one alone explains the complete correction.
For a small business with one bookkeeper, a periodic owner or accountant review of material changes can provide a proportionate control. Focus on changes to closed periods, bank details, tax codes and large balances rather than reviewing every harmless spelling correction. Keep a short record of the review and unresolved questions so the audit trail is used to understand changes, not merely retained as an unread technical log.
Reconcile the downstream effects
After correcting an entry, check the relevant bank match, invoice balance, tax report and management output. A change in one system may not automatically flow to an integration or a report already exported. Identify which outputs need refreshing and preserve the previously issued version where it forms part of the record. Do not assume that a live dashboard now showing the right number corrects a report already sent to a lender or adviser.
Where a correction affects a submitted return, establish the proper amendment route and retain acceptance evidence. Keep the reason and calculation with the original period. The person preparing the next return should be able to see whether the historic issue has already been corrected or still requires action. Otherwise, an adjustment can be omitted entirely or applied again because the previous operator's note was unclear.
Prevent silent changes to completed periods
Use period locks or equivalent controls where the software supports them, with an authorised process for reopening. Record why access was needed and what was changed. Avoid permanent administrator access for every user simply to make occasional corrections easier. A controlled exception process allows legitimate amendments while reducing the chance of an accidental historic edit during ordinary data entry.
Read Avoiding duplicate transactions in bookkeeping software for duplicate-transaction corrections and Accounting software migration support to discuss accounting audit trails and adjustment controls. Provide the transaction type, period and reason for the change, using anonymised details initially. A focused review can identify the right correction method and reporting follow-up without requiring unrestricted access to every record in the business.
At the next close, review the list of changes made to earlier periods and confirm that related reports remain reconciled. Keep explanations concise and factual. An audit trail is most useful when a person can follow the business reason and numerical effect, rather than having to interpret an unexplained sequence of deletions and replacement entries.
Illustrative scenario
A purchase is posted to the wrong period after a VAT return is filed. The reviewer records the discovery, checks the tax correction route and preserves the original and corrected entries.
Preparation checklist
- Explain the error
- Check closed-period effects
- Use controlled corrections
- Retain approval and evidence
Frequently asked questions
Is editing the ledger enough to correct a submitted VAT return?
Not necessarily. Assess the required reporting correction separately and retain the link between the amended record and the return action.
Should an issued invoice be deleted to hide a mistake?
Use the appropriate correction or credit process and preserve the required history. A tidy ledger should not come at the cost of losing the original transaction evidence.
Who should be named in the correction record?
Identify the person authorising the change and the person applying it, where different, together with the date, reason and supporting calculation.
Why lock completed periods?
A controlled lock helps prevent accidental historic changes. Legitimate corrections can still be made through an authorised process with a clear audit trail.
Official sources
Sources checked: 8 September 2026. Check the linked guidance for subsequent changes.
General information only. The appropriate action depends on your circumstances and the applicable jurisdiction.
Report a correction