A $5.2 Million Customs Settlement Shows Why Entry Data Needs Maker-Checker Controls

Customs filing is often treated as the last administrative step before cargo release. In reality, every entry is a financial and legal assertion about what the company bought, where it came from, what it is worth, and how it should be classified. When those assertions are wrong—or cannot be supported—the exposure can follow an importer long after the freight leaves the port.

A recent $5.2 million settlement puts that risk in concrete terms. It should prompt importers and freight forwarders to examine not only who transmits entry data, but who creates it, who independently approves it, and whether the organization can reconstruct every change.

The settlement is a data-governance warning

FreightWaves reported that Taiwan-based Everlight Electronics and its U.S. subsidiary agreed to pay $5.2 million to settle allegations involving falsified customs entries. The government alleged that inaccurate information was used to evade antidumping duties. The companies settled without admitting liability.

The enforcement environment is also intensifying. The same report noted that the Department of Justice Trade Fraud Task Force had surpassed $1 billion in civil and criminal recoveries in roughly one year. Another FreightWaves analysis said False Claims Act customs-fraud recoveries exceeded $570 million in the first five months of 2026—already above previous full-year totals.

Those numbers change the operational calculation. A weak control is not merely a paperwork defect. It can create duty underpayments, shipment holds, disclosures, penalties, legal expense, and reputational damage across thousands of entries.

Meanwhile, entry-level accuracy has become essential for recovering money as well as avoiding liability. Supply Chain Dive reported that U.S. Customs and Border Protection had paid $100 billion in IEEPA tariff refunds as of July 31. Whether an importer owes duties or seeks refunds, the transaction must be traceable to defensible entry data.

Assign an owner to every customs assertion

The customs broker transmits the entry, but the importer remains responsible for the business facts behind it. A reliable process assigns ownership before data reaches the broker.

Product identity: Merchandising, engineering, or product compliance should maintain an approved description tied to the SKU. Generic labels such as “parts” or “electronics” are not enough to support classification.

Country of origin: Sourcing and compliance should document where substantial transformation occurred. Supplier address, ship-from location, and origin are different fields and should never be substituted for one another.

Customs value: Finance and trade compliance should identify assists, royalties, related-party pricing, discounts, and other additions or deductions. The commercial invoice alone may not contain the complete customs value.

Tariff classification: A qualified classifier should select the code using product specifications and a written rationale. Reusing a supplier-provided code without review shifts no responsibility away from the importer.

Supplier evidence: Procurement should collect origin statements, bills of materials, affidavits, and certificates before the goods ship. Evidence requested after an inquiry is slower to obtain and less persuasive.

Broker transmission: The broker should submit only the approved data set and return the accepted entry record for reconciliation. Email instructions and spreadsheet attachments should not become an uncontrolled parallel master.

Put maker-checker approval ahead of transmission

A maker-checker control separates preparation from approval. The maker assembles the entry data and supporting evidence. The checker independently verifies high-risk fields before release to the broker.

The checker should compare the proposed entry against the purchase order, commercial invoice, product master, origin evidence, classification decision, and shipment record. The system should block self-approval and record the identity and timestamp of both people.

Risk-based routing keeps the process practical. Low-risk repeat entries with unchanged suppliers and products can follow a standard review. New SKUs, new origins, antidumping or countervailing duty exposure, related-party transactions, unusually low values, and manual overrides should require a senior reviewer.

Approval must cover changes as well as initial creation. If value, origin, classification, manufacturer, or duty treatment changes after approval, the entry should return to review. The audit log should preserve the old value, new value, user, time, reason, evidence, and affected shipment. Overwriting a field destroys precisely the history investigators need.

Connect corrections to the physical and financial record

Finding bad master data is only the beginning. A correction workflow should identify every affected purchase-order line, shipment, entry, invoice, duty payment, and customer transaction.

Start with an effective-date range and search both open and completed movements. Determine which cargo has not shipped, which entries are unliquidated, and which transactions may require a post-summary correction, protest, or prior disclosure. Compliance and counsel should decide the formal remedy; operations should provide a complete population rather than a hand-built sample.

Then reconcile corrective duties and refunds to the finance ledger. A customs adjustment should not live only in a broker portal. It should be connected to landed cost, inventory valuation, accruals, and the underlying shipment so management can see the full exposure.

Finally, test closure. Confirm that the master record is corrected, brokers received the new instruction, affected entries were addressed, and preventive controls now stop recurrence. Track the percentage of entries approved before transmission, override rates, evidence completeness, corrections by root cause, and time from issue discovery to containment.

Build compliance into the shipment workflow

Customs risk grows in the gaps between procurement, suppliers, brokers, finance, and transportation teams. A transportation platform can reduce those gaps by connecting orders, documents, approvals, shipment milestones, and exceptions in one controlled record.

CXTMS helps freight teams build auditable workflows around the data moving with every shipment. Request a CXTMS demo to see how structured approvals, document visibility, and exception management can strengthen import operations before an entry reaches customs.