Export Documents: The Same Data, Typed Six Times

In an ocean export, the cargo’s gross weight appears on the commercial invoice, the packing list, the tax invoice (NF-e in Brazil), the CE Mercante, the DU-E, and the bill of lading. The shipper’s legal name follows the same path. So do the HS code, the cargo description, and the port of destination. Six documents, at least three systems, often different people typing the same fields.

Brazilian exports grew 11.8% in the first half of 2026, according to MDIC, Brazil’s trade ministry. More volume means more shipments and more keystrokes. For freight forwarding ops teams, the export document chain is probably the most repetitive workflow they face in a given day. Every re-keyed field is a chance for the destination system to drift from the source document.

The data starts on the commercial invoice and ends on the B/L

Any operator knows the order by heart. The shipper sends a commercial invoice and packing list. Those feed the NF-e, the Brazilian tax invoice that travels with the cargo to the bonded warehouse. The forwarder then files the CE Mercante in Siscomex, a mandatory registration for every bill of lading. Next comes the DU-E, Brazil’s single export declaration in the Portal Unico Siscomex. Last is the B/L the carrier issues after loading.

Each document leans on the previous one. The CE Mercante needs cargo data from the packing list and commercial invoice: description, gross weight, cubic measurement, number of packages. The DU-E pulls from the NF-e, commercial invoice, and CE Mercante: HS code, FOB value, destination country, buyer details. The draft B/L repeats shipper, consignee, notify party, cargo description, weight, cubic measurement, containers, port of loading, and port of discharge.

In practice, the operator has the shipper’s document in one tab, Siscomex in another, the ERP in a third, and transcribes field by field. The gross weight of 14,320 kg on the packing list needs to arrive unchanged in the CE Mercante, the DU-E, and the B/L. If the operator types 14,230 kg in any of them, the discrepancy may sit there until the final cross-check, or until it triggers an amendment in Siscomex.

The repetition exists because each document has a different owner. The commercial invoice belongs to the shipper, for the sales contract. The NF-e is a tax document for Brazil’s federal revenue authority. The CE Mercante belongs to the freight forwarder, filed with ANTAQ (the national waterway transport agency). The DU-E is a customs document for clearance. The B/L belongs to the carrier, for transport. Same data, but each system wants it entered fresh.

In the CE Mercante and DU-E, a typo becomes a formal amendment

On a commercial invoice or packing list, wrong data gets fixed with an email asking the shipper for a corrected version. In the CE Mercante or the DU-E, the fix requires a formal amendment in Siscomex, complete with an audit trail, a deadline, and full traceability.

In the CE Mercante, the freight forwarder registers the export bill of lading data: shipper, consignee, cargo description, weight, cubic measurement, and linked containers. A gross weight mismatch between the CE Mercante and the B/L can block the DU-E’s endorsement (averbacao), because the system cross-references the data automatically. If the operator enters the wrong weight, they have to amend it before the export can be endorsed. The deadline for endorsement is seven days after loading.

The DU-E holds fiscal and customs data: HS code, FOB value in foreign currency, destination country, buyer details, and the operation’s regulatory classification. A wrong HS code can route the clearance to a yellow or red channel, delaying cargo release at the terminal. An FOB value that doesn’t match the NF-e triggers a tax inquiry. Every DU-E amendment after clearance stays on record and remains visible to Brazil’s federal revenue authority in future audits.

The cost of a Siscomex amendment goes well past the operator’s time. The customs broker charges for it. The carrier has a documentation deadline for the vessel. We covered the cost of incorrect data in the DUIMP in an earlier post; the mechanism on the export side works the same way. A data entry error compounds once it reaches a regulatory system.

Cross-checking is the invisible work of exports

Before filing the CE Mercante, every experienced operator cross-checks: commercial invoice, packing list, and booking confirmation side by side, comparing shipper, consignee, description, weight, cubic measurement, package count, and containers. Then they repeat the check for the DU-E against the NF-e. Then the draft B/L against the CE Mercante. Three rounds per shipment, ten to twenty minutes each when the documents are organized. When something is missing, longer.

A freight forwarder handling 200 export shipments per month goes through 600 rounds of cross-checking. At forty minutes per shipment, that’s roughly 200 hours per month spent confirming that what the operator typed matches the source document. No report measures this time. No productivity metric includes “hours of cross-checking.”

When volume rises and the operator has to handle more shipments in the same hours, cross-checking is the first thing to shrink. They switch to spot-checking: a glance at the total weight, a quick scan of the first three HS codes, and on to the next file. That’s reasonable when the CE Mercante has to be filed before the carrier’s documentation deadline. But the discrepancy that slipped through shows up when the DU-E endorsement fails, or worse, during an audit months later.

Import document cross-checking follows the same logic and hits the same bottleneck. On the export side, the pressure is higher because the freight forwarder files both the CE Mercante and the DU-E. The amendment falls on them.

The bottleneck is data entry, not cross-checking

Better cross-checking helps, but the problem starts earlier, at the point of data entry. Getting the data right the first time eliminates most discrepancies.

When the operator receives the shipping instruction and commercial invoice and manually types each field into the system, the error enters there. The cross-check that follows is really a hunt for what the data entry got wrong. If the data entered the system straight from the document, without manual typing, the cross-check would narrow to validating what the automation read. The operator would stop looking for their own mistakes.

The difference shows up at scale. An operator checking 15 fields per document, round after round, compares character by character. An extraction system that reads the document and validates each field against known rules (container number check digit per ISO 6346, port code per UN/LOCODE, currency code per ISO 4217, gross weight against the line item total) runs the check at the moment of entry and flags only the fields that remain uncertain.

The operator’s job changes. Instead of spending forty minutes per shipment verifying what they typed, they spend five reviewing what the system flagged. The other thirty-five minutes go back to actual operations: resolving exceptions, tracking shipments, answering the shipper who needs a booking correction.

In our experience with freight forwarders in Brazil, exports are where document automation pays back fastest. The document chain is long and the data repeats many times. Every field that no longer needs re-keying is a field that no longer risks a discrepancy.

Frequently Asked Questions

What documents are required for ocean exports from Brazil?

The required documents are the commercial invoice, packing list, NF-e (Brazil’s export tax invoice), the DU-E (single export declaration) filed in the Portal Unico Siscomex, the CE Mercante filed in the Mercante system, and the bill of lading issued by the carrier. Depending on the commodity and destination country, additional documents may be required, including a certificate of origin, a phytosanitary certificate (MAPA), an Ibama license, or other approvals from regulatory agencies.

What happens if the CE Mercante weight does not match the B/L?

A weight mismatch between the CE Mercante and the B/L can prevent the DU-E endorsement, because Brazil’s Portal Unico cross-references the data automatically. The freight forwarder must amend the CE Mercante so the weight matches the B/L issued by the carrier. The amendment consumes the operator’s and customs broker’s time and delays the closing of the export process.

What is the difference between the DU-E and the former Export Registration?

The DU-E (Declaracao Unica de Exportacao) replaced both the Export Registration (RE) and the Export Declaration (DE) with a single document filed in the Portal Unico Siscomex. The DU-E consolidates commercial, fiscal, and customs information into one declaration and has been mandatory for all Brazilian exports since 2018.

How Autodocs extracts document data and delivers it to Tier2 Cargo

Autodocs receives the commercial invoice, packing list, and other export documents by email, API, or directly from Tier2 Cargo. It classifies each document, extracts the fields with a confidence score and the source page, and runs validations: container number per ISO 6346, port per UN/LOCODE, currency per ISO 4217, gross weight against the line item total. Uncertain fields go to the operator for review. Fields that pass validation enter Tier2 Cargo as ready records, with no manual typing.

In the export chain described here, shipper, consignee, cargo, and container data enters once and propagates to the CE Mercante and draft B/L without re-keying. Cross-checking still exists, but it changes in nature: instead of comparing six documents field by field, the operator reviews what the system flagged.

Learn about Autodocs or get in touch.

Brazilian exports are growing, and every percentage point of growth puts more shipments on the operations desk. Cutting re-keying from six times to one cuts the odds of a CE Mercante or DU-E amendment by a similar margin. The operator who gains thirty minutes per shipment can spend that time on exceptions, on deadlines, and on shippers who need an answer.