Context: different records of the same trip

The ANTT FAQ defines the CIOT as an identifier for the record of a transport operation. The agency also clarifies that it does not replace a contract, CT-e, MDF-e, or invoice. This distinction guides the team's organization: locating a code is different from checking the coherence of the data describing the trip.

This guide does not determine whether a specific operation should generate a CIOT, nor does it interpret exceptions. For these questions, consult the corresponding section of the official FAQ and the technical person responsible for the hiring. Here, the goal is to reduce transcription errors and make pending issues understandable for those who need to resolve them.

In practice: check at three moments

Before sending to the system, gather in a form the planned origin and destination, the identifiers of the parties, and the internal reference of the hiring. Use a data source defined by the team; copying information from different messages favors contradictory versions.

After processing, record the full system feedback and link the identifier to the same operation. Error message, attempt protocol, and confirmation are not interchangeable. If there is a discrepancy, describe the affected field and forward it to the person responsible for issuance or integration, avoiding successive attempts with improvised data.

When closing the trip, compare the form with the documents and the payment record used by the company. A discrepancy should remain visible until clarified. The way to correct or cancel records depends on the applicable official procedure and is not defined by this checklist.

An example of communication failure

Imagine that the dispatch changes the agreed destination and the finance department only receives the initial version. Even if each sector has filled out its form correctly, the records may describe different trips. A unique reference for the operation and a history of changes help locate where the separation between versions occurred. The example is hypothetical; it does not characterize an infraction nor does it replace case analysis.

Impact by profile

The carrier gains an objective list of pending issues for dispatch. The shipper can check if the agreed data reached the correct provider. The autonomous can request clarification on information they do not recognize, without relying solely on an image with an isolated number.

Complete the organization with the CT-e and DACTE guide and the RNTRC consultation form. Avoid inserting personal documents in public channels when asking for help.

Source

ANTT — Frequently asked questions about CIOT, consulted on 22/09/2026. The conference guide is an operational proposal from TRRC; the applicable rules are on the official channel.