EU Country-of-Origin Reconciliation From Supplier Invoices

Country-of-origin reconciliation from supplier invoices is the importer's continuous task of capturing line-level country of origin from each inbound supplier invoice and assembling it into a portfolio dataset that feeds four downstream uses: Intrastat statistical reporting, customs entry filings, preferential-origin (FTA) claims, and audit defence when an authority challenges a duty rate. Four fields drive the work: the per-line country of origin, the verbatim origin-statement text printed on the invoice, the supplier's Registered Exporter (REX) number where applicable, and the HS chapter that governs the rule of origin. Under the EU REX system, statements on origin attached to shipments under €6,000 in value can be made out without REX registration; above that threshold the supplier must hold a REX number for the statement to be valid.

This is an importer-side problem, and it sits in a different place from the export-side commercial-invoice question that dominates the search results for this topic. The input is a backlog of incoming supplier PDFs, often from a mix of EU and non-EU manufacturers. The output is a portfolio spreadsheet keyed at the supplier-invoice-line level — not a single declaration, not a one-off filing, but a continuous dataset that has to stay current as new invoices arrive every week.

What makes the reconciliation worth doing is that the same field on the same invoice serves four different obligations on four different cadences. Intrastat is monthly statistical reporting on intra-EU goods movements. Customs entry is filed per shipment at the border. Preferential-rate claims under EU FTAs are made at entry but evidenced in continuous documentation that has to survive a verification request months or years later. Audit defence happens on demand, when a customs authority challenges a duty rate and asks the importer to substantiate the origin claim against the original invoice and supporting documents. One dataset, four uses, four different patterns of access.

The rest of the article walks the four extraction targets, then each downstream use in turn, then closes on the spreadsheet shape and how to populate it from a stack of inbound PDFs without manual entry consuming the team.

The Four Fields You Need From Each Supplier Invoice

Reconciliation begins at the document. Every supplier invoice that lands in the AP inbox carries — or should carry — four pieces of origin information, each in a different part of the page, each required for a different downstream use. Capturing all four at the line level is what lets the same dataset answer Intrastat, customs, FTA, and audit questions later.

Per-line country-of-origin marking. This is the country code or country name printed against each individual goods line, often in a column adjacent to the description and HS code. On a clean supplier invoice the marking is a two-letter ISO country code (CN, VN, BD, TR) sitting next to a description and quantity. On a multi-line invoice covering goods manufactured in different countries, this varies line by line — apparel orders from a single supplier routinely mix garments cut in one country and finished in another, and each line has to record the country attributed to that specific item. The reconciliation captures origin at the line level, not the invoice level. Recording one country for a fifteen-line invoice, when the lines actually came from three, is the most common data-quality failure the article is trying to prevent.

The verbatim origin-statement text. Where the supplier is asserting preferential origin under an EU FTA, an origin statement appears somewhere on the document — usually as a footer paragraph below the totals, sometimes on a continuation page, occasionally on a separate cover sheet attached to the invoice. The wording is not free-form. Under the EU Registered Exporter system, Annex 22-07 of the Union Customs Code Implementing Regulation (EU) 2015/2447 sets the prescribed text the supplier must use when making out a statement on origin: a single paragraph naming the country of preferential origin and, where relevant, identifying the products and the supplier's REX number. The reconciliation captures that paragraph verbatim — exact characters, no paraphrase, no summary. When a customs authority later asks to see the origin proof, the question is whether the wording on file matches the prescribed form. A summary of the gist is not evidence.

The supplier's REX number authenticating the statement. Where the statement on origin appears, it normally cites the supplier's REX registration number — the link between the supplier's claim on the invoice and the European Commission's REX database, which any customs authority can query to confirm the supplier's registration is current. The number has a fixed shape (country code plus alphanumeric identifier) and almost always appears inside or immediately adjacent to the statement-on-origin paragraph. Above the €6,000 shipment threshold, a statement on origin without a valid REX number is not valid for preferential treatment, so capturing the number is a different kind of mandatory than capturing the statement text — both have to be present, and they have to agree.

The HS chapter that governs the origin rule. The supplier's declared HS code on each line — at minimum the four-digit heading, ideally the full eight-digit Combined Nomenclature subheading or the ten-digit TARIC code where the supplier provides it — determines which product-specific rule of origin in the relevant FTA applies. A garment of woven cotton fabric falling under HS 6203 carries a different origin test from a knitted shirt under 6105, and both differ from a leather handbag under 4202. The chapter is what ties a given line to the correct rule, so it belongs on the input row in its own column rather than buried inside a free-text description. Extracting the HS chapter and country of origin from the supplier invoice as paired fields, line by line, is what makes the rule lookup possible later.

The four fields belong on every line, not collapsed into a single per-invoice "origin field." Row granularity is the supplier-invoice line; an invoice with twelve goods lines produces twelve rows in the dataset, each carrying its own country, its own HS code, and where applicable its own pointer back to the same statement-on-origin text and REX number that govern the whole invoice.

The practical reality is that not every inbound invoice will carry all four cleanly. Origin is often missing on intra-EU supplier invoices that do not need it — a French wholesaler invoicing into the Netherlands has no commercial reason to print country of origin against goods of EU origin. The origin-statement text only appears when the supplier is asserting preferential origin; for non-preferential entries it is absent by design. The REX number is missing when the supplier has not registered, when the shipment falls below the €6,000 threshold, or when the supplier is operating under approved-exporter status with a different reference instead. The HS code is sometimes missing, sometimes given at four-digit heading level only, sometimes wrong. Reconciliation has to record absence as a value — null, not skipped — because the absence itself is information that drives a follow-up query to the supplier.

---

Driver 1 — Intrastat Statistical Declarations

Intrastat is the EU's monthly statistical declaration on intra-EU goods movements, separated into dispatches (goods leaving the member state to another EU member state) and arrivals (goods entering from another EU member state). The country-of-origin field is one of the modernised statistical variables and is captured at the commodity-line level — the same granularity the reconciliation dataset already holds.

The 2022 modernisation under Regulation (EU) 2019/2152 on European business statistics is where competitor pages routinely overstate the position. The regulation made country of origin and the partner VAT identification number mandatory across EU member states for dispatches. On arrivals, adoption varied by member state. Many member states do require country of origin on the arrivals declaration as a national addition, but it is not uniformly mandatory across the bloc the way the dispatch position is. A blanket statement that origin became mandatory on arrivals across the EU in 2022 is wrong, and an importer running compliance off it will either over-collect for member states that do not need it or — more dangerously — under-deliver where the national rule does require it. Check the position with the national statistical authority of each member state the importer files in.

For an EU importer, the practical implication is that the same country of origin captured from the supplier invoice serves both ends of the picture. When goods are first imported into the EU, the origin field captured from the supplier invoice may feed an arrivals declaration if the importer's member state requires it. When the same goods are subsequently dispatched onward to another EU member state, the origin field travels with them onto the dispatch declaration. The portfolio dataset is built once at the point the supplier invoice is processed and queried twice on different cadences.

Intrastat thresholds and reporting frequency differ by member state, and many member states distinguish a simplified declaration below a higher threshold from a full statistical declaration above it. The country-of-origin field tends to be required at the higher threshold rather than the lower one, but again the rule lives at member-state level. The data is captured continuously regardless — the threshold question affects when the importer has to file, not when the reconciliation has to run.

The Intrastat row, when it is generated, draws supplier ID, invoice number, line ID, the eight-digit Combined Nomenclature code, country of origin, partner VAT ID, net mass, and statistical value from the underlying dataset. The country-of-origin column on the master row is the same column that feeds the customs entry and the FTA claim. One field, three queries.

Driver 2 — Customs Entry Filings

On every import declaration, country of origin is a mandatory data element that determines the third-country duty rate applied to the goods. The commercial invoice from the supplier is the primary documentary source for that field. Whether the importer files the declaration directly or hands the paperwork to a customs broker invoice and entry data extraction workflow, the origin per line is drawn off the invoice and the supporting documents behind it. The reconciliation dataset is the importer's authoritative copy of that origin per line — the same source the broker would otherwise pull each time, held centrally, with a known provenance.

Two distinct origin questions sit on the same shipment, and the reader has to keep them separate. Non-preferential origin is the default origin used for tariff classification, trade-defence measures (anti-dumping duties, safeguard measures), and statistical purposes. The rules for determining non-preferential origin are set in the EU Union Customs Code and apply regardless of any FTA. Preferential origin is the qualification used to claim a reduced or zero duty rate under a specific FTA, governed by the product-specific rules in that agreement. Both are recorded against the same shipment but answer different questions: where the goods are deemed to come from for general tariff and trade-policy purposes versus whether they qualify for preferential treatment under a particular agreement. The next section covers preferential origin in detail; this section focuses on the non-preferential field that lands on every entry.

The Incoterm on the supplier invoice influences which party files the entry and bears the import-side costs but does not alter the origin determination. Origin is a fact about the goods, established by the manufacturing process and the rules that classify it; the contract between buyer and seller does not change that fact. The Incoterms wording on the commercial invoice matters for who is responsible for the entry, not for what origin is declared on it.

The reconciliation problem at customs entry is what to do when the supplier invoice is incomplete. Two patterns recur. First, the invoice carries no per-line origin marking at all — common with intra-EU suppliers and with non-EU suppliers who have not yet been pushed by their importer customers to print origin per line. The importer has to go back to the supplier for the missing data before the entry can be filed correctly. Second, the invoice gives a single origin at invoice level for a shipment that actually contains goods of mixed origin, and the importer has to determine line-by-line origin from the supplier's underlying records. Both of these are recurring queries that consume time on every shipment unless the dataset records the answer once, with a pointer to where it came from, and reuses it. Capturing the result on the master row — origin, source of the answer, date confirmed, who confirmed it — is what prevents the same gap being chased twice for the same supplier.

Customs entry data also feeds the wider import-cost picture. The duty rate determined by the origin field lands on the freight or customs invoice the AP team receives a week or two after the goods themselves, and the same origin reconciliation row is what lets the cost team allocate that duty correctly back to the inventory line. For UK-importing readers handling UK postponed VAT accounting on imports, the origin field is also what reconciles the C79 import VAT certificate against the original supplier invoice and the broker's entry — same field, queried in a third place.

Driver 3 — Preferential-Origin Claims Under EU FTAs

A preferential rate of duty under an EU FTA requires proof of preferential origin. The proof can take several forms depending on the agreement and the supplier's status, and the reader's portfolio dataset has to record which form attaches to each line and where it lives. When an authority later asks why the importer paid zero duty instead of the third-country rate, the answer is a specific document type, a specific supplier reference, and a specific piece of text — not a general assertion that the goods qualify.

The REX statement on origin is the most common form of proof under modern EU FTAs, including the agreements with Canada (CETA), Japan (EU-Japan EPA), Vietnam (EU-Vietnam FTA), the United Kingdom (the Trade and Cooperation Agreement), and others. The supplier makes a statement on origin on the commercial invoice or on another commercial document related to the shipment, using the prescribed wording set out in Annex 22-07 of Implementing Regulation (EU) 2015/2447. According to European Commission Access2Markets guidance on the REX system, under the EU Registered Exporter system, for shipments with a value of less than 6,000 euro the statement of origin can be made out without the obligation to register; above that threshold the exporter must hold a REX number. The threshold is per shipment, not per supplier or per year, and it is the dividing line between an invoice that is self-evidencing for preferential treatment and one that needs the supplier's REX registration to back it.

EUR.1 movement certificates are the older paper-form proof, still in use under some agreements — notably under Pan-Euro-Mediterranean Convention rules with countries that have not transitioned to REX. The EUR.1 is issued by the customs authority of the export country, not by the supplier, and it travels separately from the commercial invoice as a stamped document. This is the fundamental contrast for the importer's reconciliation. A statement on origin is supplier-issued, sits on the invoice, and authenticates itself through the REX number where one is required. EUR.1 is government-issued, is a separate document, and authenticates itself through the customs authority's stamp and serial number. The dataset has to record which one applies per shipment and where the document is filed, because at audit they will be retrieved from different places. EUR.1 vs invoice declaration is the live distinction every importer working under a mix of FTAs has to keep straight.

The long-form invoice declaration available to approved exporters is the third form, used under some FTAs and pre-dating the REX system. It is restricted to suppliers who hold approved-exporter status with their own customs authority — a status granted on application and subject to ongoing audit. The declaration uses different prescribed wording from a REX statement on origin and cites the supplier's approved-exporter authorisation reference in place of (or, depending on the agreement, alongside) a REX number. From the importer's side, the practical difference is what appears on the invoice: a different paragraph of text, a different reference number, a different validity question to test if the claim is challenged. The reconciliation dataset records the proof type as a categorical field — REX statement on origin, EUR.1, approved-exporter invoice declaration, none — because the four are not interchangeable at audit.

The apparel and textile case is where the abstract framework hits the ground hardest, and it is worth working through because it is the case that makes the discipline worth running. HS Chapters 50 to 63 — covering everything from raw silk through woven and knitted fabrics to finished garments — carry product-specific rules of origin under the Pan-Euro-Mediterranean Convention used by EU FTAs across the Euro-Med region. The rules typically require manufacturing operations beyond simple assembly to confer originating status. Depending on the chapter, the test is fabric-forward (origin is conferred where fabric is produced from yarn) or yarn-forward (origin is conferred where yarn is produced from fibre and then woven or knitted into fabric in the same originating country). What this means for the importer is that a supplier in a PEM partner country can only claim preferential origin if the manufacturing pattern actually meets the test — fabric or yarn sourced from within the cumulation zone, processed in qualifying countries, with the finishing operations performed in the country claiming origin.

That sets the verification problem. An importer of apparel from a non-EU supplier cannot rely on the supplier's statement alone if the pattern of origin claims looks inconsistent with the manufacturing economics — for example, if a supplier in one country is claiming origin on garments made from fabrics that the country does not produce, or claims a rule-compliant cumulation that the supplier cannot evidence. Verifying the claim means holding manufacturer-level documentation correlating fabric or yarn origin to the finished goods on the invoice. The reconciliation dataset is what makes that verification structured rather than ad hoc. Every line carrying a textile HS code from a non-EU supplier sits in a queryable view, and the supporting documentation column either holds a reference or flags the line for follow-up before the next claim period.

Driver 4 — Audit Defence When a Customs Authority Challenges the Claim

When a customs authority challenges an origin claim — HMRC in the UK, a national customs administration in an EU member state under the Union Customs Code, a destination-country authority such as US Customs and Border Protection on goods re-exported from the EU — the importer is the party on the hook. The supplier's statement on origin is the starting point, not the end of the matter. If the authority is not satisfied with the supporting evidence, the duty differential is recoverable from the importer along with interest and, depending on jurisdiction and the nature of the finding, potential penalties. The reconciliation dataset's value at this point is that it is the index into the evidence: every line carries a pointer to the supplier invoice, the verbatim statement on origin, the REX number that was current at the time of the claim, and any external documentation pulled in to support the position.

Retention obligations attach to the evidence, and they outlive the claim. HMRC requires importers to retain records supporting an origin claim for four years from the date of the claim under the UK's preferential-rate framework. EU member states under the Union Customs Code apply equivalent retention windows — commonly three years from the end of the year in which the customs declaration was accepted, with national variations that extend the period in some member states. A claim made in March of one year is therefore live evidence for several years afterward, and a verification request can land on the importer's desk a long time after the goods have been shipped, sold, and forgotten. Confirm the specific retention period with the relevant authority for the jurisdictions the importer operates in.

The shape of the documentation is what takes the most thinking. The CBP textile preference verification programme is a useful reference here even though the centre of gravity for this article is EU. CBP expects the importer to demonstrate material-to-finished-good correlation — fabric and yarn origin documentation traceable through to the finished apparel, with bills of materials, manufacturer declarations, and production records that connect inputs to outputs in a way consistent with the rule the goods were claimed under. The doctrine is structurally similar across jurisdictions. When any authority audits an origin claim under any FTA, the question they are asking is the same: can the importer correlate inputs to outputs in a way that matches the rule of origin the claim was made under. If the rule is yarn-forward and the importer cannot show where the yarn came from, the claim fails on its face whether the audit is being run by CBP, HMRC, or a Dutch customs inspector.

The operational implication for the dataset is concrete. Every line has to carry, in addition to the four extraction fields from Section 2, a reference to where the underlying evidence sits — the source supplier invoice file, the verbatim statement-on-origin text, the REX number, and any supporting documentation pulled in from outside the invoice itself: manufacturer declarations, bills of materials, supplier audits, certificates of analysis. A dataset that records the claim but not the path back to the evidence is a list of assertions without a paper trail. At audit, that distinction is the difference between a defended claim and a recoverable duty.

One pattern is worth flagging because it recurs. Retention obligations apply to the evidence itself, not just to the spreadsheet that summarises it. An importer who deletes the underlying supplier PDFs at year-end as part of a routine document-clearance policy, while keeping the reconciliation summary, leaves themselves unable to defend a challenge that lands two years later. The supplier invoice — the actual PDF carrying the actual statement on origin — is the primary evidence, and the dataset's reference to it is only useful if the file is still there when the reference is followed.

---

The Spreadsheet Shape: One Row Per Supplier Invoice Line

The four drivers come together in a single row schema. One row per supplier-invoice line, fourteen columns, designed so that any of the four downstream uses can be served by selecting a subset of the same columns. The schema below is what the reconciliation dataset has to carry to satisfy Intrastat, customs entry, FTA claims, and audit defence from one source.

• Supplier ID
• Supplier invoice number
• Invoice date
• Line ID (sequential within the invoice)
• HS code (eight-digit Combined Nomenclature where the supplier provides it)
• HS chapter (derived from the HS code; carried as its own column for origin-rule lookup)
• Declared country of origin (ISO two-letter code, per line)
• Preferential-origin claim flag (yes / no)
• Proof type (REX statement on origin, EUR.1, approved-exporter invoice declaration, or none)
• REX number (where applicable)
• Statement-on-origin verbatim text (captured exactly as it appears on the invoice)
• Source file reference (supplier PDF filename and page number)
• Supporting-document reference (manufacturer declaration filename, BOM reference, or null)
• Retention-until date

Each driver queries a different subset. Intrastat draws supplier ID, invoice number, line ID, HS code, country of origin, plus quantities and values held alongside the row. Customs entry draws HS code, country of origin, and the proof-type field that determines whether the line is being entered at the third-country rate or under a preferential claim. The FTA claim itself draws proof type, REX number, statement-on-origin verbatim text, and HS chapter — the chapter being what ties the line to the correct product-specific rule. Audit defence draws source file reference, supporting-document reference, and retention-until date — the columns that turn the dataset back into the underlying paper trail.

The honest part of the spreadsheet question is the population problem. Capturing fourteen fields per line across a backlog of supplier PDFs, then keeping the dataset current as new invoices arrive every week, is the bottleneck nearly every importer hits when they sit down to actually build this. Manual entry is the obvious answer and the worst answer. The verbatim origin-statement text and the REX number are both fields where transcription error is invisible until audit — a missing accent, a wrong digit, a paraphrased clause — and they are also exactly the fields the audit goes after first. A dataset that is 90% accurate on the easy columns and unreliable on the hard ones is worse than no dataset, because it generates confidence in claims that will not survive verification.

This is where the tool that builds the row directly from the PDF earns its place. It is built to extract line-level country-of-origin and origin-statement text from supplier invoices in one pass — taking a batch of up to 6,000 files in a single job — into the column shape this section has just defined. The interaction model is a single prompt over the file batch, the same prompt for ten invoices or ten thousand, returning a structured Excel, CSV, or JSON file with one row per line item. The four extraction targets — per-line country of origin, the verbatim footer text of the statement on origin, the REX number, and the HS code — are exactly the kind of fields the prompt instructs against, and the source-file reference and page number are emitted alongside each row for the evidence chain audit defence requires. For an importer who is already maintaining the reconciliation logic in a spreadsheet, the population step is the part that does not have to be manual.

The same dataset has uses beyond the four origin drivers. The HS code, country of origin, and supplier-line columns are inputs to landed cost accounting for wholesale distributors, where freight, duty, and customs broker invoices are allocated back to inventory by line. The same shape applies in production environments — allocating freight and duty invoices to inventory in manufacturing draws on the same supplier-invoice line as the unit of allocation. The reconciliation work is done once at the point the supplier invoice is processed; everything downstream is querying the columns that work has produced.