ERP, Warehouse, Broker, and Anexo 24 Mismatch: A Practical IMMEX Scenario
This one is a walkthrough rather than an explainer. We will take a single part through five systems, show how the numbers split apart, and trace it back to the root cause. If you are an operations manager or a compliance analyst, this is the kind of puzzle that lands on your desk with no instructions.
The setup
Composite scenario: This example combines recurring data-reconciliation patterns seen in cross-border manufacturing workflows. It is not a statement about any specific company.
You import a connector. Finance asks a simple question at quarter-end: how many of these are still open against temporary import? You pull every system. Here is what you get for the same part:
| System | Part identifier | Quantity | Unit |
|---|---|---|---|
| ERP | A-100 | 10,000 | pieces |
| Broker / pedimento | A100-MX | 10,000 | pieces |
| Warehouse (WMS) | SKU 7781 | 9,850 | pieces |
| Anexo 24 | A-100 (old rev) | 9,600 | pieces |
| Production consumption | per BOM rev C | 9,400 consumed | pieces |
Five systems, five numbers. Nobody falsified anything. So where did the gaps come from?
Tracing it back
Work the differences one pair at a time, not all at once:
- ERP 10,000 vs WMS 9,850. 150 pieces are still in incoming inspection, logged in ERP at receipt but not yet put away in the WMS. Legitimate, explainable, temporary.
- WMS 9,850 vs Anexo 24 9,600. Anexo 24 was loaded from an older master-data mapping that never picked up a quantity correction. This is a data-feed problem, not a physical one.
- ERP A-100 vs broker A100-MX vs WMS 7781. Same physical part, three identifiers, no maintained cross-reference. This is the root cause hiding under the quantity noise.
- Anexo 24 9,600 vs production 9,400. Production consumed against BOM revision C, which compliance was never told about. Two hundred pieces are “missing” only because the consumption logic is out of date.
Add it up: the alarming “open balance” is mostly explainable timing and stale mappings — but only mostly. The part-number cross-reference and the BOM revision are real fixes, and without them the gap will reopen next quarter.
The actual problem
The numbers are a symptom. The disease is that no single key links the five systems and no one owns the translation between them. When a part has four names and a BOM that changes silently, reconciliation becomes archaeology.
What to fix, in order
- Establish one master part identifier and a maintained cross-reference to the broker and WMS codes.
- Make BOM revisions flow to whoever maintains Anexo 24 consumption logic.
- Record inspection and in-transit quantities so they are visible during reconciliation.
- Set a periodic reconciliation with a named owner.
What to check first
- Is there a single master identifier for each part, with a maintained cross-reference?
- Do BOM changes reach the inventory-control owner?
- Are inspection and in-transit quantities visible when you reconcile?
Before you escalate
If, after tracing, a real gap remains — not timing, not mapping, but quantity you cannot account for — that is when to bring in a customs broker or IMMEX specialist. Hand them the five-system table and your trace, not the raw exports. The work you did to isolate “explainable vs not” is exactly what makes their job fast.
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
- Anexo 24 Explained in Plain English: Inventory Control for IMMEX Operations
- BOM Changes and IMMEX Risk: When Engineering Updates Break Inventory Control
- Pedimento Reconciliation for IMMEX: What to Check Before the Numbers Drift
- IMMEX Checklist for ERP Teams: Part Numbers, BOMs, Units, and Broker Data
- IMMEX risk and data reconciliation index
Sources & further reading
- SAT — Reglas Generales de Comercio Exterior — RGCE and annex reference for inventory-control obligations.
- Diario Oficial de la Federación — Publication source for the RGCE and annex text.
- SNICE / Secretaría de Economía — IMMEX — IMMEX program context.
- SAT — Foreign trade references — Customs and certification reference.
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.