Incomplete Import Documents: The Missing Field Problem

At a Brazilian freight forwarder’s operations desk, a complete import document is the exception. The commercial invoice comes without the INCOTERM. The packing list shows gross weight but omits net weight. The B/L carries a generic description the carrier accepted but that DUIMP (Brazil’s single import declaration) rejects. For every blank field, the operator follows the same routine: spot the gap, email the overseas agent or the exporter, wait for the reply, and re-check the corrected document when it finally arrives. That reply takes hours or days, depending on the time zone. On a desk handling 80 to 120 shipments a month, these chases pile up and compete for the same working hours. What makes an incomplete document expensive is the time spent chasing the missing data, far more than the data itself.

The missing field travels with the cargo

Exporters fill out shipping documents to meet the requirements of their own country and the carrier. Brazil asks for more. The commercial invoice alone must include fourteen mandatory fields under Article 557 of Brazil’s Customs Regulation (Decree 6,759/2009): gross and net weight, INCOTERM, unit price per item, a description detailed enough for tariff classification, among others. In markets like China, India and Southeast Asia, a standard export invoice often carries fewer fields than Brazilian law requires.

The overseas agent assembles the pre-alert from whatever the exporter provides. If the invoice arrived without net weight, the pre-alert ships without net weight too. The omission travels with the cargo. The Brazilian forwarder only discovers it when the document is opened for review or when the system rejects the entry.

Most incomplete documents follow a predictable pattern: the same fields go missing from the same suppliers. A Chinese electronics exporter routinely omits net weight per item. An Indian chemical exporter routinely omits the CAS number or the percentage composition that DUIMP’s Product Catalog requires. Forwarders who map these patterns by supplier can request the data before shipment, when a correction costs one email rather than a declaration amendment.

The commercial invoice is the document that arrives incomplete most often

Of the fourteen mandatory fields under Article 557, the ones most frequently missing from invoices reaching Brazilian forwarders are the INCOTERM, net weight per item, a detailed goods description, and the transaction currency when the payment currency differs from the invoice currency. A missing INCOTERM is the costliest gap. Without it, the customs broker cannot reliably calculate customs value. Filling in the field without documentary evidence means accepting the risk of inaccurate information on DUIMP. Under Brazil’s Complementary Law 214/2025, that risk carries a fixed penalty starting at BRL 10,000 per assessment.

Then there is the generic description. Exporters write “electronic parts” or “plastic items,” which is enough for the B/L and for insurance but useless for HS code classification. The operator has to go back to the exporter and request model, composition and intended use, all mandatory attributes in DUIMP’s Product Catalog. That round trip can take two to three days when the exporter sits eight to twelve time zones away.

A packing list without detail stalls the customs broker’s review

The packing list is what Brazil’s Federal Revenue uses during physical inspection when a shipment is routed to the red channel. If the packing list groups different items on a single line, omits weight per package, or leaves out individual dimensions, the inspection becomes impractical. If the customs broker catches the omission before filing DUIMP, a correction can still be requested. If it surfaces later, during a revenue officer’s review, the shipment sits at the bonded warehouse until the revised document is issued and attached.

The fields most often missing from an import packing list are net weight per item (when the document shows only total gross weight), dimensions per package (when only total cubic volume is given), and item-level correspondence between the packing list and the commercial invoice. Without that correspondence, the customs broker cannot build the declaration item by item. The fallback is grouping by interpretation, and every wrong grouping can trigger an amended line item on DUIMP.

Weight discrepancies between the packing list and the B/L also trigger queries. The packing list typically reports the packed merchandise weight. The B/L reports the gross weight recorded at the terminal, which includes the pallet and sometimes the partial container tare. The difference can reach 5%, and during the document cross-check the customs broker must either justify it or amend.

A B/L with a blank field blocks DUIMP filing

The B/L feeds Brazil’s CE Mercante cargo manifest and, by extension, DUIMP. The most common omission on import B/Ls is a blank notify party field. Carriers accept the B/L without a notify party because the information serves the importer, and the exporter often does not know who the notify will be at destination. The operator at the Brazilian forwarder needs to fill in the field before filing the CE Mercante. When the information does not appear in any pre-alert document, the overseas agent has to be asked.

Since October 2026, Siscomex rejects DUIMP when the HS code has fewer than six valid digits, per Siscomex Import Notice 101/2026. A generic B/L description, combined with a lack of detail on the invoice, prevents correct classification and Product Catalog entry. When no document in the set carries the necessary information, the chase starts with the most basic question: what exactly is this merchandise.

The chase cycle is the real cost of an incomplete document

A weight, an INCOTERM, a more detailed description. Each one looks trivial on its own. But for every missing field, a chase sequence opens: the operator spots the omission, writes to the overseas agent (or the exporter directly), waits for a reply, reviews the corrected document, checks whether the fix is complete, and if it is not, starts over.

Each step takes minutes. The gap between steps takes days. An email sent at 4 PM Brasilia time reaches the agent in Shanghai at 3 AM local. The reply comes the next business day, if the request was clear. If the exporter does not understand what is missing, or sends a revised version with a different field wrong, the cycle restarts. In practice, chasing a single missing field takes one to three business days when the supplier is in Asia and half a day to one day when the supplier is in Europe or North America.

While the chase is open, the shipment is stuck wherever the operator found the gap. If it was spotted before DUIMP filing, the shipment waits with no clock running. If it was spotted afterward, with cargo already at the bonded facility, every idle day can generate bonded storage charges and push the free time countdown closer to the limit.

A desk handling 100 shipments a month can have, at any given moment, ten to twenty shipments waiting on at least one missing field. These shipments do not leave the operator’s list. They need daily follow-up, take up inbox space, and compete for attention with shipments that are actually moving. The operator ends up managing the wait instead of moving cargo.

Checking at origin cuts the chase at destination

The chase at destination exists because the check did not happen at origin. The overseas agent receives the exporter’s documents, forwards them to the pre-alert without verifying the fields Brazil requires, and the omission travels to Santos, Paranagua or Itajai, where fixing it costs more.

The fix is to move the checkpoint upstream. The overseas agent (or the Brazilian operator) reviews the documents as soon as they arrive, before shipment, and requests the missing data while the cargo is still at origin. At that point, the correction is an email to an exporter in the same time zone, and the revised document arrives before the cargo ships.

The practical difficulty is that the checkpoint requires knowing what to check. Brazilian legislation changes frequently, Product Catalog requirements vary by HS code, and DUIMP demands more fields than the old DI declaration. An overseas agent serving multiple destinations does not always know Brazil’s specific requirements. The operational fix is a mandatory-field checklist by document type, maintained by the Brazilian forwarder and shared with every overseas agent. Forwarders who keep that checklist current and send it as a standard instruction alongside quotation requests tend to cut chase volume by half.

How Autodocs checks fields before the data enters the system

Autodocs receives documents by email, by API, or directly from Tier2 Cargo or Tier2 Portal. It classifies the type (commercial invoice, packing list, B/L, certificate of origin) and extracts every field with its value, confidence score and source page. Before the record enters the system, a validator library checks what can be checked automatically: container number by check digit (ISO 6346), port by UN/LOCODE, currency by ISO 4217, air waybill by IATA mod-7. The forwarder’s own rules complete the validation: mandatory field present, net weight included when the commodity type requires it, INCOTERM within the accepted list.

What Autodocs cannot resolve on its own goes to a person for review, with the flagged field and the reason for the flag. The operator sees at a glance which fields are missing or inconsistent, instead of discovering them one by one as the shipment progresses. With that early visibility, everything goes out in a single email to the overseas agent, rather than a separate chase for each field.

Learn about Autodocs or get in touch.

The next step is mapping the fields that are frequently missing

The operator who handles incomplete documents every day knows which fields are most often missing, which suppliers omit the most, and which commodities demand the most detail. That knowledge usually lives in the head of whoever runs the desk. Writing it down in a list organized by supplier and document type turns individual experience into shared instructions. When the next shipment from the same supplier arrives, the review starts with the fields already known to be problematic, and the request goes out in the first email, before the problem drags on.