IMMEX Checklist for ERP Teams: Part Numbers, BOMs, Units, and Broker Data
ERP and data teams usually sit far from customs. No one calls them when a pedimento is filed. Yet the master data they maintain quietly decides whether an IMMEX reconciliation is a one-hour query or a three-week archaeology project. A part number, a unit, a BOM version — these are the keys that join the customs world to the operational one.
This is a checklist for ERP and data people who want to stop being surprised by compliance escalations they had no idea they were causing.
The keys that hold everything together
Reconciliation is a join. Imports, receipts, consumption, and exports all have to be joinable on a common key. When the keys are clean, the join works. When a part has four identifiers and a BOM that changed without a version trail, there is no reliable key, and the join falls apart no matter how good the rest of the data is.
A blunt way to say it: for IMMEX, your master data is the reconciliation. Everything else is reporting on top of it.
The checklist
| Data object | What to enforce | Why it bites under IMMEX |
|---|---|---|
| Part number | One master ID per physical part | Multiple IDs break import-to-export joins |
| Broker/customs code | Maintained cross-reference to the master | Pedimentos cannot be matched without it |
| Unit of measure | One base unit + documented conversions | Kg/piece/set drift creates phantom gaps |
| BOM version | Versioned, with effective dates | Stale consumption logic mis-relieves material |
| Status codes | Clear temporary-import flags | ”Open vs discharged” can’t be reported otherwise |
A short example
Educational scenario: This is a fictional example based on common IMMEX workflows. It does not describe any specific company.
An ERP migration is declared a success. Historical part numbers were preserved, production runs fine, finance is happy. But the migration quietly changed how units of measure were handled, and the broker files and inventory control still use the old mapping. For everyone except compliance, the project is done. For compliance, every reconciliation now needs a manual bridge between old and new unit logic — a bridge no one budgeted for.
What to check first
- Does each physical part have exactly one master identifier?
- Is there a maintained cross-reference to broker/customs codes?
- Are unit conversions defined and documented, not improvised?
- Do BOM versions carry effective dates that reach inventory control?
Questions for compliance and your specialist
- What keys does inventory control join on, and do our master records support them?
- When we migrate or restructure data, what must stay stable for reconciliation?
- How should temporary-import status be represented so it is reportable?
Before you escalate
If a past data change broke the join — duplicate part IDs, lost cross-references, a unit-logic switch — flag it to compliance before the next reconciliation cycle, not after it fails. Bring the specific objects that broke and a proposed bridge. ERP teams that surface this proactively save the whole company a painful quarter-end.
Interactive tools and visuals
Data reconciliation aids
Use these visuals and the self-test to locate quantity, unit, BOM, scrap, warehouse-transfer or pedimento mapping gaps.
Confirm any finding with your broker, advisor or qualified IMMEX specialist.
Related reading
- ERP, Warehouse, Broker, and Anexo 24 Mismatch: A Practical IMMEX Scenario
- BOM Changes and IMMEX Risk: When Engineering Updates Break Inventory Control
- Pedimento Reconciliation for IMMEX: What to Check Before the Numbers Drift
- Anexo 24 Explained in Plain English: Inventory Control for IMMEX Operations
- IMMEX risk and data reconciliation index
Sources & further reading
- SNICE / Secretaría de Economía — IMMEX — IMMEX program context.
- SAT — Foreign trade portal — Inventory-control and customs reference.
- Diario Oficial de la Federación — Primary source for rules and updates.
- Trade.gov — Mexico Country Commercial Guide — Overview for importers.
Disclaimer
This article is for educational purposes only. It is not legal, tax, customs, or accounting advice. IMMEX, import, VAT/IEPS, Anexo 24, Anexo 31, NOM, Padrón, RFC, and customs-broker obligations depend on the facts of each operation. Confirm requirements with your Mexican importer, customs broker, tax advisor, or qualified IMMEX specialist before shipping or changing your process.