Customs Filing

The entry builds itself from the shipment —
validated, priced, and frozen.

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.

18
CBP entry types in the vocabulary
2
countries live — added as data, not code
0
duty lines ever understated (unrated → blank)

The problem

Every entry is data entry, and every rejection is a surprise.

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

The data is already here. The entry is a projection of it.

  • The draft assembles from line items, parties, and documents already on the shipment — and fails closed if a destination country, procedure mapping, authority config, or line items are missing.
  • A named 7501 checklist runs before the entry can move, and again — unconditionally — at transmit. Every failure names the field.
  • Duty, MPF, and fees are computed from the actual published HTS schedule, human-approved before it goes live.
  • At transmit, the declaration is frozen and versioned — later shipment edits never rewrite what was filed.
  • Every CBP response maps through a table-driven state machine. Adding a country is seed data.

Draft entry from the shipment

Send to Customs Filing — and the entry is already populated.

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.

  • One action from a ready shipment, no form
  • Importer, value, country, status on one list
  • Practice-mode (Simulation) filings can never reach a real CBP status
How to demo
Open a ready shipment → Send to Customs Filing. Show the draft appear pre-filled. Then open Customs Filing and point at the entry list.
Target Brokerage/Account Isolated
JT
Joe · Target
Entry #ImporterCountryTypeValueStatus
QBR-2026-3231761ABC Manufacturing India Pvt LtdUS01 · Consumption$688.80Released
QBR-2026-3231809Acme CorporationUS01 · Consumption$142,400.00Transmitted
QBR-2026-3231844Nordwerk GmbHDE01 · Consumption€58,900.00Transmitted
QBR-2026-3231902Acme CorporationUS03 · AD/CVD$96,120.00Draft · from SHP-2026-000144
✓ Type 01 / 03 / 11✓ ISF 10+2✓ CBP 3461 / 7501 preview

Form 7501 validation

The rejection you're about to get from CBP — caught here first.

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.

  • Runs unconditionally server-side at transmit — 422, regardless of what the client believes
  • Readiness-score threshold is configurable
How to demo
Click Validate on a filing with a gap. Read the blocker list aloud. Fix the classification, re-validate, watch it clear to Ready for Broker Review.
Customs Filing/QBR-2026-3231902
JT
Joe · Target
✕ 2 blockers — cannot transmit
ALL_LINES_HAVE_APPROVED_DECISION2 lines: HTS present, no approved classification
PORT_OF_ENTRY_VALID_ACE_CODE"Los Angeles" → no 4-digit ACE code
✓ 9 checks passed
REQUIRED_7501_BLOCKS_POPULATEDpass
IMPORTER_CBP_NUMBER_VALIDpass · 9 digits
BOND_NOT_EXPIREDvalid until 2027-03-31
NO_BLOCKING_EXCEPTIONSpass
HTS_RELEASE_CURRENT2026 Rev 14 · 3 days old

HTS duty & MPF engine

Duty math you can trace to a published rate.

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-by-line: HTS → rate → extended value → duty
  • Section 301 applied where the rate exists in the data
  • Recomputed at creation, at transmit, and at 7501 build
  • Once approved, the 7501 draft exports to a filer profile as CSV, fixed-width CATAIR, or JSON — with a required warnings acknowledgment and a full export history
How to demo
Open the 7501 Preview tab. Walk one line end to end. Note the rate came from a named HTS release, staged DRAFT and published by a person.
QBR-2026-3231809·7501 Preview
FR
Frank
LineHTSValueRateDuty301
1 · Lithium-ion cells8507.60.0020$61,200.003.4%$2,080.80List 3 · 25%
2 · Battery mgmt boards8537.10.9170$44,900.002.7%$1,212.30—
3 · Enclosure, aluminum7616.99.5190$36,300.002.5%$907.50—
Entered value
$142,400.00
Regular duty
$4,200.60
Section 301
$15,300.00
MPF (capped)
$634.90

Declaration snapshot & CBP lifecycle

What was filed is frozen. Where it stands is one screen.

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.

  • Transmit is blocked until a licensed broker explicitly approves — a real state-machine transition, on record with who approved it and their license number
  • One stateful primary button walks the filing through check → approve → submit (and resubmit after an agency rejection); Approve for Transmission freezes the declaration under a submission hold, and filings already with the agency are read-only
  • Optional maker/checker is an account setting (off by default, Workflow policies tab): when on, the preparer cannot approve or transmit their own filing — enforced in the approve and transmit routes
  • Reject → correct the data → Save & Resubmit, threaded to the original
  • Cancellation is request-then-confirm, with the country-specific fields it needs
How to demo
Open the Response tab on a transmitted filing — walk the status history. Then the Declaration tab — point at the version number: "this is what CBP got."
QBR-2026-3231761·Response
JT
Joe · Target
Status history
Draft → Ready for Broker Review  · validate.pass · 09:14
Broker Approved  · S. Chen, License #12345 · 09:22
Transmitted  · snapshot v3 · SUBMIT · 09:23
Accepted  · cbp.accept · 09:41
Released  · cbp.release · 11:08
Declaration versionv3
Message threadSUBMIT → CBP_ACCEPT → CBP_RELEASE
Post-summary correctioneligible · 297 days remain

Canonical multi-country messaging

Adding Germany was a spreadsheet, not a sprint.

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.

  • Outbound / inbound messages validated against versioned JSON Schemas
  • A new child action (e.g. AMEND) is one seed row
  • Country/authority code lists (Type/Header/Item/Translation) bulk-load from one CSV, no per-country code
  • Which filing-status transition a CBP response triggers is itself a seed row — keyed by (country, message, response status), not hardcoded per country in application code
  • Filing Status Catalog gives every response code a canonical label and locale translations
  • Form fields bind to those same code lists as Lookup/Dropdown pickers — a real master table (Carrier, Country, Schedule B, Commerce Control List, ACE port), validated client- and server-side, never a hardcoded option list
  • Filing Configuration (platform admins only) is organised in nine groups: Catalogs (document, schema, procedure, message, status, action), Customs Versions (per country and per customer), Procedure Setup (procedure, action mapping, action configuration, action data exclusions, document configuration), Declaration Setup (declaration control, workflow, status transitions), UI & Validation (UI configuration, search fields and sources, filing validations), Code Lists, General Customs Files (country, port, unit of measure, carrier), US Customs Export Files (Schedule B / HTS, AES license codes) and Operations (submission holds)
  • Repeatable sections — multiple parties, multiple containers, multiple line-level attachments — render as add/remove/reorder array-of-object panels wired straight into the filing schema, not a fixed set of fields
How to demo
Open Filing Configuration. Show the Catalogs and Procedure Setup groups, then Code Lists → Code List — upload a CSV and the codes are live. "A country is data. That's the enterprise-scale story — one platform, not one integration per authority."
Filing Configuration/Procedure mappings
PA
Platform Admin
CountryEntry typeProcedure codeAuthorityMessage
🇺🇸 US01 ConsumptionCONSUMPTIONCBP · ACE/ABIUS_ENTRY_SUMMARY_v4
🇺🇸 US03 AD/CVDCONSUMPTION_ADCVDCBP · ACE/ABIUS_ENTRY_SUMMARY_v4
🇩🇪 DE01 Consumption4000Zoll · ATLASDE_CUSDEC_v2
🇩🇪 DE21 Warehouse7100Zoll · ATLASDE_CUSDEC_v2
🇩🇪 DE23 TIB5300Zoll · ATLASDE_CUSDEC_v2
FilingAuthorityConfigFilingMessageCatalogFilingResponseStatusMappingFilingChildActionRuleFilingCodeListHeader/ItemFilingStatusCatalog

Filing Configuration · rules as data

Validation rules, status transitions and submission holds are all configurable.

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.

  • Filing Validations: business rules scoped to a country, procedure and message name. Each rule has a severity of ERROR or WARNING, and a rule set is DRAFT, ACTIVE or INACTIVE, with change history. Only the ACTIVE rule set is run against a filing
  • ERROR blocks, WARNING informs: a failed ERROR rule that has not been overridden is a blocker. The Validate step returns it with a 422 and does not advance the filing. A failed WARNING is returned as a warning and blocks nothing. At submit, the filing gateway validates the saved copy first and returns REJECTED, with the results, before anything is sent to customs
  • Override: a broker can override a saved failed result so it stops blocking. It needs the compliance.override permission (default roles: Broker Admin, Owner, Admin). An override is honoured only if it was recorded after the filing was last changed, so editing the declaration makes it stale
  • Status Transitions: for a country, procedure, message and release, a current status plus a response status maps to a target status. The behaviour is APPLY, IGNORE or REVIEW, with an optional reason
  • Submission Holds: a declaration is frozen while a broker reviews it for submission. Admins see who holds it, when it expires and whether it is active or expired, and can release a hold
  • Releasing a hold warns that the broker must reopen the review
How to demo
Open Filing Configuration → UI & Validation → Filing Validations, then Declaration Setup → Status Transitions, then Operations → Submission Holds.
Filing Configuration/Submission Holds
PA
Platform Admin
DeclarationHeld byStatus
Reference ABroker 1ActiveRelease
Reference BBroker 2ExpiredRelease
ERROR / WARNING rulesAPPLY / IGNORE / REVIEW

Filing Configuration · declaration behaviour as data

What a declaration may do, how it looks, and which customs version it follows.

Platform admins set these per country, procedure and message from the Filing Configuration menu. No code change.

  • Declaration Control: for a country, procedure, message, status and release, sets whether Save and Transmit may Create, Replace or Discard
  • Declaration Workflow: maps an inbound response to a declaration status, with optional JEXL conditions evaluated against the request and response. A lower sequence number is evaluated first
  • UI Configuration: the form fields and layout for declaration and response views, per country, procedure, message, message type and release. Publishing checks the configuration and its master-data sources first, then makes the draft active and retires the previous active one for the same release
  • Search Fields: the searchable filing fields, each with a group, display order, a Draft, Active or Disabled status and per-locale descriptions. A missing translation shows the field key
  • Search Sources: the JSON path a search field reads, per country, procedure and message. Only a scalar field from the configured canonical schema is accepted, and a duplicate source is refused
  • Country Customs Versions: a release for a country and procedure with a valid-from date and an optional valid-to date. Customer Customs Versions then map a specific customer, or all customers, to one of them
How to demo
Open Filing Configuration → Declaration Setup → Declaration Control and Declaration Workflow, then UI & Validation → UI Configuration and Search Sources, then Customs Versions → Customer Customs Versions.
Filing Configuration/Declaration Control
PA
Platform Admin
CountryProcedureMessageStatusAllowed action
Country AProcedure 1Message 1Status 1Create
Country AProcedure 1Message 1Status 2Replace
Country AProcedure 1Message 1Status 3Discard
Declaration WorkflowUI ConfigurationSearch SourcesCustoms Versions

Filing Configuration · reference files

The customs reference files behind the pickers are maintained in the product.

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.

  • Country (ISO Code): country codes and descriptions, with each country's states and provinces
  • Port Codes: Schedule D and Schedule K ports. Search by code, name or country, filter by code system and active state, and add or edit ports. The same code under the same code system cannot be added twice
  • Unit of Measure: the CBP ACE Appendix K list. It is seeded, so you edit a unit's description and its DDTC, DEA, EPA and LCPO allowed flags rather than adding units
  • Carrier: code, name, type (Ocean, Air, Rail, Road, Courier, Postal or Other), mode of transport and country. Add and edit carriers; the code cannot change once set
  • Schedule B / HTS Code (US Customs Export Files): read-only reference ingested from the Census Bureau, searchable by code, description or classification type
  • AES License Code (AESTIR Part III, Appendix F): the code itself is protected. You edit the description, export licence number, and the flags for ECCN mandatory, licence value required and active
  • Each licence code carries sub-codes you can add, edit and remove: not-allowed MOT codes, allowed EIC codes and allowed ECCN codes
How to demo
Open Filing Configuration → General Customs Files → Port Codes, then US Customs Export Files → AES License Code and open one licence code to show its MOT, EIC and ECCN sub-codes.
Filing Configuration/AES License Code
PA
Platform Admin
CodeECCN mandatoryLicence value requiredActive
Code AYesYesActive
Code BNoNoInactive
Not-allowed MOTAllowed EICAllowed ECCN

Clear · Valuation & Assists

Buyer-provided assists are tracked as one balance across entries.

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.

  • An assist has a status of Draft, Active, Suspended or Amortized, an importer, effective dates, and a remaining value shown against its total. A draft does not affect any entry until it is activated
  • Matching rules: suppliers and manufacturers, HTS prefixes (4, 6, 8 or 10 digits) and an optional SKU pattern
  • Allocation method: lump sum, equal allocation (per entry or per unit) or value proportional. The form previews the amount, and the actual amount is capped at the remaining balance
  • On a filing the broker includes, overrides or dismisses each matching assist. An override needs the valuation.override permission and a reason code. A decision is staged for the next submission and does not move the balance
  • On submission the declared amount is apportioned to the entry lines and deducted from the remaining value, and the assist becomes Amortized at zero. Each step writes an audit log entry
  • Viewing needs valuation.read and creating or changing an assist needs valuation.update
How to demo
Open Clear → Valuation & Assists, add an assist, then show its remaining balance and the history view.
Clear/Valuation & Assists
BR
Broker
AssistTypeAllocationStatus
Assist AToolingEqual allocationActive
Assist BMaterialsValue proportionalAmortized
Include / Override / DismissAudit log

Broker packet export · QUBERE_BROKER_XML

Hand a licensed broker everything they need — one gated, versioned 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.

  • Approved values never get silently replaced by a declared value — both travel, clearly labeled
  • Content-hashed and versioned: an unchanged filing re-exports the same packet, any real change stamps a new version
  • Screening, classification, and origin status ride along as a compliance block, not a side lookup
How to demo
Open a ready filing → Export → Broker Packet (XML). Point at the Consignee/Exporter roles and the approved-vs-declared HTS pair on a line. "Your broker gets one neutral format, not a screen-scrape of our UI."
Customs Filing/QBR-2026-3231809
JT
Joe · Target
LineApproved HTSDeclared HTSApproved COOValue
18471.30.01008471.30.9100 evidence onlyDE€58,900.00
ConsigneeExporterscreeningStatus: CLEAREDcontentHash v3

PGA-by-HTS screening · coverage matrix

Know which agency needs a filing before CBP tells you.

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.

  • Compliance Checks panel and the Entry Proof builder both consume the same screen — one engine, not a UI-only badge
  • The assistant's get_pga_requirements tool reports cleared vs. unscreened distinctly, never collapsing "no filing needed" and "we don't know" into one answer
  • Said plainly: the reference table is curated/manually-imported seed data plus a bulk-import route — not a bulk CBP CATAIR Appendix PGA feed. A CBP-sourced HTS-to-PGA lookup (asked through the ABI client service) now exists alongside it: replies are ingested with provenance, "not on file" is kept as unknown, and CERT answers are labelled and never used for screening. It runs only where a deployment has configured the filer account, port and environment. Real and wired end to end, honest about the data source.
How to demo
Compliance → PGA Coverage — the coverage-matrix dashboard: rows per agency/granularity, last-verified date, source-type breakdown. Then a shipment's Compliance Checks panel showing a cleared line next to an unscreened one. "We tell you what we don't know, too."
Compliance/PGA Coverage
JT
Joe · Target
HTSAgencyGranularityLast verifiedState
8507.60.0020FDAchapter2026-08-02cleared
3808.94.5010EPAline2026-07-28requirement_found
9018.90.7580FDAheading—unscreened
SHP-2026-000188 · Compliance Checks
Line 2 · EPArequirement_found · form EPA 3540-1
Line 3 · FDAunscreened · no reference row

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 byte sent to CBP, hash-chained. Every rejection code, tested before it's live.

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.

  • Surfaced as a "Transmission Audit" tab on the filing, plus an export route that serves the record as a proof file
  • Backed by a CBP transaction test harness — 14+ scenarios: valid accept, missing-mandatory-field, invalid HTS/importer/filer/port/country/quantity rejects with real CBP condition codes (613, 875, 045, 031, 439), duplicate transaction, timeout, connection failure
  • Covers pre-transmit validation, CATAIR line assembly, and E0/E1 + X0/X1 response parsing end to end — the codec that produces what gets hash-chained is itself under test
  • Each rejection scenario carries the real ACE ABI error-dictionary code and narrative for that exact defect (e.g. invalid importer → code 101 "Importer Unknown", invalid bond → code S22) — checked against the dictionary before a run is allowed to pass, not a placeholder code
  • Certification dashboard access is gated by the same platform RBAC as the rest of the admin surface — no environment-variable bypass, no ordinary tenant-admin loophole
  • Dispatch marks a filing PROCESSING the instant it's picked up for transmission, closing the race window that could otherwise send one filing to CBP twice
How to demo
Open a transmitted filing → Transmission Audit tab — show the chained records and export the proof file. "This isn't a log table someone can UPDATE. Break one row and the chain tells you."
QBR-2026-3231761·Transmission Audit
JT
Joe · Target
Chained records
SUBMIT · recordSha256 a1f0… · prev 0000… · 09:23
CBP_ACCEPT (E0) · recordSha256 7c2e… · prev a1f0… · 09:41
CBP_RELEASE (E1) · recordSha256 9b44… · prev 7c2e… · 11:08
CBP test harness · sample scenarios
Invalid HTS rejectcondition 613 · pass
Invalid port code rejectcondition 031 · pass
Duplicate transactionpass
AbiTransmissionRecord14+ CBP scenariosE0/E1 + X0/X1 parsing

Customs Bonds

You can't file without one. Qubere tracks whether it's still enough.

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.

  • Stacking logic recommends a Single Transaction Bond or a continuous-bond rider when projected volume would exceed current coverage
  • A 30-day expiration sweep flags upcoming lapses and auto-marks a bond expired the day it lapses — both write to the audit log, not just a UI badge
  • ISF filing cross-checks this same bond table before it will let a filing submit
How to demo
Ask Qubere "is our continuous bond still sufficient?" — it calls the same sufficiency check the nightly sweep runs, not a canned answer. Note honestly: the "Verify CBP Status" button on the Bonds screen is a UI placeholder today, not a live CBP query — the sufficiency, stacking, and expiration engine is what's real and running continuously.
Bonds
JT
Joe · Target
Continuous bond · insufficient
Required (10% · trailing 12mo)$180,000
Actual bond amount$150,000
Shortfall$30,000
Stacking recommendation
TypeCONTINUOUS_RIDER
DetailRider increase recommended over STB stacking
nightly sweep · bond-monitor cronBond.status auto-updated

Filing Compliance Gate

Thirteen required checks, every filing, even the ones with no shipment behind them.

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.

  • 316 CATAIR-mandatory field rules run as part of the same gate that checks the compliance agents — one pass, not two overlapping systems
  • A standalone filing derives its line items, parties, and destination straight from declaration data and runs all 13 required agents against it
  • Restricted Party Screening on a standalone filing is recorded as an honest NEEDS_REVIEW with a clear reason rather than a false pass — there's no party-master row to screen against yet
  • Every gate evaluation writes a PipelineRunAudit row, shipment-linked or not, so the same audit trail exists either way
How to demo
Create a filing with no linked shipment, run Validate, and show all 13 required agents actually execute — including an honest NEEDS_REVIEW on party screening instead of a silent skip.
Customs Filing/QBR-2026-3231990 (standalone)
JT
Joe · Target
PGAPASS
AD/CVDPASS
Duty bond sufficiencyPASS
FTA qualificationPASS
Restricted party screeningNEEDS_REVIEW
ReasonNo party-master record to screen — declaration-only name, honestly flagged
CATAIR mandatory-field rules (316) run in the same gate pass as the compliance agents

Inline blocker resolution

Fix the blocker where you found it — never bounced to a page that can't clear it.

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.

  • Classification blockers reuse the same approval action the Products page uses, against the exact flagged line
  • Agent-decision triage reuses the existing reject/approve flow, posted to the same bulk-decisions endpoint the Actions page calls
  • A readiness-score blocker shows the real breakdown and a "Re-run Reconciliation" button backed by the same query the reconcile route already uses — the two can never disagree
  • A missing-field blocker scrolls to and highlights the exact input on the page; multiple missing fields list in the popup instead of guessing which to jump to
How to demo
Open a filing with a classification blocker, click it, approve the classification in the popup without leaving the page, and watch the blocker clear on re-validate.
Customs Filing/QBR-2026-3231902
JT
Joe · Target
Resolve without leaving Filing
LineLine 2 — Laptop computer
Classification statusPENDING_REVIEW
Same POST /api/products/[id]/classifications/[id] the Products page calls — not a separate code path

AES · US Export

Export filings in the same workbench as imports — with only the checks that apply to exports.

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.

  • Each USPPI row gets its Shipment Reference number from the server as soon as it is added, not at save
  • Commodity lines carry a running sequence number that stays stable when another line is deleted
  • With the tenant preference on, matching commodity lines are merged before every save, validate and send, and the user is told before it happens
  • Declaration tabs for exports: Parties (USPPI, Authorized Agent, Ultimate and Intermediate Consignee), Shipment, Commodities, Response Details
  • Document actions on a US export filing: Transmission, Shipper's Export Declaration, Shipment Accepted, Export Document Summary, plus a Routed Shipment Summary that is offered only when the filing is marked routed
  • An accepted USPPI cannot be deleted; the filing action is set to Cancel to withdraw it
  • Duty, 7501, valuation, preference and PGA import steps are hidden for US exports
How to demo
Open the Customs Filing Workbench, filter Country to US (Export) and Message Name to AES. Open a filing and show the party cards and commodity lines.
Customs Filing/Customs Filing Workbench
SR
Sarah
US (EXPORT) · AES 1.0.0Accepted
Registration Number / ITNreturned by the response
Importer of record · entry type · portnot applicable to exports
Declaration → Parties
USPPI · Authorized AgentComplete · Required
Ultimate Consignee · Intermediate Consigneeparty cards
Accepted USPPIcannot be deleted — set Filing Action to Cancel

ISF · Importer Security Filing

ISF 10+2 tracked from the lading date, with the data brokers keep chasing already mapped.

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.

  • ISF deadline anchored to the lading date and listed with the entry and duty deadlines
  • Seller, buyer and other shipment party roles map to single ISF party fields
  • Bill of lading details always available as a repeater on ISF forms
  • Consumption shipments get a recommendation to file ISF-10
  • CBP acceptance rules run in the validation service before submit; an ISF that cannot be built into a transmittable request is refused with a named error instead of being queued
  • Restricted-party screening is advisory for an ISF (CBP does not require it); a request that never reached CBP shows as Transmission Failed rather than looking submitted
How to demo
Open a consumption import filing, show the ISF deadline on the shipment, then open the ISF form and show the pre-mapped parties and the bill of lading group.
Customs Filing/ISF
SR
Sarah
Deadline anchorLading date
Seller · Buyermapped from shipment parties
Bill of ladingrepeatable group
Bondchecked before submit

Filing Templates

Save a finished filing as a template and start the next one from it.

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.

  • Save as Template from the filing page, with an option to save it for all users instead of only yourself
  • The New Filing flow lists templates that match the selected country, procedure, message and release, and the template can also be changed on the new filing screen
  • Filing → Templates lists every template with its message, procedure, country, release, active flag, and who created and last updated it
  • The template editor reuses the filing form; a template can be saved as is or as a new, renamed copy
  • The Templates menu item is shown to platform administrators on accounts with customs enabled
How to demo
Open a completed filing, choose Actions → Save as Template, then start a New Filing of the same type and pick the template. Show the Templates list as an admin.
Filing/Templates
SR
Sarah
Save as Template
Template nameentered by the user
Save for all usersoptional
New filing · matching templates
Country · Procedure · Message · Releasemust match
Selected templatepre-fills the declaration

Objection handling

Every hard question, answered directly.

"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

"The rejection you're about to get from CBP — we catch it here, before transmit."

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