AES response code 802 will become a materially greater operational risk for exporters when it changes from a Verify message to a Fatal error on September 25, 2026. Exporters, U.S. Principal Parties in Interest (USPPI), and customs brokers must prepare to prevent BIS license tolerance issues from stopping Electronic Export Information filings and delaying shipments.
What the AES Response Code 802 Change Means
Verify Becomes a Hard Filing Stop
AES response code 802, “BIS LIC TOLERANCE EXCEEDED,” indicates that the license value reported in the CL1 record exceeds the tolerance associated with a Bureau of Industry and Security license. Before September 25, 2026, AES generally returns code 802 as a Verify message. That status allows the filer to review the information and, depending on the circumstances, accept the warning or correct the filing.
Effective September 25, 2026, the response becomes Fatal. AES will reject an EEI filing when the projected cumulative CL1 value exceeds 110% of the BIS license value. The filer will not receive a successful acceptance for the rejected transaction, and an Internal Transaction Number cannot be relied upon for the shipment until the underlying problem is resolved and the filing is accepted.
The practical distinction is significant. A Verify message can enter an operational workflow as an exception requiring review, while a Fatal response must function as a hard stop. Filing teams cannot acknowledge code 802 and continue processing the shipment. They must correct the license data, shipment data, or authorization position and retransmit the EEI.
Exporters should also avoid treating the 10% AES tolerance as a general authorization to exceed the terms of a BIS license. The automated threshold is a filing validation mechanism, not a substitute for reviewing the license’s conditions, quantity limits, value restrictions, validity dates, end users, destinations, and authorized items. Substantive export authorization requirements continue to apply independently of whether AES accepts the filing.
How the 110% BIS License Tolerance Is Calculated
Cumulative CL1 Value Drives the Result
The code 802 calculation is cumulative rather than shipment-specific. AES considers the value already shipped under prior EEI transactions associated with the same BIS license and adds the CL1 value from the current filing. If that projected total is greater than 110% of the BIS license value, the new EEI filing is rejected.
The basic control calculation is:
Maximum AES tolerance ceiling = BIS license value × 110%
Projected cumulative usage = prior CL1 shipment values + current CL1 value
A Fatal 802 response generally occurs when projected cumulative usage is greater than the maximum tolerance ceiling. A projected amount equal to 110% does not exceed the mathematical threshold, although filers must still confirm that the transaction complies with the license itself.
For example, assume a BIS license has an authorized value of $500,000. The AES tolerance ceiling is $550,000. If prior shipments have accumulated $520,000 in CL1 value, only $30,000 remains before reaching that ceiling. A new filing for $25,000 would bring cumulative usage to $545,000, below the AES rejection threshold. A filing for $35,000 would produce a cumulative value of $555,000 and trigger code 802 after the Fatal implementation date.
This calculation becomes more difficult when multiple business units, freight forwarders, or brokers file against the same license. Each filer may see only part of the activity, while AES evaluates cumulative usage associated with the license. Exporters therefore need a centralized license ledger that records accepted EEI values, corrections, cancellations, and remaining tolerance. Merely comparing the current shipment with the original license value will not reliably prevent rejection.
Preparing Export Operations Before September 25, 2026
Build Preventive Controls Around Remaining License Value
Preparation should begin with an inventory of active BIS licenses used in AES filings. For each license, the exporter should reconcile the original authorized value, cumulative CL1 values reported on accepted EEI transactions, pending shipments, amendments, and any corrected or canceled filings. The resulting balance should be visible before a shipment is booked or released to a filing agent.
A practical readiness program should include the following controls:
- Calculate the 110% AES ceiling for every active BIS license.
- Reconcile historical EEI activity against internal shipment and license records.
- Reserve value for pending transactions that have not yet been accepted in AES.
- Block transmission when projected cumulative CL1 value would exceed the ceiling.
- Alert users as remaining value approaches internally defined warning thresholds.
- Require review when multiple filers or locations use the same authorization.
- Update standard operating procedures so code 802 is classified as Fatal after the effective date.
Internal warning levels should generally be more conservative than the AES rejection threshold. For example, an organization might initiate compliance review when cumulative usage reaches 80% or 90% of the original license value. This creates time to evaluate future demand, request an amendment or new license where appropriate, and prevent urgent shipments from reaching the filing stage without sufficient authorization capacity.
Training is equally important. Export personnel, brokers, forwarders, and customer service teams must understand that a Fatal response means the shipment cannot proceed on the rejected EEI. Escalation instructions should identify who verifies license content, who authorizes data corrections, and who contacts BIS when the issue concerns the scope or value of the export authorization. Questions about license content can typically be directed to the BIS Office of Technology Evaluation at 202-482-4933.
Responding to a Fatal Code 802 Rejection
Diagnose the Cause Before Retransmitting
When AES returns Fatal response code 802, the filer should not retransmit the same information without investigation. Repeated transmission of an unchanged CL1 value and license number will generally produce the same rejection, add noise to the audit trail, and consume time while the shipment remains blocked.
The first step is to determine whether the rejection reflects actual cumulative license usage or a data-quality issue. The review should cover the BIS license number, CL1 value, commodity-to-license assignment, prior shipment values, filing amendments, and any license updates not yet reflected in connected systems. Common causes may include a transposed license number, an incorrect value allocation, duplicate license usage, or a shipment assigned to the wrong authorization.
Resolution options typically include:
- Correcting an inaccurate license number or license-to-line mapping.
- Correcting the reported CL1 value when it does not match the supportable EEI value.
- Reducing or restructuring the shipment only when commercially legitimate and accurately reflected in the EEI.
- Obtaining a BIS license amendment or new authorization before refiling.
- Correcting earlier EEI records when documented filing errors distorted cumulative usage.
Any reduction in reported value must be based on accurate transaction data. A filer should never lower the EEI value solely to bypass an AES validation. Compliance teams should document the diagnosis, supporting records, approval, corrective action, and final accepted transmission.
Organizations should also distinguish license-content questions from AES system problems. Authorization scope, license value, and amendment needs generally require BIS expertise. Transmission failures, unexpected response behavior, or technical processing issues typically require escalation through the appropriate ACE or AES support channel. Clear routing prevents technology teams, brokers, and licensing specialists from working the wrong issue.
Strengthening License Management Across Systems
Connect ERP, Compliance, and Filing Workflows
The transition of code 802 to Fatal highlights a broader weakness in many export programs: license balances are often tracked separately from order management and EEI filing. An ERP may know the commercial value of a pending shipment, while the compliance platform holds the license record and the broker holds prior filing results. Without integration, no participant has a reliable real-time view of cumulative usage.
A stronger operating model treats the license balance as a shared control object. Accepted EEI transactions should update cumulative CL1 usage automatically. Open orders and pending filings should reserve projected value, while corrections and cancellations should adjust the available balance through controlled workflows. Users should see both the original license value and remaining operational headroom before assigning a license to an order.
Data governance is critical when more than one broker or filing platform is involved. The exporter, as USPPI, should generally maintain the authoritative license ledger rather than expecting individual service providers to calculate enterprise-wide usage. Broker agreements and filing instructions should define how license data, acceptance messages, amendments, and rejection details are exchanged.
Organizations should also establish measurable controls, such as the percentage of licensed shipments screened before booking, the number of transactions approaching tolerance limits, and the frequency of license mapping errors. These metrics help compliance leadership identify process weaknesses before they cause rejected EEI filings.
The objective is not merely to handle code 802 more efficiently. It is to move the control upstream so a shipment that would exceed the tolerance never reaches AES. Preventive validation reduces rejected filings, missed cutoffs, carrier holds, manual rework, and the compliance risk created by rushed decisions.
Frequently Asked Questions
When Does AES Response Code 802 Become Fatal?
AES response code 802 becomes Fatal on September 25, 2026. From that date, an EEI filing that exceeds the applicable BIS license value tolerance will be rejected rather than accepted with a Verify warning. Exporters and filing agents must correct the issue and obtain an accepted filing before proceeding.
What Value Triggers a BIS License Tolerance Rejection?
The rejection generally occurs when cumulative CL1 value, including the current shipment and prior shipments reported against the same license, is greater than 110% of the BIS license value. The test is cumulative, so evaluating only the value of the current transaction is insufficient.
Can a Filer Override a Fatal Code 802 Message?
No. A Fatal response cannot be handled like a Verify warning. The filer must resolve the underlying data or authorization issue and retransmit a corrected EEI filing. Available actions may include correcting mapping errors, using accurate shipment values, or obtaining an amended or new BIS license.
Does the 10% Tolerance Authorize Exports Beyond the License Value?
Not necessarily. The AES tolerance is an automated filing threshold and should not be interpreted as independent permission to exceed a license’s terms. Exporters must continue to assess the authorized value, quantities, items, parties, destinations, conditions, and validity period applicable to the license.
Who Is Responsible for Tracking Cumulative License Usage?
The exporter or USPPI should generally maintain enterprise-wide visibility into license usage, even when a broker or authorized agent files the EEI. Individual filers may not see transactions submitted by other brokers, business units, or locations, making centralized tracking essential.
How Stable Software Can Help
Automate Controls Before EEI Transmission
Fatal AES errors are best prevented before shipment data reaches the filing stage. Stable Software helps importers, exporters, and customs brokers streamline trade workflows, centralize operational data, and automate compliance controls across connected systems.
A structured technology workflow can surface remaining BIS license value, compare projected cumulative CL1 usage with configured thresholds, and route exceptions for review before transmission. It can also help teams standardize rejection handling, preserve decision records, and improve coordination among compliance personnel, operations teams, and filing agents. By moving license validation upstream, organizations can reduce manual reconciliation, avoid preventable code 802 rejections, and protect shipment schedules as the September 25, 2026 deadline approaches.
