Customs Filing
Qubere takes a shipment's line items, parties, and documents and produces a CBP entry: checked against a real Form 7501 checklist, priced with a live HTS tariff engine, snapshotted as an auditable declaration, and driven through the full transmit → response → release lifecycle. No re-keying into ACE.
The problem
What a broker or self-filer will tell you about ACE today:
"It's on the commercial invoice, it's on the packing list, it's in our product database — and someone still types it into ACE line by line."
Re-keying
"We find out an entry was wrong when CBP rejects it. Then it's a scramble to figure out which field, fix it, and resubmit — against a clock."
Rejections
"Duty math is a spreadsheet and a prayer. Nobody's confident about MPF caps, Section 301 stacking, or which HTS rate was in effect that week."
Duty math
How Qubere addresses it
Draft entry from the shipment
The entry is assembled from data the shipment already holds. It fails closed on a missing country, procedure, or line item — you never get a half-built filing that looks complete.
| Entry # | Importer | Country | Type | Value | Status |
|---|---|---|---|---|---|
| QBR-2026-3231761 | ABC Manufacturing India Pvt Ltd | US | 01 · Consumption | $688.80 | Released |
| QBR-2026-3231809 | Acme Corporation | US | 01 · Consumption | $142,400.00 | Transmitted |
| QBR-2026-3231844 | Nordwerk GmbH | DE | 01 · Consumption | €58,900.00 | Transmitted |
| QBR-2026-3231902 | Acme Corporation | US | 03 · AD/CVD | $96,120.00 | Draft · from SHP-2026-000144 |
Form 7501 validation
A named rule set runs before the entry can move and again at transmit: required 7501 blocks, an approved classification on every line, a valid importer CBP number, a real ACE port code, bond not expired, no blocking exceptions. Each failure names the exact field.
HTS duty & MPF engine
Not a model, not a heuristic — a specific published HTS release, refreshed nightly from USITC and human-approved before it goes live. If any line is unrated, the duty fields stay blank rather than understating the number.
| Line | HTS | Value | Rate | Duty | 301 |
|---|---|---|---|---|---|
| 1 · Lithium-ion cells | 8507.60.0020 | $61,200.00 | 3.4% | $2,080.80 | List 3 · 25% |
| 2 · Battery mgmt boards | 8537.10.9170 | $44,900.00 | 2.7% | $1,212.30 | — |
| 3 · Enclosure, aluminum | 7616.99.5190 | $36,300.00 | 2.5% | $907.50 | — |
Declaration snapshot & CBP lifecycle
At transmit, Qubere freezes the exact shipment, line, document, and header data as filed and builds a versioned canonical declaration. Every CBP response — accept, reject, release, hold, cancel — maps through a table-driven state machine. No logging into ACE to check.
Canonical multi-country messaging
Entry type, procedure, authority, message routing, response mapping, allowed post-filing edits, and offered actions all resolve from database tables keyed by (country, procedure), most-specific-match-wins. Germany was onboarded with zero application-code changes.
| Country | Entry type | Procedure code | Authority | Message |
|---|---|---|---|---|
| 🇺🇸 US | 01 Consumption | CONSUMPTION | CBP · ACE/ABI | US_ENTRY_SUMMARY_v4 |
| 🇺🇸 US | 03 AD/CVD | CONSUMPTION_ADCVD | CBP · ACE/ABI | US_ENTRY_SUMMARY_v4 |
| 🇩🇪 DE | 01 Consumption | 4000 | Zoll · ATLAS | DE_CUSDEC_v2 |
| 🇩🇪 DE | 21 Warehouse | 7100 | Zoll · ATLAS | DE_CUSDEC_v2 |
| 🇩🇪 DE | 23 TIB | 5300 | Zoll · ATLAS | DE_CUSDEC_v2 |
Filing Configuration · rules as data
Platform admins tune how a filing is checked, how a customs response moves it, and who is holding it — from the Filing Configuration menu, without a code change.
| Declaration | Held by | Status | |
|---|---|---|---|
| Reference A | Broker 1 | Active | Release |
| Reference B | Broker 2 | Expired | Release |
Filing Configuration · declaration behaviour as data
Platform admins set these per country, procedure and message from the Filing Configuration menu. No code change.
| Country | Procedure | Message | Status | Allowed action |
|---|---|---|---|---|
| Country A | Procedure 1 | Message 1 | Status 1 | Create |
| Country A | Procedure 1 | Message 1 | Status 2 | Replace |
| Country A | Procedure 1 | Message 1 | Status 3 | Discard |
Filing Configuration · reference files
Country, port, unit, carrier and export-licence data are real master tables that filing forms bind to. They are searchable and paginated, and only platform admins can open them.
| Code | ECCN mandatory | Licence value required | Active |
|---|---|---|---|
| Code A | Yes | Yes | Active |
| Code B | No | No | Inactive |
Clear · Valuation & Assists
An assist (tooling, materials, engineering, design or other) is registered once with its total value and currency. It is then offered on matching entries and drawn down as it is declared.
| Assist | Type | Allocation | Status |
|---|---|---|---|
| Assist A | Tooling | Equal allocation | Active |
| Assist B | Materials | Value proportional | Amortized |
Broker packet export · QUBERE_BROKER_XML
A canonical, broker-neutral packet assembled straight from the filing: Importer of Record plus any resolved Consignee / Seller / Exporter / Broker party, every line item with the approved HTS/origin kept separate from what was merely declared, documents with checksums, and the FTA preference claim if one was made — gated behind the same filing-readiness check the UI already enforces.
| Line | Approved HTS | Declared HTS | Approved COO | Value |
|---|---|---|---|---|
| 1 | 8471.30.0100 | 8471.30.9100 evidence only | DE | €58,900.00 |
PGA-by-HTS screening · coverage matrix
Every HTS code on a shipment or entry screens against a curated reference table for six agencies — FDA, USDA, EPA, FWS, CPSC, NHTSA — at exact line, heading, and chapter precedence, and lands in one of three states: cleared (an explicit row says no filing required), requirement_found (mandatory or names a form), or unscreened (no reference row at all). Not a boolean, and it never invents a fourth state.
| HTS | Agency | Granularity | Last verified | State |
|---|---|---|---|---|
| 8507.60.0020 | FDA | chapter | 2026-08-02 | cleared |
| 3808.94.5010 | EPA | line | 2026-07-28 | requirement_found |
| 9018.90.7580 | FDA | heading | — | unscreened |
Curated/manually-imported reference data (seed-hts-pga-requirements.ts + bulk import), not a live CATAIR feed. Not sold as more than it is.
ABI transmission audit trail & CBP test harness
Every outbound ABI transmission — and the matching inbound CBP response — is recorded in an append-only AbiTransmissionRecord log per account: raw payload, a SHA-256 of it, and a recordSha256 that folds in the previous record's hash. Break one link and the chain no longer verifies — there's no quiet edit.
Customs Bonds
Continuous and Single Transaction bonds are a system of record — surety, bond number, amount, effective/expiration — but the real work runs underneath: a scheduled sweep applies the actual CBP formula (10% of the trailing 12-month duty/tax/fee total, rounded up per 19 CFR 113, $50,000 statutory floor) against every account's active continuous bond, flags it insufficient the moment coverage falls short, and clears the flag automatically once it's cured.
Filing Compliance Gate
A filing only reaches Ready for Broker Review once every required Step 2 agent — PGA, AD/CVD, duty bond sufficiency, FTA qualification, filing readiness, trade compliance screening, and the CATAIR-mandatory field set — has written a real decision. That now includes standalone filings with no linked shipment, which used to permanently block on a missing-decision error no one could clear.
Inline blocker resolution
Blocking-issue links used to send a broker to a tab that couldn't actually clear the check — a classification blocker routed to a text field that never touched ProductClassification.status, a readiness-score blocker pointed at a tab with no control over Shipment.readinessScore. Each blocker now opens a popup that calls the real fix, from inside Filing.
AES · US Export
AES (Automated Export System) filings are created, tracked and sent from the Customs Filing Workbench, with the registration number (ITN) returned by the response shown next to each filing. An export has no importer of record, entry type or port of entry, so those import checks are not run and are not counted as passed.
ISF · Importer Security Filing
The ISF deadline is calculated from the lading (on-board) date and shown with the shipment's other deadlines. The filing form maps shipment parties such as seller and buyer into the matching ISF party fields, supports bills of lading as a repeatable group, and cross-checks the bond table before a filing can submit.
Filing Templates
Repeat filings should not be re-keyed. From any filing, Actions → Save as Template stores its declaration data under a name. When a new filing is started for the same country, procedure, message and release, the matching templates are offered and the chosen one pre-fills the form.
Objection handling
| "Are you actually transmitting to CBP / ACE today?" | Qubere builds and validates the ABI/ACE message, freezes the declaration, and runs the full response lifecycle — in the demo a simulated CBP response is applied inline. Live ABI transmission activates when a customer's CBP filer credentials are configured (a config switch, not a rebuild); direct ABI certification is on the roadmap. |
| "What entry types do you support end to end?" | All 18 CBP codes are in the vocabulary. The workflow implemented end to end is consumption-style entry (01 / 03 / 11). Warehouse and in-bond exist as types but don't have regime-specific tracking yet. |
| "Does duty math handle AD/CVD and Section 301?" | Section 301 is applied where the rate is in the HTS data. AD/CVD case status (active, revoked, under review, sunset) is now monitored continuously, with company-specific rate updates staged for a person to confirm before they go live — the ingestion and case-tracking are automated, only the final rate approval is manual. Exclusion-text matching against a full AD/CVD dataset is still a gap; unrated lines show blank, never a guess. |
| "Does the bond screen actually verify anything with CBP?" | The "Verify CBP Status" button on the Bonds screen is a UI placeholder today — it doesn't call CBP. What's real and running is the sufficiency formula, stacking recommendation, and expiration monitoring described above, all backed by a nightly cron and queryable through Ask Qubere. |
| "What about filings with no shipment behind them?" | Standalone filings run the identical 13-agent Step 2 gate, deriving line items, parties, and destination from declaration data. The one honest gap: restricted-party screening has no party-master record to check against for a declaration-only name, so it's recorded as NEEDS_REVIEW rather than faked as a pass. |
The close
And every entry carries a frozen, versioned snapshot: what you declared, provable, forever.
Next step: bring one of your recent entries. We'll build it in Qubere on a screen-share — draft, validate, 7501 preview — and you tell us where it would have saved you time or caught an error.
Full feature list, seed scripts, and talk track: docs/apps/customs/sales/customs-filing.md