Chile's dispatch-note rules changed while many companies were still preparing for SII Exempt Resolution No. 154 of 2025. On October 23, 2026, the SII issued Resolution No. 144, consolidating the requirements and superseding Resolution 154.
An Odoo project should therefore go beyond adding fields to a document. It must connect tax information with inventory, transport, people, vehicles and contingency procedures. According to the SII clarification dated October 29, 2026, all obligations start on May 1, 2027; taxpayers that already have the data may use the new standard from November 1, 2026.

From Resolution 154 to 144: what changed
Resolution 144 maintains the goal of improving traceability for transported goods while updating and consolidating the instructions. Required information includes origin and destination, driver and carrier identification, vehicle and trailer plates, and a precise description of the cargo. It also distinguishes self-managed transport, outsourced transport and special regimes.
The resolution provides electronic data-completion mechanisms for certain logistics information, as well as rules for virtual or printed representations, contingencies and prolonged transfers. The rules that apply depend on each operation; this article is informational and should be reviewed with the company's tax adviser.
The operational date is May 1, 2027
The SII's official clarification states that every obligation under Resolution 144 starts on that date and no individual extension request is required.
What a company should prepare in Odoo
1. Master data
Origin and destination addresses, third-party IDs, drivers, vehicles, trailers, products, units and logistics attributes need clear owners.
2. Rules by operation
Self-managed delivery, outsourced transport, internal transfers and special cases require different information and controls.
3. Connected workflow
The note should originate from the correct movement, retain links to the sale, purchase or transfer, and accept logistics data without losing traceability.
4. Contingency and audit
The business needs procedures for missing data, vehicle changes, rejections, reprints and evidence of who created or changed each item.
A recommended Odoo flow
- Document origin: create the delivery from a sale, purchase, manufacturing order or transfer.
- Pre-validation: check addresses, transfer reason, goods, quantities, carrier and available driver and vehicle data.
- Electronic issuance: generate and submit the e-document through the installed localization and authorized service, keeping its number, response and representation.
- Logistics completion: add the information required by the operating model and SII mechanism.
- Follow-up: link the note to physical dispatch, receipt, incidents and subsequent documents.
The exact design must distinguish Odoo standard functionality, the installed Chilean localization and custom development. Inventory and e-invoicing alone do not prove end-to-end compliance.
Control questions before development
- Which transport categories does the company actually use?
- Who owns carrier, driver and vehicle data?
- When is the plate known and how will it be added?
- What happens when a vehicle or route changes?
- How will offline contingencies be regularized?
- Which tests involve the e-invoicing provider, warehouse and transport teams?
SYSTCOM prepared a dispatch-note workflow demonstration. The video illustrates the operation; the final setup must be checked against Resolution 144, the SII clarification and the taxpayer's actual model.