◆ A duty rate that does not match the HS code, caught against the pedimento
The duty rate on the pedimento does not match the HS code.
On file CX-3340 (Laredo to Monterrey), the freight invoice and the pedimento were read together. The HS code on the entry classifies the goods at a 5% duty rate, but the pedimento applied 8%, an overpayment on a climbing cross-border lane. The auditor lines the two documents up side by side, flags the gap, and stages the reconciliation summary so it is a correction, not a month-end surprise.
Recommended: reconcile CX-3340 to the 5% rate for HS 8537.10 and recover the duty overpayment of about $1,460; two more files this week show the same HS-to-duty gap.
FILE CX-3340LAREDO → MONTERREY
Freight invoice
Linehaul$1,840
X-border fee$220
HS code8537.10
Pedimento
Customs value$48,600
Duty @ 8%$3,888 ⚠
HS code8537.10
HS 8537.10 = 5% DUTY−$1,460 due
◆ Flagged files Export
| File · lane | HS code | Type | Customs value | Recoverable | Status |
|---|
↳ Click any file to see the freight invoice and pedimento side by side, and the reconciliation summary.
Where the gaps are
Recoverable by type · MTD
Duty rate vs. HS code$28.6K
Customs value mismatch$14.2K
Freight vs. quote$9.8K
Fee / accessorial$5.7K
Why read both documents
Freight alone misses it
A freight-only audit never sees the duty error, and a customs-only review never sees the freight gap. Reading the invoice and the pedimento together is what catches an HS-to-duty mismatch, and it is exactly the reconciliation that gets harder as cross-border volume climbs.
Plugs into the stack Hessen already runs
read-only · works with your TMS & customs files · ~4–6 week build
TMS / freight
TMyour TMSCustoms / pedimento
PDpedimentosHS / tariff schedule
HStariff dataBroker feed
BRbroker→ Tell us your exact systems and we map the connectors to them. It reads the freight invoice and the pedimento and lines up the reconciliation. Nothing migrates.
Reconciles freight and customs charges automatically as cross-border volume climbs.
Mockup by Instive AI for Hessen Logistics · sample data
◆ Freight and customs, lined up
Reconciliation pipeline
Matched → flagged → corrected
Auto-matched, clean923 files
Flagged, summary drafted17 files
Recovered this month$58.3K
→ The matching that used to be a month-end spreadsheet runs continuously; only the gaps need a person.
By lane
Recoverable · MTD
Laredo → Monterrey$21.3K
El Paso → Juárez$15.6K
Otay Mesa → Tijuana$11.1K
Repeat HS codes
Worth a classification review
HS 8537.10 has shown a duty mismatch on three files this month. The auditor surfaces the recurring code, so the fix can move upstream to classification instead of being caught file by file.
Continuous freight-to-customs reconciliation, with the gaps drafted for you.
Reconciliation view · Instive AI for Hessen · sample data
◆ Cross-border lanes · where reconciliation pays
Laredo → Monterrey
highest volume
Files · MTD340
Flag rate2.6%
Top issueduty / HS
El Paso → Juárez
maquila freight
Files · MTD280
Flag rate1.9%
Top issuecustoms value
Otay Mesa → Tijuana
west-coast
Files · MTD220
Flag rate1.7%
Top issuefreight gap
One reconciliation, every crossing
freight + customs across all lanes
Every lane reads the freight invoice against the pedimento on the same standard. A duty mismatch at Laredo and a customs-value gap at El Paso surface the same way, which is what keeps the reconciliation from breaking as cross-border volume climbs.
One AI layer · freight + customs reconciliation across every crossing.
Mockup by Instive AI for Hessen Logistics · sample data