Last Tuesday morning, our documentation team flagged something on a draft Bill of Lading bound for Lima. The consignee name on the BL read Importadora del Sur S.A.C.. The buyer's SUNAT registration (the canonical name on file with the Peruvian tax authority) read Importadora del Sur SAC. One letter different. No period after the second "S." in one version. One had it. One did not.
To a shipper, it looks like a non-issue. To Aduanas Peru, at the discharge gate in Callao, it is a hold. A simple consignee-name mismatch can hold a container at Callao on average nine days. Peer reviews from forwarders in 2024 put the median closer to six days; under load (Christmas window, port congestion) we have seen it stretch past two weeks.
Why the variation matters in Peru
Peru's customs IT system cross-checks the BL consignee against SUNAT records. Many countries do the same. What is different in Peru: the match is character-for-character. Spanish-speaking customs authorities in LATAM often treat punctuation, accents, and corporate-suffix abbreviations as significant. S.A.C. is a different string from SAC. Both legal in different contexts. Both common on real registrations.
We caught it because our documentation desk has been bitten before. A 2024 shipment to Guayaquil was held seven days over an accent on a single letter in the buyer's nombre comercial: the BL said Jose, SUNAT said José. The container sat in Ecuador while we waited for a corrected BL and an amended ASN. The buyer's customer (a hospitality chain) absorbed the delay and the buyer absorbed two follow-on cancellations.
The checklist we now run before BL release to LATAM
Three things, every time, in this order:
- Consignee name matches the buyer's local-tax registration character-for-character. SUNAT in Peru. SUNAT counterpart in each country: AFIP in Argentina, SAT in Mexico, DIAN in Colombia, SRI in Ecuador, DGII in the Dominican Republic, SAT in Guatemala. Accents, hyphens, abbreviations: all matter.
- Product code on BL matches the product code on the commercial invoice and packing list, at 8 digits. Many shipping lines default to 6-digit HS on the BL. Aduana's reconciliation is at 8. A 6-digit BL against an 8-digit invoice can be flagged as misdeclaration even when the underlying classification is correct.
- Place of receipt and port of loading are not swapped. Common shipping-line clerical error on Mundra-origin cargo: the line system populates JNPT as the port of loading and Mundra as the place of receipt. Looks plausible. Is wrong. Holds the BL at the inland depot.
The cost of the catch
Five minutes of review by a bilingual reader who knew what to look for. We sent the BL back to the line with a single annotation: "Consignee per SUNAT: Importadora del Sur SAC (no period)." Amended copy issued the same evening. Container loaded on schedule. Buyer never knew anything was almost wrong.
That is the work. It is not glamorous. The bill for getting it wrong, on the other hand, runs into compounding columns: port storage at USD 35/day per container, demurrage that starts at USD 80/day after free time, lost interest on payment that hasn't cleared, and the cost of explaining a delay to a buyer whose own customer is waiting. None of which the buyer should ever have to think about. They asked us to ship a container. Our job is to do that, and to do it without giving them a story.
What this means for buyers in Spanish-speaking markets
If you are a buyer in Peru, Mexico, Colombia, Argentina, or anywhere in LATAM and you have had repeated customs holds on imports from India, the cause is almost never the product. It is almost always documentation that was right by Indian standards and wrong by yours. A bilingual exporter who reads your registrations in your language (not in someone else's rough translation) costs you nothing extra. It saves you the days you are already losing.
Ask any exporter you are talking to: "Do you check the consignee name against my local-tax registration before BL release?" The right answer is yes, every time, in writing.
— Nitik · Darsavio EXIM