Qubere Post-Entry Management
CBP Reconciliation, Duty Statements, Duty Statement Payments, Filer Admin Health, Prior Disclosure, Protests, and Post-Summary Corrections — each with its own deadline math, eligibility rules, and lifecycle, in one hub instead of seven disconnected spreadsheets.
The problem
What a compliance manager says about post-entry work today:
"We found out a protest window closed by missing it, not by a system telling us it was 30 days out."
No deadline visibility
"Nobody checks our fatal-error rate against the 5% ABI threshold until CBP flags it."
No compliance monitoring
"Our 1592 penalty exposure lives in a spreadsheet someone built once and never updates."
No repeatable calculation
How Qubere addresses it
Post-Entry hub
Reconciliation, duty statements and payments, prior disclosure, protests and PSC each get their own tile on the Post-Entry & Recovery hub, alongside duty drawback and entry reconciliation from a single entry point — no more remembering which corner of the app a given post-entry task lives in.
Flag now, bundle and transmit later
Flag an entry for value, classification, FTA eligibility, or 9802 at the time you file — the reconciliation deadline is computed from that entry's date, and a bundled reconciliation entry inherits the earliest deadline of everything inside it.
| RECON-2026-0018 | 3 entries | prepared |
| RECON-2026-0011 | 7 entries | transmitted |
PMS & daily statement deadline math
Periodic Monthly Statement deadlines are computed by walking business days — skipping weekends — to land on the true 15th working day of the following month; daily statements get the next business day. Every payment instruction runs through a real lifecycle, not a static status field.
| Statement | Type | Deadline | Status |
|---|---|---|---|
| PMS-2026-08 | Monthly | 2026-09-15 (15th working day) | Scheduled |
| DS-20260909 | Daily | 2026-09-10 | Settled |
Filer Admin Health
A rolling 30-day window tracks every ABI export's outcome and computes your live fatal-error rate against the regulatory 5% ceiling, alongside ABI credential and connection status — a read-only compliance dashboard, always current.
Duty Statements
Daily and Periodic Monthly Statements from CBP sit beside Duty Statement Payments. Each statement shows its payment instruction (status and deadline) or a link to set one up with the statement's number, type, date and filer already filled in. Statements still missing a final are called out, and you can ask CBP to send one again.
| Statement | Type | Payment | Status |
|---|---|---|---|
| Illustrative | Daily | Instruction set | final received |
| Illustrative | Monthly | Set up payment | needs attention |
Prior Disclosure
Enter culpability level, duty loss, entered value, and years elapsed — get a real statutory-cap calculation before you decide whether to disclose: fraud caps at domestic value, gross negligence at 4× duty loss or 40% of value, negligence at 2× duty loss or 20% of value, each collapsing to interest-only or duty-only once a valid disclosure is on file.
Protests
The protest deadline is computed from the entry's actual liquidation date the moment you start a new protest — and creation is rejected outright if that window has already closed, instead of silently accepting a doomed filing. Anything within 30 days of its deadline surfaces as urgent on the list view automatically.
| Protest | Grounds | Deadline | Status |
|---|---|---|---|
| PROT-2026-0044 | Classification | 2026-09-28 | urgent |
| PROT-2026-0031 | Valuation | 2026-11-02 | filed |
Post-Summary Corrections
Eligibility is checked against the entry's actual PSC window — a stored 270-day deadline tied to the shipment, not a guess — the filing status (must be Accepted, Released, or Liquidated, not Closed), and whether any line item already has an active drawback claim against it. Windows closing within 7 days surface as urgent automatically.
| PSC | Correction | Window closes | Status |
|---|---|---|---|
| PSC-2026-0102 | Value adj. | in 5 days | urgent |
| PSC-2026-0088 | HTS correction | in 61 days | ready |
Objection handling
| "Does this actually pay CBP or process the ACH transfer?" | No — Duty Statement Payments computes the correct working-day deadline and tracks the payment lifecycle end to end; it does not move funds itself. It's the compliance layer around your existing payment process. |
| "Is drawback part of this?" | Drawback recovery lives in its own workspace, covered in the Duty & Landed-Cost deck — this is the seven other statutory post-entry workflows, and PSC explicitly checks against active drawback claims so the two never silently conflict. |
| "What happens if we try to protest something already past its deadline?" | Creation is rejected outright — the 180-day window is computed from the real liquidation date at creation time, not left for someone to notice later. |
The close
Seven statutes, seven workflows, zero spreadsheets.
Next step: open Post-Entry, start a new protest against a long-liquidated entry, and show the deadline check reject it before it can even save.