MDF-e: Complete guide to accurately enter tractor unit and trailer data

Entering tractor unit (power unit) and trailer/semi-trailer data correctly in the MDF-e (Manifesto Eletrônico de Documentos Fiscais) is essential to avoid SEFAZ rejections, fines during inspections, and unplanned stops. In road operations, small details—such as a plate with the wrong format, a mismatched UF, or an inconsistent vehicle combination—can block authorization and delay the entire shipment.

This practical guide explains, end to end, how to identify and enter the power unit (tractor truck) and implements (trailer/semi-trailer) in the MDF-e, with examples and a checklist to cut errors. You will also see how Meu Rastreio’s MDF-e module helps standardize the process, reduce rejections, and accelerate dispatch with fiscal safety.

What the MDF-e requires for power unit and trailers (road modal)

• Tractor unit (power unit): the truck tractor that pulls the load.
• Trailer/semi-trailer: the implement(s) coupled to the power unit to carry the goods.

In the road modal of the MDF-e, you must inform:

• The power unit data (mandatory).
• Zero, one, or more trailers/semi-trailers, according to the actual combination.
• The owner’s information when the vehicle does not belong to the issuer (leased/third-party), when applicable.

Important note: whenever the power unit is changed or the trailer combination is altered during the trip, the correct practice is to close the current MDF-e and issue a new one with the updated composition.

Which fields to fill in the MDF-e (road)

Tractor unit: what to enter

• License plate (Mercosur standard or older model, no hyphen).
• UF (state) of the plate (e.g., SP, PR, BA).
• Capacity or tare/capacity, when required by the current layout in your UF.
• Vehicle owner (when not the issuer):
  • Type of ownership (owned, leased/aggregated, or third-party), when applicable.
  • CPF/CNPJ of the owner (Brazil-only IDs).
  • RNTRC (ANTT) of the owner, when required.
• Other operational information, when applicable per your operation and state rules (e.g., carrier’s RNTRC, CIOT in operations with owner-operators/aggregated fleets, among others).

Best practices for tractor unit entry

• Standardize input: no spaces, no hyphens, uppercase letters.
• Ensure the UF matches the reported plate.
• Keep RNTRC active and vehicle documents current (licensing, ANTT, etc.).
• Avoid using a power unit already linked to an active, not-yet-closed MDF-e.

Trailer/semi-trailer: what to enter

• Plate and UF of each coupled implement.
• Capacity or tare/capacity, when applicable.
• Implement owner (if different from the issuer), with CPF/CNPJ and RNTRC when required.
• Order of implements: respect the real sequence of the set (e.g., 1st semi-trailer, 2nd semi-trailer).

Best practices for trailers

• Do not repeat plates between the power unit and trailers.
• Inform all implements in the set (bitrem, rodotrem, etc.).
• If you remove or add an implement, close the MDF-e and issue another one with the new composition.

Rules and validations that most often cause rejections

• Invalid plate format (e.g., with hyphen, lowercase, extra/missing characters).
• Invalid UF or one that does not match the format rules.
• RNTRC missing, expired, or inconsistent with the owner/carrier, when mandatory.
• Duplicate vehicle/trailer in the same MDF-e.
• Number of implements incompatible with the real combination (e.g., forgot to include a semi-trailer in a rodotrem).
• Changing power unit/implement mid-route without closing and reissuing the MDF-e.
• Power unit already linked to another open MDF-e.
• Missing owner data when the vehicle is leased/third-party.

Operational tip: maintain an internal “fleet master data standard” defining mandatory fields, accepted formats, and the owner for upkeep. This reduces discrepancies across shifts and branches.

Step-by-step to fill in without errors

1. Identify the combination

• Will the set be only the power unit, or will it include 1, 2, or more implements?
• Are the vehicles owned or leased/third-party (aggregated)?

2. Validate documents before issuing

• Plate and UF of all vehicles/implements.
• RNTRC of the carrier and, when applicable, of the owner.
• Driver license (CNH) and driver data, if provided in the same flow.

3. Register/update the fleet in the system

• Keep plate, UF, ownership (owned/third-party), RNTRC, and capacities always current.
• Link implements to the most frequently used power unit to speed up selection.

4. Fill in the MDF-e

• Enter the power unit (plate, UF, and other required fields).
• Add all coupled trailers/semi-trailers, in order.
• Confirm owner and RNTRC when needed.

5. Validate and transmit

• Review formatting, duplicates, and consistency.
• After authorization, start the trip.

6. Closing

• At the end of the route, close the MDF-e within the required deadline.
• If you need to change the power unit or implements mid-route, close the current MDF-e and issue a new one.

Practical examples

• Operation with 1 semi-trailer

  • Power unit: plate ABC1D23 (SP).
  • Implement: plate XYZ4E56 (PR).
  • Owner: both owned by the issuer. No third-party data.

• Rodotrem/bitrem (2 implements)

  • Power unit: plate JKL2M34 (MG).
  • 1st semi-trailer: plate NOP5Q67 (MG).
  • 2nd semi-trailer: plate RST8U90 (BA).
  • Check implement order and do not repeat plates.

• Aggregated/outsourced fleet

  • Power unit: plate BCD9E10 (SC), third-party owner.
  • Enter owner’s CPF/CNPJ and corresponding RNTRC, when applicable.
  • Implement owned by the issuer: plate FGH1I23 (SC).
  • Verify CIOT rules and the freight contractor according to the hiring type.

• Power unit change mid-route

  • Close the MDF-e for tractor A as soon as it is replaced.
  • Issue a new MDF-e with tractor B and the same (or updated) implement combination.

Best practices for agile operations and compliance

• Standardization: adopt an internal entry guide with screenshots and examples for each branch.
• Fleet governance: centralize registration and management of expirations (RNTRC, licensing, etc.).
• Checklists by set type: 4x2 with 1 SR; 6x4 with 2 SR; tandem-axle tractor, etc.
• Audits: review rejected MDF-e weekly and define corrective actions (training, data fixes).
• Timely closing: track open MDF-e and avoid overlapping trips without closure.
• Data integration: whenever possible, reuse validated fleet master data.

How Meu Rastreio helps you fill MDF-e without headaches

Meu Rastreio’s MDF-e module is designed for the realities of day-to-day logistics, enabling fast, compliant issuance. Highlights include:

• Centralized fleet registry

  • Vehicles and implements with standardized plates, UF, ownership, and capacities.
  • Per-vehicle history and alerts for missing data.

• Assisted entry

  • Quick selection of the power unit and its associated implements.
  • Format and consistency validations (plate/UF, duplicates, mandatory fields).
  • Suggestions based on recently used combinations.

• Fewer rejections, more agility

  • Preventive alerts before transmission.
  • Real-time tracking of SEFAZ authorization status and responses.

• Governance and compliance

  • View of active MDF-e to avoid duplicate power units.
  • Reports for internal audits and performance indicators.

• Operational scalability

  • Replicable standards across branches.
  • Training and support to reduce rework for your team.

Result: more productive teams, fewer stops due to inconsistencies, and a smoother MDF-e flow—from registry to closing.

Learn more about Meu Rastreio’s MDF-e: https://meurastreio.app/pt-BR/mdfe

Trends: from manual entry to intelligent validation

The industry is moving from manual, error-prone entry to flows with intelligent validations, data reuse, and business-rule automation. Teams that invest in:

• Standardized master data
• Real-time validations
• Active monitoring of open MDF-e
• Continuous team training

reduce rejections, shorten issuance time, and keep the fleet moving with fiscal safety.

Conclusion and next step

Entering tractor unit and trailer/semi-trailer data correctly in the MDF-e is a mission-critical routine that, when well structured, prevents rejections, eliminates delays, and brings predictability to your operation. With standardized registry, consistent validations, and clear processes for power-unit changes or implement updates, your team gains both speed and compliance.

Want to see how Meu Rastreio can simplify this end-to-end and permanently reduce MDF-e errors? Book a free demo and talk to a specialist.