Electronic Invoicing in LATAM: Multi-Country Compliance Guide
Navigate electronic invoicing requirements across Latin America. Country-by-country guide covering Mexico (CFDI), Panama (FEL), Peru (SUNAT), Colombia (DIAN).
Electronic Invoicing in LATAM: Multi-Country Compliance Guide
Latin America leads the world in mandatory electronic invoicing adoption. While Europe is still rolling out its e-invoicing mandates (ViDA directive targeting 2028-2030), most LATAM countries have had mandatory e-invoicing for over a decade. Mexico launched CFDI in 2004. Brazil's NF-e went live in 2006. Chile has required electronic invoicing since 2003.
For businesses operating across multiple LATAM countries, this creates a complex compliance landscape. Each country has its own XML schema, its own tax authority integration, its own certification requirements, and its own penalties for non-compliance. This guide covers the practical technical and regulatory requirements for the major markets.
Why LATAM Leads Global E-Invoicing Adoption
LATAM governments adopted electronic invoicing earlier and more aggressively than any other region for several interconnected reasons.
Tax gap closure. Informal economies in LATAM historically represented 30-60% of GDP. Electronic invoicing creates a real-time digital trail that makes tax evasion significantly harder. Mexico's SAT (tax authority) estimates that CFDI has increased tax collection by 35% since full implementation.
Digital infrastructure investment. Rather than waiting for businesses to digitize on their own, LATAM governments built the infrastructure and mandated adoption. This top-down approach moved faster than the market-driven adoption seen in North America and Europe.
Corruption reduction. Paper invoices were routinely fabricated for tax fraud schemes. Digital invoicing with cryptographic validation and government authentication makes fabrication nearly impossible.
Real-time audit capability. Modern LATAM e-invoicing systems give tax authorities real-time visibility into every transaction. Mexico's SAT receives every CFDI at the moment of issuance. This enables proactive audit targeting and reduces reliance on annual tax returns.
The result is that any business selling in LATAM must comply with e-invoicing requirements. There is no opt-out, no minimum revenue threshold in most countries, and penalties for non-compliance are severe.
Country-by-Country Breakdown
Mexico: CFDI 4.0
Mexico has the most mature and complex e-invoicing system in LATAM.
Governing authority: SAT (Servicio de Administracion Tributaria)
Current version: CFDI 4.0 (mandatory since January 2023, with complements updated through 2025)
Key requirements:
- Every invoice must be digitally signed with a CSD (Certificado de Sello Digital) issued by SAT
- Invoices must be stamped by a PAC (Proveedor Autorizado de Certificacion) before delivery
- Real-time transmission to SAT upon issuance
- Mandatory fields include full RFC (tax ID) of both buyer and seller, fiscal regime, tax domicile ZIP code, and the CFDI usage code (Uso del CFDI)
- CFDI 4.0 requires the buyer's name to match SAT records exactly, character for character
XML structure: Mexican CFDI uses a proprietary XML schema defined by SAT. The base document includes Conceptos (line items), Impuestos (taxes structured as Traslados and Retenciones), and a Complemento section for specialized document types (payments, payroll, foreign trade).
Complements (Complementos):
- Complemento de Pago (REP): Required when payment is received at a different time from invoice issuance. This is the most complex complement and the one that causes the most errors
- Complemento de Nomina: For payroll receipts
- Complemento de Comercio Exterior: For export transactions
- Carta Porte: For goods in transit (mandatory since 2022)
PAC ecosystem: There are approximately 70 authorized PACs in Mexico. Major ones include Finkok, Diginat, Edicom, and SW SmartWeb. PAC fees range from $0.02 to $0.10 per stamp depending on volume. High-volume businesses (1M+ invoices/month) negotiate rates below $0.01.
Penalties: Failure to issue CFDI can result in fines of $17,000 to $97,000 MXN per invoice. Repeated violations can result in temporary closure of the business and cancellation of the CSD.
Colombia: DIAN Electronic Invoicing
Governing authority: DIAN (Direccion de Impuestos y Aduanas Nacionales)
Current version: UBL 2.1 based standard (adopted 2019, updated through 2025)
Key requirements:
- All taxpayers classified as "responsables de IVA" must issue electronic invoices
- Invoices must be validated by DIAN's platform before delivery to the buyer
- Use of XML based on UBL 2.1 standard (closer to international standards than Mexico's proprietary format)
- Digital signature using a certificate issued by an authorized certification entity
- Buyer must acknowledge receipt (acuse de recibo) through DIAN's platform
Technical integration:
- DIAN provides a free web portal for low-volume issuers
- API integration available through authorized technology providers
- Invoices must be transmitted in real-time and validated before they are considered legally valid
- DIAN returns a CUFE (Codigo Unico de Facturacion Electronica) as the unique identifier
Document types: Factura electronica de venta (sales invoice), nota debito (debit note), nota credito (credit note), and documento soporte (for purchases from non-taxpayers).
Penalties: Fines up to 15,000 UVT (approximately $230,000 USD in 2025) for systematic non-compliance.
Peru: SUNAT Electronic Invoicing
Governing authority: SUNAT (Superintendencia Nacional de Aduanas y de Administracion Tributaria)
Current version: UBL 2.1 based format
Key requirements:
- Mandatory for all businesses with annual revenue above 75 UIT (approximately $90,000 USD)
- Voluntary adoption available for smaller businesses
- OSE (Operador de Servicios Electronicos) model where authorized operators validate and transmit invoices to SUNAT
- PSE (Proveedor de Servicios Electronicos) for electronic transmission only
Document types: Factura electronica, boleta de venta electronica (simplified invoice for consumers), notas de credito and debito, guia de remision (shipping guide), and comprobante de retencion/percepcion.
Technical integration: SUNAT offers both a free portal (SEE-SOL) and API-based integration through OSEs. The XML schema follows UBL 2.1 with SUNAT-specific extensions. Digital signatures use X.509 certificates.
Key nuance: Peru requires a separate electronic waybill (guia de remision electronica) for goods transport, similar to Mexico's Carta Porte but with different technical requirements.
Panama: FEL (Factura Electronica)
Governing authority: DGI (Direccion General de Ingresos)
Current version: SFEP (Sistema de Facturacion Electronica de Panama)
Key requirements:
- Mandatory for all taxpayers classified as "contribuyentes" since 2022
- Invoices must be authorized by a PAC (Proveedor Autorizado Certificado)
- XML format specific to Panama DGI
- Real-time validation and transmission
- QR code mandatory on printed representations
PAC providers in Panama: The PAC ecosystem is smaller than Mexico's, with approximately 10-15 authorized providers. Major ones include Edicom, EFact, and local providers.
Penalties: Fines of $1,000 to $5,000 USD per infraction, with escalation for repeat violations.
Chile: SII Electronic Invoicing
Governing authority: SII (Servicio de Impuestos Internos)
Current version: DTE (Documento Tributario Electronico)
Key requirements:
- Mandatory for all businesses since 2018
- Invoices are XML documents signed with a digital certificate from an SII-authorized provider
- Transmission to SII within 3 business days of issuance (more relaxed than real-time requirement in Mexico)
- Buyer can accept or reject invoices through the SII platform (Registro de Compras y Ventas)
Technical integration: SII provides well-documented web services for invoice submission, status queries, and document retrieval. The XML schema is proprietary but well-maintained. Integration is generally considered more straightforward than Mexico or Colombia.
Unique feature: Chile's SII Mercado Publico platform integrates electronic invoicing with government procurement, so businesses selling to the government must use the same e-invoicing system.
Brazil: NF-e and NFS-e
Governing authority: SEFAZ (Secretaria da Fazenda) at the state level for goods; municipal governments for services
Current version: NF-e 4.0 for goods; NFS-e (varied by municipality)
Key challenge: Brazil's system is the most fragmented in LATAM. NF-e (Nota Fiscal Eletronica) handles goods and follows a national standard administered by SEFAZ. But NFS-e (Nota Fiscal de Servicos Eletronica) is managed at the municipal level, and each of Brazil's 5,570 municipalities can have its own format, rules, and integration requirements.
NF-e for goods:
- National XML schema, version 4.0
- Real-time authorization by state SEFAZ
- Digital certificate (e-CPF or e-CNPJ) required
- DANFE (Documento Auxiliar da Nota Fiscal Eletronica) as the printable representation
NFS-e for services:
- Historically each municipality had its own format
- National NFS-e standard (ABRASF layout) adopted by major cities but not universal
- Integration complexity multiplied by the number of municipalities you operate in
ICMS considerations: Brazil's ICMS (interstate goods tax) calculations are notoriously complex, with different rates for different product categories and interstate transactions. Your e-invoicing system must handle these calculations correctly.
Multi-Country Architecture for Regional Operations
If your business operates across multiple LATAM countries, building separate e-invoicing implementations per country is not sustainable. Here is the architecture pattern that works.
Abstraction Layer Design
Build a core invoicing engine with a plugin architecture:
Core layer (shared):
- Invoice data model (internal canonical format)
- Business rules engine (validation, calculation)
- Document lifecycle management (draft, issued, cancelled, credited)
- Audit trail and logging
- API for upstream systems (ERP, POS, e-commerce)
Country plugin (per-country):
- XML/UBL schema generation
- Digital signature application
- Tax authority API connector
- PAC/OSE/certification provider integration
- Country-specific tax calculations
- Local validation rules
This architecture means adding a new country requires building one new plugin, not redesigning the entire system. The custom systems approach allows the core to remain stable while country-specific logic is isolated.
Common XML Considerations
Despite different schemas, there are patterns across LATAM e-invoicing formats:
- All require XML digital signatures (XMLDSig or similar)
- All use X.509 certificates for signing
- All require unique document identifiers (UUID/CUFE/folio)
- All support credit notes and debit notes as correction mechanisms
- All require tax breakdowns at the line item and document level
Where they diverge:
- Mexico uses a proprietary schema; Colombia and Peru use UBL 2.1; Chile and Brazil use their own formats
- Cancellation procedures vary widely (Mexico requires buyer consent for cancellation; Colombia does not)
- Timing requirements range from real-time (Mexico, Colombia) to 3 business days (Chile)
Integration with ERPs
Most businesses connect their e-invoicing system to an ERP. Common integration patterns:
Direct API integration: The ERP calls the e-invoicing API when creating an invoice. Works well for modern cloud ERPs (SAP Business One Cloud, Oracle NetSuite, Odoo).
File-based integration: The ERP exports invoice data as CSV or XML files to a watched directory. The e-invoicing system picks them up, transforms them, and submits. Common with legacy ERPs.
Middleware/iPaaS: Tools like MuleSoft, Boomi, or open-source alternatives (Apache Camel) act as the translation layer. Suitable for complex environments with multiple ERPs per country.
ERP-native plugins: SAP, Oracle, and Microsoft Dynamics have built-in or marketplace plugins for LATAM e-invoicing. These can work for single-country deployments but often fall short for multi-country requirements.
Timeline of Key Mandates
| Country | Mandate | Status | |---------|---------|--------| | Chile | All businesses must use DTE | Active since 2018 | | Mexico | CFDI 4.0 mandatory | Active since Jan 2023 | | Brazil | NF-e 4.0 for goods | Active; NFS-e national standard ongoing | | Colombia | UBL 2.1 e-invoicing | Active since 2019, expanded through 2025 | | Peru | E-invoicing for businesses > 75 UIT | Active, threshold lowering | | Panama | SFEP mandatory for all taxpayers | Active since 2022 | | Ecuador | SRI e-invoicing | Active since 2022 | | Costa Rica | DGT e-invoicing | Active since 2018 | | Guatemala | FEL mandatory | Active since 2022 | | Uruguay | CFE (Comprobante Fiscal Electronico) | Active since 2019 |
The trend is clear: every LATAM country is moving to mandatory e-invoicing. If your country is not on this list yet, it will be soon.
Choosing a Compliance Platform
For businesses that do not want to build their own e-invoicing infrastructure, several platforms offer multi-country compliance solutions:
Enterprise platforms (1M+ invoices/year):
- Edicom: Covers 30+ countries, strong in LATAM
- Sovos (formerly Trunomi/Taxweb): Deep LATAM coverage, acquired multiple local providers
- Avalara: Growing LATAM presence, strong in tax calculation
Mid-market platforms (10K-1M invoices/year):
- Gosocket: LATAM-focused, good coverage in Central America
- Bind ERP: Mexico-focused with expanding coverage
- Alegra: Strong in Colombia, Peru, and Panama
Key evaluation criteria:
- Country coverage (do they support ALL your current and planned markets?)
- API quality (REST vs SOAP, documentation quality, sandbox environment)
- Certification maintenance (do they handle schema updates when tax authorities change requirements?)
- SLA for document processing (critical during tax authority downtime)
- Support hours and language (24/7 support in Spanish is a must)
- Pricing model (per-document vs. monthly flat rate vs. hybrid)
For multi-country operations processing more than 50,000 invoices per month, a combination of a commercial platform for standard invoicing plus custom development for complex scenarios (Carta Porte, Complemento de Pago, specialized industry requirements) typically yields the best results.
Penalties for Non-Compliance
Non-compliance with e-invoicing requirements in LATAM carries real consequences:
- Mexico: Fines per invoice, CSD cancellation (effectively shuts down your ability to invoice), criminal liability for fraudulent invoicing (up to 9 years in prison under the "factureras" law)
- Colombia: Fines up to 15,000 UVT, inability to deduct expenses without valid electronic invoices
- Brazil: Seizure of goods in transit without valid NF-e, fines of 50-100% of the invoice value
- Chile: Fines and inability to claim tax credits on purchases without valid DTE
- Peru: Fines and exclusion from government procurement
Beyond direct penalties, non-compliance creates operational problems: customers cannot deduct your invoices as expenses, which means they will stop buying from you and switch to a compliant supplier.
Ready to Simplify Multi-Country E-Invoicing?
At Soluciona Labs, we help businesses build and maintain compliant electronic invoicing systems across Latin America, from single-country deployments to multi-country platforms handling millions of documents. Reach out for a compliance assessment of your current invoicing infrastructure.