Cross-Checking Import Documents: Where Errors Hide

Brazil’s Customs Regulation (Regulamento Aduaneiro, art. 557) lists 14 mandatory fields on every commercial invoice for imports. Most of those fields appear, with the same expected value, in at least one other document in the shipment file. Gross weight shows up on the packing list and the bill of lading. The goods description shows up on the certificate of origin and the import declaration (DUIMP, Brazil’s single import declaration). The country of origin shows up on the B/L and the certificate.

Each document comes from a different source at a different point in time. The exporter fills out the invoice. The overseas agent or carrier issues the B/L. The chamber of commerce in the exporting country issues the certificate. Four independent sources need to agree on dozens of fields, and the document review most customs brokers run today checks each document internally, field by field, without systematically cross-checking one against another. The discrepancy that slips through is the one that surfaces during DUIMP risk profiling.

The same data appears in four documents

Gross weight appears on the commercial invoice (it feeds customs valuation), the packing list (it describes the packages), the B/L (the carrier needs it for stowage and freight calculation) and the DUIMP (the Receita Federal, Brazil’s federal tax authority, uses weight to validate classification and compute duties per statistical unit). If the exporter entered 1,250 kg on the invoice and the overseas agent entered 1,520 kg on the B/L because they weighed the cargo with maritime packaging, both numbers are correct within the context of whoever produced them. The customs broker in Brazil must decide which one to declare on the DUIMP. Reviewing each document on its own turns up no error. The discrepancy only shows when the two are placed side by side.

The goods description creates a similar problem. The invoice might say “stainless steel fittings, assorted,” the packing list might say “fittings” and the certificate of origin might say “stainless steel articles for industrial use.” None of the three is wrong. All three describe the same cargo. But the HS code (NCM in Brazilian nomenclature) that the customs broker must declare on the DUIMP requires a classification that does not always match any of these descriptions word for word. When the invoice description is too generic to support the declared HS code, the gap becomes a fiscal query during document review.

The Incoterm on the commercial invoice also splits across documents. An invoice declaring FOB needs freight and insurance stated separately so customs can compute the CIF value, which is the duty base in Brazil. When freight is already embedded in the invoice total but the Incoterm reads FOB, the duty base is wrong. The Receita Federal cross-checks the Incoterm against declared freight and total value, and the inconsistency feeds the risk profile during DUIMP risk channeling.

Brazil’s penalty regime changed in 2026

Until December 2025, the fine for inaccurate information on an import declaration followed art. 711 of the Customs Regulation: 1% of customs value, with a floor of BRL 500 and a cap of 10% of total value. On a USD 50,000 import, that came to roughly BRL 2,500 to BRL 3,000. Complementary Law 227, published in January 2026, introduced a new regime for informational infractions with a base fine of 100 UPF (roughly BRL 20,000) per inaccurate data point, a BRL 10,000 minimum and a 50% surcharge for repeat offenses within three years, according to an analysis published by Conjur.

The risk structure changed. Under the percentage-based fine, low-value imports carried proportionally low penalties, and many document errors passed with an absorbable cost. Under the fixed fine, every inconsistent field costs the same regardless of cargo value. A USD 10,000 import with two inaccurate fields can generate BRL 40,000 in fines, more than the merchandise itself. Joint regulations between the Receita Federal and the IBS Steering Committee are still being drafted, and enforcement during this transition phase is advisory regarding the new taxes. The law, however, is already in force. For the customs broker who signs the declaration, cross-checking documents has become risk management with fixed price tags.

Document inconsistency triggers a red channel

IN RFB 680/2006, the regulation governing import customs clearance, lists inconsistency between supporting documents as a criterion that feeds the importer’s risk profile and steers the DUIMP toward more restrictive inspection channels. In the red channel, inspection is both documentary and physical: an auditor from the Receita Federal reviews every document, compares data across documents and against the cargo, and average clearance time runs five to eight business days. The cost of incorrect data on a DUIMP was covered in a separate post. This one is about the mechanism that leads there.

The cost of a red channel goes beyond the fine. Cargo sits in the bonded warehouse, accumulating storage charges that scale daily. Eight business days in the red channel means roughly two calendar weeks with cargo sitting idle, and storage can exceed several thousand BRL per container before the goods are released. For the freight forwarder, the red channel means rework: the operator must gather supplementary documentation, respond to auditor queries and follow the case until release.

Rectifying a DUIMP that has already been filed requires authorization from a federal auditor (AFRFB). If the auditor determines the inconsistency needs further clarification, they can issue additional requirements to the importer. When a regulatory agency (ANVISA, MAPA, Inmetro) also requests rectification, the flow passes through the auditor before returning to the agency, and each additional step pushes clearance further out. A document discrepancy that could have been resolved before filing turns into weeks of delay after it.

Five cross-checks that fail most often

Certain cross-checks between documents account for the majority of discrepancies that trigger fiscal queries.

Incoterm versus itemized costs. The commercial invoice declares FOB, but the total already includes freight. The customs broker needs to break out freight and insurance to calculate the CIF value, the duty base in Brazil. If the invoice does not itemize these costs and the B/L does not show freight either, the calculation rests on an estimate that inspection can challenge.

Goods description versus HS code. An invoice that reads “auto parts, assorted” or “electronic accessories” cannot support an eight-digit HS code. The classification requires material composition, product function and, in many cases, dimensions. When the review cross-checks the invoice description against the HS code on the DUIMP and the description on the certificate of origin, the lack of specificity registers as a discrepancy.

Value and quantity totals across documents. The packing list details packages with weight and contents per case. The invoice lists items with unit price and total. When the sum of weights on the packing list diverges from the total weight on the invoice and the B/L shows a third number, the auditor reviewing in the red channel faces three versions of the same data point. On imports with dozens of line items, this discrepancy almost always comes from rounding or unit conversion. Even so, the review must trace the origin of the number in each document to show the difference is formal and does not change the duty.

Unit of measure. The commercial invoice uses commercial units (pairs, boxes, rolls). The DUIMP requires the statistical unit defined by the HS code (kilograms, meters, units). Conversion depends on data not always explicit on the invoice. The gap between declared quantity and statistical-unit quantity is one of the most common reasons for a fiscal query.

Country of origin. The certificate of origin issued in the exporting country may read “Made in China, processed in Vietnam.” The DUIMP asks for the country of origin, defined as the country where the last substantial transformation occurred. If the certificate points to one country and the DUIMP records another, a Mercosur or ALADI preferential agreement can be invalidated and the import duty rate changes.

Manual cross-checking works until volume outgrows the team

Document cross-checking by experienced professionals works. A senior customs broker reviews the invoice, the B/L and the packing list side by side and spots the discrepancy in minutes. The problem starts when the volume of declarations no longer allows that level of attention for each one.

A brokerage handling 200, 300, 400 declarations per month, each with four to six documents and 14 or more cross-checkable fields, hits that limit quickly. A full cross-check of all relevant fields across all documents in a single shipment takes 15 to 25 minutes. Multiply by 300 monthly processes, and that is 75 to 125 hours per month spent solely on cross-referencing document data. That time competes with filling out the DUIMP, classifying goods, monitoring risk channeling and responding to auditor queries. In practice, cross-checking gets limited to the most obvious fields (total weight, total value, package count). Fields that require interpretation, like description versus HS code, Incoterm versus itemized costs, or country of origin versus certificate, depend on the individual analyst’s experience and attention at that moment.

And the DUIMP keeps gaining fields. Since September 27, 2026, the declaration requires the state and municipality of the consumption location for each line item, needed for IBS and CBS tax allocation during the tax reform transition, per a Siscomex communique. Every new field is another cross-check point against exporter documentation. The broader challenge of import document review was covered in a separate post. The specific point here is what happens when the volume of cross-checks exceeds what manual review can cover.

What automated cross-checking handles and what it leaves to the broker

An automated document review tool reads the fields from import documents (commercial invoice, packing list, B/L, certificate of origin), extracts each value and cross-checks equivalent fields across documents. Container number validated against the ISO 6346 check digit. Port verified against the UN/LOCODE table. Currency verified against ISO 4217. Invoice total weight compared with packing list weight and B/L weight. Declared Incoterm compared with the presence or absence of itemized freight and insurance. Certificate-of-origin country compared with the country declared on the invoice.

The output is a list of discrepancies, with the field, the value from each document and the read confidence. The decision on each discrepancy stays with the compliance analyst. A generic invoice description may be acceptable depending on the HS code and the SH chapter. A 3 kg gap between B/L weight and packing list weight may be maritime packaging, and the customs broker knows that. The tool flags; the analyst decides. The gain is in where the time goes: instead of spending 15 to 25 minutes per shipment finding discrepancies, the analyst spends that time deciding on the ones the tool already found.

For the customs broker, the most direct benefit is traceability. In a manual review, proof that documents were cross-checked depends on the memory and notes of whoever did the checking. In an automated review, every cross-check is logged with date, field, value from each document and validation result. When the Receita Federal audits the process later, that trail documents what was verified before the DUIMP was filed.

Frequently Asked Questions

What happens when the commercial invoice and the bill of lading disagree on an import?

The discrepancy is one of the criteria the Receita Federal’s risk profiling uses to assign the DUIMP’s inspection channel. If the weight, description or Incoterm on the invoice contradicts the B/L, the declaration is more likely to be routed to the red channel, where inspection is both documentary and physical. Average clearance time in the red channel runs five to eight business days, and the cargo accumulates storage charges throughout.

Does cross-checking documents before filing reduce the risk of a red channel?

When done before filing the DUIMP, yes. Risk profiling evaluates consistency between supporting documents and declared data. If the customs broker identifies and corrects discrepancies before filing, the shipment’s risk profile improves. Corrections made before filing do not trigger the art. 715 fine under the Customs Regulation. Discrepancies found by inspection after filing lead to assessment notices.

What fields does the Receita Federal cross-check during DUIMP risk profiling?

The system cross-checks HS code attributes against declared DUIMP data: value per statistical unit, weight, country of origin, Incoterm and goods description. It also factors in the importer’s and customs broker’s history. Inconsistencies between supporting documents (commercial invoice, B/L, packing list, certificate of origin) and declaration data feed the risk calculation that determines the inspection channel.

How Autodocs cross-checks document fields before filing

The workflow described in this post, extracting fields from each import document and cross-checking them before filing, is what Autodocs does. Documents arrive by email, by API or straight from Tier2 Cargo. Autodocs classifies each one (commercial invoice, packing list, B/L, certificate), extracts fields with confidence scores and source page references, and runs its validator library: container check digit (ISO 6346), port code (UN/LOCODE), currency (ISO 4217), country (ISO 3166), plus whatever rules the brokerage defines. Fields that pass validation flow through as clean records. What remains uncertain goes to a human reviewer, with the discrepancy already flagged and both values displayed side by side.

For the customs broker, the practical result is a documented cross-check: every field, every document, every validation result logged in the audit trail before any data reaches Siscomex.

Learn about Autodocs or get in touch.

Every customs brokerage already cross-checks import documents in some form. The difference between doing it unsystematically and doing it with a documented trail is the difference between relying on whoever checked it and having a record that answers any question from the Receita Federal. If your brokerage processes enough volume that manual review leaves fields uncovered, the next step is to count how many cross-checks per shipment your team actually completes today and compare that with what the job requires.