How to Choose Anexo 24 & SCCCyG (Anexo 31) Software in Mexico: RFP Checklist for US IT & CFOs

When a US company launches a Mexican manufacturing subsidiary, or graduates from a Shelter operator to its own standalone IMMEX program, the IT Director and Controller quickly discover that global ERP platforms (SAP S/4HANA, Oracle Cloud, NetSuite, Plex, QAD, Microsoft Dynamics 365, Infor) cannot natively satisfy Article 59, Section I of the Mexican Customs Law or Anexo 24 and Anexo 30/31 (SCCCyG) of the General Foreign Trade Rules (RGCE).

Selecting the wrong Anexo 24 software, or worse, letting a local customs broker track your inventory on spreadsheets or a closed proprietary portal, creates a hidden compliance debt that only surfaces years later when AGACE audits your plant or threatens to suspend your 16% VAT Certification.

This vendor-neutral technical guide gives US IT architects, ERP managers, and CFOs the exact RFP evaluation matrix needed to select, integrate, and audit an Anexo 24 and SCCCyG platform.


1. Why Global ERPs Cannot Replace a Dedicated Anexo 24 Engine

US IT teams frequently ask: “Why can’t we just build a custom report inside SAP or NetSuite to satisfy Anexo 24?” Look at the seven structural gaps between a standard financial/manufacturing ERP and Mexican customs law:

RequirementStandard Global ERP (SAP / Oracle / NetSuite)Dedicated Mexican Anexo 24 + SCCCyG Engine
1. Primary Tracking KeyTracks inventory by SKU Part Number, Plant, Storage Location, and Accounting CostTracks every unit back to the 15-digit Customs Pedimento Number + Line Sequence (Tabla 551) + 8-Digit Tariff Fraction + Entry Date
2. Unit of Measure Dual-LedgerConsumes BOMs in Engineering/Commercial Units (UMC: Pieces, Feet, Rolls, Liters)Translates UMC consumption into Mexican Tariff Units (UMT: Kilograms, Square Meters) per pedimento lot
3. Customs File IngestionCannot natively parse Mexican SAAI .M validation files, VUCEM COVE XMLs, or monthly SAT Data Stage (501/551/554/557) tablesAutomatically ingests .M files, COVE XMLs, and Data Stage ASCII tables, linking invoice SKUs to grouped pedimento tariff lines
4. SCCCyG (Anexo 30/31) VAT Credit AccountingTracks VAT in general ledger financial accountsTracks Forma de Pago 21 credits by 8-digit Tariff Fraction in MXN, calculates proportional credit amortization per FIFO lot, and generates the statutory pipe-delimited .txt SCCCyG Discharge Report
5. Multi-Tier Retention AgingTracks shelf-life or accounting obsolescenceTracks 18-month (IN), 6-month (V1), 12-month (Annex II), and 36-month (OEA Rule 7.3.3) statutory customs clocks simultaneously
6. USMCA Article 2.5 Duty CalculationNo native concept of NAFTA/USMCA duty deferral offsetsCalculates Mexican IGI owed on non-originating (Chinese/Asian) inputs exported to the US/Canada under USMCA Article 2.5
7. Apartado C Online SAT PortalMajor security risk to expose global ERP directly to external tax auditorsPublishes an isolated, read-only Apartado C web portal updated within 48 hours strictly for SAT/AGACE auditors

2. The 6 Non-Negotiable Technical Capabilities in Your Software RFP

When interviewing Mexican Anexo 24 software vendors, do not let the sales rep spend 45 minutes showing you static catalog screens. Require a live technical demonstration of these six mission-critical capabilities:

Capability 1: Dynamic Per-Lot UMC-to-UMT Conversion (No Residual Crumb Balances)

Ask the vendor: “What happens when Lot 1 of part RESIN-A arrives on Pedimento A at 1,000 Lbs = 453.59 Kg, and Lot 2 arrives on Pedimento B at 1,000 Lbs = 460.00 Kg?”

  • Weak legacy software uses a single static conversion factor in the Material Master (0.45359 Kg/Lb), leaving 6.41 Kg and its proportional $ MXN value stranded forever on Pedimento B in SCCCyG!
  • Enterprise-grade Anexo 24 software stores the actual UMT / UMC ratio per pedimento line (Tabla 551) (or automatically clears residual UMT and MXN rounding crumbs when 100.00% of the lot’s UMC quantity is consumed), guaranteeing that when physical inventory hits 0, both the Anexo 24 UMT balance and the SCCCyG MXN credit balance hit 0.00.

Capability 2: Automated Data Stage (501/551/557) + COVE XML + .M File 3-Way Reconciliation

The software must include a built-in Data Stage Audit Module that automatically compares:

  1. The daily .M files and COVE XMLs transmitted by your customs brokers;
  2. Your ERP Goods Receipts and Shipment Invoices; and
  3. The official monthly SAT Data Stage ASCII files (501, 505, 551, 554, 557, 701). It should immediately highlight any orphan pedimento, missing R1 rectification, or $1.00 MXN variance between Table 551/557 (Forma de Pago 21) and your Anexo 24 database.

Capability 3: Compliant, Isolated Apartado C Portal + 48-Hour Automated ETL

To comply with Anexo 24 Apartado C:

  • The system must support automated daily (T+24h) SFTP/REST API ingestion from your ERP (SAP IDocs/BAPIs, Oracle REST, NetSuite SuiteTalk, or automated flat-file drops) and automated daily broker .M/COVE pulls, complete with a Pre-Load Staging Quarantine so bad data is flagged for your compliance team before it corrupts the live FIFO ledger.
  • It must provide a dedicated, read-only Auditor Web Profile that displays only the statutory Apartado A Catalogs, Customs Module, and FIFO Reports, with full query logging so your compliance team receives an instant alert whenever SAT’s AGACE user logs into the portal.

Capability 4: Integrated SCCCyG (Anexo 30/31) Simulator & .txt Validator

Never buy an Anexo 24 system that treats Anexo 30/31 (SCCCyG) as an afterthought. The software must maintain a mirror SCCCyG ledger inside the application that:

  • Tracks every Forma de Pago 21 and Forma de Pago 6 credit by 8-digit Tariff Fraction and Entry Month/Year;
  • Pre-validates the generated .txt Discharge Report against all SAT SCCCyG business rules (checking for over-discharges, invalid tariff fractions, and unmodulated return pedimentos) before you upload it to the SAT portal; and
  • Reconciles your uploaded .txt reports against the PDF/Excel Estado de Cuenta downloaded from SAT.

Capability 5: Engineering BOM Versioning (Fechas de Vigencia) & Multi-Level Sub-Assemblies

Manufacturing plants constantly execute Engineering Change Notices (ECNs), component substitutions, and multi-level sub-assemblies.

  • Your Anexo 24 software must support date-effective BOM versions (estructuras con vigencia por rango de fechas) so that an export pedimento (RT) in January discharges the January BOM, while an RT in March discharges the March BOM, without overwriting historical discharges when you re-run a FIFO audit.

Capability 6: Electronic Customs Dossier Repository (Expediente Digital: Art. 36-A & 59-V)

Under Article 36-A and Article 59, Section V of the Mexican Customs Law, the company must preserve the complete electronic dossier for every pedimento (XML/PDF Pedimento, COVE XML/PDF, Commercial Invoice, Packing List, Bill of Lading, Origin Certificates, E-Documents, and Manifestación de Valor E2 + Art. 81 RLA attachments). Choosing a platform that stores and links the complete digital dossier directly to each pedimento record in Anexo 24 saves hundreds of hours during AGACE audits.


3. Hosting, Data Ownership & Contractual Safeguards for US Buyers

Before signing a software license or SaaS agreement in Mexico, enforce these three contractual clauses:

  1. Unconditional Database Ownership & Open-Format Exit Clause: Explicitly stipulate in the contract that your Mexican subsidiary owns 100% of its database, and that upon termination or non-renewal, the vendor must deliver a complete, unencrypted SQL backup plus CSV/Excel exports of all Catalogs, Pedimentos, FIFO Discharge Links (Relación de Descargos Entradas vs. Salidas), and Digital Dossiers within 10 business days at no extra hostage fee.
  2. Independence From Any Single Customs Broker: Never sign up for an Anexo 24 instance that is legally owned by or contractually tied to remaining with a specific customs broker (Agente Aduanal). Your Anexo 24 system is your corporate tax book of record; customs brokers should be replaceable data suppliers feeding that book.
  3. SLA for SAT Regulatory Updates (RGCE / LIGIE / NICO / Apartado C): Ensure the annual maintenance fee includes guaranteed turn-key updates whenever SAT or the Ministry of Economy modifies the TIGIE tariff schedule, NICO codes, Anexo 22 appendices, SCCCyG .txt layouts, or Anexo 24 Apartado C technical specifications.

Frequently asked questions

Can SAP, Oracle, NetSuite, or Plex handle Mexico's Anexo 24 and Anexo 30/31 natively without specialized software?

No. Standard global ERPs track inventory by SKU part number, warehouse bin location, and standard/moving-average cost in commercial units (UMC). They do not natively parse Mexican SAAI .M validation files, COVE XMLs, or monthly SAT Data Stage (501/551/557) files, nor do they execute pedimento-lot FIFO (PEPS) discharges by 8-digit Mexican tariff fraction in Tariff Units (UMT), calculate USMCA Article 2.5 non-originating duty offsets, generate SCCCyG .txt credit discharge files, or host an isolated Apartado C portal for SAT auditors.

Should we let our Mexican customs broker manage our Anexo 24 in their own software for free?

Relying solely on a customs broker's 'free' Anexo 24 hosting is one of the highest-risk mistakes a US manufacturer can make. First, if you use more than one broker (e.g., Laredo land freight plus Monterrey air freight or Manzanillo ocean freight), a single broker lacks visibility into your complete operation. Second, the broker does not have real-time access to your internal ERP engineering BOM changes, scrap write-offs, or cycle count adjustments required under the 48-hour Apartado C mandate. Third, if you ever switch customs brokers, extracting your historical Anexo 24 database and SCCCyG audit trail often becomes a costly hostage negotiation.

What is the most important technical feature to test in an Anexo 24 software demo?

Test how the software handles UMC-to-UMT conversion variances across different pedimento lots (Dynamic Lot Conversion Factor vs. Static Master Catalog Factor), and ask to see its automated pre-validation engine reconciling SAT Data Stage Tables 501, 551, and 557 against COVE XMLs and SCCCyG credit balances.

How does the software comply with Anexo 24 Apartado C without exposing our corporate ERP?

A properly architected Anexo 24 platform operates as an independent cloud or on-premise compliance database fed daily via API/SFTP from your ERP and customs brokers. It publishes a read-only web portal containing strictly the statutory Apartado A catalogs, customs entries/exits, and FIFO balance reports for SAT's AGACE login, with zero network pathway back into your corporate ERP.

How long does it take to implement or migrate an Anexo 24 and SCCCyG system?

A greenfield implementation with automated daily ERP and broker interfaces typically takes 6 to 10 weeks. A historical migration (reconstructing and auditing 2 to 5 years of historical Data Stage pedimentos, open FIFO balances, and historical SCCCyG discharge reports from a legacy system or Shelter operator) typically takes 8 to 14 weeks depending on data cleanliness.

Does your operation have a case this page does not resolve?

This page explains the framework; it cannot decide your case. Describe the concrete situation and we will tell you what to ask, what to document and — where it applies — what kind of specialist or tool to look for.

AMMEX is an independent platform operated by Heberey LLC. We review your inquiry internally; any possible sharing with an external provider requires your prior authorization.

No legal, tax, accounting or customs advice is provided, and no certifications or authorizations are processed.