When Your Customer Controls the Freight, Who Files the EEI? A Routed-Export and AES/EEI Filing-Governance Program

Who files the EEI in a routed export transaction?

In a routed export transaction, the foreign buyer (the FPPI) authorizes a U.S. agent to file the Electronic Export Information (EEI), and that agent becomes the filer. But routing the freight does not change who the U.S. Principal Party in Interest (USPPI) is, and it does not automatically move your export-control liability with it. That gap is what GingerControl, a trade compliance AI platform, is built to close: it governs the Schedule B classification, ECCN, and license research every EEI depends on, so the answer holds no matter which forwarder files.

Does authorizing your customer's forwarder to file the EEI transfer your export-control obligations?

No. Under the Foreign Trade Regulations, routing moves who files the EEI. Under the Export Administration Regulations, the USPPI still owns the license determination unless the foreign party gives a separate written assumption of that responsibility. Routed-export EEI filing governance means governing both.

When your customer controls the freight, the Electronic Export Information often gets filed by a forwarder you never see, or never gets filed at all, and the exposure still lands on you. A routed export transaction is one where the Foreign Principal Party in Interest (FPPI) authorizes a U.S. agent to file the EEI on its behalf under FTR 15 CFR 30.3, but it does not change who the U.S. Principal Party in Interest (USPPI) is. GingerControl is a trade compliance AI platform that governs the Schedule B classification, ECCN, and license research every EEI depends on, then standardizes the AES data prep, so routed shipments file under one rule set instead of scattered broker trust. For an exporter shipping under hundreds of Ex Works or FCA contracts a quarter, that is the difference between a clean audit trail and a penalty exposure that runs to $17,412 per violation.

Last updated: July 2026

Why routed-export EEI filing quietly becomes ungoverned

Most export compliance programs are built around the shipments the company controls: the USPPI arranges the freight, its forwarder files the EEI, and the data flows from the same catalog every time. Routed transactions break that model on purpose. The moment a sale moves to Ex Works, FCA, or FOB terms and the foreign buyer nominates its own U.S. forwarder, three things happen at once, and none of them are visible from your ERP:

The filer changes. The FPPI's U.S. agent now prepares and files the EEI, working from data your team hands over, not from your own system of record.
The authorization changes. Filing authority now flows from the FPPI to its agent through a power of attorney or written authorization your team never sees.
The liability does not change. You are still the USPPI. The EEI still carries your name, your EIN, and the classification and license data you supplied.

For a multinational exporter running hundreds of routed shipments a quarter across multiple legal entities, this is where fragmentation sets in. Different buyers nominate different forwarders. Each forwarder asks for data in a different format. Nobody owns the Schedule B numbers, the ECCNs, or the license determinations that populate the EEI, so they get re-derived, shipment by shipment, by whoever happens to be on the email thread. The result is the export-side twin of the data-silo problem trade teams already know on the import side: the same product classified inconsistently, license calls made without a governed rule set, and no single record of what was actually filed.

The pain is not that routed transactions are illegal or exotic. They are ordinary. The pain is that the responsibility split is real and the governance is absent, so the EEI gets mis-filed or unfiled and the USPPI carries a liability it cannot see.

Who files the EEI, the USPPI, the FPPI, or the agent?

Start with the definitions, because the whole responsibility split turns on them. Under 15 CFR 30.1, the USPPI is "the person in the United States that receives the primary benefit, monetary or otherwise, from the export transaction," and the FPPI is "the person located abroad who purchases the goods for export or to whom final delivery of the goods will be made." A routed export transaction is defined as "a transaction in which the FPPI authorizes a U.S. agent to facilitate export of items from the United States on its behalf and prepare and file the EEI."

The U.S. Census Bureau, which administers the Foreign Trade Regulations, puts the governance point plainly: a routed export transaction "changes who is authorized to file the EEI," but it does not change who the USPPI is. Only the filer moves.

Here is how the responsibilities actually split, standard versus routed, under 15 CFR 30.3:

Question	Standard export transaction	Routed export transaction
Who is the USPPI	The U.S. party receiving the primary benefit	The same U.S. party, unchanged
Who may file the EEI	The USPPI, or a U.S. agent the USPPI authorizes	The U.S. agent the FPPI authorizes (or the USPPI, only if the FPPI authorizes it in writing)
Who holds the filing authorization	USPPI to its agent (power of attorney or written authorization)	FPPI to its agent (power of attorney or written authorization)
Who supplies classification and value data	The USPPI or its authorized agent	The USPPI provides the Section 30.3(e)(1) data elements to the FPPI's agent
Who owns the EAR license determination	The USPPI as exporter	The USPPI, unless the FPPI provides a 15 CFR 758.3(b) writing assuming it

Two obligations survive the hand-off and land on the USPPI regardless of who files. First, the USPPI "shall retain documentation to support the information provided to the agent" and provide the agent with complete, accurate, and timely export information, and it must keep that documentation for five years from the date of export under 15 CFR 30.10. Second, the USPPI has a right it should always exercise: on request, the FPPI's authorized agent must provide the USPPI a copy of the power of attorney or written authorization from the FPPI and the data elements the agent filed. If your program is not routinely pulling back the filed data elements and the Internal Transaction Number (ITN) that confirms the EEI was accepted, you are trusting, not governing.

The data elements the USPPI must hand over

In a routed transaction, the USPPI provides the FPPI's agent the export data set out in Section 30.3(e)(1), which the Census Bureau describes as "the data elements, such as Schedule B number, value, quantity, etc." In practice this is the Schedule B or HTS number, the value and quantity, the origin-of-goods indicator, the USPPI name, address, and identification number, and, critically, the export license number, license exception, or ECCN. Every one of those elements is a classification or licensing decision. If they are not governed centrally, each becomes a per-shipment guess made under time pressure by whoever answers the forwarder's email.

Does a routed-export authorization move your export-control liability?

This is the question that turns a filing mechanic into an enforcement exposure, and it is where most programs get it wrong. The Foreign Trade Regulations and the Export Administration Regulations are two different regimes with two different answers about who is responsible.

Under the FTR, the routed authorization moves the EEI filing to the FPPI's U.S. agent. Under the EAR, that same authorization does nothing to the license determination. 15 CFR 758.3(b) states that the USPPI must "determine licensing authority (License, License Exception, or NLR), and obtain the appropriate license or other authorization," unless the USPPI "obtains from the foreign principal party in interest a writing wherein the foreign principal party in interest expressly assumes responsibility" for those obligations. And the EAR is explicit that responsibility cannot be relieved merely by using agents or delegating functions.

Quotable insight: A routed-export authorization under FTR 15 CFR 30.3 moves who files the EEI to your customer's U.S. agent. It does not move your export-control liability. Under EAR 15 CFR 758.3(b), the USPPI still owns the license determination unless the FPPI gives a separate writing expressly assuming it. Two regimes, two writings, one common failure: assuming the freight hand-off covered both.

So a routed export transaction can leave the USPPI in an exposed position: not the filer of record, but still the party responsible for whether the shipment needed a BIS license, a State Department authorization, or nothing at all. If the FPPI's forwarder under-classifies the ECCN or treats a controlled item as NLR, and there is no 758.3(b) writing on file, the licensing violation is yours. For USML items, the stakes are higher still: EEI must be filed predeparture, and the timing is governed by the ITAR at 22 CFR 123.22, so a routed hand-off that delays or drops the filing is a compliance failure on a controlled article.

When is EEI filing required, and what does a missed filing cost?

Not every export needs an EEI, and knowing the boundary is the first governance rule. Under 15 CFR 30.37(a), the low-value exemption applies when "the value of the commodities shipped from one USPPI to one ultimate consignee on a single exporting conveyance classified under an individual Schedule B number or HTSUSA commodity classification code is $2,500 or less." That exemption is per commodity classification, not per shipment, and it disappears the moment a license is involved. Under 15 CFR 30.2, EEI "shall be filed" regardless of value for shipments requiring a BIS license, shipments subject to the ITAR, and other controlled categories. Get the classification wrong and you can misjudge the filing obligation itself.

When filing is required, the deadline depends on the mode of transport. These are the predeparture timeframes for shipments that are not licensed and not on the USML, under 15 CFR 30.4:

Mode of transport	Predeparture EEI filing deadline
Vessel	24 hours prior to loading cargo on the vessel at the U.S. port
Air	2 hours prior to the scheduled departure of the aircraft
Truck	1 hour prior to arrival of the truck at the U.S. border
Rail	2 hours prior to the train arriving at the U.S. border
Mail	2 hours prior to exportation
USML or licensed shipments	Predeparture; USML timing per ITAR 22 CFR 123.22

The penalties are not theoretical. The FTR civil penalty provisions at 15 CFR 30.71 authorize up to $10,000 per violation for failing to file, up to $1,100 for each day of delinquency for a late filing (capped at $10,000 per violation), and up to $10,000 per violation for filing false or misleading information. Those base figures are adjusted annually for inflation under the Federal Civil Penalties Inflation Adjustment Act. The current maximums published at 15 CFR 6.3, under the authority of 13 U.S.C. 304 and 305, are $17,412 per violation and $1,740 for each day of delinquency. Multiply that across a quarter of ungoverned routed shipments and the arithmetic changes the conversation with the CFO.

Building the routed-export and AES/EEI filing-governance program

A governance program does not try to make the USPPI the filer on every routed shipment. That fights the regulation. It makes the data and the authorizations consistent, so it does not matter which forwarder files: the Schedule B number, the ECCN, the license call, and the recordkeeping are the same every time, and the paper trail comes back to you.

The program has five moving parts, and each maps to a place where GingerControl replaces a manual, per-shipment guess with a governed decision. GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, screen for export controls, and track policy changes, and its export tooling is contract-based, so the build is scoped to how your entities actually export.

Approach to routed-export EEI governance	Schedule B and HTS classification	ECCN and USML classification	License determination and denied-party screening	Rule-based AES/EEI data standardization	One governed USPPI/FPPI rule set across entities
GingerControl	Audit-ready research reports with the full GRI reasoning chain	Control-parameter analysis across all 10 CCL categories and all 21 USML categories	Commerce Country Chart cross-reference plus OFAC SDN, BIS Entity List, Denied Persons, and Unverified List screening	Fixed-rule validation and pull-from-ACE data prep via Automation	One source for the data elements every filer works from
Spreadsheet plus broker trust	Manual lookups, quality varies by person	Manual self-classification by category guess	Separate manual steps, rarely documented	Re-keyed per shipment per forwarder	One spreadsheet per broker relationship
Legacy GTM module	Catalog lookup, limited reasoning	Partial, varies by module	Add-on modules, separately licensed	Configurable but integration-heavy	Varies by deployment and entity

Bottom line: For an export compliance lead governing routed shipments across multiple legal entities and dozens of buyer-nominated forwarders, GingerControl standardizes the classification, ECCN, and license data every EEI depends on into one rule set, so the filing is consistent no matter who files. A spreadsheet-plus-broker-trust model is best suited to a single-entity exporter with one forwarder relationship and a stable product mix.

The five parts of the program:

Govern the classification. Every EEI needs a Schedule B or HTS number. Deriving it once, centrally, with GingerControl's classification research, kills the "same product, different code across entities" problem before it reaches a forwarder. GingerControl's HTS Classification Researcher follows the same reasoning process a licensed customs broker uses, GRI analysis, Section and Chapter Note review, and CROSS ruling research, and produces audit-ready documentation that supports the classification decision. It does not provide legal advice or replace licensed customs expertise, and its outputs are research for your team or your broker to review, not a substitute for the filer's professional judgment.
Govern the ECCN and license call. This is the exposure that survives the routed hand-off. GingerControl's Export Control Compliance screens products against all 21 USML categories and classifies ECCNs across all 10 CCL categories with deep control-parameter analysis and the "specially designed" test under EAR Part 772, then determines the license requirement against the Commerce Country Chart and screens the end user. Every evaluation comes back with an audit-ready reasoning chain, which is exactly the documentation a 758.3(b) analysis and a self-disclosure depend on.
Govern the authorizations. Standardize two writings, not one: the FTR power of attorney or written authorization that lets the FPPI's agent file, and, where you want the USPPI to retain no EAR exposure, the 758.3(b) writing in which the FPPI expressly assumes licensing responsibility. Track them by counterparty, with expiry dates.
Govern the AES data prep. GingerControl's Automation hands the repetitive, rule-based work to software: assemble the Section 30.3(e)(1) data elements, run fixed-rule validation before the data leaves your building, pull supporting records from the ACE portal, and route a clean, consistent data package to whoever is the designated filer. The company or its authorized agent remains the filer of record; the program governs the data they file from.
Govern the record. Pull back the ITN and the filed data elements on every routed shipment, and retain them for the five-year FTR window. This closes the loop that broker-trust leaves open.

Frequently asked questions

Who files the EEI in a routed export transaction, the USPPI or the FPPI? In a routed export transaction, the FPPI authorizes a U.S. agent, and that agent files the EEI; the FPPI itself cannot file because the filer must be in the United States. For an exporter running hundreds of routed shipments a quarter, the risk is losing sight of what was filed under your name. GingerControl's Automation pulls the filed data elements and ITN back from the ACE portal so your governed record matches what the agent submitted.

Does a routed export transaction change who the USPPI is? No. A routed export transaction changes who is authorized to file the EEI, but the USPPI, the U.S. party receiving the primary benefit, stays the same and retains recordkeeping and data-accuracy responsibility. For a multinational exporter with multiple selling entities, that means the liability is centralized even when filing is not. GingerControl's Export Control Compliance produces the audit-ready ECCN and license documentation that keeps that retained responsibility defensible.

What data elements must the USPPI provide to the FPPI's agent? Under FTR Section 30.3(e)(1), the USPPI provides the export data elements, including the Schedule B or HTS number, value, quantity, origin indicator, USPPI identification, and the ECCN or license information. For a team supplying data to a dozen different forwarders, format drift is where errors enter. GingerControl's HTS Classification Researcher and Export Control Compliance derive those elements once, centrally, as audit-ready research the whole program works from.

What are the penalties for failing to file the EEI? The FTR authorizes civil penalties up to $10,000 per violation for failure to file, plus up to $1,100 per day of delinquency for late filing, with current inflation-adjusted maximums of $17,412 per violation and $1,740 per day under 15 CFR 6.3. For an exporter with a quarter of ungoverned routed shipments, that compounds fast. GingerControl's Automation applies fixed-rule validation to catch missing or non-compliant data before a filing deadline is missed.

Does authorizing my customer's forwarder to file the EEI transfer my ECCN and license obligations? No, not by itself. Under EAR 15 CFR 758.3(b), the USPPI retains the license determination unless the FPPI provides a separate writing expressly assuming it; delegating the filing does not delegate the licensing responsibility. For export compliance leads, that is the most misunderstood point in routed exports. GingerControl's Export Control Compliance documents the license determination and control-parameter analysis that a 758.3(b) position, or a voluntary self-disclosure, has to rest on.

When is EEI filing required, and how does the $2,500 exemption work? EEI is generally required when a single Schedule B or HTS commodity line exceeds $2,500 in value, but it is required regardless of value whenever a license is needed or the item is subject to the ITAR, per 15 CFR 30.2 and 30.37. For teams shipping mixed consignments, misclassification can hide a filing obligation. GingerControl's HTS Classification Researcher and Export Control Compliance establish the classification and control status that determine whether an EEI is required at all.

Putting one governed USPPI/FPPI rule set behind every export filing

Routed export transactions are not the problem. The absence of a rule set behind them is. When your customer controls the freight, you cannot control who files, but you can control the classification, the ECCN, the license determination, and the record that every filing depends on, so it does not matter which forwarder submits the EEI.

Get the ECCN and license determination the EEI depends on with GingerControl's Export Control Compliance, and hand the AES/EEI data prep to Automation so every routed-export shipment files consistently under one governed USPPI/FPPI rule set. Export Control Compliance is contract-based; start with a scoped build and explore the Live AI Compliance Hub at app.gingercontrol.com.

GingerControl is not just a tool. We work with exporters and trade compliance teams on process consulting, digital transformation strategy, and end-to-end custom system development, every engagement gated by a free 30-minute Compliance Audit. Talk to our team.

For the classification foundations underneath the EEI, see our guides to Schedule B classification and AES filing and HTS code versus Schedule B code, and for the broader management system, building an export compliance program for EAR and ITAR.

References

[REF 1] U.S. Census Bureau, Foreign Trade Regulations, 15 CFR 30.1 (Definitions) Data cited: Definitions of routed export transaction, USPPI, FPPI, EEI, ITN, authorized agent, and filer. Source: 15 CFR 30.1, Foreign Trade Regulations

[REF 2] U.S. Census Bureau, Foreign Trade Regulations, 15 CFR 30.3 (Filer requirements and responsibilities of parties) Data cited: Standard versus routed filer responsibilities; power of attorney or written authorization; USPPI Section 30.3(e)(1) data elements; USPPI right to request the authorization and filed data. Source: 15 CFR 30.3, Foreign Trade Regulations

[REF 3] U.S. Census Bureau, Foreign Trade Regulations, 15 CFR 30.2 and 30.37 (Filing requirements and low-value exemption) Data cited: EEI required regardless of value for licensed and ITAR shipments; the $2,500 per Schedule B or HTS commodity low-value exemption. Source: 15 CFR 30.37, Foreign Trade Regulations

[REF 4] U.S. Census Bureau, Foreign Trade Regulations, 15 CFR 30.4 (Filing procedures and predeparture deadlines) Data cited: Predeparture EEI filing timeframes by mode of transport; USML predeparture requirement referencing ITAR 22 CFR 123.22. Source: 15 CFR 30.4, Foreign Trade Regulations

[REF 5] U.S. Bureau of Industry and Security, Export Administration Regulations, 15 CFR 758.3 (Responsibilities of parties to the transaction) Data cited: USPPI retains license determination unless the FPPI provides a writing expressly assuming responsibility; responsibility not relieved by using agents. Source: 15 CFR 758.3, Export Administration Regulations

[REF 6] U.S. Department of Commerce, 15 CFR 30.71 and 15 CFR 6.3 (Civil penalties and inflation adjustments) Data cited: FTR civil penalty structure; current inflation-adjusted maximums of $17,412 per violation and $1,740 per day of delinquency under 13 U.S.C. 304 and 305. Source: 15 CFR 6.3, Civil Monetary Penalty Adjustments for Inflation

[REF 7] U.S. Census Bureau, "Understanding Routed Export Transactions," Global Reach Blog Data cited: A routed export transaction changes who is authorized to file the EEI but not who the USPPI is; USPPI data-element and five-year recordkeeping responsibilities. Source: Understanding Routed Export Transactions, U.S. Census Bureau

[REF 8] CBP Ruling HQ H290535 and HQ H350722 Data cited: Classifying goods beyond six digits for importation constitutes customs business requiring a licensed broker; basis for the HTS Classification Researcher positioning. Source: CBP Customs Rulings Online Search System (CROSS)