Postponed VAT accounting: an enterprise guide to import controls

What is postponed VAT accounting?

Postponed VAT accounting, usually shortened to PVA, allows an eligible UK VAT-registered business to account for import VAT through its VAT Return instead of paying that VAT upfront and recovering it later. The normal input-tax recovery rules still apply. For a business entitled to recover the full amount, the corresponding return entries can offset. A business with restricted recovery must calculate the restriction rather than assume that PVA makes the import tax-free.

The commercial benefit is a reduction in the cash tied up between importing goods and recovering VAT. That is a financing benefit, not a reduction in the purchase price or customs duty. Finance teams should assess it alongside their actual import volumes, recovery position and administrative costs. A large theoretical benefit is of little use if an agent keeps selecting another payment method or the statement cannot be reconciled at period end.

The useful unit of control is the individual import entry. A supplier may invoice one group company while another company is named in the customs process. A freight bill may combine transport charges with tax disbursements. A single consignment may generate several documents. The finance system needs a traceable relationship between these records; a generic overseas-supplier tax code cannot establish that relationship on its own.

Start with the importer and the movement of goods

HMRC permits PVA for qualifying imports into Great Britain from outside the UK, and into Northern Ireland from outside the UK and EU. No separate PVA approval is required. The business must be UK VAT-registered, and the eligibility conditions include the relevant business use, the right to dispose of the goods and the VAT registration number on the declaration. Special circumstances need separate review: a goods movement involving Northern Ireland should never inherit a Great Britain rule simply because the supplier is overseas.

Create an importer record distinct from the supplier record. Capture the importing legal entity, its VAT registration, EORI, establishment, customs representative and the person responsible for the tax decision. HMRC’s EORI guidance explains when the customs identifier is needed. It serves a different purpose from a company registration number, and maintaining all three identifiers does not make them interchangeable.

For a group with central purchasing, ask which entity buys the goods, which has the right to dispose of them, which appears on the declaration and which accounts for the VAT. Resolve inconsistent answers before scaling the process. Company identity information can help clarify names and entity relationships, but it cannot determine import VAT entitlement from a company name alone. Contracts, customs records and the actual transaction remain necessary evidence.

Which guidance changes should your procedure reflect?

An old implementation note can remain in a broker’s instructions long after the official guidance changes. Record the authority and review date beside each operational rule. A statement publication date, an update to guidance and the start of a legal requirement are different events. The timeline below deliberately labels them separately; it is not a list of new tax mandates.

Two checks deserve attention in an existing procedure. HMRC’s current declaration guidance specifies the VAT registration number at header level in Data Element 3/40 and says not to use payment method G in Data Element 4/8 for this purpose. Its statement guidance now says statements are usually available by the tenth working day. Older instructions referring to a sixth or eighth working day should be reviewed rather than copied into an escalation rule.

On 19 May 2026, HMRC added guidance about duplicate entries on monthly PVA statements. This is a practical reason to revisit controls even if the importing business has used PVA for years. The change does not mean every repeated supplier amount is an error; the comparison needs the customs reference and supporting entry evidence.

Give the customs agent an instruction they can execute

HMRC requires written instructions where another person imports on your behalf using PVA. Where the supplier arranges the import, agree the VAT-accounting approach with that supplier so the correct written instructions reach the person making the declaration. Preserve the instruction and the version that applied to the shipment. An assumption in a procurement conversation is not a reliable substitute for an operational record.

The instruction should identify the importing entity and approved identifiers, the intended VAT treatment, the relevant goods or shipment scope and the escalation contact. Define what happens if the agent receives conflicting information or cannot apply the intended treatment. Avoid a blanket instruction that encourages an agent to force PVA onto movements outside its scope. Have tax and customs owners agree the exceptions before handing the process to a shared-service team.

Representation also needs clarity. HMRC distinguishes direct and indirect representation and explains their liability consequences. Appointing an agent does not remove the importer’s responsibility for due diligence. Review the agreement for access to declaration copies, correction responsibilities, service hours and evidence delivery. These are operational controls that procurement can negotiate and finance can test, rather than relying on a broad assurance that customs is being handled.

Retrieve every import VAT statement before it becomes an archive problem

The monthly import VAT statement is accessed through the Customs Declaration Service. HMRC says PVA statements are normally available by the tenth working day of the month and directly accessible for six months after publication. Download and retain them. For a VAT group, importing members obtain their own statements and pass them to the representative member. A group-level return therefore needs a completeness check across all importing members, not just one login.

CDS access deserves its own owner and backup. HMRC’s subscription guidance links the business’s EORI and CDS account to its sign-in details and provides for team-member access. Confirm that the people preparing the return can retrieve the correct records before the filing window. A broker’s ability to submit a declaration should not be treated as proof that your finance team can retrieve the corresponding statement.

Maintain a monthly control sheet listing expected entity/EORI combinations, statement period, retrieval date, file location, total, reviewer and outstanding issues. An empty statement and a statement that nobody downloaded are different outcomes. Keep the original file together with any reconciliation and approved adjustment. The six-month online window is an access limit; HMRC’s general VAT record-retention requirement is at least six years, subject to relevant exceptions.

Reconcile entries, not only the monthly total

HMRC’s statement explanation separates the monthly summary from individual entries. The detailed section includes the import date, entry reference, declarant’s reference, declarant EORI and VAT amount. Use those fields to connect the customs record to the shipment and the accounting record. The intermediary’s EORI can appear in the declarant field; that does not make the intermediary the owner of the goods.

Build a reconciliation that can identify both missing and unexpected entries. Begin with the imports you expected from logistics and customs records, then compare those with the statement. Also work backwards from statement entries to supporting records. A one-way check can confirm every expected shipment while leaving an unrelated or duplicate entry unnoticed. Review mismatches by cause, rather than placing every difference in a general suspense account with no owner.

HMRC identifies a duplicated statement entry by the same movement reference number and VAT amount and instructs businesses to adjust the statement manually and account for the revised amount. Preserve the original statement, the evidence supporting the duplicate and the approved reconciliation. A system should flag candidates for review, not delete every repeated value: separate imports can legitimately carry identical amounts. Keep any estimate previously accounted for visible so its later replacement does not become a second full posting.

A postponed VAT accounting example for the finance team

Illustrative example: an importer has an agreed import VAT value of £100,000, a 20% VAT rate and £20,000 of import VAT to account for. Assume the goods qualify for PVA, the entry belongs to the business and all required evidence is held. With full input-tax recovery, the import contributes £20,000 to box 1 and £20,000 to box 4. The goods value contributes £100,000 to box 7, without duplicating a value already included in the return preparation.

Change only the recovery assumption: if an approved calculation permits recovery of 60% of that import VAT, box 4 includes £12,000 and the net VAT effect is £8,000. This is arithmetic under an illustrative assumption, not a prescribed partial-exemption percentage. The actual recovery method and any annual adjustment must follow the business’s circumstances. Finance should store the recovery decision separately from the gross tax liability so a later review can reconstruct both.

The £100,000 input is the import VAT value, not necessarily the overseas supplier’s invoice total. HMRC’s valuation guidance starts from customs value and adds relevant duties and incidental expenses. The customs-value method also depends on the transaction: a free sample or a branch transfer may not qualify for Method 1. Resolve those issues with the customs owner before an accounts-payable rule simply multiplies every foreign invoice by 20%.

Keep postponed VAT separate from C79 and duty deferment

A duty deferment account delays payment of customs charges and generally consolidates them into a monthly Direct Debit. HMRC includes import VAT in that arrangement when PVA is not used. PVA instead accounts for the relevant import VAT through the VAT Return. A business may therefore need customs-duty payment arrangements even when its import VAT uses PVA. These are separate decisions, and a logistics invoice should not blur them.

HMRC’s current C79 service guidance covers certificates showing import VAT paid using a duty deferment account. It directs PVA users to their postponed import VAT statements instead. Where your business uses both approaches across different imports, reconcile both populations. Do not post a tax amount from a freight invoice and then claim it again when a certificate or statement arrives. The reference connecting a charge to its customs entry is more useful than a label saying VAT.

The national statistics illustrate why terminology matters. HMRC reported £162 billion of Home VAT receipts and £9 billion of non-postponed import VAT receipts for 2024–25, rounded to billions. PVA receipts cannot readily be separated from Home VAT. Those two categories must not be used to calculate a PVA adoption rate or to claim that only £9 billion of import VAT existed. The graph compares receipt categories, not importers or tax savings.

Define the exception process before the filing deadline

Give each exception a decision owner and a resolution date. Missing entries require a check of the declaration and the EORI used; HMRC specifically suggests checking another group or closely related company’s statement where relevant. Missing access requires an account or service investigation. A valuation difference belongs with the customs and tax owners. Treating all three as a supplier-master issue sends work to the wrong team and delays the close.

Keep the original import period visible when information arrives late. The return must reflect the appropriate accounting period, while the reconciliation must prevent estimates and subsequent confirmed amounts from both being counted in full. Where an amount has changed after filing, HMRC distinguishes nil-net-tax adjustments from cases requiring its error-correction procedures. Tax should assess the facts and correction route; the software should preserve the audit trail rather than silently overwrite the earlier return.

A practical exception register should show the entry reference, amount, legal entity, affected return, evidence available, provisional treatment, reviewer and next action. Track unresolved value as well as the number of items. One high-value unresolved import may matter more than many low-value administrative questions. Closure should require evidence that the source problem and accounting consequence were both addressed, rather than merely marking an email thread complete.

An enterprise implementation checklist

Test the process with a controlled sample before extending it across business units. Include a normal PVA entry, an import handled through a paid-VAT route, a restricted-recovery case, a group-member entry, a statement duplicate and a late correction. Use synthetic cases where necessary and label them as such. The goal is to demonstrate the route from evidence to return, including failure handling, rather than to produce a successful screenshot of one tax code.

Measure the process after implementation. Useful measures include statement completeness by entity, unmatched entry value, duplicate candidates awaiting review, recurring broker errors and elapsed time to resolve material exceptions. Do not invent a target match rate before observing the business’s records. Establish a baseline, identify the largest repeat causes and assign the remediation to someone able to change the upstream process.

• Tax: approve scope, movement rules, recovery treatment and correction decisions.
• Customs: confirm the importing entity, identifiers, valuation and declaration instructions.
• Procurement: agree evidence delivery, escalation and correction responsibilities with representatives.
• Finance operations: retrieve every required statement and reconcile both PVA and paid-VAT records.
• Data owners: keep effective-dated links between legal entities, VAT registrations and EORIs.
• Controller: review material exceptions and confirm evidence retention before sign-off.

What to ask a provider before automating the workflow

Ask the provider to demonstrate a mismatch, not just a clean lookup. Can the workflow distinguish an unresolved company name from an unavailable authority service? Can it retain the supplied identifier alongside the matched record? Does it show when supporting information was retrieved? Can reviewers explain why two records were linked, and can an incorrect link be reversed without losing its history? These questions expose whether automation makes exceptions easier to control or merely hides them.

For a customs or accounting integration, ask separately about statement retrieval, declaration references, duplicate handling, recovery restrictions and return mapping. A company-data service should not be assumed to perform those functions. VATFind can support the company and tax-identifier research step within its available coverage; the customs statement, transaction evidence and tax decision remain distinct parts of the process. Evaluate each component against the task it actually performs.

Finally, keep jurisdiction-specific rules separate. Ireland also offers postponed accounting, but Revenue describes its use through the Irish VAT3 Return under Irish conditions. A shared label does not justify copying UK return boxes or CDS instructions into another country. A scalable operating model reuses the evidence discipline and responsibility structure while keeping local rules, authority services and filing mappings explicit.