Match each postponed import VAT entry to its customs evidence, resolve exceptions, and give the VAT reviewer a traceable statement-to-return bridge.
A monthly postponed import VAT statement can agree to the ledger in total and still contain the wrong imports. One missing entry and one duplicate can cancel each other out. A previously estimated amount can also be counted again when the actual statement arrives.
For a UK VAT-registered goods importer already using postponed VAT accounting (PVA), reconciliation should therefore prove both which entries belong and how their amounts reach the VAT return. This guide sets out a working register, exception routes and a review gate. The ownership rules and workflow states below are recommended internal controls, not additional HMRC requirements. Special schemes, restricted input tax recovery and unusual import arrangements need a separate tax assessment.
Define what this reconciliation closes
The output is an approved evidence pack for one importing entity, EORI number and reporting period. It connects the statement, import records, accounting records and proposed return treatment. It does not prove a supplier has been paid or that customs duty has settled.
This is also different from reverse charge VAT review for international services: goods-import PVA depends on customs entries and the postponed import VAT statement, not simply the wording on an overseas service invoice.
Use the states Collected → Matched → Exception review → Tax approved → Recorded → Reconciled → Closed. An exception can return to Matched when corrected evidence arrives. If the evidence or amount changes after approval, reopen the affected review rather than silently replacing the approved calculation.
Collect the right statement before matching
HMRC says statements are usually available by the tenth working day of the month. Its statement-access guidance says to download and retain each statement: ordinary online access lasts six months, after which statements are archived. The CDS dashboard provides guidance for accessing older statements. A VAT-group member that imports goods should obtain its own EORI statement and send it to the representative member.
Make the importing entity—not the freight forwarder—the owner of the collection checklist. Give a named backup responsibility for obtaining the source document if the usual preparer is absent. Access should use the business’s established authorized arrangements; do not place login details in a reconciliation register.
- Save the original statement with its month, entity and EORI identification.
- Obtain the customs-entry listing and the agent’s supporting references.
- Collect relevant import purchase records and the accounting report used for VAT preparation.
- Bring forward estimates, unresolved entries and adjustments already reported, so they cannot be posted twice.
Build an entry-level reconciliation register
Start with an import reference, not an invoice amount. A single supplier invoice may relate to more than one declaration, and equal VAT amounts do not by themselves identify duplicate entries. Preserve the source reference even when accounting software uses a different transaction identifier.
According to HMRC’s statement explanation, individual entries include the import date, entry number, declarant’s reference, declarant’s EORI and VAT amount. Those fields provide the starting point for matching; the internal owner and review fields below complete the operational record.
| Field group | Record | Completion evidence |
|---|---|---|
| Scope | Importing entity, EORI, statement month and VAT period | Reviewer confirms the population belongs to the return being prepared |
| Entry identity | Customs entry/MRN, agent reference and linked purchase record | Traceable source documents, with split or combined relationships explained |
| Amount bridge | Statement VAT, accounting amount, prior estimate and proposed difference | Calculation explains the change without repeating a previously reported amount |
| Exception | Reason, evidence request, responsible owner and next review date | Response resolves the issue or records the tax reviewer’s decision |
| Approval and recording | Reviewer, approved version, posting reference and return working-paper reference | Recorded figures agree to the approved treatment |
| Closure | Residual difference, decision and retained source version | No unexplained difference is hidden by a balancing entry |
The preparer builds the register and investigates mismatches. The customs agent supplies declaration evidence or explains allocation. The tax reviewer decides return treatment and recoverability. The accounting owner records approved adjustments. In a small team, combine responsibilities where necessary but retain a second-person review of changes that affect the return.
Route exceptions before approving the total
Missing entries and wrong-entity allocations
HMRC’s return-completion guidance says to check a VAT-group or closely related company’s statement when an expected entry is missing, and ask the customs agent to confirm the correct EORI allocation. Do not create a second accounting entry merely because the item is absent from the first statement you downloaded.
Keep an open request against the customs reference. Record who checked the related entity, what the agent confirmed, and which reviewer will decide the reporting response. A supplier invoice alone does not resolve an EORI mismatch.
Duplicate statement entries
HMRC identifies duplicated entries by the same movement reference number and VAT amount and says to adjust the statement manually and account for the revised VAT amount. Preserve the downloaded original alongside the reconciliation adjustment. Record the two source rows and the reason one is excluded; do not delete the evidence or remove every repeated amount.
Unavailable statements and earlier estimates
HMRC’s statement-access guidance permits estimates when statements cannot be accessed and explains that, once the statement becomes available, the difference must be reflected on the next return. Keep the original estimate, its basis and the period in which it was reported. Later, bridge the actual amount to that estimate rather than adding the full statement value again.
Give each unresolved estimate its own owner and follow-up date. “Statement unavailable” is an exception state, not a permanent explanation for a recurring unreconciled balance.
| Exception | Owner and evidence | Release condition |
|---|---|---|
| Entry missing | Preparer and agent: EORI, declaration and related-entity check | Tax reviewer approves documented treatment; unresolved source issue remains tracked |
| Possible duplicate | Preparer: identical MRN and VAT amount, source-row comparison | Reviewer approves the explained adjustment, not an amount-only deletion |
| Actual differs from estimate | Preparer: earlier reported estimate and actual statement | Only the supported difference moves into the applicable adjustment process |
| Recoverability uncertain | Tax reviewer: business use and relevant recovery assessment | Approved input-tax treatment; do not assume output and input VAT cancel |
| Evidence changes after approval | Accounting owner and reviewer: old/new versions and impact | Reapproval and linked correction record before revised closure |
Work an illustrative statement-to-records bridge
Suppose a fictional importer has four legitimate entries with VAT of £2,000, £1,500, £900 and £600: £5,000 in total. Its downloaded statement shows £5,900 because the £900 entry appears twice with the same MRN and VAT amount. The preparer retains both rows and documents a £900 duplicate adjustment, giving an adjusted statement total of £5,000.
The accounting records contain £4,700. Tracing each legitimate entry shows that the fourth import was recorded at an estimated £300 rather than its actual £600. The difference is £300:
- Downloaded statement: £5,900.
- Less documented duplicate: £900.
- Adjusted statement: £5,000.
- Accounting amount before correction: £4,700.
- Supported accounting difference: £300.
Assume this is a current-period preparation example and the estimate has not yet been included in a submitted return. The reviewer approves the £300 correction under the company’s accounting configuration, then checks that recorded import VAT agrees to £5,000. The worked bridge is not a universal journal or a claim that £5,000 is automatically recoverable.
If the £300 estimate had already been reported, the team would instead link the previously submitted amount and obtain approval for the applicable adjustment route. That is why a register needs both the statement period and the earlier reporting reference.
Approve the return bridge, then close the evidence pack
HMRC requires PVA reporting in the VAT accounting period covering the import date. Its return guidance places VAT due in box 1, VAT reclaimed subject to normal recovery rules in box 4, and imported goods’ value excluding VAT in box 7. The statement VAT total is therefore not the box 7 value. For discovered errors, apply HMRC’s appropriate correction route rather than assuming every adjustment is a nil-net-tax correction.
Before release, the reviewer should be able to follow every reconciliation adjustment to its evidence and every approved amount to the return working papers. Reconcile all months included in the return, bring forward unresolved issues explicitly, and require an explanation for differences rather than accepting a total-only tie.
HMRC’s manual-adjustment control guidance explains digital VAT-account recording and retaining supporting calculations separately for the audit trail. An evidence register is not a substitute for recording tax adjustments in the required compatible software. Keep the approved reconciliation version, source statements, correspondence, calculation, posting references and reviewer decision together.
Where Workhint fits
The coordination problem is the handoff between a preparer requesting evidence and a reviewer authorizing the next step. Workhint’s Workflow Engine supports defined requests and approvals, routing to roles, and required details, files or notes before work advances. Those are relevant building blocks for a document-review process.
Its workflow automation software solution describes structured forms and tracking stages, approvals, owners and next actions. A proposed PVA review design could use an evidence request followed by a human review gate. Confirm the exact configuration and record-handling needs before implementation.
This is a workflow-design example, not evidence of a native HMRC/CDS connector, automated VAT calculation, import-entry matching or VAT filing. Customs records, tax decisions and accounting entries remain with their appropriate authoritative systems and responsible specialists.
Frequently asked questions
Is agreeing the statement total enough?
No. Offsetting errors can leave the total unchanged. Match entry identities, explain the differences and connect approved amounts to the accounting and return records.
Should box 1 and box 4 always be equal?
No. Input-tax recovery follows the normal rules. The reviewer must consider recovery restrictions instead of treating PVA as an automatic full offset.
Can a missing statement be treated as zero?
Not merely because it is unavailable. Follow HMRC’s current access and estimation guidance, retain the basis, and track the later actual-to-estimate adjustment.
When is the reconciliation closed?
Under the proposed internal control, close it when the reviewer has approved the evidence and treatment, recording references are linked, and residual issues are either resolved or explicitly carried forward with an owner. Reopen the review if material evidence changes.

Leave a Reply