Mexico — CFDI Types & Testing Reference

This guide covers two things that don't fit into a single payload example: the CFDI 4.0 invoice type variants you'll encounter as a developer (Ingreso, Factura Global, Egreso, RFC Genérico, RFC Extranjero), and the SAT sandbox test data (test RFCs and certificates) available through Vertex's certification provider, Quadrum.

Full raw XML examples and certificate downloads live on Quadrum's wiki.

---

CFDI Invoice Type Variants

Ingreso, Factura Global, RFC Genérico, and RFC Extranjero are all issued through the same Vertex document — invoice_type: "debit", document_type: "invoice" — and differ only in specific fields. Egreso is its own document type (see below).

Ingreso

Standard income invoice. The most common type you'll issue.

Factura Global

Not a separate document type — it's an Ingreso with one addition: the <cfdi:InformacionGlobal> node (Año, Meses, Periodicidad), used to consolidate retail sales to the general public instead of billing each customer individually. Typically issued end-of-day or end-of-period.

To issue a Factura Global:

• buyer.company.tax_registrations[].number = XAXX010101000 (RFC genérico)
• buyer.company.name = PUBLICO EN GENERAL (exact string — this is what tells Vertex/SAT it's a global invoice, not a generic-RFC one-off sale)

Egreso (Credit Note)

Used to cancel or partially reduce a previously issued Ingreso. Unlike the variants above, this is its own Vertex document type:

• invoice_type: "credit"
• document_type: "credit note"

Must reference the original CFDI's UUID via CfdiRelacionados (SAT side).

RFC Genérico

For a buyer who is a member of the general public but is billed individually rather than folded into a Factura Global.

• buyer.company.tax_registrations[].number = XAXX010101000 (same RFC as Global)
• buyer.company.name = anything other than PUBLICO EN GENERAL — this is the field that distinguishes it from a Factura Global at the same RFC.

RFC Extranjero

For foreign buyers without a Mexican RFC.

• buyer.company.tax_registrations[] needs two entries:
  • One with type: "RFC", number: "XEXX010101000", location: "MX"
  • A second entry with type: "tax_id", number: <foreign tax ID, maps to SAT NumRegIdTrib>, location: <foreign country code, ≠ "MX" — this is what maps to SAT ResidenciaFiscal>

---

Test Environment — RFCs & Certificates

Vertex's SAT sandbox testing runs through Quadrum's DEMO environment. These RFCs and certificates are test-only — never use them in production.

Test RFCs — Emisores (Suppliers)

Use these as supplier_company_id in test payloads. Each has a CSD (Certificado de Sello Digital) and FIEL (Firma Electrónica) pair.

Certificate downloads (CSD + FIEL, per RFC) are on Quadrum's wiki — not redistributed here since they're binary files tied to Quadrum's sandbox: Quadrum — Archivos de Certificados.

Test RFCs — Receptores (Buyers)

Use these as buyer in test payloads. These do not have certificates — they're buyer-only.

More test RFCs are listed on Quadrum's wiki if these don't cover your test case.

RegimenFiscal Mapping (SAT → Vertex)

Maps SAT catalog c_RegimenFiscal to the Vertex value expected in company.tax_registrations[].status (where type = "RFC").