TL;DR — Quick Summary
Fix Aspel SAE global invoice CFDI 4.0 errors: InformacionGlobal periodicity, generic public RFC, ObjetoImp, and duplicate tickets before PAC stamping.
When Aspel SAE builds a global invoice under CFDI 4.0 and the PAC rejects it—or SAE errors before sending XML—the failure is usually in InformacionGlobal, the public general receiver, or wrong tickets, not PAC connectivity. This guide covers period-close errors (daily through bimonthly) and the correction order used in Mexican deployments.
The error
Typical messages when stamping a global invoice from SAE 8.x / 9.x:
Error generating global invoice
CFDI 4.0 schema validation failed
CFDI40162 — Periodicidad field is not valid
CFDI40173 — Meses does not match periodicity
Receiver data error (tax regime or CFDI use)
ObjetoImp does not match transferred tax
SAE may build the invoice but the PAC returns CFDI401xx in seconds. Keep the pre-stamped XML; the SAT validator names the exact node.
CFDI 4.0 requirements for global invoices
A global invoice covers general public sales (tickets without nominative CFDI). CFDI 4.0 requires:
| Receiver field | Usual value |
|---|---|
| RFC | XAXX010101000 |
| Name | PUBLICO EN GENERAL |
| Receiver tax regime | 616 |
| CFDI use | S01 |
| Receiver postal code | Issuer establishment CP |
InformacionGlobal must declare Periodicidad (01–05 per catalog), Meses, and Año aligned with included ticket dates. Wrong any of these and stamping fails even if the peso total is correct.
Cause 1: Misconfigured public general customer
Most common after migrating from CFDI 3.3 or cloning companies.
Check in SAE:
- Customer catalog has XAXX010101000 without spaces.
- Name is PUBLICO EN GENERAL in uppercase.
- Regime 616 and use S01 on the customer card.
- Postal code matches issuer location, not a random CP.
In Configuration → Company → Electronic invoicing, ensure global invoicing points to this customer, not an old RFC with a different regime from another branch.
Cause 2: Wrong periodicity or months
The SAT validates periodicidad against obligation and ticket date range.
Typical mistakes:
- 04 Monthly when daily or weekly is required.
- 05 Bimonthly without an allowed regime.
- Meses blank or wrong month for the closing period.
- Año not matching ticket year.
Fix: Open Invoicing → Global invoice, set date range, choose allowed periodicity, verify month/year before stamping. If you get CFDI40162/40173, adjust only those fields and regenerate XML.
Cause 3: Duplicate or already invoiced tickets
Including a ticket that already has a nominative CFDI causes rejection or electronic accounting mismatches.
Procedure:
- Run period sales/ticket report.
- Filter tickets without individual UUID.
- Exclude unposted returns.
- Match ticket sum to global total before PAC.
Cause 4: ObjetoImp and IVA mismatch
Each line needs ObjetoImp. Public sales often use 0% IVA or exempt; ObjetoImp 02 without a correct Traslado node fails validation.
After catalog updates, recalculate the global invoice before stamping.
Cause 5: CSD or PAC when the message is not “global”
401 certificate, PAC timeout, or invalid seal point to infrastructure—see dedicated guides. If normal invoices stamp and only global fails, return to causes 1–4.
Step-by-step fix
- Audit XAXX010101000 customer (616, S01, issuer CP).
- Close ticket period without gaps; export internal ticket list.
- Generate global in Facturación → Factura global; confirm InformacionGlobal in preview/XML.
- Stamp, download XML, verify on SAT portal, book UUID in revenue entry.
- If already stamped wrong, cancel with correct SAT motive and re-issue—do not double-cover the same period.
Prevention
- Standardize XAXX010101000 across branches.
- Operational report of tickets pending global inclusion.
- Fiscal calendar for required periodicity by regime.
- Keep SAE service pack current for SAT catalog updates.
- Train cashiers: individual invoice OR global batch, not both.
Summary
- Global invoice CFDI 4.0 failures in SAE are usually receiver 616/S01, InformacionGlobal, or already invoiced tickets.
- Fix XAXX010101000 and issuer CP before blaming the PAC.
- Align ObjetoImp with IVA on the aggregated line.
- Validate XML on the SAT portal after success.