European groups opening a subsidiary in Chile quickly discover a sobering fact: the country made e-invoicing mandatory for large businesses as early as 2014, and for all taxpayers by 2018. Long before the EU began rolling out B2B e-invoicing requirements, Chile’s Servicio de Impuestos Internos (SII) had already migrated its entire business ecosystem to a real-time clearance model. This guide covers the obligations currently in force, the technical pitfalls to avoid, and the ERP options available to bring your Chilean subsidiary into compliance.
The SII: Latin America’s Most Mature E-Invoicing System
History: From Voluntary Pilot to Universal Mandate
Chile’s track record here is that of a true pioneer. Launched in 2003 as a voluntary pilot open to large enterprises, the SII’s Documentos Tributarios Electrónicos (DTE) system went through three waves of mandatory rollout:
- 2003: DTE pilot programme launched on a voluntary basis (CIAT, milestones Chilean SII)
- 2014: Mandatory for large businesses (annual revenue above 2.4 billion CLP) (SAP Community, Chile e-invoicing 2014)
- 2018: Extended to all VAT-registered taxpayers (Fonoa, Chile e-invoicing guide)
- 2022: Boleta electrónica made mandatory for all B2C transactions
This timeline puts Chile well ahead of the EU, where the ViDA directive will not generalise mandatory B2B e-invoicing until 2028–2030.
Documentos Tributarios Electrónicos (DTE): Official Document Types
The term DTE covers all fiscal documents managed by the SII. The main document types your ERP must support:
| Code | Document | Primary use |
|---|---|---|
| Type 33 | Factura electrónica afecta | Standard B2B with IVA 19% |
| Type 34 | Factura no afecta o exenta | B2B without IVA (exempt services) |
| Type 39 | Boleta electrónica afecta | B2C with IVA |
| Type 41 | Boleta electrónica exenta | B2C without IVA |
| Type 52 | Guía de despacho electrónica | Delivery note |
| Type 56 | Nota de débito electrónica | Debit note |
| Type 61 | Nota de crédito electrónica | Credit note |
| Type 110 | Factura de exportación electrónica | Export invoicing |
A Chilean subsidiary’s ERP must map these document types to its own chart of accounts and ensure consistency with monthly VAT returns (Formulario F29).
DTE Lifecycle: Generation, SII Stamp, Transmission, Acknowledgement
Unlike the European Peppol model (direct peer-to-peer transmission), the SII applies a clearance model: every DTE must be validated by the tax authority before it can be sent to the buyer.
- The ERP generates the DTE as a signed XML using the company’s digital certificate.
- The XML is submitted to the SII via its REST API (or through a certified middleware provider).
- The SII validates the signature and content, then applies its electronic stamp (timbre electrónico — validated folio).
- The issuer transmits the stamped DTE to the recipient.
- The recipient sends an acuse de recibo (acknowledgement of receipt) within 8 working days.
A DTE without a valid SII stamp has no legal value. The buyer cannot deduct IVA on a rejected or unstamped DTE — which creates a direct tax risk for your subsidiary and its local suppliers.
Legal Obligations in Force in 2026
Any Entity Holding a Chilean RUT Is Subject to DTE Rules
As soon as an entity obtains a RUT (Rol Único Tributario — Chile’s equivalent of a company tax number), it is subject to DTE obligations. This applies to subsidiaries of European groups, Chilean companies with foreign shareholders, and branches (agencias) of foreign companies registered in Chile. The law provides no exemptions for foreign-owned entities.
IVA (Chilean VAT) is set at 19% (SII.cl, IVA rate 2026). It is recoverable by VAT-registered companies through the Formulario F29 (monthly VAT return). The ERP must handle the Chilean chart of accounts, SII document codes, and F29 mechanics to ensure correct IVA recovery.
Boleta Electrónica Mandatory Since 2022 (B2C)
The boleta electrónica has been mandatory for all B2C transactions since 1 March 2022. Unlike the B2B factura (transmitted directly via the SII), the boleta must be accessible to the end consumer via the SII portal. Since May 2025, merchants equipped with POS terminals are also required to provide a printed copy to the customer (Círculo Verde, DTE obligations 2024).
Penalties: RUT Suspension, Fines, and Tax Non-Deductibility
The penalty regime is progressive based on the severity of the infringement (Fonoa, Chile e-invoicing penalties):
- Serious infringement (non-issuance of a DTE): up to 300% of the transaction amount, capped at 120 UTM
- Less serious infringement (incorrect amounts, missing mandatory fields): up to 150% of the amount, capped at 12 UTM
- Minor infringement (minor data errors): up to 50% of the amount, capped at 40 UTA
Beyond fines, the SII can suspend a company’s RUT, bringing all its Chilean operations to a halt. A rejected DTE that is not corrected leads to IVA non-deductibility on the buyer’s side — a tax exposure that far exceeds the administrative penalty itself.
Adapting Your ERP to SII Compliance
Mandatory Architecture: Digital Certificate + CAF
Two technical prerequisites are required before any DTE can be issued:
Chilean Qualified Digital Certificate
The ERP cannot sign DTEs without a certificate issued by a Certification Service Provider (CSP) accredited by the Chilean Ministry of Economy. The main accredited CSPs are Acepta (integrated into Sovos since 2023), E-Cert, and TokensChile. A European eIDAS certificate is not recognised by the SII.
CAF (Código de Autorización de Folios)
The SII does not allocate invoice numbers on the fly. Companies must request blocks of folios (pre-authorised sequential numbers) from the SII in advance. These folios are delivered as a signed XML file — the CAF. The ERP must:
- Store CAF files for each DTE document type
- Allocate folios sequentially without gaps
- Anticipate depletion and automatically trigger renewal requests
An ERP that does not manage the CAF lifecycle can find itself without available folios and unable to issue invoices in production — a complete operational standstill.
SAP S/4HANA in Chile: The DRC LATAM Module
SAP handles SII compliance through its DRC (Document and Reporting Compliance) module. The Chilean localisation covers DTE XML generation, digital certificate signing, SII submission, status tracking, and CAF management. SAP DRC integrates natively with SII-certified middleware partners, including Sovos/Acepta (SAP Community, Chile DTE implementation).
For a group already on S/4HANA, activating the Chilean localisation is the lowest-risk path — provided you budget for a configuration project with a certified LATAM integrator, since SII specifics do not activate with a few clicks.
Odoo and Business Central in Chile: Through Certified Local Partners
Microsoft Dynamics 365 Business Central has a LATAM localisation developed and maintained by certified Microsoft partners. The Chilean localisation covers DTE management, SII connectivity, and the local chart of accounts (KCP Dynamics, Business Central LATAM Chile). Always verify that the chosen partner has passed SII certification on the official validation environment.
Odoo (Community and Enterprise) is widely used among Chilean SMBs thanks to local modules developed by partners such as Iterchia or Trescloud. Quality varies by partner — always request a live demonstration in the SII certification environment before signing any contract.
SII Certification Middleware for European Groups
For groups that prefer not to manage SII connectivity directly from the ERP, a certification middleware provider is the standard approach:
| Provider | ERP Integration | LATAM Coverage | European Support |
|---|---|---|---|
| Sovos (ex-Acepta) | SAP, Oracle, Dynamics | Chile, Mexico, Brazil, Colombia, Argentina | Strong — EU presence (Sovos, Acepta acquisition) |
| EDICOM | SAP, Oracle, Sage, Dynamics | Full LATAM | Strong — headquartered in Spain |
| SureSystems | SAP, JDE, Oracle | Chile + Brazil | Moderate — Chile expertise |
| Pagero (Thomson Reuters) | SAP, Oracle, Dynamics | Partial LATAM | Strong — SAP integration |
For a European group active across multiple LATAM countries, Sovos or EDICOM offer the advantage of covering several jurisdictions on a single platform while simultaneously addressing European obligations (Peppol, ViDA).
5 Questions to Ask Before Opening a Chilean Subsidiary With a European ERP
1. Has my ERP already passed SII certification?
Any software issuing DTEs must complete the SII certification procedure on its official validation environment. Major ERPs (SAP, Dynamics, Oracle) have already done this. For mid-market or custom ERPs, budget 3 to 6 months for technical certification.
2. Does my company hold a Chilean digital certificate?
A European eIDAS certificate is not recognised by the SII. A certificate from an accredited Chilean CSP is mandatory before the first DTE in production.
3. Is CAF management automated in my ERP?
If CAF renewal is a manual process, that is an immediate operational risk. The CAF lifecycle must be automated, verified, and tested before go-live.
4. Does my finance team understand the Formulario F29?
The F29 is Chile’s monthly IVA return. Its logic differs significantly from VAT returns in the UK, Germany, the Netherlands, or other EU countries. Chile-specific accounting training is essential before the first month-end close.
5. Do I have a certified SII local partner for production incidents?
The SII communicates exclusively in Spanish. A technical incident in production — DTE rejection, folio blockage, or a change to the Anexo Técnico — requires a locally available contact who can respond quickly. Since November 2026, the SII has imposed new transport detail requirements on DTEs (LLB Solutions, Anexo Técnico 2.5) — a local partner is essential to absorb these regulatory updates without disruption.
Quick Comparison: Chile and the Other Major LATAM Economies
European groups operating across the region typically manage several e-invoicing systems in parallel. All major LATAM countries apply a clearance model — but formats, agencies, and technical requirements differ significantly:
| Country | Authority | Universal mandate | Standard | Key distinction |
|---|---|---|---|---|
| Chile | SII | 2018 | DTE / XML SII | Mandatory CAF, software certification |
| Mexico | SAT | 2014 | CFDI 4.0 | Sector-specific fiscal complements |
| Brazil | SEFAZ | 2010 | NF-e, NFS-e, CT-e | Over 60 different document types |
| Colombia | DIAN | 2021 | DIAN XML UBL | Asynchronous validation possible |
| EU (ViDA) | National tax auth. | 2028–2030 | Factur-X, Peppol | Model Y — portal + accredited PDPs |
For a European group simultaneously opening subsidiaries in Chile, Mexico, and Brazil, managing three distinct and incompatible systems justifies investing in a multi-LATAM middleware platform from day one.
To go deeper on ERP compliance across other LATAM markets, see our ERP and CFDI 4.0 guide for Mexico subsidiaries and our SPED and NF-e guide for European companies in Brazil. To frame the end-to-end ERP deployment for a foreign subsidiary, our international ERP deployment guide (rollout, local instances) covers the key project milestones.
