Document Management & Recordkeeping
Every uploaded original is stored immutably, hashed, and re-verified on every read. Every extracted fact traces back to a page and a box. One click assembles the audit package CBP would ask for — so 19 U.S.C. § 1509 recordkeeping stops being a shared drive and a prayer.
The problem
"Trade documents are in email, a shared drive, and the broker's system. No single index. Someone sent a revised invoice — is it the one we filed on?"
No system of record
"A CF-28 or audit request lands and we spend two weeks assembling the file."
Audit fire drill
"We can't prove a document wasn't altered after the fact."
No tamper-evidence
How Qubere addresses it
Immutable vault & provenance
Original bytes stored once, SHA-256 re-verified on every read. Every extracted field: page → bounding box → canonical artifact → original. Absence is preserved — a null page means the parser didn't report one, never a default.
One index · inbound email · reconciliation
Forward documents to a client-specific address. Clean files enter the document pipeline; clear matches attach within that client. Unknown senders and conflicting shipment identifiers wait in Email review, with evidence beside the decision.
| Document | Type | Shipment | Source | State |
|---|---|---|---|---|
| bol_scanned_0912.pdf | Bill of Lading | SHP-000144 | OCR retry | |
| commercial_invoice_88.pdf | Commercial Invoice | SHP-000144 | portal | active v2 |
| packing_list_88.pdf | Packing List | SHP-000144 | upload | conflict: total ≠ invoice |
Source-of-truth precedence
A $500 delta between packing list and invoice used to always freeze on a manual review. An account can instead publish a precedence policy — "packing list wins on total value" — and every future conflict on that field resolves the same way, with the resolution itself written once as a durable, auditable record.
Document Rules Studio
A broker's per-account requirement — always flag a packing list with no signature, always route a certain client's invoices for a second look — is authored as a typed, versioned rule instead of a code change or a note in someone's head, and it goes through the exact same audit trail as every other action on the record.
Field-level explanation
Next to any field on record is an explain control that reads the same provenance chain — source document, page, confidence signals, and any precedence or reconciliation decision that touched it — and states it as a short, sourced answer instead of prose someone has to write by hand for an audit response.
Correction-learning rule suggestions
Every recorded field-review correction is aggregated by field and document type. Once a field crosses a real repeat-correction threshold, it surfaces as a suggestion — evidence a reviewer can act on, never an auto-applied change to the record.
Audit room · Reasonable Care package
One click assembles a Reasonable Care package and a Focused Assessment file for a ±7-day window around a filing — the declaration, the classification decisions with evidence, the documents, the timeline. Every compliance audit run is timestamped and exportable as importer due-diligence evidence.
Automatic customer document package
Publishing an Entry Proof now automatically assembles a customer-visible package — every document tagged for customer visibility, plus a generated CBP Form 7501 PDF — into a single zip stored as a new, portal-visible ShipmentDocument. Nobody has to remember to build it by hand.
Cross-shipment duplicate detection
Every inbound attachment — whether it lands through normal processing or is released out of quarantine — is checked against documents already on file elsewhere in the account. A match surfaces as an advisory notification to the people who can act on it, without ever blocking storage or parsing.
Relevance-ranked full-text search
A GIN-indexed, weighted full-text vector now sits on every document, so a search term ranks the best match first instead of just filtering. Filenames and identifiers weigh higher than incidental text, and the same query still works even against a database that hasn't run the latest migration.
| Document | Rank | Shipment |
|---|---|---|
| commercial_invoice_88.pdf | 0.91 | SHP-000144 |
| acme-manufacturing-rate-card.csv | 0.44 | SHP-000112 |
| packing_list_88.pdf | 0.31 | SHP-000144 |
Canonical file naming
Alongside the untouched original filename, every document now carries a generated, canonical display name — {documentType}_{shipmentNumber}_{YYYYMMDD}{ext} — built the moment the document intelligence agent classifies it. The messy inbound name stays on record; the canonical name is what people actually see.
Objection handling
| "Do you replace our DMS / SharePoint?" | For trade documents, yes — with provenance and audit-packaging those systems don't have. It's not a general enterprise content platform. |
| "Retention policy / legal hold?" | Originals are immutable and audit-logged. Formal retention-schedule automation and legal-hold workflow aren't first-class yet — the guarantee today is "nothing is mutated or silently deleted." |
| "Can we bulk-import our back catalog?" | Documents can be uploaded in bulk and extraction runs on each. There's no dedicated historical-archive migration tool — scope a large back-file as a services engagement. |
The close
Immutable originals, versioned processing, and a one-click ±7-day evidence bundle. That's the § 1509 answer.
Next step: bring a recent entry file. We'll upload the documents, show the provenance and reconciliation, then generate the audit package you'd hand CBP.
Full detail: docs/apps/customs/sales/document-management.md