EO 14411 Could Bring Foreign Export Declarations Into U.S. Entries
Primary lensCustoms enforcement
Sub-topicClassification and valuation
Evidence base9 records used
Use caseCustoms exposure review
Section 3(b) reaches a foreign customs file, not another U.S. form
Executive Order 14411 does not yet require filing a named foreign export document. Section 3(b) directs the Secretary of Homeland Security, within 90 days, to take steps to require submission of any documentation or information that a foreign exporter had to provide to its customs administration before export to the United States.
The order was signed June 3, placing the 90-day date on September 1. If implemented broadly, an importer could have to place the foreign export filing beside the U.S. entry. The practical problem would be explaining any difference between them.
The Federal Register and official CBP materials reviewed for this article as of July 17 did not include a Section 3(b) rule, form, data specification, or filing instruction. September 1 is not a confirmed effective date for a new importer submission. It is the date by which the order directs the Secretary to take steps to establish the requirement, not necessarily to complete a final rule or begin filer compliance.
The new risk is a mismatch across two customs filings
Section 3(b) of Executive Order 14411 makes the foreign customs submission relevant to CBP, while 19 CFR 141.86 defines core information in the U.S. invoice record. The records are not designed by the same agency and may be prepared by different parties at different times. Because each follows a different legal system, the comparison may involve different currencies, units, classifications, party identifiers, or correction procedures.
A discrepancy may reflect timing or legal definitions rather than evasion, but the importer still needs an explanation.
Consider the fields that may overlap when the relevant foreign record contains them. The exporter named abroad may not match the seller or manufacturer identified in the U.S. file. The export description may be commercially accurate but less specific than the description supporting the U.S. classification. A foreign tariff code should not be mapped mechanically to the HTSUS.
Possible explanations for a value difference include legal purpose, currency date, charge treatment, transfer-pricing steps, or a multi-party sale. The review should also check whether one record uses country of export where the other uses country of origin, whether the units differ, whether the foreign record groups goods that the U.S. entry separates, or whether a correction reached only one filing.
None of those differences is inherently improper. If CBP receives both filings, it could ask the importer to explain a material difference. An explanation documented before entry would be easier to defend than one assembled during an audit. The difference itself would not establish noncompliance.
The importer may be asked to explain a statement its supplier or foreign broker made to another government.
The importer may have to explain a filing it did not make
The U.S. importer of record sits at an awkward point in this design. Under 19 U.S.C. 1484, the importer uses reasonable care to make entry and provide information needed for release, duty assessment, statistics, and other legal requirements. Yet the source record contemplated by Section 3(b) originates upstream and may be created or controlled by a foreign exporter, foreign broker, forwarder, or local entity.
That gap changes the practical meaning of vendor management. A purchase order requiring “all customs documents” is not enough if the buyer does not know which document exists, who can retrieve it, whether it was corrected, or how long retrieval takes. A supplier may send a commercial invoice immediately while treating its export declaration as a local compliance record. A forwarder may hold the final accepted version. A related-party seller may use a classification or value convention built for the export country's rules.
If the foreign record becomes a routine submission, the importer will need a documented handoff before cargo moves. The parties must know who obtains the accepted filing, checks it against the entry, resolves differences, and retains the final version.
The order does not assign those roles or say whether the importer, broker, carrier, or foreign exporter will transmit the information. The eventual implementing action may distribute responsibility differently. Importers can still check whether they can obtain the source record.
A broker cannot reconcile facts it never receives. A broker can map a defined record to a CBP filing format and transmit what the client supplies. The broker cannot decide why an export value differs from U.S. entered value or which version of a corrected foreign filing is authoritative without source facts from the parties.
The review must begin before the broker handoff. Trade compliance needs procurement to identify every seller in the transaction, tax to provide pricing inputs, logistics to provide shipment data, and the foreign filer to provide the accepted record. If CBP makes submission routine, those materials will need to be reviewed together.
Intermediary purchases make access harder. The party sending the invoice to the U.S. buyer may not be the exporter or manufacturer. The party with access to the foreign customs portal may have no contractual duty to send an accepted declaration or later correction. The near-term task is to identify who controls each source record and whether the importer can obtain it in time.
CBP's retained-record model shows what Section 3(b) would change
Current U.S. recordkeeping provides the most useful comparison. Covered parties retain required records, and CBP may examine relevant records or demand required entry records in an investigation or inquiry.
19 CFR 141.86 already gives the U.S. file substantial detail, including parties, merchandise description, quantity, value, charges, origin, packing, and an English version of the invoice. The recordkeeping statutes sit behind that filing. 19 U.S.C. 1508 establishes the duty, while 19 U.S.C. 1509 allows CBP to examine relevant records and demand required entry records. CBP's Entry Summary Record-Keeping guidance, February 13, 2026 states the practical rule, with entry records generally kept for five years and produced on demand even when CBP waived production at entry.
Those authorities do not currently make every foreign export filing a routine U.S. submission. Section 3(b) could move foreign-source material from the edge of a company's supporting file into the submission workflow.
It could also change when an ordinary discrepancy becomes visible to CBP. Today, an importer may build its entry from the commercial invoice, purchase records, origin support, and broker instructions. If CBP later requests a retained foreign declaration in an audit, the timing and context of that request differ from a routine submission requirement. The importer would still have to produce required records within the time allowed under existing law. A routine or pre-release requirement could place the comparison in CBP's hands earlier. The implementing action would determine whether every covered entry must include the record, whether CBP limits submission to higher-risk entries, or whether importers provide it only after a defined request.
The order leaves the hard filing questions unanswered
Some countries use several export, transit, tax, or statistical filings for one movement. The implementing document will have to identify which one reaches the U.S. file and whether the importer supplies the document, selected data, or proof that no filing was required.
Harder cases begin when the exporter has no direct relationship with the importer or local law restricts disclosure. Translation, corrections, and consolidated filings will also need a workable path. The current invoice translation rule does not answer those questions for a new foreign record.
The scope of the eventual requirement will determine whether CBP receives foreign filings routinely or only in defined cases, and how much the process costs to operate. Retrieving one accepted export filing from a related company is different from collecting filings across many countries and unrelated suppliers.
The September deadline comes before the next COAC meeting
Executive Order 14411 says implementation must be consistent with applicable law, including the Administrative Procedure Act. 5 U.S.C. 553 requires published notice and an opportunity to participate for covered rulemaking, while identifying exceptions. Not every policy, form instruction, or guidance document automatically requires notice-and-comment. The implementation method determines when public input occurs and what binds filers.
A CBP notice on the Commercial Customs Operations Advisory Committee, Docket No. USCBP-2026-0463, July 13, 2026 postponed the July 15 meeting to September 23. That meeting now falls after the order's September 1 date. COAC is not the government's only channel for industry input, and the notice does not establish whether other engagement will occur. The postponed meeting cannot provide a public forum for input before September 1. The order does not require a completed final rule by that date.
Importers should watch the document that actually implements Section 3(b), not infer a duty from the presidential deadline. A Federal Register proposal could supply definitions and a comment period. A final rule could include an effective date and transition. A CBP notice, technical message, or form instruction could take a different route. Until that record appears, companies should map the data without inventing a filing requirement.
Importers can test access before CBP sets a format
A useful pilot can begin with a few high-value trade lanes. For each one, the importer can check whether a foreign filing was required and ask the supplier for the accepted version. The time and effort needed to retrieve it will expose gaps before CBP sets a format.
When the document arrives, trade compliance can compare the fields that overlap with the entry and ask the team responsible for the source data to explain each difference. The comparison should preserve units, currency, and correction history rather than force identical values.
A pilot should show whether the importer can obtain the required record, connect it to the right entry, and explain a difference. A missing record should first be distinguished from a shipment that required no filing or was subject to a legal disclosure restriction.
A narrow filing rule would cut the workload
The workload changes if DHS defines a small document set, limits the requirement to specified entries, or requires submission only after a defined request. A rule covering records importers already receive would be easier to operate than one requiring importers to collect every document mandated by a foreign customs authority. Whether a request-based approach satisfies the order will depend on the final text and legal basis.
Treatment of unavailable records and corrections matters as well. A clear exception and a way to explain legitimate differences would reduce the chance that routine inconsistencies delay release. Without either protection, an importer could face a hold while it resolves the discrepancy.
The implementing document should identify the covered records, filer, timing, and exceptions. For now, importers can test access without treating the executive order as a current filing instruction.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.