TRE Data and Import VAT Compliance for UK Importers

TRE data gives UK importers a line-level record of the import VAT declared on every customs entry. That makes it the most reliable base for checking Postponed VAT Accounting entries, C79 certificates and VAT return figures against what was declared at the border. Reconciling these regularly is the fastest way to find and fix import VAT compliance errors.

Import VAT errors are among the most common findings in TRE data analysis. Postponed VAT Accounting (PVA) changed how UK importers account for import VAT, but reconciliation mistakes remain widespread. This guide explains what the Trader Records Extract shows about your import VAT position, where errors creep in, and how to build a reconciliation routine that stands up to HMRC scrutiny.

What does TRE data show about import VAT?

The Trader Records Extract (TRE) is HMRC's line-level report of the customs declarations linked to your EORI number, drawn from the Customs Declaration Service (CDS). It replaced the older summary-level MSS reports, and it contains duty and VAT amounts for every customs declaration line rather than monthly totals.

For import VAT work, the fields that matter most are:

• Movement Reference Number (MRN), which ties each line back to a specific declaration.
• Customs value, the base on which import VAT is calculated.
• Duty and VAT amounts as declared to HMRC for each line.
• Method of payment codes, which show whether VAT was postponed or paid at the border.
• Declaration dates, needed to match each line to the correct VAT period.
• Importer and declarant EORI, which reveals declarations made in your name by brokers and carriers.

This line-level visibility enables systematic reconciliation against three records: your VAT returns (Boxes 1 and 4), your C79 import VAT certificates, and your monthly postponed import VAT statements. Each of those documents tells you what HMRC thinks happened. The TRE tells you what was declared, line by line.

How does Postponed VAT Accounting affect your VAT return?

Since 1 January 2021, VAT-registered importers have been able to use Postponed VAT Accounting to account for import VAT on their VAT return instead of paying it at the border. HMRC's guidance on accounting for import VAT on your VAT return sets out who can use it and when. The cash-flow benefit is real, but PVA also moves the compliance burden from the border to your VAT return.

PVA touches three boxes on the return:

• Box 1: the import VAT due under PVA, taken from your monthly postponed import VAT statement.
• Box 4: the same VAT reclaimed as input tax, subject to the normal recovery rules.
• Box 7: the value of the imported goods, included in your total purchases.

The monthly statement is downloaded from the CDS financial dashboard, and HMRC only makes each statement available for a limited period, currently six months. Miss the window and you are reconstructing figures from declaration records instead of working from the official statement.

Where C79 certificates still apply

Not every import goes through PVA. Where import VAT is paid at the border or through a duty deferment account, HMRC issues a monthly C79 import VAT certificate as the evidence for reclaiming that VAT as input tax. Many importers run both regimes at once, often without realising it, because different brokers make different choices on the declaration.

What are the most common import VAT errors in TRE data?

When importers reconcile TRE data against their VAT records for the first time, the same problems appear repeatedly:

• Double accounting. A broker pays import VAT at the border while the declaration is also flagged for PVA, or a statement entry is posted twice. The VAT ends up in Box 1 and on a C79, overstating liability or recovery.
• PVA declared but never brought to account. The declaration selects postponed accounting, but the statement figure never reaches Box 1. The return understates output tax and HMRC's records no longer match yours.
• Reclaiming from the wrong evidence. Input tax claimed from a broker invoice rather than the C79 or PVA statement. The amounts rarely agree, and the broker invoice is not the right evidence for import VAT recovery.
• Wrong EORI or VAT number on the declaration. The import lands on someone else's statement, or never appears on yours. Group structures and carrier-completed declarations are frequent causes.
• VAT calculated on an incorrect customs value. Classification and valuation errors feed straight into the import VAT figure. If the customs value is wrong, the VAT is wrong too.
• Missed statements. Because PVA statements are only available for six months, gaps appear in the records and estimated figures are never trued up against the official numbers.

None of these errors are visible from the VAT return alone. They only surface when declaration-level data is laid alongside the statements and the return, which is exactly what TRE analysis does.

How to reconcile TRE data against your VAT records

A repeatable import VAT reconciliation has six steps:

1. Pull your TRE for the period. Request the extract through Government Gateway, or use a platform that retrieves it automatically, and confirm it covers every EORI in the group.
2. Split lines by payment method. Separate postponed lines from lines where VAT was paid at the border or by deferment. The method of payment codes in the TRE identify each.
3. Match postponed lines to PVA statements. Every postponed line should appear on a monthly statement. Investigate lines with no statement entry, and statement entries with no matching TRE line.
4. Match border-paid lines to C79 certificates. Confirm the certificate totals agree with the VAT amounts in the extract for the same month.
5. Trace totals to Boxes 1, 4 and 7. Statement totals should reconcile to Box 1, recovery to Box 4 within the normal input tax rules, and import values to Box 7.
6. Correct the differences. Adjust the next return or use HMRC's error correction process, and record the root cause so the same mismatch does not recur.

The specific mismatches this routine surfaces, and how to resolve each one, are covered in more depth in our guide to fixing import VAT and PVA reconciliation errors with TRE data.

What happens if import VAT errors go uncorrected?

Customs declarations remain open to HMRC review for three years after clearance, and import VAT sits squarely within the scope of a post-clearance audit. Overclaimed input tax invites assessments, interest and penalties. Underclaimed VAT is your own cash left with HMRC until you correct the position.

The bigger issue is that import VAT errors are rarely one-offs. A broker defaulting to the wrong payment method, or a declaration template carrying the wrong VAT registration, repeats the same error on every shipment. A mistake worth a few pounds per line becomes material once it is multiplied across a year of declarations.

Automating import VAT checks across every declaration line

Checking thousands of declaration lines against statements and returns by hand is possible for one quarter and unsustainable as a routine. BorderAudit treats this as a platform problem: automated HMRC data retrieval pulls your TRE through Government Gateway before the download window closes, then reconciliation checks run across every line rather than a sample.

Postponed and border-paid lines are separated automatically, VAT amounts are recomputed from the declared customs values, and mismatches against your statements are flagged for review. The same declaration data feeds the duty-side checks too, so the classification and valuation errors that distort import VAT are caught at the source. You can start on the free tier and see your import VAT position across your declaration history before deciding whether ongoing monitoring is worth paying for.

Next steps for UK importers

Three things to take away:

• TRE data is the declaration-level source of truth for import VAT, covering both postponed and border-paid lines in one extract.
• Reconcile monthly: PVA statements are only available for six months, and estimated figures harden into errors if they are never checked.
• Automate once volumes make manual matching impractical, and fix root causes in broker instructions and templates rather than patching symptoms.

If you want to know what a line-level check would find in your own declarations, check your eligibility for a free BorderAudit audit. It takes a couple of minutes and covers import VAT alongside duty, classification and origin.