When the UK left the EU VAT system on 1 January 2021, every business importing goods into the UK faced an immediate operational change. EU goods, which had previously moved under intra-EU VAT rules with no import VAT triggered at the border, were suddenly subject to the same import VAT treatment as goods arriving from any other part of the world.
For UK mid-market businesses importing regularly from EU suppliers, that change created a cash flow problem that had not existed before. Under the traditional import VAT payment method, a business pays VAT at the point goods enter the UK and then reclaims it on the next VAT return. For a business importing £500,000 of stock per month at a standard 20 percent VAT rate, that means a rolling £100,000 cash position tied up in import VAT at any given time, waiting to be reclaimed in the following quarter.
HMRC introduced Postponed VAT Accounting, known as PVA, to address that problem. For businesses that use it correctly, PVA is genuinely useful. For businesses that use it incorrectly, or that rely on software that handles it imprecisely, it creates compliance exposure that HMRC is increasingly active in identifying.
This post explains how PVA works, where UK importers get it wrong, and what the right software platform does to handle it correctly.
What Postponed VAT Accounting Actually Does
Under PVA, businesses do not pay import VAT at the point goods enter the UK. Instead, the VAT is accounted for on the VAT return using figures from the Monthly Postponed Import VAT Statement, known as the MPIVS, which HMRC makes available online each month. Taxset
The mechanics work like a reverse charge. Import VAT is recorded as output tax in Box 1 of the VAT return and simultaneously reclaimed as input tax in Box 4, while the total value of imports is declared in Box 7. For businesses that reclaim all their input VAT, the net effect on the return is zero. Invoicedataextraction
PVA is optional. If a business prefers, it can pay VAT upfront at the border and receive monthly C79 import VAT certificates from HMRC to reclaim the VAT later. But for businesses importing regularly at volume, the cash flow advantage of PVA over the C79 method is material. A quarterly filer importing £500,000 of goods per month could otherwise have over £300,000 tied up in import VAT at any given time. XeroVjmglobal
To use PVA, the business must be VAT-registered in the UK, must import goods into Great Britain, must hold a GB-prefixed EORI number used in customs declarations, and must include its UK VAT number in those declarations. There is no application process and no permission required. Businesses must register with the Customs Declaration Service, which replaced the old CHIEF system and now serves as the UK’s sole customs declaration platform. Trueman BrownXero
What Changed in 2025
The core PVA mechanics have not changed since 2021, but there was a notable update in mid-2025 worth understanding. As of June 2025, HMRC removed the previous mandatory requirement for deferred declarations. PVA remains mandatory only for B2B imports into Northern Ireland from outside the EU valued under £135. For the vast majority of UK mainland importers, PVA remains optional but beneficial. Vjmglobal
VAT applies to all goods imported into the UK when the consignment value exceeds £135. For B2B imports at or below that threshold, the UK business recipient accounts for VAT via reverse charge rather than through PVA. Vjmglobal
HMRC’s compliance activity around PVA has also increased. PVA creates a digital trail between customs declarations, import VAT statements, and VAT returns, which means discrepancies are easier for HMRC to identify. VAT compliance activity has increased significantly in recent years, with HMRC carrying out more VAT investigations and making greater use of data matching and digital reporting systems. Lwaltd
For UK importers, that increased scrutiny means the margin for error on PVA returns has narrowed. Getting the mechanics right matters more now than it did in the early years after introduction.
Where UK Importers Get PVA Wrong
The compliance errors HMRC identifies most consistently in PVA returns fall into a small number of recurring categories. Understanding them is the first step to avoiding them.
Using estimates instead of HMRC statements
Businesses should always use the figures shown on the Monthly Postponed Import VAT Statement from HMRC rather than relying solely on supplier invoices or customs paperwork. The MPIVS is the authoritative source. Using estimates, even carefully calculated ones, creates a discrepancy between what the business submits and what HMRC’s own systems show. That discrepancy is exactly what HMRC’s data matching process is designed to identify. Taxset
The practical problem is that MPIVS statements are not always available when the VAT return needs to be filed. Statements become available online through the Customs Declaration Service typically in the month following the import period. For businesses filing quarterly returns with tight deadlines, waiting for the statement is not always operationally convenient. Many businesses estimate and then forget to reconcile when the statement arrives. That is the error pattern HMRC sees most often.
Accounting for PVA in the wrong period
A critical detail that catches many businesses out: import VAT must be accounted for in the VAT return period that covers the date of import, which is the date shown on the customs declaration. This is not the date the MPIVS is downloaded, and it is not the date the goods physically arrive at the warehouse. Invoicedataextraction
For a business importing goods on 28 March, the import VAT belongs in the March return even if the MPIVS for that period only becomes available in April. If the statement arrives after the return has already been filed, the business may need to correct the return rather than simply including the figures in the next one. Period mismatches are one of the most common errors HMRC identifies, and they can trigger amendment requests and interest charges even when the underlying VAT position is correct. Invoicedataextraction
Incorrect VAT return box entries
The three-box structure of a PVA return is straightforward in principle but produces errors in practice when finance teams are working manually or when software does not populate the boxes correctly from MPIVS data.
Box 1 must include the full import VAT amount alongside all other output VAT for the period. Box 4 must include the same import VAT amount as reclaimable input tax, subject to the business’s normal input VAT recovery rules. Box 7 must include the total net value of all imported goods. If the business is not fully taxable, the amount of import VAT in Box 4 will not equal that in Box 1, and the correct recovery percentage must be applied rather than claiming back the full amount. Partially exempt businesses that apply a full recovery rate by mistake create a material compliance error rather than a timing one. Crowe
Not downloading MPIVS statements at all
Businesses must opt for PVA on customs declarations and download Monthly Postponed VAT Statements from HMRC as evidence for VAT recovery. Some businesses instruct their freight forwarder to apply PVA on declarations but never access the MPIVS themselves, relying instead on the customs paperwork their agent provides. The customs paperwork is not a substitute for the MPIVS. It does not contain the same figures, it is not what HMRC’s systems cross-reference, and it does not constitute valid evidence for VAT recovery in the same way. Businesses that cannot produce MPIVS statements for the periods under review during a VAT enquiry face a difficult conversation about the validity of the input VAT they have claimed. VATupdate
Flat Rate Scheme miscalculation
Businesses on the VAT Flat Rate Scheme must account for PVA imports outside their Flat Rate Scheme turnover calculation, adding the full amount of import VAT to Box 1 after completing the FRS calculation. This is a specific rule that sits outside the normal FRS mechanics and is easy to miss for businesses that adopted PVA after joining the FRS without revisiting how their VAT return process works. Applying the FRS rate to import VAT instead of adding the full amount separately produces an understated Box 1 figure that HMRC’s data matching will eventually surface. Vjmglobal
What the Right Software Does
Manual PVA compliance is a process risk. The error patterns above are not signs of careless finance teams. They are the predictable output of a process that requires multiple manual steps, depends on data arriving from an external government portal on a specific timeline, and needs to populate VAT return boxes correctly across different business VAT profiles.
The right software eliminates most of that manual process by handling PVA mechanics structurally rather than leaving them to a manual reconciliation step.
HMRC data connection
A platform with a native HMRC integration pulls the MPIVS data directly from the Customs Declaration Service rather than requiring the finance team to log in to the government gateway, locate the statement, download it, and manually transfer the figures. The statement figures arrive in the platform and populate the relevant VAT return fields automatically. The risk of using the wrong source data or transferring figures incorrectly disappears because the data transfer is not manual.
Period assignment from import date
The period mismatching error happens because manual processes apply the figures when they arrive rather than when they belong. Software that assigns PVA VAT amounts to the period of import date automatically, regardless of when the MPIVS becomes available, eliminates this error at the source. The return for March reflects March import activity. The fact that the March statement arrives in April does not cause a period shift in the platform because the assignment logic uses the declaration date, not the statement download date.
Correct box population
A platform that understands PVA mechanics populates Boxes 1, 4, and 7 correctly as a function of how the import record is structured, rather than requiring the finance team to know the mapping and apply it manually. For partially exempt businesses, the platform applies the correct recovery percentage to Box 4 rather than defaulting to full recovery. The VAT return reflects the right position without the finance team needing to remember a compliance rule that sits outside their normal return process.
Audit trail from import to return
The digital trail that HMRC uses to identify discrepancies between customs declarations, MPIVS statements, and VAT returns is the same trail the platform maintains for internal governance. Every import, every MPIVS figure, and every VAT return entry links back to the underlying customs documentation. When HMRC requests supporting evidence for a specific period, the platform produces it without a manual archive search.
How Monesize Core Handles This
Monesize Core’s HMRC module was built specifically for UK VAT compliance in the Making Tax Digital environment. VAT obligations sync directly from HMRC into the platform. Return drafts go through structured internal review before submission. Adjustments apply where the compliance picture requires them.
For UK importers using PVA, the module handles the import VAT workflow inside the same operational environment where procurement, inventory, purchasing, and accounting all live. A purchase from an EU supplier flows from the vendor record through the Purchases module, with the import and PVA designation handled at the point of record creation rather than as a separate compliance step added at return time.
The connection between operational procurement activity and VAT compliance is structural rather than manual. The finance team is not reconciling MPIVS figures against purchase records at quarter end because the platform has already maintained that connection throughout the period.
This sits within a broader operational platform designed for UK mid-market businesses with 100 to 500 employees running real procurement workflows, multi-branch inventory, and compliance obligations that go beyond what accounting software handles cleanly. The HMRC module is one component of a connected operational environment, not a standalone compliance tool that needs to be fed data from other systems.
The full platform stack costs $7,500 per month at standard pricing with no per-user fees. For businesses on the First 10 Customer annual programme, the full stack runs at $3,750 per month with pricing locked for the contract duration.
The Compliance Picture Is Getting Clearer
PVA has been in place since January 2021. HMRC has had five years to build the data matching infrastructure that cross-references customs declarations with MPIVS statements and VAT returns. The businesses that were getting away with estimates, period mismatches, and incorrect box entries in the early years are now operating in an environment where those errors surface more reliably.
For UK importers running significant import volumes, the question is not whether to use PVA. The cash flow case for it is clear. The question is whether the process handling it is accurate enough to withstand the scrutiny that HMRC’s digital compliance infrastructure now applies to every return.
The right software makes that question easier to answer.
To see how Monesize Core handles postponed VAT accounting for UK importers automatically, request a demo with the team.