FTZ e214 error 238 creates a hard stop when an admission claims Direct Delivery but the destination FIRMS code lacks the required approval in ACE. For FTZ operators and customs brokers, resolving the rejection requires validating site authorization and related facility data—not repeatedly retransmitting the same FT10 information.
What FTZ e214 Error 238 Means
FTZ e214 error 238, “FIRMS CODE NOT APPROVED FOR DIRECT DELIVERY,” applies when the FT10 record contains a Direct Delivery indicator of “Y” but the identified FTZ site is not approved for that privilege. ACE rejects the admission because the transaction claims processing authority that is not associated with the destination FIRMS code.
The error entered ACE Production on September 17, 2026, giving the system a dedicated validation for this specific mismatch. Before that change, filers could encounter less precise admission-on-file or FIRMS-related errors. The dedicated code allows operators and brokers to distinguish a Direct Delivery authorization problem from formatting, bond, facility-type, or deactivation issues.
Why Direct Delivery Authorization Matters
Direct Delivery is generally available for qualifying low-risk, repetitive shipments when the zone operator has obtained the necessary approval. It can allow merchandise to move into an FTZ without waiting for prior approval of each individual admission, but it is a controlled privilege rather than a default filing option.
Approval is associated with the FTZ site represented by the FIRMS identifier. An operator’s broader authority to operate a zone does not automatically establish Direct Delivery approval for every site, subzone, or FIRMS code under its control. Likewise, a broker’s ability to transmit e214 data does not determine whether the site is authorized.
Error 238 is therefore not usually corrected by changing a filer profile or resending an identical transaction. The filing must accurately reflect the site’s approved status. If Direct Delivery applies, the underlying ACE facility record must show the authorization. If it does not apply, the admission generally must follow the standard process without claiming Direct Delivery.
How to Diagnose and Resolve Error 238
A disciplined review should separate the immediate Direct Delivery mismatch from related FIRMS configuration problems. The filer and operator should confirm the transaction data and site status before involving the local port or opening a technical support case.
Start With the FT10 Record
The first step is to inspect the FT10 Direct Delivery indicator and destination FIRMS identifier. The indicator must contain a valid “Y” or “N.” Error 047 may appear when that value is missing or invalid, while error 238 specifically indicates that “Y” was transmitted for a site that ACE does not recognize as approved.
The filer should verify that the FIRMS code belongs to the actual destination site. A valid code for another facility, subzone, or operator location does not satisfy the requirement. Correcting a typographical or site-selection error may resolve the rejection without any change to the site’s authorization.
Validate the FIRMS Record and Bond
If the destination FIRMS code is correct, the operator should confirm four elements:
- The FIRMS code is active.
- The facility is identified as Facility Type 02, indicating an FTZ site.
- An active Type 4 FTZ operator bond is associated with the facility.
- The site is approved for Direct Delivery in ACE.
Errors 210 through 213 can point to deactivated FIRMS status, an incorrect facility type, a missing Type 4 bond, or a terminated bond. Error 164 may arise when the site is invalid, lacks Direct Delivery authority, or does not have the required admission on file.
Escalate the Authorization Mismatch
When the site should be approved but ACE continues to return error 238, the FTZ operator should engage the local port of entry responsible for the zone. The inquiry should include the Zone ID, FIRMS code, port code, admission number, rejection details, and confirmation of the active bond. Retransmission should wait until the facility record or filing data has been corrected.
Preventing Direct Delivery Rejections
The most effective control is to validate Direct Delivery eligibility before an e214 reaches ACE. Because authorization is site-specific, relying only on customer profiles, prior shipment behavior, or operator-level assumptions creates avoidable rejection risk.
Build a FIRMS Authorization Pre-Flight Check
A filing workflow should maintain a controlled record of each FTZ site’s FIRMS code, Zone ID, supervising port, facility type, bond status, and Direct Delivery approval. When the FT10 indicator is “Y,” the system should compare the destination against that authorization record before transmission.
The pre-flight process should also block Direct Delivery claims when authorization data is missing, expired, disputed, or awaiting confirmation. A warning alone may be insufficient because production teams working under time pressure can override nonbinding alerts. A hard validation rule generally provides stronger protection against preventable ACE rejects.
Establish an Error-Code Decision Tree
Standard operating procedures should distinguish error 238 from nearby e214 errors:
- 047: Review whether the Direct Delivery indicator is missing or contains a value other than “Y” or “N.”
- 164: Confirm the FIRMS code, Direct Delivery authority, and whether an admission must already be on file.
- 210: Determine why the FIRMS code is deactivated and coordinate restoration with the responsible port.
- 211: Verify that the facility is recorded as an FTZ site under Facility Type 02.
- 212 or 213: Review whether the required Type 4 bond is absent or terminated.
- 238: Confirm that the specific FIRMS code is approved for Direct Delivery.
Control Changes Across Operations and Compliance
Authorization changes should flow promptly to brokers, self-filing teams, warehouse personnel, and trade technology administrators. FTZ operators should periodically reconcile ACE Portal facility data against internal master data, particularly after bond renewals, site activations, organizational changes, or updates involving the supervising port.
Performance reporting can further identify recurring problems. Tracking rejects by FIRMS code, filer, error number, and root cause helps compliance leaders distinguish isolated data-entry mistakes from systemic master-data or authorization failures.
- On September 14, 2026, CBP issued CSMS #69902241 announcing that new e214 FTZ admission error code 238 (“FIRMS CODE NOT APPROVED FOR DIRECT DELIVERY”) would deploy to ACE Production on September 17, 2026 (already live in Certification); Appendix P and the ACE FTZ CATAIR chapter were updated the same day to add the code and clarify Direct Delivery rules. Trade parties with FTZ Operator ACE Portal access were advised to verify Zone ID, FIRMS Code, and Port Code data.
- ACE CATAIR Appendix P (e214 FTZ Admission Error Codes, Version 2.5 dated August 2026, posted September 14, 2026) now lists error 238 with the description that the FIRMS code must be approved for Direct Delivery; this is a hard reject when the FT10 Direct Delivery Indicator is “Y” but the site FIRMS is not authorized.
- The companion ACE Foreign Trade Zone CATAIR (Version 3.1.3, August 2026, posted September 14, 2026) updated FT10 record language and added an explicit note: if the Direct Delivery Indicator is “Y”, the FIRMS Identifier (positions 53-56) must be approved for Direct Delivery. Direct Delivery itself remains the 19 CFR 146.39 procedure for qualifying low-risk, repetitive shipments that skip prior CF-214 approval.
- Industry coverage (International Trade Today, September 14, 2026) reported the same CSMS details; no subsequent public reports of deployment delays, widespread rejections, or further CBP updates were located in the following weeks. No practitioner discussions of error 238 or related Direct Delivery FIRMS issues appeared in recent X posts.
Frequently Asked Questions
Is FTZ e214 Error 238 a Fatal Rejection?
Yes. Error 238 prevents acceptance of the e214 admission because the transaction claims Direct Delivery for a FIRMS code that ACE does not recognize as approved. The filer generally must correct the indicator, destination FIRMS code, or underlying site authorization before retransmitting.
Can a Broker Change the Direct Delivery Indicator From “Y” to “N”?
Only when “N” accurately reflects the transaction and the admission will follow the applicable non-Direct Delivery process. Changing the indicator solely to bypass the rejection can create a mismatch between the electronic admission, physical cargo movement, and the operator’s procedures. The broker should coordinate the change with the FTZ operator.
Does an Active FIRMS Code Prove Direct Delivery Approval?
No. Active status is only one part of the validation. A site can have an active FIRMS code and be properly identified as an FTZ facility while still lacking Direct Delivery approval. The facility must also have the appropriate bond status and site-specific authorization.
Who Should Contact CBP When the Site Should Be Approved?
The FTZ operator will typically be best positioned to contact the local port overseeing the zone because the issue concerns the facility’s authorization record. The broker can support the inquiry with rejection messages, transmission details, and FT10 data. Clear coordination prevents duplicate or conflicting requests.
Should the Filer Keep Retransmitting While Authorization Is Reviewed?
Generally, no. Repeatedly sending unchanged data will not correct the ACE facility record and can complicate operational tracking. The parties should first validate the filing, confirm the site’s status, and obtain any necessary correction from the supervising port before submitting another Direct Delivery admission.
How Stable Software Can Help
Automate FTZ Admission Controls
Stable Software helps FTZ operators and customs brokers introduce stronger controls before e214 admissions reach ACE. Configurable validations can compare the FT10 Direct Delivery indicator against site-level FIRMS authorization data, flag inactive facilities, and identify missing bond or facility attributes before transmission.
Centralized exception workflows also give operations and compliance teams a consistent way to assign error 238 investigations, preserve supporting details, document port communications, and control retransmission. Reporting by FIRMS code and rejection type can expose recurring master-data weaknesses before they disrupt additional admissions.
Organizations seeking to reduce avoidable FTZ rejects and improve admission visibility can learn more at stablesoftware.com.
Resources
| Type | Resource |
|---|---|
| Primary PDF | ACE CATAIR Appendix P e214 FTZ Admission Error Codes (dated 09/14/2026) |
| Document page | ACE CATAIR Appendix P FTZ Error Messages |
