What is a supplier's declaration?

Q: What is a supplier's declaration?

A supplier's declaration is a supplier's statement on the customs origin of the goods delivered - in particular whether they have preferential origin under the EU's free trade agreements. It is the basis on which exporters issue proofs of preference such as the EUR.1 or origin declarations.

Q: What is a long-term supplier's declaration (LTSD)?

The LTSD covers recurring deliveries of goods of the same kind over a period of up to two years, instead of declaring each consignment individually. It must be kept current: if the origin changes, the supplier must revoke or correct the declaration.

Q: What is the legal basis of the supplier's declaration?

The Union Customs Code and its Implementing Regulation (EU) 2015/2447, which govern form, contents and periods of the supplier's declaration - including the long-term variant.

Q: What happens if a supplier's declaration is incorrect?

If the declared preferential origin turns out to be wrong, proofs of preference can become invalid - the customer faces post-clearance recovery of duties and interest, and in repeat cases the loss of authorisations. That is why supplier's declarations belong systematically captured, verified and monitored for currency.

Q: Can AI read supplier's declarations automatically?

Yes. Supplier's declarations come in many formats - as a form, a letter paragraph or an invoice note. AI-based extraction captures issuer, goods, HS codes, origin statements and validity periods, matches them with article master data and flags expiring long-term declarations.

Definition, legal basis and practice of the supplier's declaration - from preferential origin to the long-term declaration and automated capture

Published 1 September 2026

The supplier’s declaration is a supplier’s statement on the customs origin of the goods it delivers - above all on whether they hold preferential origin under the European Union’s free trade agreements. It is the connecting link of the preference chain: on its basis, the exporter issues proofs of preference such as the EUR.1 movement certificate or origin declarations, which enable reduced or zero duties for the customer in the country of destination.

Key facts

The legal basis is the Union Customs Code and Implementing Regulation (EU) 2015/2447.

The long-term supplier’s declaration (LTSD) covers recurring deliveries for up to two years - but must be actively kept current.

Incorrect declarations endanger the preference at the customer: post-clearance duties and interest are the real follow-up costs.

Formats are arbitrary (form, letter, invoice note) - which makes systematic capture laborious without AI support.

The shared data core with EUR.1 and certificates of origin is the customs tariff number (HS code).

Single and long-term supplier’s declarations

Single supplier’s declaration: applies to one specific consignment; frequently as a note on invoice or delivery note.
Long-term supplier’s declaration (LTSD): covers recurring deliveries of goods of the same kind over up to two years. It reduces paperwork considerably but shifts the duty towards monitoring: if an LTSD expires or the origin changes (say, through a change of upstream supplier), affected proofs of preference must be stopped - otherwise the exporter declares an origin it can no longer substantiate.

In practice, an exporting company manages hundreds to thousands of supplier’s declarations from different issuers, in different formats and with different validity periods - an inventory-management task that quickly outgrows Excel.

Why capture is error-prone

Three structural reasons:

Format variety. There are prescribed wordings but no mandatory form - declarations arrive as standalone documents, letter paragraphs or notes, scanned or digital.
Data linkage. Every declaration must be assigned to the right articles and HS codes; bulk lists across many article numbers are common and must reach master data position by position.
The time dimension. LTSD validity periods expire asynchronously; without monitoring, gaps emerge that only surface in a customs audit - with post-clearance recovery as the price tag.

AI-based capture and verification

Template-free extraction reads issuer, goods descriptions, HS codes, countries of origin and validity periods from arbitrary formats, matches them with article master data and keeps the inventory current: expiring long-term declarations are flagged, missing ones requested, contradictions between declaration, EUR.1 and invoice marked - every statement anchored to its source location in the document (visual grounding). How this works together with certificates of origin and the EUR.1 is shown in the post Reading supplier’s declarations with AI.

Frequently asked questions (FAQ)

What is a supplier’s declaration?

A supplier’s statement on the customs origin of delivered goods - the basis on which exporters issue proofs of preference such as the EUR.1.

What is a long-term supplier’s declaration (LTSD)?

A declaration for recurring deliveries of goods of the same kind over up to two years. It saves individual declarations but must be actively monitored and corrected when origin changes.

What is the legal basis of the supplier’s declaration?

The Union Customs Code and Implementing Regulation (EU) 2015/2447, which govern form, contents and periods.

What happens if a supplier’s declaration is incorrect?

Proofs of preference can become invalid; the customer faces post-clearance duties and interest. That is why declarations belong systematically captured, assigned and monitored.

Can AI read supplier’s declarations automatically?

Yes - issuer, HS codes, origin and validity are extracted from arbitrary formats, matched with master data, and expiring LTSDs are flagged.

Further reading: The solution page customs document automation shows capture, matching and generation of origin and customs documents in context - EU-hosted, live in under 4 weeks.

Request Demo Back to Glossary