LandedFees
All guides/Guides

From Flagged Finding to Filed Correction: The LandedFees Remediation Workflow

Customs compliance is a workflow problem, not a knowledge problem. The LandedFees remediation flow moves anomalies from detection to filed correction in five steps: audit surfaces the finding, findings queue triages by severity, tasks queue drafts the filing, approver signs off, reconciliation logs the outcome. Here is what each stage does and how the handoffs work.

Updated 2026-08-227 min read
remediationworkflowfindingstasks

Try the calculator

Run a real calculation for this lane in under a minute. Free, no card.

Open calculator

From Flagged Finding to Filed Correction: The LandedFees Remediation Workflow

Customs compliance is a workflow problem, not a knowledge problem. Most importers know the mechanics of Post Summary Correction, 1520(d) claims, and protests. What fails in practice is the handoff between "someone noticed a problem" and "the correction is filed with CBP within the statutory window."

The LandedFees remediation workflow is the pipeline that closes that gap. Five stages, each with a clear owner and a full audit trail. This guide walks through each stage and the handoffs between them. Start at landedfees.com/audit.

Stage 1: Audit surfaces the finding

Audit runs unattended on ingested entries. Sources include:

  • CBP Form 7501 PDF uploads to landedfees.com/audit.
  • ACE ABI data extracts for importers with automated pull authorized.
  • Broker-submitted CSV entry summaries for consolidated portfolios.

For each entry, the audit engine runs the pattern library in parallel:

  • HS classification cross-check against current HTSUS.
  • Chapter 99 stack analysis against current CBP CSMS anti-stacking notices.
  • AD/CVD scope check against ITA case database.
  • FTA eligibility check against Special column of HTSUS.
  • MPF cap and HMF applicability audit.
  • Duplicate fee detection.
  • Undervaluation red flag against FRED PPI benchmarks.
  • Drawback candidate identification against export declaration data (when available).

Each pattern produces zero or more anomalies per entry. Anomalies carry a severity (blocker, high, medium, informational), a recommended remediation mechanism, and a recoverable-dollars estimate.

Audit is fully automated. No human touches the entry at this stage.

Stage 2: Findings queue triage

Anomalies land in the findings queue sorted by severity and recoverable dollars. This is compliance analyst work: confirm the anomaly, add context, decide route.

Common triage decisions:

  • Confirm and route to task. Anomaly is real, remediation mechanism is clear, recoverable dollars justify the filing effort. Findings converts to task with the recommended filing type attached (PSC, 1520(d), protest, or drawback).
  • Confirm and dismiss. Anomaly is real but not worth remediation (recoverable dollars below threshold, or the correction opens exposure to a bigger issue). Dismissal is logged with reason.
  • Escalate. Anomaly requires manager or outside counsel review before deciding. Escalation routes to a manager queue with the finding context attached.
  • False positive. Anomaly is not real (audit engine mis-flagged). Feedback loops into the audit engine to reduce false positive rate.

Every triage decision is logged with timestamp, actor, and reason. The audit trail is preserved through the full lifecycle.

Blockers (undeclared AD/CVD scope, deposit rate mismatch on active order) auto-escalate to compliance manager. High-value findings above a configurable threshold (default 10,000 USD recoverable) auto-route for expedited review.

Stage 3: Tasks queue drafts the filing

Confirmed findings that need remediation land in the tasks queue. This is compliance analyst plus broker collaboration: prepare the filing package, gather supporting documentation.

The tasks queue drafts the filing package automatically based on the remediation type:

  • PSC: amended 7501 with the correction, supporting documentation checklist (producer affidavit for 232 derivative splits, USMCA certification for missed FTA claim, exclusion documentation for missed 301 exclusion), ACE ABI submission format.
  • 1520(d): cover letter on company letterhead, importer declaration, FTA certification of origin template, refund calculation, entry-line schedule.
  • Protest: CBP Form 19 template pre-filled with entry number, protested decision, grounds statement, and supporting exhibits list.
  • Drawback: drawback claim template with import entry reference, export declaration reference, drawback type (unused merchandise 1313(j), manufacturing 1313(a), or substitution).

Supporting documentation gaps are flagged. The task cannot move to approval stage until documentation is complete.

Tasks carry a deadline (PSC 314-day window, 1520(d) 1-year window, protest 180-day post-liquidation window) and surface in a deadline dashboard 30 days out.

Stage 4: Approver signs off

Every filing requires an authorized signer per company compliance policy. The approval stage is where the approver reviews the drafted filing package, verifies supporting documentation is complete, and either signs off (task moves to filed status) or returns to drafter with revision request.

The approver dashboard shows:

  • Pending approvals sorted by deadline urgency and recoverable dollars.
  • Full audit trail per task: detection, triage, drafting, current state.
  • One-click signoff or return-to-drafter with comment.

Approver identity and timestamp are logged. This is the record CBP wants when they open a compliance measurement audit.

After signoff, the filing package is submitted to CBP (via broker for ACE filings, direct to CEE for 1520(d)) and the task moves to filed status.

Stage 5: Reconciliation logs the outcome

The reconciliation queue tracks the filing through CBP acknowledgment, response, and final liquidation.

For a PSC:

  • CBP acknowledgment (usually within 48 hours).
  • CBP acceptance or rejection.
  • If rejected, back to tasks for revision.
  • If accepted, entry re-liquidates on the amended terms.

For a 1520(d) claim:

  • CBP receipt confirmation.
  • 90-day review clock under 19 CFR 181.31.
  • CBP approval or denial.
  • If approved, refund process and interest calculation.
  • If denied, protest within 180 days.

For a protest:

  • Port Director review.
  • Approval, denial, or suspension pending review.
  • On denial, escalation to CEE, and ultimately to Court of International Trade if pursued.

Reconciliation status is visible per finding, per task, per filing. Roll-up dashboards show portfolio-level recovered dollars, pending recoveries, and rejected filings requiring rework.

Handoff mechanics

Each stage transition carries a payload:

  • Audit to findings: anomaly details, severity, recoverable dollars estimate.
  • Findings to tasks: confirmed anomaly, remediation type, drafter assignee.
  • Tasks to approval: drafted filing package, supporting documentation completeness check, deadline.
  • Approval to filed: approver identity, signoff timestamp, submission channel.
  • Filed to reconciliation: CBP acknowledgment reference, expected response window.

Handoffs are logged. Nothing gets lost between stages.

Notifications and escalations

Configurable notifications keep the workflow moving:

  • New blocker finding: immediate notification to compliance manager.
  • New high-value finding above threshold: notification to compliance analyst queue.
  • Task drafted, awaiting approval: notification to approver.
  • Deadline approaching (30 days out): notification to task owner.
  • CBP response received on filed correction: notification to task owner.
  • CBP rejection: notification to task owner and compliance manager.

Notifications route via email, Slack webhook (enterprise), or Teams webhook (enterprise). Configuration is per-user and per-severity.

The audit trail as evidence file

Reasonable care under 19 USC 1592(a) is what separates a negligence penalty (2x the duty loss) from a fraud finding (up to the domestic value of the merchandise). The remediation workflow produces the audit trail automatically:

  • Timestamped detection log per anomaly.
  • Triage decision with reasoning per finding.
  • Drafting history with document version control per task.
  • Approver signoff with identity and timestamp.
  • CBP submission with reference number.
  • CBP response and outcome.

This is the evidence file that answers a CBP CF-28 compliance measurement request in one email. The alternative (reconstructing the audit trail from email threads and shared drives when CBP asks) is expensive and error-prone.

Integration with existing broker relationships

The workflow does not require replacing the broker relationship. It adds an audit and remediation layer on top:

  • The broker continues to file entries in ACE.
  • The audit engine ingests the filed entries and runs the pattern library.
  • Findings and tasks flow through the internal workflow.
  • Filing packages export to the broker for ACE submission (or direct to CEE for 1520(d)).
  • Filed status updates via broker webhook or manual confirmation.

For brokers who want the audit engine as a value-add for their importer clients, the API surfaces findings per client for the broker's review dashboard.

Multi-tenant workflow for broker service providers

Broker service providers running compliance for multiple importer clients get multi-tenant workflow support:

  • Findings segmented by importer.
  • Tasks assigned per client.
  • Approver roles per client (client-side signer vs broker-side signer).
  • Reconciliation tracked per client and rolled up per broker for portfolio metrics.

Broker-level dashboards show portfolio compliance health across clients, most common finding patterns, and recovery velocity metrics.

Run the workflow on your next audit

Start at landedfees.com/audit with a 7501 upload. Confirmed findings land in findings. Drafted filings flow through tasks. Filed corrections track through reconciliation. Full audit trail preserved end-to-end.

Related guides

Citations

Frequently asked questions

What is the LandedFees remediation workflow?

A five-stage pipeline that moves customs compliance anomalies from detection to filed correction. Stages: audit engine surfaces anomalies, findings queue triages by severity and recoverable dollars, tasks queue drafts the appropriate filing (PSC, protest, 1520(d), drawback), an approver signs off, and the reconciliation queue logs the outcome and tracks liquidation. Each handoff carries a full audit trail.

Who acts on each stage?

Audit runs unattended on ingested entries. Findings triage is compliance analyst work: confirm the anomaly, add context, decide route. Tasks drafting is compliance analyst plus broker collaboration: prepare the filing package, gather supporting documentation. Approval is compliance manager or authorized signer per company policy. Reconciliation is automated tracking with alerts on liquidation events.

How does the workflow handle escalations?

Each finding carries a severity (blocker, high, medium, informational) and a recoverable-dollars value. Blockers auto-escalate to compliance manager. High-value findings above a configurable threshold auto-route for expedited review. Approaching deadlines (PSC 314-day, 1520(d) 1-year, protest 180-day) surface in a deadline dashboard 30 days out.

Can I integrate with my existing broker workflow?

Yes. The tasks queue exports filing packages as PDF or ACE-compatible ABI files for broker submission. Filed status can be updated via broker webhook or manual confirmation. The workflow does not require replacing the broker relationship; it adds an audit and remediation layer on top.

What audit trail does the workflow produce?

Timestamped log of every stage transition per finding: initial detection, triage decision, task creation, filing package generation, approver signoff, filed with CBP, CBP response, liquidation outcome. This is the evidence file that answers a CBP CF-28 compliance measurement request in one email.

Ready to calculate?

Get a real number for your shipment in under a minute.

Free, no card, full breakdown of duty, VAT, freight, and fees.

Try the calculator Look up an HS code

Related guides

Undervaluation Red Flags: Benchmark Invoices Against FRED PPI Before CBP Does

CBP valuation enforcement runs on statistical anomaly detection at scale. If your invoice unit price is more than one standard deviation below the industry Producer Price Index benchmark, an Automated Targeting System flag is likely. Here is how the LandedFees engine benchmarks invoice values against FRED PPI series and factory-quoted comparables so importers see the flag before CBP does.

Section 338 Canada T-Minus 8: 19 CFR 146.3 Port Director Escalation Timeline and the 30-45 Day Response Math

Section 338 duties on covered Canadian-origin imports take effect August 19 2026 at 12:01 AM EDT. Eight days out and CBP has still not published a CSMS message, which means FTZ operators are working from the July 20 2026 Presidential Proclamations 11061, 11062, and 11063 plus their Annex II subheading lists as the only authoritative source. Operators asking for CSMS before coding Form 214 admission under Privileged Foreign are creating a filing bottleneck that only a written port director determination under 19 CFR 146.3 can resolve. This walkthrough covers the 30 to 45 day CBP response norm on 146.3 requests, the pre-cliff vs post-cliff filing math, why documented escalation still protects the Post Summary Correction and 19 USC 1520(d) refund pathway even when the letter lands after August 19, and the concrete duty numbers on a 500k CIF Ontario furniture entry where the difference between running the 146.3 request and accepting the operator's verbal is 250k in avoidable duty.

Textile Substantial Transformation Under 19 CFR 102.21 vs 134.35: Which Rule Controls Section 301 Forced-Labor Tier Assignment

Post-July 24 2026 Section 301 forced-labor tier assignment for Chinese-origin textile and apparel content is not controlled by the default substantial transformation rule at 19 CFR 134.35. It is controlled by the textile-specific rules of origin at 19 CFR 102.21, which apply a distinct hierarchy that in most cases fixes country of origin at the location where the fabric was knit or woven, not where the garment was cut and sewn. This walkthrough covers the 19 CFR 102.21(c)(1) through (c)(5) hierarchy, the fabric-formation test, why Vietnam and India-origin garments with Chinese yarn or fabric inputs typically flip to Chinese origin for Section 301 forced-labor tier purposes, the BOM and tariff-shift documentation CBP is requesting for Tier B claims, and how tier-2 supplier origin declarations become load-bearing when the mill invoice trail is thin.

Section 338 Canada T-Minus 12: FTZ Privileged Foreign Election Deadline and In-Transit Rule Absence

Section 338 tariffs on covered Canadian-origin imports go live August 19 2026 at 12:01 AM EDT under Presidential Proclamations 11061, 11062, and 11063. Unlike Section 122 which included an in-transit exception for goods on water before the effective date, the three July 20 2026 Section 338 proclamations contain no in-transit rule. This is a hard cliff: liquidation snaps to date of entry per 19 CFR 141.68 regardless of when the goods left Canada. The only pre-effective planning lever is a Foreign Trade Zone Privileged Foreign election filed before the August 19 cutoff, which locks the pre-S338 duty status and preserves the option to withdraw the goods later at the pre-S338 rate. This walkthrough covers the FTZ Privileged Foreign mechanic under 19 USC 81c(a), the CBP Form 214 filing procedure, the interaction with USMCA which does not waive Section 338, and the T-12 through T-0 operational checklist for importers holding Canadian goods in bonded warehouse or FTZ.