FTZ e214 error 238 is a fatal ACE rejection indicating that the destination site’s FIRMS code is not approved for Direct Delivery. For FTZ operators and customs brokers, resolving it requires more than retransmitting the admission: the filing must be reconciled with the site’s authorization, facility status, and bond configuration.
What FTZ e214 Error 238 Means
Direct Delivery Depends on Site-Level Authorization
Error 238 returns the message “FIRMS CODE NOT APPROVED FOR DIRECT DELIVERY.” It generally occurs when an e214 admission includes a Direct Delivery indicator of Y in the FT10 record, but ACE does not recognize the destination FIRMS code as approved for that privilege.
Direct Delivery allows qualifying merchandise to move into a foreign-trade zone under an accelerated admission process, subject to applicable authorization and control requirements. It is a privilege granted for an eligible FTZ site rather than a default filing option available to every zone operator. A site may have a valid FIRMS code and operate as an FTZ while still lacking Direct Delivery approval.
Error 238 is therefore not merely a formatting warning. It is typically a hard rejection tied to the relationship between the declared filing treatment and the authorization associated with the destination facility. Repeating the same transmission without changing the filing or correcting the site record will generally produce the same result.
The correct response depends on the underlying transaction:
- If the shipment legitimately qualifies for Direct Delivery and the site should be authorized, the operator must confirm that the approval is accurately reflected in ACE.
- If the filer selected Direct Delivery by mistake, the FT10 must be corrected so the admission follows the appropriate non-Direct Delivery process.
- If the authorization status is uncertain, the filing should be held until the FTZ operator and supervising port resolve the discrepancy.
Changing the indicator solely to bypass the rejection is not appropriate when the merchandise has already moved or is being handled under Direct Delivery procedures. Filing data, operational events, and site privileges must remain aligned.
How to Diagnose Error 238 Before Retransmission
Validate the FIRMS Record in a Logical Sequence
Effective e214 rejection management starts with the site master data rather than the shipment line details. Error 238 specifically identifies missing Direct Delivery approval, but neighboring FIRMS and admission errors can reveal additional conditions that must be addressed before a successful retransmission.
A broker or FTZ operator should use the following triage sequence:
- Confirm the destination FIRMS code. Verify that the code transmitted on the admission belongs to the intended FTZ site. A valid code for another facility does not satisfy the destination requirement.
- Check whether the FIRMS code is active. Error 210 indicates that the FIRMS code has a deactivated status. The site operator will generally need to work with CBP cargo personnel to restore or clarify the record.
- Confirm Facility Type 02. Error 211 means the FIRMS code is not identified as an FTZ site. Direct Delivery approval cannot compensate for an incorrect underlying facility classification.
- Review the Type 4 FTZ bond. Errors 212 and 213 generally indicate that no Type 4 bond is listed for the FIRMS code or that the listed bond has been terminated. The operator should verify the bond number, activity type, effective status, and facility association.
- Confirm Direct Delivery approval. After the foundational FIRMS data is validated, determine whether ACE reflects Direct Delivery authorization for that specific site.
The filer should also inspect related transmission conditions. Error 047 means the Direct Delivery indicator is missing or invalid rather than unsupported by the site authorization. Error 164 can arise when a non-Direct Delivery admission is not on file, the FIRMS code is invalid, or the zone lacks the relevant authorization.
This sequence prevents teams from treating error 238 as an isolated software issue. If the site should be approved and all supporting data appears correct, the FTZ operator should contact the local port of entry overseeing the zone. Retries should pause until the authorization record is confirmed or corrected.
Preventing Direct Delivery Rejections Through Better Controls
Build Authorization Checks Into the Admission Workflow
The most reliable way to prevent FTZ e214 error 238 is to validate facility eligibility before the FT10 record is created. Many admission failures occur because filer workflows treat the Direct Delivery indicator as shipment-level data without checking the site-level privilege that supports it.
A strong pre-transmission control should evaluate at least four elements: the destination FIRMS code, active facility status, Facility Type 02 classification, and an active Type 4 FTZ bond. If the FT10 Direct Delivery indicator is Y, the workflow should also confirm that Direct Delivery approval is associated with the same FIRMS code.
Maintain Governed FTZ Site Master Data
FTZ operators and brokers should maintain a controlled facility profile for each zone site they serve. That profile should generally include:
- FIRMS code and legal facility identity
- Supervising port of entry
- Facility type and current operating status
- Direct Delivery approval status
- Type 4 bond number and effective status
- Approval effective dates or known limitations
- Escalation contacts for the operator, broker, and port
The data should be reviewed whenever a site opens, changes operators, updates a bond, modifies admission procedures, or experiences a CBP status issue. Periodic verification is also prudent because an authorization that was valid during onboarding may not remain accurately reflected after operational or administrative changes.
Filing systems can strengthen these controls by preventing users from setting the Direct Delivery indicator to Y for an unapproved facility. Exception logic should distinguish between an invalid indicator, an inactive FIRMS code, a non-FTZ facility type, a bond problem, and missing Direct Delivery approval. This precision helps compliance teams route each rejection to the correct owner instead of relying on repeated submissions or broad technical support tickets.
Standard operating procedures should also map error codes 047, 164, and 210 through 213 alongside error 238. Treating these validations as a connected control framework reduces admission delays and creates a clearer audit trail.
Frequently Asked Questions
Is FTZ e214 Error 238 a Fatal Rejection?
Yes. Error 238 generally prevents acceptance of the e214 because the filing claims Direct Delivery for a FIRMS code that ACE does not recognize as approved. The admission must be corrected, or the site authorization issue must be resolved, before a successful retransmission can occur.
Can a Filer Change the Direct Delivery Indicator From Y to N?
The indicator may be corrected when Y was entered in error and the transaction is properly handled through a non-Direct Delivery admission process. It should not be changed merely to bypass the rejection if the merchandise moved under Direct Delivery procedures. The electronic filing must accurately represent the operational facts.
Does an Active FIRMS Code Prove Direct Delivery Approval?
No. Active FIRMS status confirms only one part of facility eligibility. The code must generally identify a Facility Type 02 FTZ site, have the appropriate active Type 4 bond association, and carry separate Direct Delivery approval when that privilege is claimed.
Who Should Be Contacted When the Site Should Be Approved?
The FTZ operator should generally contact the local port of entry responsible for supervising the zone. The broker should provide the rejected admission details, destination FIRMS code, error message, transmission date, and confirmation of the site’s facility and bond status to support efficient investigation.
Should the Broker Keep Retransmitting While Authorization Is Reviewed?
No. Repeated transmissions normally add noise without correcting the underlying authorization mismatch. The filer should stop retries, preserve the rejection details, validate the FT10 and facility data, and retransmit only after the filing or ACE authorization record has been corrected.
How Stable Software Can Help
Automate FTZ Admission Validation and Exception Handling
Stable Software helps customs brokers and FTZ operators replace manual admission checks with structured, repeatable controls. Configurable workflows can validate FIRMS codes, Direct Delivery eligibility, facility type, bond data, and FT10 indicators before an e214 reaches ACE.
When a rejection occurs, centralized exception management can classify the error, preserve transmission history, assign the issue to the appropriate team, and prevent unproductive retries. This gives compliance leaders clearer oversight while helping operations teams resolve admissions faster and maintain a defensible audit trail. Learn more about modernizing FTZ filing and customs workflows at Stable Software.
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 |
