// FIELD BRIEFING // THE TRADE UNDERGROUND

The Everlight Settlement Is a Trade Compliance Checklist: What to Do Monday Morning

A $5.15 million False Claims Act settlement hides a second, quieter allegation – one about a bill of materials, not a lie at the border. Most compliance programs would sail right past it. Here is the work order.

On August 5, 2026, the U.S. Attorney’s Office for the District of Maryland announced that Everlight Electronics Co., a publicly traded Taiwanese manufacturer of light-emitting diodes, and its Texas-based subsidiary, Everlight Americas, agreed to pay $5.15 million to resolve allegations under the False Claims Act, the common law, and the Tariff Act of 1930 that they knowingly failed to pay duties on LEDs imported from China. The case began as a qui tam complaint from a former employee, Tao Wang, who will take home $876,146 – about 17 percent of the recovery. United States ex rel. Wang v. Everlight Electronics Co., No. TDC-21-cv-1607 (D. Md.).

If you run an import compliance program, skip the headline number and read the allegations as a work order. The government described two distinct fact patterns, and the second one is not a story about a company lying at the border – it is a story about a compliance process that failed at the bill-of-materials level. Most programs are built to catch the first pattern and would sail right past the second.

// Two Fact Patterns – And Only One Is On Your Radar

From July 2018 through January 2022, the government alleged classic transshipment: Everlight knew the LEDs were made in China, routed them through Taiwan, and declared Taiwan as the country of origin to avoid Section 301 duties. Your existing controls – country-of-origin screening, transshipment red flags, supplier vetting – are designed for exactly this, and most teams would flag it.

From January 2022 through November 2025, the theory changes. The government alleged that Everlight imported LEDs from Taiwan that were nonetheless Chinese-origin “based on the country of origin of the dice of the LED” – the semiconductor die – because the company failed to segregate Chinese-made dice from Taiwanese-made dice during manufacturing. There is no forged label here. There is a real Taiwanese assembly operation that still produced Chinese-origin goods, because the essential component kept its origin and the shop floor commingled it.

That is substantial transformation applied at the component level. Under longstanding CBP practice, the origin of a semiconductor device generally follows the diffusion or fabrication of the die, not final assembly, packaging, or test. Assembly and test steps in a third country usually do not create a new article with a new name, character, and use.

“Assembled in Taiwan” is a claim you have to prove at the BOM level – not a conclusion you inherit from your supplier’s invoice.

// Run Substantial Transformation At The BOM Level – And Paper It

Pull your highest-duty, highest-volume part numbers and build a documented origin determination for each. Identify the component that imparts the essential character – for electronics that is typically the wafer or die; for other goods it may be a motor, an active pharmaceutical ingredient, or a casting – and trace where that component is actually made. Capture the tariff-shift or essential-character reasoning, the engineering inputs, and the conclusion in a file you can hand to an auditor. Under the reasonable-care standard, a contemporaneous, reasoned origin analysis is your best evidence that any later error was a mistake, not knowledge.

// Treat Commingling As A Control Failure, Not An Accident

Everlight’s second scheme was, at its core, a lot-segregation breakdown: Chinese and Taiwanese dice flowed into the same finished LEDs without a system to keep origins distinct. If your suppliers – or your own plants – mix same-part components of different origin, your origin declarations are only as reliable as your inventory controls. Ask for lot-level traceability, require origin to be preserved through each production step, and treat “we buy dice from multiple countries and pool them” as a finding that demands segregation or a first-in / worst-case origin rule, not a shrug.

// Tighten Supplier Declarations And Recordkeeping

Origin statements on a commercial invoice are not a determination; they are an input. Get manufacturer affidavits that name the die or critical-component source, build the right to audit into supplier agreements, and reconcile what suppliers certify against what your BOMs and engineering data show. Keep the supporting records for five years under the recordkeeping rules and make sure the origin analysis is part of the entry file – not sitting in an engineer’s inbox. When CBP issues a CF-28 or CF-29 on one of these lines, the quality of that file determines whether you are explaining a defensible position or scrambling.

// Build The Post-Entry Loop: Monitor, Self-Test, Disclose

The programs that survive this enforcement wave are the ones with a working feedback loop. Run periodic post-entry reviews on tariff-sensitive origin claims, sample them against supplier reality, and when you find an underpayment, use the prior-disclosure mechanism under 19 U.S.C. 1592(c)(4) before a whistleblower or a CF-28 finds it for you. A timely, complete prior disclosure caps exposure and is powerful evidence against the knowledge and reckless-disregard theories that drive False Claims Act liability. The Tariff Act’s Section 592 regime has always policed false statements at entry; what is new is the FCA’s “reverse false claim” overlay – knowingly avoiding an obligation to pay – which adds treble damages, per-claim penalties, and private relators.

// Assume The Tip Is Coming From Inside

The relator here was a former employee, and his roughly 17 percent share of a $5.15 million settlement is a standing advertisement to anyone who has seen the shop floor. The people who understand your dice sourcing and your origin logic are exactly the people who can hand the government its case. Make internal reporting easy, investigate concerns quickly, and document that you acted. A raised-and-ignored origin question is the difference between a negligent error and a knowing one under the FCA’s scienter standard.

// The Backdrop Is Not Softening

Everlight is not an outlier. On August 29, 2025, DOJ launched a cross-agency Trade Fraud Task Force pairing the Civil and Criminal Divisions with the Department of Homeland Security, and it has openly encouraged whistleblowers to file under the FCA. Recent customs FCA resolutions have reached well into the tens of millions, including a $54.4 million settlement with Ceratizit USA over evaded duties – the largest customs FCA settlement on record. With Section 301 tariffs still in force and the tariff landscape expanding, the number of entries carrying a plausible “knowing underpayment” theory has grown sharply.

A settlement carries no admission of liability, and the government’s “dice” theory is an allegation, not adjudicated law. But compliance teams do not get to wait for a litigated opinion. Assume CBP and DOJ will read substantial transformation the way Everlight suggests – to the essential component, not the final assembly step – and make sure your origin files can withstand a reviewer who already knows where the die was made.