A mandatory field does not make the data appear.

On 23 October, Chile's Internal Revenue Service (SII) published Resolution 144 on invoices and dispatch notes. The required information includes the actual origin and destination, driver, carrier and vehicle. The resolution generally takes effect on 1 November 2026, with a deadline of 1 May 2027 to implement the third-party dispatch note or the specified interoperability mechanisms. This is not a blanket postponement. The resolution recognises that, in certain operations, the issuer does not yet have all the transport details when issuing the document.

For an importer, manufacturer or retailer working with third parties, the question is not simply which field to add to the system. It is who has each piece of information, when they have it, how they pass it to the next person responsible and what happens when the driver or vehicle changes. My reading is that the document makes visible the coordination that needs to underpin it. The resolution does not establish that any particular company is failing.

So what?
Before commissioning a technology change, it is worth building a clear picture of the journey from the order through preparation, transport allocation and dispatch to receipt. Drawing the usual route is not enough: we need to examine what happens when there are changes, partial deliveries and exceptions. One hypothesis to investigate is whether information is being required before it exists, or whether it already exists but does not reach the person who needs it.

In the current-state process work I have undertaken on insurance and claims at a logistics company, the starting point has also been to compare responsibilities, documents, systems and the experience of those who perform the work. These are different operations, but the need to build a shared understanding is the same.

At Corte Consultores, we start with the decision the team needs to support. We compare processes, documents, systems and first-hand accounts as baseline evidence before recommending changes. Depending on what we observe, the appropriate response may be to clarify responsibilities, adjust a decision criterion, coordinate with the operator or integrate information. Not every gap is resolved by adding another screen.

For customers (CX), what matters is that the order arrives and the information is consistent. For employees (EX), what matters is not having to reconstruct every dispatch through phone calls, emails and duplicate records. Reducing that work could avoid delays, rework and costs, but first we need to establish where they arise and how much they represent.

My take:
A document may require a piece of information without anyone in the operation being responsible for it. If we do not know where it originates, who validates it and how it is updated, the system may simply record uncertainty more neatly without resolving it. Clarity first, then transformation.

#E2EProcesses #Logistics #Interoperability #ProcessManagement