Purchaser
Owns product, supplier, price, and purchase facts.
From the CBP perspective, every shipment must prove who is responsible, what the goods are, how they are classified, what they are worth, where they originated, how duties are calculated, and where the evidence lives.
Entry number, IOR, HTS, origin, entered value, duty.
Goods, price, buyer, seller, quantity, Incoterm.
Route, container number, shipper, consignee, bill of lading number.
Manufacturer, buyer, seller, EIN, account, authorization.
Owns product, supplier, price, and purchase facts.
Importer of Record, accountable to CBP for the filing.
Files on behalf of the IOR and owns entry filing facts.
Forwarders, carriers, and NVOCCs generate shipping evidence.
Official system for review, liquidation, refunds, and audits.
Connects roles, documents, fields, and risks into an evidence system.
If the need is framed as OCR, file classification, or CAPE entry-number export, the product becomes a one-off utility.
Mike’s new direction is a compliance verification database: every entry needs sources, relationships, check results, and next steps.
AI should stay focused on evidence organization and risk signaling: evidence supports / evidence missing / needs review / potential issue.
PDFs, Excel files, screenshots, archives, duplicates, corrupt files, and inconsistent naming.
Connect Document, Party, Product, Shipment, Entry, EntryLine, and each field source.
Outputs worklists, readiness status, review tables, CAPE lists, and audit binders.
Every field needs a source page, confidence, supporting relationships, and review status. That is what makes agent findings handoff-ready.
Batch / Document / Party / Product / Shipment / Entry / EntryLine
ExtractedField / EvidenceLink / source document / page / confidence
VerificationCheck / Finding / QuestionnaireItem / AuditBinder
Files may be PDFs, Excel workbooks, screenshots, or archives. The uploader may be an importer, purchaser, IOR, broker, or compliance team.
Generate a batch ID and upload manifest to record exactly what the client submitted.
The system unpacks, deduplicates, validates, and detects corrupt files; scanned files proceed to OCR.
Each file gets a type assessment, readability status, and processing log for downstream extraction.
entry、IOR、HTSUS、value、duty
Goods, buyer, seller, quantity, invoice amount
HBL / MBL, container number, carrier, ports
manufacturer、seller、buyer、ship-to
EIN, registration details, entity status
ACE、5106、TAO、ACH、Notify Party
POs, payments, contracts, certificates of origin, specifications
Field + source page + confidence
This phase does not judge risk. It reliably extracts key facts from each file type and records which document and page each fact came from.
After the batch completes, the system links the same entry, shipment, parties, products, and supporting documents.
As files finish, the system creates provisional links so business users can see progress.
After processing finishes or the user closes the batch, merge aliases and match key fields.
Every relationship has a source and version so later review is traceable.
Check whether the entry has 7501, invoice, packing, B/L, ISF, and IOR-related materials.
Normalize HTSUS, Chapter 99, IOR, EIN, port, manufacturer, and related naming.
Keep clean facts, conflicts, and missing evidence for later compliance agents.
Distribute by entry / product / IOR scope
ACE、5106、TAO、ACH、Notify Party
Country-of-origin and manufacturer evidence
Classification consistency and supporting documents
Invoice, declared value, payment, and discounts
Special tariff and exemption support documents
ready / candidate / blocked
Chapter 99, IEEPA, MPF, HMF, AD/CVD
Buyer-provided tooling, design, materials, and related signals
Multi-tier transaction and first-sale document chain
All check results flow into a unified findings queue
Conflicts, gaps, low-confidence items, and blockers from Phase 5
Normalize status, severity, entry scope, and suggested owner
Assign to importer, purchaser, IOR, broker, or lawyer
Ask only for facts the files cannot answer, and request supporting materials
Reviewed, supplemented, or accepted as an open reservation
After supplementation, rerun only affected scope, then return to Normalize / Human review
Add facts, upload files, or accept the open issue
Reviewed, supplemented, and reservations recorded
Organize evidence package, manifest, source files, and exception notes by entry
Export check results into business-ready tables and lists
audit binder + evidence index + worklists
CAPE CSV, account checklist, code table, risk workbook
Importers, IORs, brokers, compliance managers, and counsel can keep working from it
CAPE readiness
Account / payment
Import codes
HTS classification
Tariff classes
Valuation basis
Country of origin
Assists signals
First sale packet
Exemption docs
Audit binder
Human review
Each verification domain leaves an evidence status, risk finding, owner, and next step.
Classify files, extract fields, and preserve source and confidence.
Compare invoice vs 7501, HBL vs ISF, IOR vs EIN.
When files are insufficient, the system generates follow-up questions.
Broker, compliance manager, or lawyer confirms HTS, origin, valuation, and first sale.
Evidence chain + CAPE readiness + account/payment readiness + audit binder.
HTS, tariff, origin, valuation, party / supply-chain verification.
Assists, first sale, exemption documentation, product master history.
Continuous compliance database: continuously import broker / ERP / ACE data and monitor historical changes.
A deliverable that leadership, compliance teams, brokers, and counsel can continue working from.
Output structures such as summary, index, worklist, review tables, and binder.
From Batch and Document through Finding, Questionnaire, and AuditBinder.
Classification, extraction, graphing, domain checks, audit package, and human review.
The core state machine revolves around evidence: what it supports, what is missing, who reviews it, and what comes next.
The MVP does not try to cover every legal issue; first make one entry evidence chain work end to end.
Refund is the business entry point; the long-term value is a continuously compounding compliance database.
A finding with no source, no owner, and no next step should not enter the main product workflow.