Electronic boleta SII: what changes from March 2026 in Chile — SMB guide

What changes from March 2026

Starting March 23, 2026, every in-person point of sale in Chile without a thermal printer must deliver the electronic boleta to the customer through a digital channel — email, SMS, WhatsApp, or QR. As of May 27, the preparation window has closed: non-compliance is a Tax Code Art. 97 penalty of up to 5 UTM (about CLP 335,000) per breach. Separately, the expanded electronic dispatch guide took effect on May 1.

Chile's tax authority (Servicio de Impuestos Internos, SII) rolled out three waves of changes to the DTE (Documento Tributario Electrónico) regime in 2026. This is not cosmetic. It is the final cut-off for the remaining analog tail in retail. Print-only is officially dead.

Below: the three 2026 waves in detail, the Odoo technical requirements under l10n_cl, the most common migration mistakes, and an anonymous case of a Chilean retail chain that closed compliance in six weeks.

One-minute summary:

• January 1, 2026. The mandatory printed electronic stamp on the paper boleta was removed. Marketplaces (Mercado Libre, Falabella, Ripley, Cencosud) now must report SMB-seller transactions to the SII.
• March 23, 2026 (SII Exempt Resolution N° 53). In-person merchants without a thermal printer must deliver the boleta through a digital channel.
• May 1, 2026. The electronic dispatch guide (DTE 52) now requires expanded fields — origin/destination, carrier, vehicle plate, nature of the movement.
• Penalties. Tax Code Art. 97 — up to 5 UTM (about CLP 335,000, ~USD 375) per breach. The UTM in May 2026 sits near CLP 67,000.
• Minimum Odoo stack: l10n_cl + email/WhatsApp + retry queue + delivery audit log.

2026 timeline: the three waves, no fluff

The electronic boleta has been mandatory since March 2021 (Law 21,210, Tax Modernization). By 2024, roughly 90% of SMBs were issuing DTEs through the SII Mipyme portal or commercial platforms. What happened in 2026 was the closure of the remaining analog gaps — not a brand-new requirement.

#1. January 2026 — end of the stamp, marketplaces report

From January 1, the SII removed the requirement to print the electronic stamp on the paper representation of the boleta. The paper ticket is now a human-readable copy; the legal record lives in the SII's digital trail.

The same decree forced marketplaces (Mercado Libre Chile, Falabella, Ripley, Cencosud) to deliver SMB-seller transaction data to the SII. The "I sell through the platform and skip the boleta" loophole is gone — the platform reports on its own.

#2. March 23, 2026 — the headline change for retail

The SII Exempt Resolution N° 53 introduced the rule: an in-person merchant without a thermal printer must send the boleta through a digital channel at the moment of sale. Accepted channels:

• Email (standard SMTP).
• SMS.
• WhatsApp (via a verified Business API).
• QR on the POS screen, scanned by the customer.

It applies to: tablet-register stores without a printer, mobile POS, street-market vendors, service businesses (barbershops, repair shops) using a card reader.

#3. May 1, 2026 — expanded electronic dispatch guide

From May 1, the electronic dispatch guide (DTE 52) must include precise origin and destination addresses, carrier ID (a company RUT or a driver's RUN), vehicle license plate, and the nature of the movement (sale, consignment, repair, internal transfer). The SII's stated goal: close the "gray" movement of goods without clear paperwork.

Technical requirements in Odoo (l10n_cl)

The base setup for Chile is the l10n_cl module (community + Enterprise extensions from Odoo SA and the OCA, Odoo Community Association). Without it, any attempt at Chilean localization is a workaround. If you are starting from scratch, read Odoo in Chile first for the full-stack picture.

#1. l10n_cl and SII folios

l10n_cl installs the chart of accounts (Chilean PCGA), the DTE types, and the SII API integration. From there:

1. Get an SII-accredited digital certificate (the DTE's electronic signature).
2. Request folios on the SII "Mantenedor de Folios" portal — one batch per type: 33 (invoice), 39 (taxable boleta), 41 (exempt boleta), 52 (dispatch guide).
3. Load the folios into Odoo: Accounting → Configuration → DTE Folios.
4. Activate the sequence per DTE type.

Without folios loaded, Odoo cannot generate a valid DTE — there is nothing to assign the correlative number from.

#2. Delivery channels: where migrations break

Email is standard (SMTP under General Settings). WhatsApp needs a separate integration:

• WhatsApp Business API. You need a Meta Business Account, a verified phone number, and approved templates. Apps: whatsapp_odoo from Cybrosys or odoo_whatsapp from the OCA. Meta verification takes 2 to 4 weeks — it is the longest critical path in the whole migration.
• SMS. Odoo IAP SMS works, but a local provider (Comuniko, Kannel) is usually cheaper per message.
• QR. Generated on the POS screen at checkout and pointing to a cloud-hosted PDF. Implemented with pos_qr_invoice or a custom extension.

#3. Retry queue and audit log

The most-skipped piece. Email bounces, WhatsApp templates get rejected, SMS goes undelivered. The SII does not care about the reason — the boleta has to arrive. The minimum:

• A retry policy on mail.mail: three attempts with back-off.
• A log of every attempt (delivery_status, delivery_attempts, last_attempt_at).
• A cron job that resends failed boletas within the next 24 hours.
• An alert when failures cross 2% per day.

#4. Dispatch guide: new fields in l10n_cl_edi_stock

For the May changes, extend l10n_cl_edi_stock with: transportista_rut, vehiculo_patente, tipo_traslado (selection), direccion_origen, direccion_destino (street + comuna + city at minimum). Without those fields the SII rejects the XML — and the goods cannot move legally.

When digital delivery applies, when it does not

Resolution 53 is not universal. Five typical scenarios in a Chilean SMB:

Retail store with a thermal printer. Digital delivery does not apply. You hand over the paper ticket and the digital record posts to the SII in the background. But: if you also run an online channel, that channel must still deliver digitally.

E-commerce. Compliant by default — the boleta is generated and emailed to the customer automatically. Just make sure partner.email is required and validated at checkout.

Restaurant with tablet registers. No thermal printer means digital delivery is required. The lowest-friction setup: QR on screen at check-close plus an email/WhatsApp option. Walk-in customers rarely give an email — the QR saves you.

Open-air market or ambulant vendor. The hardest case: no fixed location, unstable Wi-Fi, customers without a smartphone. The SII allows a contingency mode (offline) with upload within 24 hours, but that does not waive digital delivery. The working setup: a mobile app, SMS (works on feature phones), and an offline queue.

Marketplace-only seller. The "the SII does not see me" assumption stopped working in January 2026. The platform reports your RUT and the sale amount. If you did not issue a DTE, the gap is visible — and the penalty applies.

Common migration mistakes

Five patterns that repeat when helping Chilean SMBs ship 2026 compliance:

1. "I installed l10n_cl and forgot the folios." Odoo is configured, ready, and the first DTE submit returns "No folios available." Folios have to be requested and loaded manually. The SII issues batches of 100 to 500 numbers, which a busy register burns through fast.

2. "I use WhatsApp without a verified Business API." A personal WhatsApp account for boletas violates Meta's terms of service and does not count as an official channel in front of the SII. Only verified Business API works: Meta direct or via Twilio, MessageBird, 360dialog.

3. "I fill the dispatch guide with the minimum fields." Through April, writing "internal transfer" in the comment field was enough. From May 1, the SII rejects XMLs without structured fields. The result: the goods are legally stuck, delivery is delayed, the customer is angry.

4. "I never set up retries." An email bounce means an undelivered boleta. The SII does not care that the customer's inbox is full. Retries and an alternative channel are mandatory.

5. "I do not track CLP/USD on cross-border sales." Platforms like Mercado Libre Internacional bill in USD; the boleta is issued in CLP. With CLP projected in the 806–941 range by late 2026, the gap between the sale date and the cash-in date creates an accounting drift the bookkeeper catches late.

Anonymous case: 40-store retail chain, 6-week migration

An anonymous home-electronics chain in Santiago and the regions. Pre-2026 stack: Odoo 17 Enterprise + base l10n_cl + physical POS with thermal printers. The problem: 14 of the 40 stores were pop-ups in shopping malls running tablets without printers.

Six-week plan, starting in February:

1. Connection audit at each store (Wi-Fi stability, 4G fallback).
2. Install whatsapp_odoo and complete Meta Business API verification (a single central account).
3. Get the "Tu boleta SII" template approved by Meta (no promotional content — otherwise rejection).
4. Per-store config: email primary, WhatsApp secondary, QR fallback for walk-ins.
5. A retry cron plus a Slack alert when failures crossed 5% per hour.
6. Pilot in 3 stores in February, full rollout by mid-March.

Results as of May 27, 2026:

Meta verification is the critical path. If you did not start in December, you did not make March.

Next step: checklist and audit

Are you a Chilean SMB without clear compliance footing? Download the SII 2026 Checklist — a step-by-step audit for retail and services, with the three 2026 waves and cases broken down by point-of-sale type. If you need concrete support on l10n_cl, book a 30-minute Odoo audit — we review the configuration and hand you a punch list.

Neighbouring countries with similar 2026 compliance waves: SUNAT 2026 Peru, ARCA/AFIP Argentina, CFDI 4.0 Mexico. This is not legal advice — for case-specific questions (especially cross-border and marketplace exposure) consult your accountant.

Frequently asked questions