In-Bond — Troubleshooting ACE Errors
Identify, fix, and prevent common ACE rejects for in-bonds
← Back to In-Bond Manual ← Back to Main Manual

Overview

ACE rejects include a code and message describing what went wrong. This guide highlights high-frequency in-bond errors and quick fixes. Use it alongside the official ACE error dictionaries for precise definitions and the latest updates.

  • Scope: In-bond creation, amendment, arrival, and export/close transmissions.
  • Where to see errors: ABI/In-bond transmission queue, response panel, or status dashboard.

How to Read ACE Errors

Code & Message

Example: 028 - FIRMS CODE NOT ON FILE — Check the FIRMS code and port pairing; correct, then retransmit.

Some modules use F### or alphanumeric codes; always match the code to the message text returned.

Context

Confirm which action failed (Create / Amend / Arrive / Export), which field it refers to (e.g., FIRMS, port, SCAC, quantity), and which record (in-bond no., bill).

Next Steps

  • Fix the specific field cited.
  • Save the correction and retransmit.
  • If unclear, consult the References and/or your Client Rep.

Troubleshooting Workflow

  1. Open the failed transaction in the module you used (Create / Delete / Arrive / Export).
  2. Read the error code + text; identify the field involved.
  3. Validate supporting data (port codes, FIRMS, SCAC/IATA, quantities/UOM, voyage/flight, bill numbers).
  4. Correct only the cited field(s), add a brief remark, and retransmit.
  5. If the error persists, check for routing conflicts (wrong port for the selected type) or status conflicts (already arrived/exported).
  6. Escalate port-specific cases to the port’s In-bond desk or your Client Rep.

Common In-Bond Errors & Fixes

FIRMS / Facility

  • 028 — FIRMS CODE NOT ON FILE: Verify the FIRMS code and port pairing; confirm active status with the facility. Fix the code and retransmit.
  • 051 — FIRMS NOT BONDED FACILITY TYPE: Use a bonded facility appropriate to the movement type.
  • 127 — FIRMS CODE REQUIRED FOR PORT: Provide the receiving facility’s FIRMS for that port.
  • 210 — FIRMS CODE IS DEACTIVATED: Use an active FIRMS or confirm reactivation.
  • 211 — FIRMS CODE IS NOT AN FTZ: For FTZ transactions, ensure the FIRMS corresponds to an FTZ site.
  • 212 / 213 — Missing/Inactive Bond on FIRMS: Facility must have required bond(s) on file; coordinate with the operator.

These examples are documented in to ACE CATAIR Error Codes. (See References)

Bill / Status

  • 180 — BILL IN HELD STATUS: The bill is held; resolve the hold before export/close or use correct bill.
  • 201 — DUPLICATE MESSAGES DETECTED: Remove duplicates and retransmit only once for the same flight/voyage event.
  • Bill not on file / mismatch: Ensure MBL/HAWB numbers match manifest, including dashes/format.

Ports / Routing

  • Invalid port code: Use a valid CBP port for the movement type (IT: destination; IE/T&E: export).
  • Port/type conflict: Verify the in-bond type (61/62/63) aligns with the selected ports.

Carrier / Conveyance

  • Invalid SCAC/IATA: Confirm the correct carrier identifier for the mode.
  • Missing voyage/flight: Provide conveyance details when required by mode/port.

Quantities / Units

  • UOM mismatch: Unit of quantity must match the manifest (e.g., CTN, PCS).
  • Qty/weight out of tolerance: Correct quantity or weight to match documentation.

Status Conflicts

  • Already Arrived/Exported: Some changes are not allowed post-arrival/export; consider cancel & re-issue per port policy.
  • Duplicate in-bond: Ensure you are not recreating an existing number; check search and recent transmissions.

FTZ-Related Errors

  • Confirm FTZ FIRMS and zone identifiers align with the movement (some errors require FTZ-designated FIRMS).
  • Verify Type 4 bond and active bond status when required.
  • Ensure export routing (port/mode) is valid for IE/T&E out of an FTZ.

Prevention & Best Practices

  • Use SEARCH to locate bills and avoid typos in MBL/HAWB.
  • Keep reference tables (ports, FIRMS, carriers) current; validate against recent filings.
  • Use Standard Key Words [] for consistent remarks describing fixes.
  • When amending, change only the cited fields and retain an audit remark.

References