The fields that must agree are the HS code on each product, the EORI numbers of the importer and exporter, and the origin declaration on each item. They must match across your ERP master data, commercial invoice and customs declaration. A mismatch can delay clearance or change the duty you pay.
Key takeaways
- The HS code belongs on the item master, so every order inherits one classification instead of a typed guess.
- Each legal party needs its own EORI number, and the declaration must reference the party that actually imports or exports the goods.
- Origin should be stored per product and per supplier, together with the basis on which the origin claim rests.
- Customs checks compare the declaration against the documents behind it, so one inconsistent field can trigger a query or a hold.
- A short recurring review of master data catches most mismatches before goods reach the border.
Customs declarations are short, but they draw on data from several places. Sales orders, purchase records, warehouse systems and freight documents all carry a piece of the picture. When an ERP holds those pieces in separate, inconsistent places, the declaration becomes the first point where the differences show. This article explains the three fields that cause most trouble, how to store them so they stay aligned, and how to recognise the failures early.
Where does the HS code belong in your ERP?
The HS code belongs on the item master record, so that every sales or purchase line for that product uses the same classification. Typing the code into each order invites drift, because two people can classify one product differently on the same day.
The Harmonized System is maintained by the World Customs Organization, which sets the six-digit structure shared by most trading countries. The European Union adds further digits in its Combined Nomenclature, which is published as EU law and available on EUR-Lex. Your ERP therefore needs to store the full code that applies in the territory where the goods cross the border, not only the first six digits.
Trade-offs of item-level classification
Classifying at item level gives consistency, but it creates a maintenance task. Someone must own the master data and review it when product designs change. Without an owner, the item record becomes the last thing anyone updates.
Item-level codes also fail for certain products. Kits and bundles may need a classification that differs from their components. Variants of one product can fall under different codes depending on material or function. In these cases the ERP needs a rule that states which record drives the declaration, rather than assuming the parent item is always correct.
Which EORI number goes on which record?
Each party that imports or exports goods needs its own EORI number, and the declaration must name the party that is legally responsible for the transaction. The EORI number should sit on the partner record in the ERP and be linked to the entity that uses it. The European Commission describes the registration system on its customs pages.
The Union Customs Code, Regulation (EU) No 952/2013, sets out the framework in which EORI numbers are used. This article is general information and not legal or tax advice. Which party is the declarant in a given transaction is a question for your contracts and for qualified advisers.
Where EORI data fails
The most common failure is a subsidiary shipping under the group parent's number, or a forwarder's number appearing on a shipment where the company is the actual importer. The ERP cannot detect these errors by format alone, because both numbers are valid. A review step that compares the declared party with the commercial party is what catches them.
How should origin fields be stored and checked?
Origin should be stored per product and per supplier, together with the reason the origin claim is valid. A single origin field on the product record is not enough, because the same item can come from different factories with different origins.
Origin rules depend on the trade agreement, the product and the proof required. The European Commission publishes guidance on origin and preferences on its customs pages. Your ERP should record which proof supports each origin claim, so that the commercial invoice and the declaration reference the same evidence.
Trade-offs of storing origin
Storing origin per supplier makes the data accurate but heavier to maintain. Storing it per product is simpler but fails when sourcing changes. Manufactured goods add a further layer, because components may come from several countries and the origin of the finished product depends on the applicable rules. Bill of materials data must then be linked to the origin record, which many standard ERP setups do not do by default.
What goes wrong when customs data does not match?
A mismatch usually leads to a query, a hold or a corrected declaration, and in some cases to a different duty outcome than the one you planned for. The declaration is checked against the documents behind it, so any difference between the declaration and the invoice draws attention.
- The HS code on the declaration differs from the code on the commercial invoice.
- The EORI number belongs to a party that does not appear on the contract or invoice.
- The origin stated on the invoice relies on a proof that is missing or expired.
- The same product carries two different codes in two warehouses or two ERP instances.
Each of these failures starts in master data, not at the border. This is why the fix is usually a change to how data is stored and linked, rather than a change to the declaration itself.
How do you keep the fields matching in practice?
You keep the fields matching by assigning an owner, linking each field to its source record and reviewing exceptions on a fixed schedule. Technology helps, but ownership decides whether the data stays correct.
- Name one owner for classification and one for origin, and record who approves changes.
- Store the HS code, EORI number and origin on the records that drive the declaration, with validity dates.
- Generate the commercial invoice and the declaration from the same fields, not from copies.
- Run a check before shipment that compares the code, party and origin across documents.
- Review changes to products, suppliers and nomenclature each quarter, and log every correction.
When the ERP connects to a customs or freight system, the integration must carry these fields in both directions. Rui Codex offers technical implementation support for ERP and CRM integration and for system integrations that move this data between tools. We do not provide legal, tax or compliance advice, and we do not audit or certify your declarations.
Hypothetical examples of mismatched customs data
Here are two hypothetical scenarios:
In the first, a product record holds a classification that was correct for an earlier version of the item. The sales team creates a new order from a copy of an old quote, so the invoice shows the old code while the declaration system pulls the current one. The mismatch is caught at the border, and the fix is a master data change plus a review of open orders.
In the second, a company ships through a forwarder that declares under its own number, while the commercial invoice names the company as exporter. The ERP stores both numbers without a rule that says which is correct for this route. The remedy is a required field that links each shipment to the declaring party, checked before the document is issued.
Neither scenario describes a real organisation. They illustrate where the fields usually drift apart.
Common questions about this topic
Review the questions below for short answers to the points most teams ask first. Each one links back to the practical steps described above.
Consider a project consultation if your products span several origins or your ERP runs in more than one country. Request a project consultation at the Rui Codex contact page.
Frequently Asked Questions
Should the HS code be stored on the product or on each order line?
The HS code should be stored on the product master record, and order lines should inherit it. Storing it only on order lines lets two people classify the same product differently, which creates inconsistencies that surface at clearance. Keep a validity date on the code so you can trace which orders used an earlier classification.
Can one EORI number be used for several group companies?
No, each legal entity that imports or exports goods needs its own EORI number. Using a parent company's number for a subsidiary's shipment can make the declaration inconsistent with the commercial documents. Check which company is the contracting party for each route and link the shipment to that entity in your ERP.
Why does origin need to be stored per supplier?
Origin depends on where goods are produced, so the same product can have different origins when it comes from different suppliers or factories. A single product-level field becomes wrong as soon as sourcing changes. Recording origin per supplier, together with the evidence that supports it, keeps invoices and declarations aligned.
What is the fastest way to find existing mismatches?
Export the HS code, EORI number and origin for recent shipments and compare them with the records on the commercial invoices. Group differences by product and by supplier to find the source. Start with the items that move through the most shipments, because errors there repeat most often.
Conclusion
Customs data in an ERP is only reliable when the HS code, EORI number and origin are stored where they are created and reused everywhere else. Assign owners, link fields to the records that drive the declaration and check consistency before goods leave. These steps cost less effort than correcting a declaration after a query. If your ERP and shipping tools do not yet share this data cleanly, email info@ruicodex.com to discuss your project, or request a project consultation at https://ruicodex.com/Contact. You can also review delivered work at https://ruicodex.com/CaseStudies.
Sources
- Regulation (EU) No 952/2013 laying down the Union Customs Code - Publications Office of the European Union
- Economic Operators Registration and Identification number (EORI) - European Commission
- Harmonized System nomenclature overview - World Customs Organization