Overview

The EDI Simple 86 Entry Load program allows a user to load a batch of Section 321 (de minimis) shipments from a tab-delimited file. FasTrax converts each record into a Simple 86 filing and presents the batch list for review, transmit, printing, and billing.

This workflow is intended for customers clearing high volumes of Section 321 shipments where the shipment detail originates in a warehouse, e-commerce, or order management system and is provided to FasTrax via an EDI file.

Important

All Section 321 rules apply (for example: shipment values under the de minimis threshold, and operational controls such as avoiding duplicate consignee patterns based on client procedures). This page documents the FasTrax screens and workflow; eligibility and compliance rules remain the responsibility of your brokerage/compliance team.

Implementation note

Use of this program may involve additional charges for implementation of the EDI file format. Contact ATS to review your file layout and implementation requirements.

Pre-Requisites

Before using the EDI Simple 86 load, confirm your master data and EDI layout are ready. This reduces rejects and rework during batch processing.

EDI File Layout Approved — Your tab-delimited file format must match the layout implemented for your site. Contact ATS if you need a new layout or modifications.
Parties Available — Client Account and Importer of Records must be added to the Customer Master database first.
Shipper/Consignee records used will be loaded from the EDI Record
Compliance Controls — Your team should validate that Section 321 eligibility rules and internal procedures (value limits, duplication controls, prohibited goods, PGA requirements, etc.) are applied before transmit.

Best practice: run a small test batch first and confirm results before moving to production volume.

ACE ET86 EDI Load (Batch)

This screen is used to create a new EDI batch and load shipment rows from a tab-delimited file. The batch list displays each created file number and key reference details so the operator can review the load before transmit or billing.

To create a new batch, enter your department code with NEW in the Batch# or (NEW) prompt (for example: 01.NEW). After loading, the system displays the shipment list for review.

Key prompts

Batch# or (NEW) — Create a new batch or retrieve an existing batch for review.
Department No. — Department code associated with the batch.
Client Account# — Customer/account used for batch routing and controls.
Imp. of Record# — Importer of record tied to the loaded shipments (as provided by file).
Trans. Mode — Mode of transport value used for Simple 86 mapping.
Entry Port — Port code used for the filings created in this batch.
AMS? — Indicates whether AMS-related processing is expected for the batch.
BL Number / SCAC Code / Trip# — Shipment identifiers used for routing and tracking (site usage may vary).
Arrival Date — Arrival date used for release timing and validations.
Truck Plates — Optional identifier when used for border/ground moves.
PC File Name — Path/filename of the tab-delimited file used to load the batch.
Format — File format indicator (TAB).
Batch List — Displays loaded file numbers and key shipment identifiers (shipper/consignee/product/value).

Tip

Review shipment values and consignee patterns before transmit. If a shipment requires correction, open the detail record and verify the item line(s) before posting/transmitting.

Command Line

The batch screen includes a command line for batch-level actions such as transmit, billing, printing, posting, and quitting. This allows the operator to process an entire batch in a controlled sequence.

Line# (Q)uit (T)ransmit (I)nvoice (PR)int (P)ost

Line# — Move to (or select) a line number in the batch list.
(T)ransmit — Transmit all entries in the batch to CBP at once.
(I)nvoice — Create Billing/AR charges for the batch (based on your billing interface setup).
(PR)int — Print the complete batch or batch summary (site options may vary).
(P)ost — Save/post the batch updates before transmit or billing.
(Q)uit — Exit the screen without saving any changes made in the current session.

Operational sequencing

Many teams follow: Load → Review → Post → Transmit → Review Responses → Invoice (timing may vary by customer and operational policy).

ACE Section 321 Entry (Detail)

This screen displays the detail for a single Simple 86 filing created from the batch. Use it to verify header values (importer, seller, consignee, transport, port, bill/trip identifiers) and the item/HTS line details created for the shipment.

In many implementations, the batch screen allows the operator to open a highlighted shipment to review or correct details before transmit. The detail screen also shows HTS lines, quantities, values, and PGA indicators when present.

Key fields shown

File # or (NEW) — The individual Simple 86 file created from the batch.
Entry Number — Entry identifier (assigned or tracked by workflow/site configuration).
EDI Batch Number — Links the filing back to the source EDI batch.
Client Account / Imp. of Record — Customer and IOR identifiers.
Trans. Mode / Entry Port — Routing and port mapping fields.
Selling Party / Consignee Party — Parties used for the Simple 86 filing.
SCAC & BL # / Trip No / Arrival Date — Shipment references used for tracking.
HTS Lines — HTS number, description, country, quantity, item value, and PGA indicators.
Totals — Item count and total value for the shipment.

Line# Xmi(T) (PR)int (A)BI (Q)uit (P)ost (N)ext P(R)evious

Line# — Move to (or select) a line number in the batch list.
Xmi(T) — Transmit this entry in the batch to CBP at once.
(PR)int — Print Simple 86 filing details.
(A)BI — View CBP/ABI responses and release status.
(Q)uit — Exit the screen without saving any changes made in the current session.
(P)ost — Save/post the entry updates
(N)ext — Move to the next entry in the batch list.
P(R)evious — Move to the previous entry in the batch list.

Tip

If totals or HTS lines do not match the source data, confirm the tab-delimited file layout and mapping rules with ATS before processing large batches.

Best Practices

Start with a test batch: Validate your file layout and mapping before scaling.
Pre-validate 321 eligibility: Confirm value limits and internal duplication controls before transmit.
Review before transmit: Spot-check several records in the detail screen for HTS, values, and parties.
Post intentionally: Use (P)ost to commit the batch before sending or invoicing.
Coordinate billing rules: If you use (I)nvoice, confirm billing interface setup matches customer expectations.

Frequently Asked Questions

What file format is required for the load?

This program loads a tab-delimited file (Format: TAB). The file layout is site-specific and must match your implemented EDI mapping. If you need a new layout or changes, contact ATS.

Can I transmit all Simple 86 entries at once?

Yes. Use (T)ransmit from the Command Line to transmit all entries in the batch as a single operational action (with each entry transmitted individually as required by CBP).

When should I use (I)nvoice?

Use (I)nvoice when you are ready to create billing/AR charges for the batch. This relies on your Billing Interface Setup rules and customer billing configuration.

Why might shipments reject after loading?

Common causes include missing/invalid party records, values outside your operational controls, or EDI layout mismatches. If rejects appear unexpectedly, confirm mapping rules and the tab file layout with ATS.