Preflight CAPE refund data before it enters the customs workflow
Saxum creates a controlled preflight: the claimed population is reconciled to source records, errors are surfaced, and every transformation is documented for professional review.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Current program snapshot
CAPE means Consolidated Administration and Processing of Entries. CBP launched its first phase in ACE on 20 April 2026 as an electronic pathway for eligible IEEPA duty-refund claims. Eligibility and customs strategy remain with the importer and its authorized customs professional.
Why the standard portal or checklist is not enough
Refund opportunities can involve large entry populations, repeated transformations and strict portal or broker handoffs. Formatting is only one risk; population completeness, duplicate logic and source traceability matter too.
Best-fit customer
Importers and customs advisers working on eligible entry populations
Problems this product helps control
CAPE refund data, ACE entry populations and IEEPA duty-recovery inputs that need reconciliation before a customer or customs adviser acts on them.
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- Candidate entry population
- Broker or ACE extracts
- Eligibility assumptions supplied by adviser
- Required import template or current instructions
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Population completeness check
- Duplicate and identifier exception register
- Format and field validation report
- Source-to-output traceability table
- Corrected draft where deterministic
- Broker/counsel review checklist
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Freeze
Record the source population and the eligibility assumptions supplied by the customer.
Validate
Check identifiers, duplicates, required fields and template conformance.
Trace
Bind each output row to its source evidence.
Handoff
Deliver a reviewable draft without claiming legal eligibility.
Connect refund eligibility work to deadlines, evidence and realized cash
CAPE cases can reconcile the customer-supplied entry population, preserve filing-date inputs, separate unsupported legal conclusions and show estimated, received and outstanding recovery amounts.
Deadline calendar
Surface customer-supplied filing and review dates without inventing protest, liquidation or eligibility deadlines.
Savings realization
Compare estimated refunds with amounts received and identify the remaining population requiring customer or broker action.
Controlled handoff
Assign exceptions, attach source documents, obtain professional review and release a signed packet only after blocking issues are resolved or explicitly waived.
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
Every engagement starts with scope confirmation. Pilot and research offers are intentionally limited until the workflow is proven on paid cases.
Request a CAPE data preflight →CAPE Refund Preflight FAQ
Direct answers on access, responsibility, deliverables and limits.
No. Eligibility must be confirmed by the importer’s customs professional or counsel.
No. The useful scope includes population completeness, duplicates, traceability and exception evidence.
No. Saxum prepares and controls the data handoff.
By record count, source-system complexity and the number of unresolved exceptions.
Yes. They serve the same importer journey but remain separate deliverables.
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 12 August 2026. Re-check before each engagement.
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
Saxum Control Platform
Run this workflow in the encrypted control room
Schedule or run the engine, apply saved mappings and connectors, assign exceptions, collect evidence, complete Human ReviewPass and publish signed outputs with measurable value reporting.
Open the control room