SAT Data Stage vs. Anexo 24 Reconciliation: How to Audit Records 501, 551 & 554

In Mexican customs compliance, there is only one source of truth for what your company legally imported and exported: SAT’s SAAI database, delivered to importers each month as the Data Stage (Glosa) report.

A common failure mode in US-owned Mexican manufacturing plants occurs when the trade compliance team feeds Anexo 24 solely from the PDF pedimentos and .M files emailed by their primary customs broker, without cross-reconciling against the monthly Data Stage file issued directly by SAT. Within a single year, missed air-freight clearances, uncommunicated R1 rectifications, late-closing consolidated pedimentos, and unit-of-measure discrepancies between Table 551 and the plant’s ERP will break both the Anexo 24 FIFO ledger and the SCCCyG (Anexo 30/31) VAT credit account.

1. What Is SAT’s Data Stage File and How Is It Structured?

Between the 1st and the 7th day of every month, SAT generates a password-protected archive for each registered importer (via the Matriz de Seguridad / SOIA portal) containing roughly 25 to 30 pipe-delimited (|) ASCII text files. Together, these relational tables reconstruct every field of every pedimento paid under the company’s Mexican tax ID (RFC) across all 50 Mexican customs ports during the prior month.

While IT teams often see a confusing folder of numbered .txt or .asc files, seven core tables govern 99% of an IMMEX compliance audit:

2. The 5-Step Monthly Data Stage vs. Anexo 24 Reconciliation Protocol

Even though Anexo 24 Apartado C requires updating your inventory system within 48 hours of each crossing, you must execute a 100% Monthly Closing Reconciliation between days 5 and 10 of the following month as soon as SAT releases the official Data Stage package:

Step 1: Header Population Check (Table 501 vs. Anexo 24 Headers)

Cross-match every unique key (Patente + Aduana + Pedimento) in Table 501 against the pedimentos loaded in your Anexo 24 system for the month.

• What you frequently catch:
  1. Orphan Air/Courier Importations: An engineer ordered replacement CNC spindles or urgent electronic reels via DHL/FedEx/UPS at Monterrey, Guadalajara, or Mexico City Airport (Aduana 470/800), and the courier’s broker cleared it under your RFC without copying your border compliance team.
  2. Month-End Consolidated Pedimentos (Pedimentos Consolidados): A weekly consolidated IN or RT pedimento opened in late March was closed and paid on April 2nd, causing cutoff timing differences between ERP shipments and customs payment dates.
  3. Unreported R1 Rectifications (Table 701): A broker filed an R1 pedimento to fix a value, tariff fraction, or UMT quantity, leaving your Anexo 24 running on the superseded original pedimento data.

Step 2: Line-Item & SCCCyG Credit Check (Tables 551 + 557 vs. Anexo 24 Lines)

Filter Table 551 joined with Table 557 where Contribución = 3 (IVA) and Forma de Pago = 21 (Crédito en IVA e IEPS).

• Sum the Commercial Value in Mexican Pesos (Valor Comercial MXN) and Quantity in Tariff Units (Cantidad UMT) by 8-digit tariff fraction (Fracción Arancelaria).
• Compare that table against:
  1. Your SCCCyG (Anexo 30/31) Statement of Account (Estado de Cuenta) on the SAT portal; and
  2. Your Anexo 24 Temporary Import Entries Report.
• Rule of Iron: These three numbers (Data Stage 551/557 with FP 21 = SCCCyG New Credits = Anexo 24 Temporary Entries with FP 21) must match to the exact peso and exact UMT decimal.

Step 3: Bridging the “Grouping Gap” (Table 551 vs. COVE XML vs. ERP Part Numbers)

Why do Anexo 24 systems drift away from Data Stage? Because of broker line-item grouping (agrupación de partidas):

• Suppose your commercial invoice and COVE XML contain 15 different resistor SKU part numbers (RES-01 through RES-15), all classified under tariff fraction 8533.21.01.
• On the pedimento (Table 551), the customs broker groups all 15 part numbers into Line Item #1 (Secuencia 1): 8533.21.01 | 500,000 Pza | 120.500 Kg | $450,000 MXN.
• Your Anexo 24 system must break that single Table 551 line back down into the 15 individual ERP part numbers using the COVE XML (Table 505), while ensuring that the sum of the 15 SKU weights (Kg UMT) and values (MXN) in Anexo 24 equals 120.500 Kg and $450,000 MXN with zero rounding discrepancy.

Step 4: Auditing UMC-to-UMT Ratios in Table 551

Write a simple script or Excel query on Table 551 dividing Cantidad UMT by Cantidad UMC for every line item imported during the month, and compare that ratio against last month’s ratio for the same tariff fraction.

• If last month your steel fasteners (7318.15.99) had an average ratio of 0.0150 Kg per Piece, and this month Line Item #4 shows 0.1500 Kg per Piece (a 10x decimal slip by the broker’s classifier), catching it on Day 6 allows you to file an R1 rectification before transmitting your SCCCyG discharge report, saving you from an artificial over-discharge (sobredescargo).

Step 5: Auditing Identifiers in Table 554 (V1, TL, PS, RO, AF)

• Virtual Transfers (V1): Verify that every V1 pedimento in Table 501/554 lists the valid IMMEX program number of the counterparty in Complement 1, and that you hold the signed copy of the counterparty’s mirror V1 pedimento closed within the statutory 20-day window under RGCE Rule 4.3.21.
• Fixed Assets (AF): Verify that every AF line in Table 551 has its corresponding brand, model, and serial numbers documented in the COVE / E-Document and loaded into the Anexo 24 Fixed Assets module.

3. Summary Checklist: Monthly Data Stage Audit Gate

Before your compliance team generates the monthly .txt discharge file for SCCCyG (Anexo 30/31), require the controller or compliance manager to sign off on these four zero-tolerance checks: