Will Claiming Overpaid Duty Trigger an HMRC Audit?

The instinct most importers never say out loud

In over four decades of customs compliance practice, one conversation comes up more than almost any other. A business has been overpaying import duty. The evidence is clear. The recovery mechanism is straightforward. And then someone in the room says it.

"We don't really want to draw attention to ourselves."

It is the most understandable and most costly instinct in UK customs compliance. The logic runs roughly like this: if we submit a C285 amendment and claim back overpaid duty, HMRC will look at our declaration history. If they look at our declaration history, they might find problems we haven't found yet. Better to absorb the loss and stay invisible.

The "don't poke the bear" mentality is real, it is widespread, and it is built on a misunderstanding of how HMRC compliance activity actually works. This post is about why that instinct costs businesses far more than the duty they are trying to protect — and why auditing your declarations is closer to protection than exposure.

The logic of not claiming, and where it breaks down

The fear is not irrational. HMRC does conduct post-clearance audits and compliance checks. Businesses are right to take that seriously. The question is whether filing a legitimate duty recovery claim is what triggers that scrutiny.

It is not.

HMRC's compliance activity runs on risk profiling. The methodology looks at declaration patterns, commodity code consistency, valuation anomalies, origin documentation gaps, and statistical outliers across your import history — and compares them against sector benchmarks and known risk indicators. A business that files a C285 for an overpaid duty claim has submitted a document that, by definition, identifies a specific, corrected error. That is not a risk signal. That is transparency.

The businesses that attract HMRC attention are the ones whose declaration patterns suggest systemic errors that no one appears to be catching or correcting. The importer who never audits, never corrects, and never files a recovery claim is not invisible to HMRC. They are simply unexamined — until they are.

What "not poking the bear" actually costs

Set aside the audit risk question for a moment and look at what the passive approach costs in straightforward financial terms.

HMRC reports that UK businesses overpay approximately £2 billion in import duty every year. That figure is not dominated by large multinationals with dedicated compliance teams. It reflects the accumulated effect of commodity classification errors, valuation mistakes, and procedure code issues across thousands of SME importers who import regularly, trust their brokers to file correctly, and never look at the declarations afterwards.

Every year an overpayment goes unaddressed is another year of duty paid at the wrong rate. It is also another year of statutory interest accruing on the accumulated overpayment — an entitlement that exists in law, must be claimed separately from the principal recovery, and that most businesses who do eventually claim their duty back never pursue at all.

The cost of the "don't poke the bear" approach is not just the overpaid duty. It is the compounding of that overpayment year on year, plus the interest, plus the missed opportunity to correct the underlying error before HMRC finds it on their own terms rather than yours.

An importer overpaying £20,000 per year on a misclassified commodity line loses £80,000 over four years in principal overpayment alone — before statutory interest, and before considering what a compliance check finding looks like compared with a voluntary self-correction.

The case for auditing your declarations before HMRC does

If errors exist in your declaration history — and HMRC's own published compliance data suggests a significant proportion of importers have them — those errors exist whether or not you look for them. HMRC can find them on their risk-profiling cycle. You can find them first.

Finding them first gives you something HMRC's compliance check cannot give you: choice. A voluntary disclosure made proactively, before any HMRC-initiated review, is treated materially differently from a disclosure made in response to a compliance check. The duty owed is the same. The penalty treatment is not. HMRC guidance is explicit that unprompted voluntary disclosures attract significantly reduced penalties compared with prompted disclosures made during a check.

The business that audits its declarations, identifies its errors, voluntarily corrects where needed, and files legitimate recovery claims where they exist is demonstrating exactly the kind of internal oversight that HMRC's risk model rewards. Businesses with a history of proactive compliance activity and voluntary correction are less likely to face a compliance check, not more.

The voluntary disclosure advantage in plain terms

A voluntary prior disclosure to HMRC is a formal notification that you have identified an error in previously submitted declarations and are correcting it. It is not an admission of wrongdoing. It is not an invitation for a broader audit. It is a recognised, formal process that HMRC has designed specifically to encourage self-correction.

Under HMRC's penalty framework, a business that makes an unprompted voluntary disclosure before any compliance contact from HMRC faces a potential penalty of zero to thirty per cent of the duty involved, depending on behaviour classification. The same error discovered by HMRC during a compliance check, with no prior disclosure, can attract penalties of thirty to one hundred per cent.

That differential exists precisely because HMRC wants businesses to self-correct. The regulatory design rewards the businesses that look at their own declarations rather than waiting to be found.

Three questions worth sitting with

When was the last time anyone audited your import declarations?

Not reviewed the shipping documents. Not checked the invoices. Actually cross-referenced your CDS declaration data against commodity codes, procedure codes, and applicable duty rates for a representative sample of entries. If the answer is never, or not recently, your compliance position is unknown to you. HMRC's risk model is working on it regardless.

Do you know whether you have been overpaying duty?

Most importers who discover they have been overpaying duty are surprised by the amount. The errors are usually not dramatic misclassifications. They are small systematic differences — a commodity code applied consistently but one classification step away from the correct code, generating a marginally higher duty rate on every single entry for years. Those differences accumulate. HMRC reports £2 billion a year in overpayments across the UK importer base. That figure exists because the errors are common, not exceptional.

If HMRC conducted a compliance check on your last three years of declarations tomorrow, what would they find?

That is not a rhetorical question. It is the most useful compliance planning question an importer can ask themselves. If the honest answer is "I don't know," then you are in the same position as the businesses the "don't poke the bear" logic was supposed to protect — exposed, but without the information to do anything about it.

How MyCustomsInfo® changes this calculation

The "don't poke the bear" mentality persists in part because the alternative — knowing your compliance position — has historically required significant time and resource. A thorough declaration audit of several years of import history, manually, is a substantial undertaking. Most businesses do not have the internal resource to do it.

MyCustomsInfo® changes that calculation. The platform runs a post-clearance audit of your full CDS declaration history automatically. It identifies overpayments, flags classification and procedure code issues, calculates the statutory interest entitlement alongside the principal recovery, and gives you a clear compliance picture within 14 days of each month end.

The businesses that use it are not taking on more risk. They are taking on less. They know what their declarations contain. They can correct errors before HMRC finds them. They can recover what they are owed. And they hold the strongest possible position if HMRC ever does come knocking.

Not poking the bear is not a compliance strategy. Knowing what the bear already knows is.

Book a 20-minute compliance review with the MyCustomsInfo® team. We will walk through what a declaration audit covers, what it typically finds for businesses in your sector, and what your recovery and disclosure position looks like. No obligation. No HMRC involvement. Just your data, reviewed on your terms.