MDF-e · Electronic Manifest of Fiscal Documents
The manifest starts with the tripand closes with it.
The MDF-e comes out of the run sheet your team already builds: vehicle, driver, route and linked documents. On arrival, closing happens together with the last delivery.
- Issued from the run sheet
- DAMDFE in the driver app
- Automatic closing
- Open-manifest alert
- API and native integration
SÉRIE 1 · Nº 004471
Operation
ROM 4471 · São Paulo → Vitória
Driver
JOÃO M. DE SOUZA
Vehicle
ABC-1D23
Documents
12 NF-e · 3 CT-e
Gross weight
8.420 kg
CIOT
0000 0000 0000 0000
Toll voucher
Registered
Authorized · SEFAZ
Who it is for
Whoever puts cargo on the road manifests the trip
The obligation comes from the trip, not from the invoice. It reaches you along two paths.
You issue CT-e on the trip
Every trip needs a manifest grouping the fiscal documents travelling in that vehicle. The MDF-e comes out of the load already built in the system.
- One manifest per vehicle, with the CT-e of that trip
- Add a document or swap the driver mid-route
- Closing recorded when the trip ends
You haul with your own fleet or a self-employed carrier
Whoever issues NF-e and moves the cargo in an owned, leased or self-employed carrier's vehicle also manifests the trip on interstate operations — and, in several states, on intrastate ones too.
- Manifest generated from the fleet run sheet
- CIOT and toll voucher reported inside the manifest itself
- Pending closings visible before they become a problem
How it works
Four steps, all inside the operation
No step asks you to open another portal or retype data that is already in the system.
- 01
Close the run sheet
The vehicle load already has route, driver and fiscal documents in Meu Rastreio.
- 02
Check vehicle and driver
Plate, driver, route and unloading cities are validated before transmission; whatever is missing shows on screen.
- 03
Authorize with SEFAZ
The manifest is transmitted, comes back with access key and protocol, and the DAMDFE lands in the driver app.
- 04
Close on arrival
Once the last delivery of the trip is done, closing is recorded — and whatever stays open becomes an alert on screen, not a problem found weeks later.
Already in your flow
Four documents, one single flow
CIOT, MDF-e, CT-e and the toll voucher already run in Meu Rastreio. They are not separate portals: each one has an API and is natively integrated with the route planner and the driver app.
API for your ERP
All four documents have an API: your system sends the operation and gets back code, key, receipt and status.
Native in the route planner
The planned route already carries the itinerary, toll plazas, vehicle and driver — exactly what each document requires.
Native in the driver app
CIOT, DAMDFE, DACTE and the toll voucher receipt land on the phone of whoever is driving, next to the day's route.
What the module does
The fiscal obligation at the pace of the operation
Issued from the run sheet
Vehicle, driver, route and documents come from the load that is already built.
Automatic closing
A finished trip closes the manifest, without depending on someone remembering at the end of the day.
Open-manifest alert
MDF-e still waiting to be closed show up in a list, before they block the next issuance.
DAMDFE in the driver app
The driver leaves with the DAMDFE and its QR code on the phone, and the printout becomes optional.
Adding documents en route
Cargo picked up mid-route enters the manifest through an event, with nothing redone.
Driver swap
A replacement driver is added to the trip through the driver-inclusion event.
CIOT and toll voucher
A trip with a self-employed carrier carries the freight payment data inside the manifest itself.
Contingency
If SEFAZ goes down, the trip leaves and the transmission is regularized afterwards.
API and integrations
Receive loads from your ERP and send key, protocol and closing back to your system.
Questions about MDF-e
What people ask before signing
Informational content about MDF-e regulation. It does not replace tax advice.
What is the MDF-e?
It is the Electronic Manifest of Fiscal Documents, model 58. In a single document authorized by SEFAZ, it gathers the fiscal documents (NF-e and CT-e) travelling inside one vehicle on one trip.
Who has to issue it?
The carrier that issues CT-e for the trip, and the NF-e issuer that moves its own cargo in an owned, leased or self-employed carrier's vehicle. The rule applies to interstate operations and, in several states, to intrastate ones as well — check the legislation of your state.
Do I need one MDF-e per invoice?
No. It is one manifest per vehicle per trip, grouping the documents travelling in that load.
What happens if I do not close the manifest?
The MDF-e stays open at SEFAZ, the trip remains recorded as in progress, and the pending item can block new issuances. That is why closing is tied to delivery completion.
Can an MDF-e be cancelled?
Yes, within the deadline set by law (as a rule, 24 hours after authorization) and as long as the manifest has not been closed and the trip has not started. After that, the way out is closing it.
What if the load changes mid-route?
A new document enters through the DF-e inclusion event and a driver change through the driver inclusion event, with no second manifest.
Does the driver need a printed DAMDFE?
The DAMDFE can be presented digitally, with its QR code, straight from the driver app. Printing is up to the operation.
I already issue CIOT in Meu Rastreio — does anything change?
The flow does not change. The same trip that generates the self-employed carrier's CIOT carries that data in the manifest's payment information group.
Can it integrate with my ERP?
It can. Loads can arrive through an integration or the API, and key, protocol and closing go back to your system.
Documents of the operation
The four documents of a road trip
All of them already available in Meu Rastreio, issued from the same operation.
Stop issuing the manifest after the truck has left
We show the flow running with your loads, your vehicles and your documents.
