Overview
Cargo Release (SE) transmits the shipment’s release request and minimal data to CBP. Entry Summary (AE) sends detailed fiscal/statistical data to liquidate duty and fees. Together, they represent the backbone of customs clearance in ACE.
- Release-first vs. summary-first: Your port and entry type determine whether SE precedes AE or both are sent in close sequence.
- Status notifications: Both processes return structured acceptance/reject messages and status updates (SO for SE, UC for AE).
Technical specifications for both filings are defined in CBP’s ACE CATAIR chapters and related implementation guides.
Core Workflows
1) Cargo Release
- Create Release with conveyance/bill, parties, and preliminary line details.
- Transmit SE; monitor SO Status Notifications.
- Resolve rejects using code text; re‑transmit as needed.
2) Entry Summary
- Build the AE with lines, duties/fees, and PGA flags as required.
- Transmit AE; monitor UC Status and pay via statements when applicable.
- Address UC requests (documents, corrections) promptly.
3) Queries & Reconciliation
- Use summary queries to verify filing and payment state.
- Track exceptions via ABI Responses and resolve quickly.
Key Datasets & Message Types
Cargo Release (SE)
- SE: Cargo Release transaction
- SO: Cargo Release Status Notification
- PGA Message Set (as required)
Entry Summary (AE)
- AE/AX: Entry Summary Create/Update
- UC: Entry Summary Status Notification
- JC: Entry Summary Query
Error References
- ACE Error Dictionary (general)
- PGA Error Dictionary (for Partner Government Agencies)
See links below for the official CBP specifications.
CATAIR Quick Links (CBP.gov)
Cargo Release
Entry Summary
Error Dictionaries & General
Operational Tips
- If SE is rejected, correct only the cited field(s) and retransmit before proceeding to AE.
- For UC requests, respond quickly to avoid holds; track via your ABI Responses screen.
- Keep reference codes (ports, FIRMS, SCAC, UQ) current to minimize rejects.