Overview

The ISF / Cargo Entry Type workflow is used to create and maintain the core header information for an ISF filing and/or ACE Cargo Release record. From the header screen you can access supporting tabs/screens for Reference Numbers, Container Information, Comments, and HTS detail.

If you are creating a new file, enter your department code .NEW at File No. (I.e 01.NEW) To edit an existing record, enter the existing file number.

Navigation notes

Use Enter to accept a value and move through fields.
Use standard FasTrax lookup keys (e.g., / (Slash), to Search where enabled.
Related screens are reached from the Modify or Command Line.

Pre-Requisites

Before creating an ISF or ACE Cargo Release record, certain master data must already exist in FasTrax. Completing these steps in advance prevents validation errors, rejected transmissions, and rework.

ISF Importer Setup
The ISF Importer must be created in the Customer database with the correct EIN or IRS Number. The importer record must also include valid bond information appropriate for ISF and/or Cargo Release filings.
Manufacturer & Party Records
Manufacturers and all associated parties (seller, buyer, consignee, ship-to, consolidator, etc.) should be created and maintained in the Parties Entry screen prior to entry.

Best practice: complete and verify all required master data before starting the entry. Clean setup significantly reduces ISF rejects and downstream ACE errors.

ACE Cargo/ISF Entry (Header)

This screen stores the core header values used by both ISF filings and ACE Cargo Release records. FasTrax intentionally uses a single, shared entry screen to initiate either workflow.

When creating a new record, the system first captures the common data elements required for ISF and Cargo Release (importer, parties, carrier, voyage, ports, and dates). If the user answers Y to the ACE Cargo (Y/N) prompt, FasTrax dynamically enables the additional fields required for an ACE Cargo Release.

This design ensures consistent data entry, reduces duplicate maintenance, and allows the same file to support ISF-only, Cargo Release-only, or combined ISF + Cargo Release workflows depending on operational requirements.

Key prompts

File No or (NEW) — Enter an existing file number to edit, or NEW to create.
Date / By — System-stamped transaction date and user ID.
Entry Number — The entry/cargo release identifier associated with this filing (if applicable).
ACE Cargo (Y/N) — Indicates whether this record is intended for ACE Cargo Release activity.
ISF Importer — Importer of record used for ISF (often drives validations and party lookups).
SF Trans. No. — Site-defined transmission or interface tracking number (if enabled).
Transp. Mode — Transportation mode used for the filing (site-defined coding / ACE mapping).
Action Code / Reason Code — Filing action intent and reason, used for changes/updates (when applicable).
Sail Date (ETD) — Expected sail date; used for timing validations and compliance tracking.
Submission Type / Ship Type — Defines the filing/submission characteristics (site configuration may vary).
Documents Recd. — Tracks receipt of required documents for compliance readiness.
Carrier Code / BL Code / SCAC & B/L No — Carrier and bill identifiers tied to the shipment.
Imp. of RecordMost times it's the same as the ISF Importer but may be different.
Manufacturer / Selling Party / Buying Party / Consignee / Ship to Party / Consolidator / Cntr Stuff Loc / Booking Party — Parties used for ISF/Cargo. If there are multiple Parties then enter MULTI and system will prompt at the line leve.
Foreign Port Qualifier / Foreign Port UnLading / City Delivery Qualifier / Foreign City of Delivery — Foreign location qualifiers and port/city references.

Tip

Standardize party creation (Importer/Consignee/Manufacturer/Seller/Buyer) in your master tables first. Clean party data reduces ISF rejects and speeds entry.

Command Line

The Entry screen includes a command line for access to related sub-screens and actions.

L# (H)TS Pa(R)t# P(O)# (C)ntrs Xmi(T) (PR)int (A)BI Cm(N)ts (Q)uit (P)ost

L# — Move to the specified line number on the current screen.
(H)TS — Opens the HTS Detail screen.
Pa(R)t# — Opens the same HTS screen with an additional option to enter SKU/Part# values from the Parts database (where enabled).
P(O)# — Opens the Reference Number(s) sub-screen.
(C)ntrs — Opens the Container Information screen.
Xmi(T) — Transmit ISF Record to CBP.
(PR)int — Print ISF Information.
(A)BI — Opens the ABI Response screen (responses/messages returned by CBP/ACE).
Cm(N)ts — Opens the Comments sub-screen.
(Q)uit — Exits without saving.
(P)ost — Saves updates and/or creates the ISF record.

Reference Number(s)

Store reference numbers tied to the filing for searching, cross-referencing, and customer reporting.

Purchase Order # — One or more PO values associated with the shipment/file.
Importer Ref # — Customer-provided reference used for tracking and client reporting.
Exporter Ref # — Exporter/supplier reference (when provided).

Use consistent formatting for references (avoid special characters when possible) so searches and exports remain reliable.

Container Information

Maintain container records linked to the filing. Container details commonly drive downstream compliance checks and reporting.

Container Number — The equipment number (format per carrier/terminal requirements).
SCAC — Carrier SCAC associated with the equipment/move (if required by workflow).
Type — Container type code (site-defined).
Size — Container size (site-defined).

Validation note

Keep SCAC and container number formats consistent with the carrier’s documents to avoid mismatches during queries.

Comments

Record an internal audit trail of notes, exceptions, and follow-ups associated with the filing.

Person — User initials or ID creating the comment.
Comments — Free-text notes; use for exception tracking and handoffs.
Entered — Date the comment was recorded.

Best practice: include what changed, why it changed, and what follow-up is required (if any).

ISF Filing Detail (HTS)

Maintain HTS lines for ISF detail. These lines typically support commodity-level detail reporting and may feed downstream validations.

File Number — The filing file number (read-only header reference).
Importer — Importer reference (read-only header reference).
Line # — Detail line sequence.
HTS Number — Harmonized Tariff Schedule classification for the line. You can do a word search or enter the first 4 or 6 digits of the HTS to search
Description — Display field from the HTS Number entered.
Cty — Origin Country code of product being imported.
Manufacturer Name — Manufacturer tied to the line.

Tip

Keep manufacturer records clean and standardized (same spelling, consistent country codes).

Best Practices

Create parties first: Ensure Importer/Consignee/Manufacturer/Seller/Buyer records exist and are standardized before building ISF.
Consistency wins: Use consistent reference formats (PO, Importer Ref, Exporter Ref) to improve inquiry and reporting reliability.
Audit trail: Use the Comments screen for handoffs and exceptions (what changed, why, and next steps).
Validate before transmit: Confirm ports, carrier/SCAC, bill numbers, and sail date accuracy to reduce rejects.

Frequently Asked Questions

Should I use NEW or an existing file number?

Use NEW to create a new ISF/Cargo record. Use an existing file number when you need to update the header, maintain PO/Reference Numbers, update Containers, add Comments, or edit HTS detail.

What happens when I answer Y to ACE Cargo (Y/N)?

FasTrax uses the same entry screen for both ISF and Cargo Release. When you answer Y, the system dynamically enables the additional fields required for an ACE Cargo Release workflow while retaining the original ISF header data. You can still continue to maintain supporting details such as PO/Refs, Containers, Comments, and HTS.

What is the difference between (P)ost and (Q)uit?

(P)ost saves your work and creates/updates the record. (Q)uit exits without saving any changes made in the current session. See Post & Quit for workflow guidance.

Do I need container records for every filing?

Not always—it depends on the shipment and your compliance process. If container data is known, entering it in Container Information improves reporting accuracy, ACE/AMS query matching, and reconciliation.

What is the best way to track exceptions or internal handoffs?

Use Comments to document what changed, why it changed, who owns the next step, and any deadlines. This creates a simple audit trail for compliance review and team handoffs.

When should I transmit the ISF to CBP?

Transmit after you’ve confirmed the key identifiers on the header and supporting details (as applicable): PO/Refs, Containers, Comments for exceptions, and HTS detail.