Finding a VAT error is a reason to investigate promptly, not to force a balancing entry into the next return. You need to establish what happened, which periods are affected and which correction route applies.
In this article
- Identify the error and affected period
- Work out the amount and cause
- Confirm the correct correction method
- Keep evidence of the action taken
Start by separating an error on an already submitted return from an ordinary current-period adjustment. A genuine later refund is different from discovering that the original sale was recorded twice. That distinction affects both the records and the way you report the change.
Freeze the evidence, then investigate
Save the relevant invoices, credit notes, ledger reports, original return and submission confirmation. Record when the issue was found. If you change an entry immediately without preserving the original position, another reviewer may struggle to reproduce your calculation.
Prepare a short error log with these fields:
| Field | Why it matters |
|---|---|
| Affected transaction and period | Links the issue to the submitted figures |
| Original VAT treatment | Shows what was previously declared |
| Correct treatment and evidence | Supports the revised calculation |
| VAT difference | Measures the tax effect rather than just the invoice value |
| Cause and discovery date | Explains the circumstances and follow-up |
| Proposed correction route | Prevents duplicate reporting |
Also identify whether the same cause affected other transactions. A wrong default code may have been used repeatedly; one duplicate invoice may be an isolated mistake. Search related entries before concluding that you have measured the complete error.
Calculate the net VAT error carefully
Work out VAT underdeclared and overdeclared across the relevant errors, then establish the net result. Exclude deliberate errors from this calculation and report them separately. Do not use the gross value of invoices as if it were the VAT error. Keep separate workings for each affected period so the net amount can be checked.
HMRC allows qualifying errors from the previous four years to be adjusted on the next return where the net error is £10,000 or less, or between £10,000 and £50,000 and does not exceed 1% of the current return’s box 6 figure. Errors outside those limits, and deliberate errors, need separate notification. See HMRC’s correction rules, including the detailed time-limit rules.
The thresholds do not excuse inaccurate records or make every small error harmless. They help select a reporting method. Where behaviour, timing or a disputed VAT treatment is uncertain, take advice before deciding how to proceed.
Use the current notification route
HMRC’s VAT error reporting checker directs businesses towards updating a return, making an online correction or notifying in writing. Form VAT652 is no longer the correction route. Avoid following an old downloaded checklist without checking the live guidance.
Before sending a separate notification, assemble the VAT number, affected periods, tax differences and explanation. Keep a copy of what was sent and a record of subsequent HMRC correspondence. If someone else prepares the correction, clarify who authorises it and who monitors the response.
When an error is corrected through a return, retain workings that show exactly how it enters the VAT account. A reviewer should be able to distinguish ordinary period activity from the correction without guessing from a single journal description.
An illustrative duplicate purchase
Suppose a small wholesaler discovers that a supplier invoice was captured from email and entered again from a paper copy. The business reclaimed the same input VAT twice on a submitted return. This is an illustrative scenario.
The bookkeeper preserves both entries and the supporting invoice, checks the original return, and searches for further duplicate invoice numbers. They calculate the VAT overclaim and test the complete net error against the relevant reporting conditions. They then agree the correction route with the owner.
Deleting one ledger entry may repair the current books, but does not by itself demonstrate that HMRC has received the necessary correction. The working paper connects the ledger repair to the return adjustment or separate disclosure and confirms that the amount will not be reported twice.
Think about penalties without making assumptions
The outcome can depend on how an error arose and how it is disclosed. A method 1 return adjustment is not itself a penalty disclosure. For a careless error, HMRC requires separate notification to obtain the maximum available penalty reduction; explain any adjustment already made so it is not counted twice. See Notice 700/45, section 4. HMRC’s inaccuracy penalty guidance explains the relevance of behaviour and disclosure.
A factual explanation is more useful than a vague statement that the software failed. Describe the control that was missing, the transactions affected and what you changed. Do not speculate about deliberate conduct; obtain advice where the facts raise that concern.
Close the cause as well as the correction
After reporting, assign a prevention step. Duplicate invoices may call for invoice-number checks. Misclassified sales may need a product-code review. Unrecorded credits may need a monthly supplier statement reconciliation. Give the change an owner and check that it works at the next close.
Keep unresolved technical queries separate from confirmed errors. If you are unsure whether a transaction was taxable, collect the contract and evidence before selecting a different code.
For support organising records and reviewing the appropriate correction process, enquire through EPOS Accountancy’s VAT service. Supply the original return, your error log and relevant deadlines so the required scope can be agreed. Fee information is on the pricing page.