SII 2026: the full compliance checklist for SMBs in Chile

One-minute summary — three waves, one register

Chile's SII rolled three regulatory waves in 2026 — January, March, and May — and each one opened its own window for fines of up to 60 UTM (~USD 4,500) per infraction. If your Odoo still runs on stock l10n_cl with no extensions, penalties are already accruing. This checklist closes the gap step by step.

• January (Resolución Exenta 207) — the mandatory fiscal mark print on the boleta electrónica is dropped, and marketplaces pick up new reporting obligations.
• March (Resolución Exenta 53) — merchants with no thermal printer must deliver the boleta via email, SMS, WhatsApp, or QR code.
• May 1 — the electronic shipping note (DTE 52, guía de despacho) now requires driver RUT, license plate, nature of the movement, and exact addresses.
• The fine — Art. 97 No. 10 of the Tax Code: up to 60 UTM (~USD 4,500) per infraction, CAF folio block, and possible cargo embargo at roadside inspection.
• Technical reality — Odoo's stock l10n_cl does not cover any of the three waves without extension work. We walk it through field by field below.

What changed in 2026 — wave-by-wave timeline

Starting January 1, 2026 the SII activated the densest regulatory sequence of the last five years. This is not a single deadline — it's three parallel chains, each with its own scope and its own penalty. Miss January and March, and the damage is already running. May is the surgical one: a malformed guía can leave a truck stranded at the warehouse gate. For regional context, the same pattern repeats with local twists in our DGI Panama 2026 checklist and our SUNAT 2026 timeline.

#1. January wave — boleta electrónica and marketplaces

Under Resolución Exenta No. 207, the SII touched two independent fronts.

End of mandatory fiscal-mark printing. When issuing a boleta electrónica at the register, the visual SII mark no longer has to be printed. The merchant gains format flexibility: paper, screen, or QR code.

New marketplace tax duties. Platforms like Mercado Libre, Falabella, Ripley, and Linio must report extended seller and transaction data to the SII. The goal is closing the grey zone of online commerce, where the SII used to see only aggregates.

What this means for an SMB — if you sell on a marketplace and also via your own site or a physical store, your taxable base is now cross-checked automatically across channels. One undeclared Mercado Libre order triggers an SII alert the next day.

#2. March wave — digital boleta delivery

Under Resolución Exenta No. 53, merchants with no printing equipment must deliver the boleta via a digital channel: email, SMS, WhatsApp Business, or a QR the customer scans from the POS screen.

Most-exposed sectors:

• Delivery and dark kitchens — no physical handoff point for paper.
• Professional services (hair salons, stylists, tutors) — no traditional register.
• Marketplace sellers — issuance happens off-premise.
• E-commerce — the boleta is generated when the online payment confirms.

If you already run POS + thermal printer, this deadline passed you by. If you're digital-first, you need automated delivery via an ESP or the WhatsApp Business API.

#3. May wave — electronic shipping note

The toughest deadline of the year. The SII required a surgical expansion of the electronic shipping note (DTE 52). New mandatory fields:

Without those fields, the DTE fails SII validation. Without an accepted guía, the truck does not legally leave the warehouse — and at roadside inspection, a missing valid guía opens the door to the Art. 97 No. 10 penalty in the Tax Code.

Minimum Odoo stack to comply

To cover all three waves in Odoo Enterprise, you need six components working together. Drop one, and the others can't compensate. Our Odoo Chile implementation always starts from this stack.

#1. The l10n_cl module and its extensions

Stock l10n_cl (Odoo Enterprise) supports DTE types 33, 34, 39, 41, 52, 56, and 61, the SII certificate connection, XML generation per schema, and CAF-based folio numbering. But it does not cover three things: the 2026 extended guía fields (you add custom fields), WhatsApp Business delivery (you integrate the API), and marketplace reconciliation (middleware or a dedicated connector).

#2. Digital certificate and SII connection

Without a valid .pfx file from an accredited CA (E-Sign, E-Certchile, Acepta), Odoo sends zero DTEs. The certificate lasts 1 to 3 years. Check the expiration date today — this is the root cause that left several SMBs blocked in December 2025.

#3. CAF — folio authorization code

A CAF is a batch of folios authorized by the SII for a specific DTE type. When folios run out, Odoo stops generating new documents and the register is blocked. The boleta requires a separate CAF for each document type (39, 41).

#4. Digital delivery channel

To comply with Resolución 53, you need at least one channel live:

• Email — outbound SMTP, boleta templates, PDF attachment. Setup: ~USD 300.
• WhatsApp Business API — via Twilio, MessageBird, or direct Meta integration. Enterprise whatsapp_marketing module + workflow. USD 2,500–3,500.
• SMS — Twilio Programmable SMS with a short URL to a signed PDF. ~USD 500.
• QR — POS display with a link to the PDF. ~USD 400.

#5. Electronic shipping note — extended fields

For the May deadline: extend stock.picking with custom fields (driver_rut, driver_name, vehicle_plate, vehicle_type, movement_nature). Link res.partner to a carrier type with RUT validation. Update the XML template for DTE 52. Test in the SII certification environment before production — 2–4 weeks of real testing. Reference docs live in Odoo's Chile localization guide.

#6. Marketplace reconciliation

If you sell on Mercado Libre, Falabella, or Ripley: connect the marketplace API with a packaged module or a custom connector. Each marketplace order creates a sale.order in Odoo. Each sale automatically issues the boleta or factura and ships it to the SII. Run a daily report that reconciles marketplace volume vs Odoo volume — without that cross-check, duplicates surface only at month close.

When it works — and when it doesn't

The stack above is not priced equally for every operation. Before committing budget, place yourself in one of these three profiles. For a quick diagnostic, we run a 30-minute Odoo audit.

It works: retail with typical e-commerce

One store + Shopify or WooCommerce, B2C, 50 to 500 boletas a day. Stack: Odoo Enterprise with l10n_cl, a one-week custom build for email delivery, no marketplace. Budget: USD 1,500–3,000 upfront + USD 200/mo support. Timeline: 3–5 weeks. It works because the volume fits standard modules, email is the simplest channel, and customization stays minimal.

It needs tuning: multichannel marketplace seller

You sell on Mercado Libre + Falabella + your own site. Volume between 500 and 5,000 daily transactions. Stock l10n_cl breaks: Mercado Libre emits its own tax data in parallel and, without reconciliation, you end up with duplicate DTEs and inconsistent taxable bases. Fix: middleware between marketplace and Odoo. Either built in-house (Python + Celery + queue) or commercial (Tickets API, EDIX, local integrators). Budget: USD 5,000–15,000, timeline 8–14 weeks.

It does not cover: transport company with 50+ daily trips

If you're a carrier with an in-house fleet generating 50+ guías a day, you need a TMS on top of Odoo. Stock l10n_cl + stock does not deliver the per-trip traceability (driver, vehicle, nature) the SII demands from May onward. Fix: Odoo Studio customization + GPS integration (CargoFleet, Cordial, Wialon Chile). Budget: USD 10,000–25,000, timeline 8–12 weeks.

If you've already missed a deadline

Don't panic — but don't ignore it. The SII opens a self-disclosure window via Operación Renta. Document the exact date of non-compliance and the affected volume. Prepare period-by-period rectificatorias. Hire a compliance consultant (an Odoo partner with SII certification) — USD 2,000 on a well-built rebuttal beats USD 10,000 in accumulated fines. Then: stabilize first, monthly audit second.

5 common findings the SII catches

After reviewing several Odoo implementations in Chile, these five patterns repeat the most under audit. None of them are exotic — all of them are operational.

#1. Expired digital certificate

The most common error between December and January. The certificate expires, Odoo silently stops sending DTEs, the SII logs automatic non-compliance, and the fine lands 30 days later. Fix: an Odoo cron that fires alerts at 60, 30, and 14 days to expiry, escalating to the CFO if no one responds.

#2. Boleta CAF exhausted

A CAF is a batch of folios. When it runs out, Odoo cannot generate the next DTE — the register is blocked. Many SMBs request the new CAF on the same day the old one runs out and lose 4–8 hours waiting for SII approval. Fix: auto-request the next CAF at 80% usage of the current batch.

#3. Marketplace taxable base ≠ Odoo taxable base

Mercado Libre reports tax data to the SII for its transactions. If you issue boletas in Odoo in parallel for the same sales, you get duplicates. The SII sees a taxable base × 2, opens an observation, and you burn a week in rebuttals. Fix: an explicit, written rule — either the marketplace issues, or you do, never both. File it formally with the SII.

#4. Shipping note without driver RUT (after May 1)

From May, the SII rejects guías without full driver data. The truck stalls at the gate; the operation freezes. Especially painful for SMBs that hire drivers via app (Uber-style logistics). Fix: pre-populated driver registry inside Odoo, validation at guía creation, and an integration with the freelance pool.

#5. Boleta delivered to customer, rejected by the SII

A classic race condition: Odoo ships the DTE to the customer by email, but the SII submission returns with an XML schema error. The customer thinks the boleta is valid. The SII thinks it doesn't exist. 90 days later, the non-issuance fine arrives. Fix: a retry queue, a daily report that reconciles "sent to customer" vs "accepted by SII," and an alert dashboard when the delta is greater than zero.

Anonymous case: 12-store retail chain, Santiago

Situation (January 2026). Apparel retail chain, 12 stores in the Metropolitan Region, ~150 boletas per store per day, ~1,800 transactions total. Stack: Odoo 16 Enterprise with stock l10n_cl, no custom extensions. The team learned about Resolución 207 from the press and started late.

What they did, in order.

1. Audit of the existing Odoo (1 week): three expired certificates, CAF at 95% usage, no digital delivery channel.
2. Bought new certificates from E-Certchile (3 days).
3. Rolled out email-based boleta delivery (2 weeks of dev + tests).
4. Mercado Libre connector for marketplace reconciliation (4 weeks).
5. Extended the shipping note with the May fields (3 weeks in parallel).

Outcome.

• 100% January-wave compliance by January 25 — 3 weeks after kickoff.
• 100% March-wave compliance, on deadline.
• 100% May-wave compliance by April 20, with 10 days of margin.
• Direct cost: ~USD 4,200 across certificates, dev, and testing.
• Avoided fines (60 UTM ~ USD 4,500 per infraction × 12 stores × monthly under non-compliance): theoretical exposure of USD 648,000 annually.

The 12 days we lost between the news and the decision to start were the most expensive of the project — not in hours, but in risk.

Download the full SII 2026 checklist

We've built an Excel checklist with every item in all three waves, the deadlines, owner roles, and budget estimates. It includes links to current resolutions and the SII certification environment URL. Request it on the resources page and it lands the same day.

FAQ