New U.S. Customs Rule: Your Export Filings Now Have to Match

What did the June 2026 customs executive order change for exporters?

On June 3, 2026, the White House signed an executive order titled "Strengthening Customs Enforcement." It directs U.S. Customs and Border Protection to require, within 90 days, submission of the paperwork a foreign exporter had to file with its own country's customs authority before shipping to the United States. In plain terms, your home export filing is about to become part of the U.S. import record.

The order's text is specific. Section 3(b) directs the Secretary of Homeland Security to take steps to mandate the submission of "any documentation or information that the foreign exporter was required to submit to the foreign customs administration prior to exporting to the United States." That is a new category of document at the U.S. border — one the importer never had to hand over before.

The order is Executive Order 14411, published at 91 FR 35125 on June 10, 2026. For most exporters the headline is simpler than the legal reading: the two records that describe your shipment — the one you file at home and the one your buyer files at U.S. entry — now sit in the same file, where a customs officer can compare them line by line.

What did CBP actually publish on September 2, 2026?

An advance notice of proposed rulemaking, not a rule. "Heightened Import Disclosures for Supply Chain Visibility" was published in the Federal Register on 2 September 2026 under docket number USCBP-2026-1058. Its stated action is "Advance notice of proposed rulemaking," and its comment period runs until 1 December 2026. There is no regulatory text to comply with yet, and no effective date.

What the notice does give you is a list. CBP writes that foreign export documentation "may include" the following six items, and every one of them is a document you already produce:

• Export declarations made by the foreign exporter to the foreign customs authority — CBP notes these "may show declared value, classification, and quantity."
• Commercial invoices "showing the transaction value declared to the foreign customs authority."
• Packing lists "to verify the contents, weight, and packaging of the shipment."
• Certificates of origin "submitted to the foreign customs authority substantiating the origin of the goods."
• Export licenses or permits "required for the export of controlled, restricted, or dual-use goods."
• Transport documents — bill of lading or air waybill — "that were required as part of the export manifest filing with the foreign customs authority."

The notice is equally explicit about what CBP wants to do with them. It asks how importers should build "internal controls and reconciliation processes … to identify discrepancies between the information on foreign export documentation and the entry or entry summary filed with CBP," and gives the example of a foreign export declaration listing "a different value, quantity, or classification from that on the entry summary." A separate question asks how an importer can be sure the document handed to CBP "is the exact document submitted to the foreign customs administration, and has not been modified." The purpose CBP names for all of this is detecting practices such as dual-invoicing.

One question in the notice is worth reading if you sell to U.S. buyers, because it is about you rather than about them: CBP asks what "lead time" importers currently need "to obtain foreign export documentation from their foreign suppliers." However that question gets answered, the answer describes a request that will land in your inbox.

Does this apply to a small exporter shipping to the U.S.?

Yes, if you ship to U.S. buyers. The legal duty to submit sits on the U.S. importer of record, but the document they have to produce is yours: the declaration you filed with your home customs authority. Whatever your country calls it, your buyer will now need a copy from you.

That export declaration goes by different names. In the European Union it is the export declaration behind the EX-1 / MRN. In India it is the Shipping Bill. If you export from the United States it is the Electronic Export Information filed through AES. The form differs; the principle does not — it is the official record of what you told your own government you were shipping, at what value, under which classification.

The practical change is that this record stops being private between you and your own customs office. Your U.S. buyer will ask for it, and it will be compared against the commercial invoice, packing list, and entry they file on the U.S. side. If your export declaration says one thing and your invoice says another, the gap is now visible at the border.

When does the requirement take effect, and is it in force yet?

It is not in force, and as of 9 September 2026 no date has been set. When this post was first written in July, the honest answer was that the executive order gave CBP roughly 90 days and that early September was the date to plan around. That window has now passed, and what arrived on 2 September was an advance notice asking questions — the earliest stage of U.S. rulemaking, before any proposed regulatory text exists.

The realistic sequence from here is: comments close 1 December 2026, then CBP may issue a notice of proposed rulemaking with actual text, then another comment period, then a final rule with an effective date. Each of those steps takes months, and none of them is guaranteed. Anyone telling you a foreign-export-documentation requirement starts in September 2026 is reading the executive order's deadline for CBP as if it were a deadline for you. It is not.

What is worth acting on is narrower and cheaper. Your U.S. buyers read the same news. Some will start asking for the export declaration well before any rule exists, because their own compliance teams would rather have it on file than scramble later. And the notice has already told you which figures will be compared when it does arrive.

For a one-to-ten-person exporter, "prepare now" does not mean new software or a compliance department. It means making sure the numbers on your export documents already agree with each other, so that when the two filings are read together there is nothing to explain.

Which fields have to agree across your export filing and the U.S. entry?

The two filings describe the same shipment, so the fields that identify and value it must read the same on both. CBP's own example of a discrepancy names three of them — value, quantity, and classification. Before the goods leave, check these six against each other; this is the short list an officer comparing the records would look at first:

• Parties. The exact legal name and address of the exporter and of the importer or consignee — matched, not abbreviated on one document and spelled out on the other.
• Commodity description. The same wording of what the goods are, not a paraphrase. "Cotton knit t-shirts" and "apparel" are not the same description to customs.
• HS / tariff code. The same classification to the same number of digits. A code that differs between your export filing and the U.S. entry is the clearest kind of discrepancy.
• Quantity and packages. Units, carton counts, and totals that tie out. The invoice, the packing list, and the declaration should agree on how much and how many.
• Value and currency. The invoice value and currency that match what you declared at export. Duty is assessed on value, so a mismatch here draws the most attention.
• Country of origin. One origin, stated the same way on every document — the invoice, the certificate of origin, and both filings.

None of these are new fields. They already appear on your commercial invoice and packing list. What changes is that a second reader — the U.S. entry — now has to see the same values you filed at home.

How do you keep your export documents consistent?

The mismatch risk is usually not fraud. It is copy drift. The commercial invoice, the packing list, and the certificate of origin get built at different times, often from an older file, and a value moves — a carton count updated on one document but not another, a description reworded, an HS code corrected in one place only. A customs hold that used to come from one filing looking wrong can now come from two filings not matching.

Three things reduce that risk without adding overhead:

• Build the invoice, packing list, and certificate of origin from one source of the shipment's facts, so a value entered once appears the same everywhere.
• Run the six-field check above before you file — parties, description, HS code, quantity, value, origin — comparing the documents to each other, not just proofreading each alone.
• Keep the export declaration and the commercial invoice in the same folder per shipment, so the two records that will be read together are stored together.

This is where a focused tool helps. ovrseas builds your commercial invoice, packing list, and certificate of origin from one master record, so the parties, HS code, quantity, value, and description carry across the set without re-typing — the same figures your export declaration and the U.S. entry both draw from. It does not file to any customs authority and does not check your classification for you; it removes the re-keying that creates the mismatches in the first place. For an exporter shipping 5 to 30 containers a month off spreadsheets, that is the gap worth closing.

The short version

Executive Order 14411 (June 3, 2026) directed CBP to require the foreign exporter's home-country documentation as part of the U.S. import file. On 2 September 2026 CBP responded with an advance notice of proposed rulemaking, docket USCBP-2026-1058, open for comment until 1 December 2026. Nothing is in force and no effective date exists. What the notice does supply is the target list — export declaration, commercial invoice, packing list, certificate of origin, export licence — and the fields CBP intends to reconcile: value, quantity, classification. The exposure was never the new form. It is your home export filing and the U.S. entry disagreeing. Get the six shared fields to agree across your documents now, and the cross-check has nothing to flag whenever it arrives.