SII 2027 in Chile: what SMBs should prepare in 2026

The Law 21.713 clock — what's coming in 2027

SII closes the digital reform cycle of Law 21.713 in 2027. The full roadmap has not been published yet. Read the text today and you migrate calmly. Wait for the Resolución Exenta 60 days before the deadline and you end up queued behind thousands of other SMBs for the two Odoo Gold Partners in Chile.

In April 2026 the Kast government made the 12.5% PYME income-tax rate permanent (régimen 14D). The political signal is clear: the state wants a formalized, digital SMB sector. The price for the rate cut is compliance overhead. Every SII wave forces system changes. January 1, 2026 ended the obligation to print the electronic mark on in-person boletas (Resolución Exenta 207/2025). March 1, 2026 introduced the electronic boleta through digital channels — WhatsApp, SMS, email, QR — under Resolución Exenta 53/2026. May 1, 2026 brought the expanded guía de despacho with driver, vehicle, and trip-type fields.

On the 2027 horizon comes the next step: full marketplace reporting through the SII portal, mandatory Registro de Beneficiarios Finales (RBF) for every legal entity with no capital threshold, the DTE XML schema upgrade to version 2.0, and broader VAT withholding on non-resident digital-service providers. Penalties run from 1 to 60 UTM — CLP 67,000 to 4,000,000, roughly USD 75 to 4,500 at 890 CLP per USD in May 2026. DTE folio blocking lasts until the root cause is fixed — meaning no invoices and operational freeze for as long as it takes.

This article is a preview of what SII is preparing. It rests on the text of Law 21.713, the Resoluciones Exentas published in 2025–2026, and the SII's historical cadence (60–90 days between publication and effective date). Exact 2027 dates will be confirmed by SII publications in Q4 2026. If you plan adaptation with a partner, the window is already open.

One-minute summary

• Law 21.713 ("Law on Compliance with Tax Obligations", published October 24, 2024) frames the reform through 2028. Phasing runs quarter by quarter.
• 2026 brings three waves: January (end of the printed electronic mark), March (boleta via digital channels), May (expanded guía de despacho).
• 2027 targets four milestones: migration to DTE schema 2.0, mandatory RBF with no threshold, universal marketplace reporting, broader VAT on digital services for more non-resident providers.
• The 12.5% PYME tax rate became permanent in April 2026 — it widens the ICP for serious ERP consulting in the country.
• Odoo's l10n_cl covers roughly 80% of the base. Marketplace integration and WhatsApp channel are separate work.
• The prep window runs June through December 2026. Adapting in Q1 2027 means joining the queue behind thousands of SMBs at Chile's two Gold Partners.

Context: Law 21.713, the reform map through 2028

Law 21.713 was published in the Diario Oficial on October 24, 2024 under the full name "Ley que establece normas para asegurar el cumplimiento de las obligaciones tributarias y otorga incentivos para el cumplimiento voluntario". It is the largest Chilean tax modernization since the 2014 Bachelet reform. The text bundles 28 articles plus a set of transitorios, with full implementation scheduled over four years — 2025 to 2028.

The key blocks that shape the SII 2027 roadmap:

1. General Anti-Avoidance Rule (NGA) reinforced — the "economic reasonableness" threshold drops; SII gains authority to revisit operations with suspicious structures.
2. Registro de Beneficiarios Finales (RBF) — every legal entity must declare its ultimate beneficial owners; the registry is available to SII and to the Unidad de Análisis Financiero (UAF).
3. DTE modernization — new XML schema, real-time validation API, broader transmitted-data scope.
4. Marketplace reporting — intermediating platforms file on behalf of their sellers.
5. VAT on digital services — expanded list of taxable services for non-residents.
6. AEOI / CRS expansion — broader information exchange with the OECD.
7. Crypto and digital assets — separate asset disclosure in an annex to the F22.
8. Whistleblower protections — protections and incentives for people who report avoidance schemes.

Four of the eight blocks are already partly live in 2025–2026 (NGA, partial RBF for CMF-regulated entities, initial marketplace, streaming VAT). The other four close phase in 2027. Historically the SII publishes Resoluciones Exentas 60–90 days before the effective date — if a new phase starts in January–March 2027, official documentation will land between October and December 2026.

Timeline 2026 → 2027: wave after wave

January 2026 — already in force. End of the obligation to print the electronic mark on in-person boletas (Resolución Exenta 207/2025). Initial fiscal-reporting duties begin for marketplace platforms, but only domestic platforms with annual revenue above UF 300,000 are covered at this stage.

March 2026 — already in force. Electronic boleta via digital channels (Resolución Exenta 53/2026): email, SMS, WhatsApp, QR. Printing becomes optional at the buyer's choice. Control runs through the DTE flags MedioPago and CanalDespacho.

May 1, 2026 — critical deadline. Electronic guía de despacho with expanded fields: origin and destination at street level (not just comuna), transport company RUT, driver RUT and name, vehicle plate, and trip type (sale / transfer / return / consignment / sample). Applies to all guías. The deadline matters most in retail e-commerce because Mercado Libre Chile and Cornershop already require compliant guías from their sellers.

Q3–Q4 2026 — projected. Publication of the DTE 2.0 schema in beta (SII sandbox). Opening of the RBF registry for legal entities with capital above UF 5,000. Marketplace reporting expanded to platforms with annual revenue above UF 100,000.

January 2027 — projected. Mandatory migration of all taxpayers to the DTE 2.0 schema. RBF mandatory for every legal entity with no threshold. Digital-service VAT expands from B2B SaaS to cross-border professional services.

May–July 2027 — projected. Real-time DTE validation via a new API (replacing today's Envío service). Digital-asset reporting (crypto and tokenized) — a new form F47 or annex to the F22.

Technical work in Odoo: what to configure

Odoo l10n_cl already covers the basic DTE stack, but 2027 calls for extensions. Layer by Layer:

#1. DTE schema 2.0 — XML upgrade

The current DTE XML schema (version 1.0, approved by Circular SII 75/2003 with patches) holds around 200 fields. Schema 2.0, expected in sandbox in the second half of 2026, adds:

• Expanded BeneficiarioFinal block — RUT and ownership share when the recipient is a legal entity.
• MedioEntrega — channel through which the document was delivered (email / SMS / WhatsApp / portal).
• ReferenciaOrden — marketplace order ID for platforms.
• Geolocalizacion — for guías, coordinates of origin and destination.
• MetadataAuditoria — creation timestamp, system hash, sequence integrity.

What this means for Odoo: the l10n_cl_edi module (community + enterprise) needs an upgrade. On Odoo 17 or 18, the official update lands from Odoo SA in Q3–Q4 2026. On Odoo 14–16, the choice is migrate or pay a partner to backport. Backporting l10n_cl to Odoo 14 runs USD 8,000 to 15,000 in development, not counting regression testing.

#2. Digital boleta — channel integration

l10n_cl_boletas ships with email delivery. WhatsApp Business API, an SMS gateway, and the QR shortlink are separate add-ons. Options:

• WhatsApp: the whatsapp enterprise module (Odoo 17+) with a boleta_dte template approved through Meta Business Manager.
• SMS: an external gateway (Twilio, MessageBird) via sms_api_twilio or a custom connector.
• QR: auto-generated link to the boleta PDF on a public Odoo URL — built into l10n_cl_boletas.

WhatsApp messaging in Chile runs around CLP 50 per conversation (USD 0.06). For a retail PYME with 5,000 boletas a month that means about USD 300/month in operating cost.

#3. Guía de despacho — expanded data

Fields required from May 2026: RutTransportista, NombreChofer, PatenteVehiculo, RutChofer, IdAdicional (trip type). On stock.picking in Odoo, add the new fields through a custom module and map them in the XML by overriding _l10n_cl_edi_post_create_xml. Budget: 40–60 hours of development plus SII sandbox certification.

#4. Registro de Beneficiarios Finales (RBF)

RBF is a separate SII registry, not part of DTE. Odoo integration runs through a partner extension: a beneficiario_final_rut field on res.partner for legal entities, mandatory annual refresh under Law 21.713, and reporting through CSV export or an API once SII opens the endpoint in the second half of 2026.

#5. Marketplace reporting

Selling through Mercado Libre, Amazon, Falabella.com, or Cencosud.cl means the platform reports on your behalf. That creates double reporting: your boleta and the marketplace report must match. Without reconciliation, SII catches the gap and asks for an explanation. In Odoo, this is solved with integrations like mercado_libre_connector (community modules of variable quality) or a custom integration against the MELI Developer API plus Odoo's connector framework.

#6. VAT on digital services and withholding

Buying SaaS from non-residents (HubSpot, Salesforce, Atlassian, AWS) means Odoo must withhold VAT through fiscal_position_chile_extranjero and the IVA_retenido_19 tax. Most PYMEs miss this and pay the full invoice without withholding — the audit penalty runs 30% of undeclared VAT. Setup details live in the Odoo Chile fiscal localization docs.

When it fits and when it doesn't

SII 2027 hits different business profiles differently. The table reads the impact by archetype.

For marketplace-only or legacy-vendor cases, the Odoo rescue playbook is worth reading before any decision.

Five typical mistakes

#1. Ignoring RBF until the last minute

Registro de Beneficiarios Finales is not DTE — it is a separate registry. Many SMBs assume "the accountant handles it". The RBF refreshes every 12 months and the late-filing fine runs 1 to 60 UTM (CLP 67,000 to 4,000,000). Real case: a family company with three-holding structure — the accountant filed RBF incorrectly, SII asked for proof of ownership, the fine landed at CLP 1,800,000 (USD 2,020).

#2. Vendor lock — Defontana, Manager, Nubox without an exit strategy

Closed vendors update on their own schedule. If Defontana isn't ready for DTE 2.0 by January 2027, there is no way to force an upgrade. The open-source stack (Odoo + l10n_cl) keeps you in control. Real case: an e-commerce client on Defontana — the vendor delayed the expanded-guía release by two weeks past May 2026, the client received four rejected guías in that window and lost three days of shipping.

#3. WhatsApp boleta without proper template approval

Meta Business requires template approval for transactional messaging. Many SMBs wire Odoo to WhatsApp, send the first boletas — and 48 hours later the WhatsApp Business account is blocked for "promotional content without opt-in". The correct path: template in utility category, content like Tu boleta {{1}} de {{2}} está disponible aquí: {{3}}, Meta approval in 24–72 hours.

#4. Hard-coded rules in custom Odoo modules

If a partner wrote a custom DTE generation module in 2020 with hard-coded XML schema, the 2.0 update is a rewrite. Real case: a company paid USD 35,000 for a custom module in 2020. In 2026 the original partner dropped support; the new partner quoted USD 22,000 to refactor for schema 2.0. The fix: use stable l10n_cl_edi community/enterprise and override only specific methods — never reinvent the XML generator.

#5. Failing to reconcile F29/F22 against DTE

The monthly F29 (VAT) and annual F22 (Income) must match the DTE records held by SII. Any gap (for example, vendor invoices not loaded in Odoo but visible in the SII RCV) gets flagged and a question follows. With the metadata-audit field of DTE 2.0, SII automates that match on its side and divergences show up instantly. The fix: monthly Odoo vs SII RCV reconciliation (via l10n_cl_rcv_import).

Case: Santiago retail PYME — migration to a 2027-ready stack

Client: a cosmetics retailer in Providencia, Santiago. 12 employees, two physical stores, Shopify e-commerce, and sales through Mercado Libre Chile. Annual revenue near USD 1.2M. Going into 2025 they ran Defontana for DTE and a custom Shopify-to-Defontana sync stitched together in Zapier.

2025 baseline. Defontana updated slowly. The Zapier sync broke whenever the product catalogue changed. Manual reconciliation between Shopify, MELI, and Defontana took the accountant 12 hours per month. The Zapier writer code was written by an employee who had since left, with no documentation.

Solution (Q1 2026 → Q2 2026). Migration to Odoo 18 Community Edition with l10n_cl_edi (community fork) and l10n_cl_boletas. Shopify integration via shopify_connector_odoo. Custom MELI connector through the MELI Developer API — four weeks of development. Digital boleta via WhatsApp Business API with a Meta-approved utility template. Custom stock.picking extension for the May-2026 guía fields. Reconciliation pipeline: a nightly cron crossing Odoo invoices against SII RCV. RBF setup: two beneficial owners identified (50/50 partnership).

Outcome (as of May 2026). Manual reconciliation dropped from 12 hours/month to 1.5 hours/month (−87%). DTE rejection rate fell from 4.2% to 0.6% (−86%). The client hit the May 2026 deadline at 100% readiness, two weeks ahead. The RBF cleared on first submission with no SII queries.

Cost. USD 28,500 one-time plus USD 1,200/month in support. ROI: 11 months, funded by reclaimed accountant hours and zero rejections. For 2027 the client is ready — they only need an upgrade of the l10n_cl_edi community fork and a small marketplace-reporting endpoint adjustment when SII publishes it.

SII 2027 readiness checklist

To gauge readiness for 2027 we built a 24-point checklist across six blocks (DTE 2.0, digital boleta, expanded guía, RBF, marketplace reporting, digital-service VAT). Download the SII 2027 Readiness Checklist free (email-gated). For a personal diagnostic, book an Odoo audit — 30 minutes to review your current stack.

Closing: what to do in the next 7 days

SII 2027 is not a surprise reform. It closes the cycle of Law 21.713 published 18 months ago. Anyone who read the text in October 2024 is already planning the migration. Anyone who learns about it from this article in May 2026 still has time.

Next seven days:

1. Ask your accountant for the company's Law 21.713 compliance audit status.
2. Download the SII 2027 Readiness Checklist and walk through it.
3. Run a gap analysis on your current DTE infrastructure.
4. If you use Defontana / Manager / Nubox, request their DTE 2.0 roadmap.
5. If you use Odoo, confirm your version and upgrade plan.
6. Compare your readiness against the critical 2027 dates.

Related reading: Odoo in Chile — country pillar, Audit your Odoo in 30 minutes, Odoo rescue playbook, Odoo implementation for SMBs, SII compliance course for SMBs. For the technical detail see SII 2026 — what is already in force and Pricing intelligence for Chile retail.

FAQ