An EU Long Term Supplier's Declaration can support preferential origin for later EU exports, but only within the correct legal and commercial setting. U.S. suppliers handling Mexican-made goods should not treat the LTSD as a universal certificate. They should map the transaction to the applicable trade agreement and proof-of-origin rules.
What an EU Long-Term Supplier's Declaration Does
Supporting Preferential Origin Within the EU
A Long-Term Supplier's Declaration, commonly abbreviated as LTSD, is generally used when a supplier provides goods to a customer in the European Union over an extended period. It communicates whether those goods qualify as originating under specified preferential trade arrangements.
The customer may use that information when manufacturing, reselling, or exporting products from the EU. For example, an EU exporter might rely on supplier declarations when determining whether a finished product satisfies the origin rules under an EU free trade agreement.
The LTSD framework is established through Commission Implementing Regulation (EU) 2015/2447, particularly Articles 61-66 and Annexes 22-15 through 22-18. Its structure and legal function place it within the EU preferential origin system. In practice, LTSDs are generally issued by EU-established suppliers to customers within the EU.
An LTSD Is Not an Import Origin Document
An LTSD is not normally the proof of origin presented to EU customs for goods arriving from a non-EU country. Import preference must instead be supported by the specific proof authorized under the applicable agreement. Depending on the agreement, that could be a movement certificate, statement on origin, invoice declaration, or another prescribed document.
This distinction is critical. A supplier declaration supports an EU operator's origin analysis. It does not replace the formal proof required for an import preference claim. Likewise, a generic certificate of origin may document where goods were produced, but it does not necessarily establish preferential origin or authorize a reduced duty rate.
Why Non-EU Suppliers Generally Should Not Sign an LTSD
Territorial Scope and Legal Purpose
EU customs legislation generally applies throughout the customs territory of the Union. The United States and Mexico are outside that territory. Although the LTSD provisions may not contain a single sentence stating that every declarant must be established in the EU, the declaration's function, prescribed wording, and relationship to EU preferential origin procedures generally limit its use to EU supply chains.
The framework also recognizes certain connected preferential origin arrangements, including qualifying movements within the Pan-Euro-Mediterranean system. That does not make the EU LTSD form available to suppliers in any country. A U.S. business cannot create authority to issue an EU supplier declaration merely because an EU customer requests one.
Signing a declaration without a valid legal basis can create material compliance exposure. The EU customer may rely on it to issue an origin statement, obtain preference for its customer, or support an origin determination during verification. If the declaration is not valid, multiple transactions and downstream preference claims may be affected.
Mexican-Made Goods Supplied Through the United States
A U.S. supplier selling Mexican-made goods to an EU customer should generally provide the origin evidence authorized under the relevant EU-Mexico trade framework, if the goods qualify. The supplier must also consider whether routing through the United States satisfies applicable non-alteration, transport, and documentary requirements.
Mexican manufacture alone does not guarantee preferential Mexican origin. The product must satisfy the agreement's product-specific rule, and the required proof must be issued or made by an authorized party. If the shipment loses eligibility because of processing, storage, routing, or documentation issues, an LTSD cannot restore that eligibility.
How to Respond to an EU Customer's LTSD Request
Identify the Customer's Intended Use
The first step is to determine why the EU customer wants the declaration. Some procurement systems request an LTSD from every supplier without distinguishing between EU and non-EU vendors. In other cases, the customer may be attempting to establish the originating status of components used in products exported under an EU trade agreement.
The response should ask which preferential arrangement, destination country, product, and tariff classification are involved. It should also confirm whether the customer needs evidence for an import claim, an EU-origin calculation, or a downstream export. These are separate compliance questions that require different documentation.
Validate Origin Before Providing Alternatives
The supplier should review the country of production, tariff classification, bill of materials, processing history, and applicable product-specific origin rule. For goods made in Mexico and distributed through the United States, the review should also cover custody, repacking, storage, and any operations performed outside Mexico.
If the goods qualify, the supplier should identify the precise proof of origin permitted by the applicable agreement. A commercial certificate of origin should not be presented as equivalent to a preferential origin statement unless the governing rules expressly allow it.
Give a Clear, Controlled Response
A non-EU supplier can explain that it is not positioned to execute an EU LTSD and can offer the appropriate import origin documentation instead. The response should avoid making an unsupported promise that the EU customer can automatically issue its own LTSD based on that documentation.
The EU customer remains responsible for determining whether it may issue a supplier declaration or make a later preferential origin statement. Records exchanged between the parties should clearly identify the products, covered period, origin criterion, trade arrangement, and limitations of the information supplied.
Building Strong LTSD and Origin Controls
Separate Import Proof From Supplier Declarations
Companies should maintain separate procedures for import preference documents and EU supplier declarations. The import procedure should verify the agreement, origin rule, exporter eligibility, proof format, and transport conditions. The LTSD procedure should establish who may issue a declaration, which products it covers, how origin was substantiated, and when it must be updated or withdrawn.
Long-term declarations should not be treated as indefinite certifications. Changes in sourcing, production, tariff classification, or applicable origin rules can invalidate prior conclusions. Suppliers should typically conduct periodic reviews and notify affected customers when originating status changes.
Procurement and enterprise resource planning systems can create risk when they request identical documents from every supplier. Vendor location, shipment origin, manufacturing origin, and intended preferential arrangement should drive the document request. Automated workflows should distinguish EU suppliers from non-EU suppliers and distinguish preferential origin from non-preferential country of origin.
Prepare for Digital Supplier Declaration Data
EU preferential origin procedures are moving toward standardized electronic data exchange. Commission Implementing Regulation (EU) 2026/1183 introduces codified data elements and revised supplier declaration processes, with key changes scheduled to apply in stages beginning in 2027 and 2028. Broader EU customs modernization will continue through the following years.
These changes do not convert the LTSD into a document for U.S. or Mexican suppliers. They reinforce the need for structured product, origin, supplier, and agreement data. Trade compliance teams should begin aligning declaration records with consistent data fields while retaining controls for legacy forms during the transition.
- Recent EU developments on Long Term Supplier's Declarations (LTSDs) focus on upcoming digitalization, form updates for new trade partners, and the broader customs reform. LTSDs remain an intra-EU tool issued by EU-established suppliers under CIR (EU) 2015/2447 (as amended).*
- Commission Implementing Regulation (EU) 2026/1183 of 2 June 2026 amends UCC Implementing Regulation (EU) 2015/2447 on preferential origin procedures. It replaces Articles 61-65 with standardized, codified data elements for supplier declarations (new Annex 22-15) to support electronic exchange between suppliers and exporters. The new format and related rules apply from 23 June 2028 (some origin provisions from 23 December 2027). This prepares for full digital data exchange starting around 2030.
- Standard forms for supplier declarations and LTSDs (for goods with preferential origin) were updated in July 2026 to add new FTA partners such as Kenya, MERCOSUR (applicable from 1 May 2026), and Wallis and Futuna. Previous form versions remain valid. IHK guidance from 21 October 2026 confirms this.
- The new Union Customs Code, Regulation (EU) 2026/2108, was published on 19 September 2026 and entered into force on 20 September 2026 (general application from 21 September 2027, with phased rollout to 2034). It introduces an EU Customs Data Hub and other reforms but does not immediately alter LTSD rules; implementing acts will address origin procedures later.
- Guidance from WKO, IHK, and others (updated through October 2026) reconfirms LTSDs apply only to EU-established suppliers for intra-EU movements to support preferential origin (e.g., for further export under FTAs). Non-EU suppliers (such as US or Mexican) must instead use the origin proofs specified in the relevant trade agreement (EUR.1, statement on origin, etc.). No regulatory change supports LTSD use by non-EU suppliers. Revised Pan-Euro-Med rules fully apply from 1 January 2026, with transitional notes on older LTSDs.
- No notable practitioner discussions on X in the past 30 days addressed LTSD scope for non-EU suppliers.
Frequently Asked Questions
Can a U.S. Supplier Sign an EU LTSD?
Generally, no. An EU LTSD operates within the EU preferential origin framework and is typically issued by an EU-established supplier to an EU customer. A U.S. supplier should provide the proof or supporting origin information authorized under the applicable trade agreement instead of signing an EU form without a legal basis.
Is a Certificate of Origin Enough for Preferential Duty?
Not necessarily. A standard certificate of origin may identify the country where goods were produced, but preferential duty treatment requires the proof specified by the relevant trade agreement. The importer must also confirm that the goods satisfy the applicable origin rule and any transport or non-alteration conditions.
Can an EU Customer Create an LTSD From a Mexican Origin Certificate?
Not automatically. The EU customer must determine whether it is legally entitled to issue a supplier declaration and whether its evidence supports the required preferential origin conclusion. A Mexican proof of origin may support an import claim, but it does not by itself authorize every later EU origin claim.
Does Shipping Mexican Goods Through the United States Affect Preference?
It can. Storage, repacking, processing, customs control, and shipment documentation may affect compliance with the applicable transport or non-alteration rule. The parties should review the specific agreement before claiming EU preferential treatment for goods routed through the United States.
What Should a Non-EU Supplier Provide Instead of an LTSD?
The supplier should provide the exact proof permitted under the governing agreement, if the goods qualify. It may also provide supporting production, classification, and origin information under appropriate confidentiality controls. The documentation should clearly state its purpose and should not be labeled as an EU LTSD.
Are LTSD Rules Changing With EU Customs Modernization?
Yes, the procedures and data formats are being modernized, with phased changes expected from 2027 onward. These updates emphasize standardized electronic data and stronger origin records. They do not generally expand LTSD eligibility to suppliers established in the United States or Mexico.
How Stable Software Can Help
Strengthening Broker-Led Trade Compliance
Origin documentation affects classification, duty calculations, entry review, and downstream compliance decisions. Customs brokers need disciplined workflows that distinguish supporting commercial records from documents that legally authorize preferential treatment.
Stable Software develops trade compliance software for customs brokers, including tools that brokers can provide to importer clients under their own filer code. Its flat-license model does not take a percentage of recovered refunds. Brokers evaluating technology for importer-facing compliance services can learn more about Stable Software's approach on the customs broker solutions page.
Resources
| Type | Resource |
|---|---|
| Source | Primary source |



