EU customs declaration audit checklist

Last updated 27 September 2026

A useful customs audit is not a search for refunds alone. It checks whether each declaration can be reproduced from the product, trade lane, valuation evidence and rules that applied on the declaration date. Possible overpayments, underpayments and evidence gaps should remain separate throughout the review.

A worked evidence-gap example

Illustrative example, not a customer case: an invoice includes a product code, but the review file has no specification showing the material and intended use. Record the finding as an evidence gap, assign the request for a specification to the purchasing owner, and set a due date. Leave the financial effect unconfirmed. A missing document alone does not establish an incorrect code or a refund.

1. Define the review population

• Importing legal entities and EORI numbers.
• Member States of import and customs offices involved.
• Declaration dates, procedures and broker relationships.
• Product families, origins and suppliers.
• Duty, import VAT and trade-measure amounts paid.

Start with a controlled period and a complete population of entries. A small representative review is easier to validate than a large file whose declarations cannot be tied back to source documents.

2. Collect the evidence once

• Customs entry export or MRN-level declaration data.
• Commercial invoices, credit notes and packing lists.
• Product specifications, catalogues and classification records.
• Proof of origin, supplier declarations and preference records.
• Freight, insurance, assists, royalties and other valuation support.
• Broker instructions, licences, certificates and authority decisions.
• Duty-paid and import-VAT accounting evidence.

3. Run the field-by-field checks

1. Parties and representation: importer, declarant, representative status, EORI and responsibility should agree with the mandate and commercial transaction.
2. Procedure: requested and previous procedures, additional procedure codes and relief conditions should match what happened to the goods.
3. Classification: the goods description, materials, function and condition should support the declared CN or TARIC code. Use the HS, CN and TARIC comparison to distinguish the code levels. The European Commission notes that classification determines both duty and non-tariff measures.
4. Description and quantities: commercial description, net mass, gross mass, package count and supplementary units should be internally consistent.
5. Origin: non-preferential origin, preferential origin and country of dispatch should not be treated as the same data point.
6. Preference: the preference code, agreement, qualifying rule and proof held on the declaration date should form a complete evidence chain.
7. Customs value: invoice amount, currency, Incoterm, freight, insurance, assists, royalties, additions and permitted deductions should reproduce the declared value.
8. Measures and documents: anti-dumping, countervailing, safeguard, quota, suspension, licence and certificate requirements should be tested for the product, origin and date.
9. Duty calculation: tax base, rate, preference, additional duties, units and exchange rates should recalculate to the amount assessed.
10. Accounting tie-out: assessed duty and import VAT should agree with deferment statements, broker invoices and finance records without silently netting credits against liabilities.

For steel, use the melt-and-pour evidence update to check the document trail. For goods within CBAM scope, the CBAM verification briefing explains why installation and emissions records need their own evidence chain. Read each publication with its stated date and sources.

4. Look for portfolio patterns

A declaration can look plausible in isolation and still be an outlier. Compare the same product across brokers, suppliers, origins and months. Prioritise changes in commodity code, origin, value per unit, preference use, duty rate and document references. Repeated manual overrides and one-off zero-duty results deserve evidence, not assumptions.

5. Classify every outcome

• Supported: the declaration reproduces from the evidence and rule in force.
• Evidence gap: the position may be correct, but the file does not yet support it.
• Possible repayment: the amount paid appears higher than the amount legally payable and needs professional validation.
• Possible underpayment: the review indicates a liability or a declaration that may need correction.
• Process improvement: no historic amount is proven, but instructions, master data or evidence controls should change.

Official sources

• European Commission: tariff classification of goods
• European Commission: EU Binding Tariff Information
• European Commission: Binding Origin Information
• European Commission: Union Customs Code guidance documents
• EUR-Lex: Union Customs Code

How The Declarant fits

The Declarant can screen declaration data, group repeated patterns, expose inconsistent fields and quantify possible variances for human review. It does not decide the legal position or submit a correction.

Check one declaration free, read the duty recovery guide or return to all customs guides.