Doc. Type — Trade Compliance Tool

Your invoices pass the eye test.
Do they pass this test?

Missing PO numbers, quiet line-item math errors, grand totals that don't actually add up, and HS-6 codes nobody double-checked — the things a fast manual review skims right past. This catches them before your compliance team, or a customs officer, does.

◆ Field & math validation ◆ HS-6 classification (USITC + AI) ◆ Filtered pass/fail reports
DOCUMENT CLEARED Aug 09 2026
Order Number✓ found
Payment Terms✓ found
Line math (12 rows)✓ verified
Grand total✓ reconciled
HS-6 classification✓ 8471.30
Workflow

Three steps. No spreadsheet gymnastics.

Upload, check, download — the same discipline as a customs desk, minus the manual line-by-line squinting.

01 / UPLOAD

Drop in the document

PDF, Excel, or a photo of a scanned invoice. Text-based or scanned — both are handled, the scanned ones read via AI vision.

02 / CHECK

Pick the mode, run it

Invoice Compliance validates fields, math, and totals. Supporting Document Audit checks whatever mandatory fields you name — COOs, packing lists, BOLs.

03 / DOWNLOAD

Get a clean report

Pass/fail per document, filtered by date range and status, with invoice and supporting-document reports kept separate.

Common misses

What a five-minute manual review usually lets through

Every row below is a real failure mode this tool is built to flag — not hypothetical edge cases.

Field Why it slips past manual review
Grand Total Stated total looks plausible at a glance — but doesn't match the sum of quantity × unit price across all line items. Silently wrong
Line-item Math One row out of forty has a typo'd unit price. Nobody re-multiplies forty rows by hand. Easy to miss
Order Number / Terms Present on most invoices from a supplier, so the one time it's missing doesn't stand out. Assumed present
HS-6 Classification Copied from the last shipment's paperwork without re-checking it still fits this product's actual description. Assumed unchanged
Supporting Documents Certificate of Origin or packing list is missing a mandatory field entirely, not just filled in wrong. Not cross-checked
Under the hood

Built around how trade documents actually get checked

Not a generic OCR wrapper — logic specific to invoice structure and tariff classification.

Two check modes

Invoice Compliance for full field + math + total validation, or Supporting Document Audit for whatever mandatory fields you define — COOs, BOLs, packing lists.

Σ

Real math validation

Every line recalculated from quantity × unit price, then reconciled against the stated grand total — not just a presence check.

HS

HS-6 classification

Free USITC keyword lookup, or AI reasoning through the General Rules of Interpretation with a stated confidence level, so you know when to double-check.

👁

Reads scanned documents

Text PDFs and Excel are read directly. Scanned PDFs and photographed invoices are read through AI vision — no separate OCR step to manage.

Separated, filterable reports

Filter your check history by date range and pass/fail status, then download invoice and supporting-document reports as two distinct exports.

Private, per-user history

Sign in and every check you've run stays yours — a running record you can filter and revisit, not a one-off tool that forgets everything.

VS
Built by

Built by someone who does this job, not just codes it

I'm V Sathish Kumar, a Sourcing Process Analyst working in trade compliance and procurement — Oracle GTM, HTS/HSN classification, export documentation, the actual paperwork this tool checks.

This started as a way to stop re-checking the same invoice fields by hand every day, and turned into something built the way a compliance analyst would want it built: math that's actually recalculated, classification that shows its reasoning, and reports that separate invoices from supporting documents instead of dumping everything into one pile.

Oracle GTM HTS / HSN Classification Incoterms Export Documentation BPA Management
READY FOR CLEARANCE Check your first doc

Stop finding the mismatch after it ships.

Upload one invoice and see exactly what it catches — the check itself is free to try.