ACE Cargo Release & ISF
ISF / Cargo Release entry, transmit, ABI checks, queries & reporting
← Back to Customs Introduction Brokerage Menu

Overview

The ACE Cargo Release & ISF menu is the operational hub for creating and transmitting ISF filings and Cargo Release activity, verifying ABI/ACE transmission results, and running common reports and queries.

This menu is organized into two columns: Entry & Transmit and ACE/ABI & Reports. Some items open their own detailed pages (guided pages), while other items will be documented here within this page.

Guided Pages
Options documented as separate pages for step-by-step entry and maintenance workflows.
Includes: entry creation screens, party entry, and maintenance setup.
Placeholders on this page
Options documented as sections below (screens will be added as you send them).
Includes: transmit batch, transmission checks, queries, and reports.

Guided Pages

The following options are maintained as separate pages. This keeps the menu page clean and allows each workflow to expand with field-by-field definitions, validation rules, and examples.

ISF / Cargo / Entry Type
Create and maintain ISF and Cargo Release filings and related entry-type workflows.
EDI for Simple 86 Entry Type
Prepare and manage EDI steps associated with the Simple 86 workflow.
Parties Entry
Maintain shipment/entry parties used by ISF and Cargo Release (importers, consignees, notify, etc.).
Maintenance Menu
Setup tables and reference data used throughout ISF and Cargo Release workflows.

Simple 86 Entry

The Simple 86 Entry screen is used to create and maintain Section 321 (de minimis) cargo release filings through ACE. This workflow is intended for qualifying low-value shipments and provides a simplified data set while still enforcing required compliance controls.

FasTrax uses a dedicated Simple 86 entry screen to capture the minimum data elements required by CBP for Section 321 release. Party, shipment, and commodity details are validated based on Simple 86 rules rather than full ISF or Cargo Release requirements.

This entry type is commonly used for high-volume e-commerce shipments and expedited releases where shipment value and eligibility meet Section 321 guidelines.

Key prompts

  • File No or (NEW) — Enter an existing Simple 86 file number to edit, or NEW to create a new Simple 86 record.
  • Date / By — System-assigned transaction date and user ID.
  • Entry Type — Identifies the filing as a Simple 86 (Section 321) entry.
  • Importer / Buyer — Party responsible for the shipment; must exist in the customer/party database.
  • Seller / Shipper — Foreign seller or shipper of the goods.
  • Carrier / SCAC — Carrier transporting the shipment.
  • Bill / Tracking No. — Bill of lading, airway bill, or parcel tracking reference.
  • Arrival Date — Estimated or actual arrival date used for release timing.
  • Country of Origin — Country where the merchandise was manufactured.
  • Value — Total shipment value used to validate Section 321 eligibility.
  • Description — Plain-language description of the merchandise.
Tip
Ensure importer and seller records are fully defined before creating Simple 86 entries. Clean party data reduces rejects and improves automated release rates.

Command Line

The Simple 86 Entry screen includes a command line for navigating related sub-screens and performing transmission and maintenance actions.

L# Xmi(T) (PR)int (A)BI (Q)uit (P)ost
  • L# — Move to the specified line number on the current screen.
  • Xmi(T) — Transmit the Simple 86 filing to CBP.
  • (PR)int — Print Simple 86 filing details.
  • (Q)uit — Exit without saving.
  • (P)ost — Save updates and/or create the Simple 86 record.

ISF Batch Transmission

The ISF Batch Transmission screen allows users to select one or more ISF records and submit them to CBP as a controlled transmission group. This provides a centralized way to manage queued ISF filings before transmission.

The screen is divided into two panes. The left pane displays files currently available on the Transmission Queue, while the right pane shows files that have been selected for transmission during the current session.

Key prompts

  • Enter Department — Limits the queue to ISF records associated with the specified department.
  • Enter File No. — Allows selection of a specific ISF file number to add to the transmission set.
  • Files on Transmission Queue — Displays ISF records eligible for transmission.
  • Files Selected for Transmission — Displays ISF records chosen for the current transmit batch.
Operational note
Files remain in the transmission queue until successfully transmitted or removed by operational action. Use this screen to control timing, grouping, and review prior to submission to CBP.

Check ABI Transmissions

Placeholder — This section will cover how to review ABI/ACE transmission queues, statuses, and retry/exception workflows.

Screen placeholder — Check ABI Transmissions

ACE Individual File Response

Placeholder — This section will document retrieving and reviewing individual file responses, including message interpretation and next steps for corrections.

Screen placeholder — ACE Individual File Response

5106 Importer

Placeholder — This section will cover creating/reviewing importer information used for ACE filings and related compliance references.

Screen placeholder — 5106 Importer

ACE Cargo / AMS Query

Placeholder — This section will document how to query ACE/AMS for cargo status and reconcile results back to your shipments/entries.

Screen placeholder — ACE Cargo / AMS Query

Shipment’s Report

Placeholder — This section will document report parameters, output fields, and recommended filters for operational review.

Screen placeholder — Shipment’s Report

Parties Report

Placeholder — This section will document generating party reports for auditing, compliance, and customer review.

Screen placeholder — Parties Report

Parties Relationship Report

Placeholder — This section will document relationship reporting (links between parties and shipments/entries) and typical uses.

Screen placeholder — Parties Relationship Report

Section 321 Report

Placeholder — This section will document the Section 321 reporting options, common compliance checks, and export/print practices.

Screen placeholder — Section 321 Report

Best Practices

  • Standardize references: Use consistent shipment/entry reference patterns to simplify queries and reporting.
  • Transmit discipline: Run batch transmits at defined times and review file responses before end-of-day closeout.
  • Exception handling: Maintain a short checklist for resolving common ACE rejects (missing data, invalid codes, timing).
  • Limit setup access: Restrict maintenance changes to supervisors and document approvals/changes.

FAQ

Why don’t I see all options?
Menu options can be controlled by permissions and enabled modules. If an option is missing, confirm your role and security access.

Where should I start for a new ISF or Cargo Release workflow?
Start in the guided pages (ISF/Cargo/Entry Type or Simple 86 Entry Type) and follow the step-by-step screens.

How do I confirm a transmit succeeded?
Review transmission status and responses in the sections below for ABI checks and file responses once those screens are documented.

Quick Resources