Customs refund time limit: three years that end quietly

A demurrage invoice arrives by post and demands a response. An overpaid customs duty arrives nowhere. It simply sits in a declaration that no one will open again, and one day it stops existing as a right.

This article is about how the deadline is actually counted, and why in practice it is missed almost every time.

Four grounds

The Union Customs Code provides for the repayment or remission of import or export duty on four grounds:

Overpaid amounts. The most common case. This covers a wrong tariff code, a late-arriving proof of preferential origin, or costs included in the customs value without justification.

Goods that are defective or do not comply with the terms of the contract. The importer rejects the goods because they are damaged or don't match what was ordered.

An error by the competent authorities. Customs made a mistake, and the debtor could not reasonably have detected it. This last condition is in practice the hardest to meet.

The principle of equity. The broadest and least frequently applied ground.

A separate route also exists — invalidation of the declaration. If customs invalidates a declaration, the customs debt simply ceases to exist, and any amount paid is refunded.

From when the deadline is counted

This is where the most common mistake is made.

The deadline is counted not from the goods' arrival, not from when the declaration was filed, and not from the day of payment. It's counted from the day of notification of the customs debt.

In practice these dates often coincide or nearly coincide — but not always. If the debt is established later, for instance following an inspection, the deadline starts from that later moment. So before deciding whether you still have time, first find the exact notification date, not the declaration date.

The general deadline for overpaid amounts, an authority's error, and the equity ground is three years. For defective goods the deadline is shorter.

Worth double-checking: the exact deadlines and how they're counted differ by ground, and in some cases the deadline can be extended if the person proves the application wasn't filed in time due to unforeseeable circumstances or force majeure. In any specific case, this should be confirmed by your customs broker.

It's also worth knowing about the amount threshold: customs repays or remits amounts from €10 upward. Smaller amounts are formally repaid only if specifically requested.

Why three years means zero in practice

A long deadline looks like a favour. In reality it works the other way.

There's no pressure. Anything with a deadline three years out doesn't make this week's list. Or next week's. And so on, until the deadline stops mattering.

There's no responsible person. A demurrage invoice has a recipient — someone opens it and has to decide. An overpaid duty has no recipient. It's no one's task, so it becomes no one's priority.

People change faster than the deadline. Over three years, the logistics manager changes, the broker changes, sometimes even the accounting system changes. The knowledge that "something was off with that Vietnam shipment" walks out the door with the person.

The amounts are only visible when added up. A single case looks too small. Forty cases over three years look entirely different. But no one adds them up, because that would require reviewing the whole archive — which is, again, a task with no deadline.

How the archive erodes

A practical consequence worth understanding before planning a review: your stock of recoverable amounts shrinks every month.

Declarations for which notification of the debt was received thirty-five months ago have one month of life left. Those at thirty-seven months already have none. Every month, one month's worth of import volume drops out of the window.

That's why any retrospective review starts with the oldest still-valid month, not the most recent one, even though intuition says otherwise. The newest declarations will wait another two years. The oldest won't wait even a week.

What to do in practice

First — set the boundary. Find the date three years back and check how many declarations fall into the next two or three months from that boundary. That's your most urgent segment.

Second — review four things. Does the tariff code match the actual description of the goods. Was a preferential rate available, and did the proof of origin arrive after the declaration. Were only justified costs included in the customs value. Does the same MRN repeat.

Third — hand it to your broker with an explanation. Not a list, but each case with documents and a description of the circumstances. Customs assesses the explanation, not just the set of documents.

Fourth — stop the flow. A retrospective review is a one-off. If you don't change the process, in a year you'll have a new archive just like this one.

Where Demurrit fits in

The Customs module works on both sides. In the ongoing flow, it flags declarations with structural discrepancies — a missing proof of preferential origin, a duplicate MRN — before they become history. In the archive, it applies the same check to three years of data and ranks the results by how much time is left before the deadline.

The module shows the tariff difference based on your own declaration data, but never predicts a refundable amount and never files an application with customs. The amount is calculated and the application prepared by your customs broker — they see documents the system doesn't, and they take on professional responsibility for the assessment.

This division isn't caution for its own sake. An unfounded request for a customs refund carries liability in some Member States, and that liability rests with the person filing the application. Software that "guaranteed" a result would shift a risk to the client that they can't see.