Back to resources

What Is FTZ Software? ICRS, E-214 Admissions, and Weekly Entry Explained

FTZ software is the inventory control and recordkeeping system (ICRS) a foreign-trade zone operator uses to meet CBP's requirements in 19 CFR Part 146. It records every admission, zone status, movement, and withdrawal, and prepares the filings that go with them: E-214 admissions, weekly entries, and the annual reconciliation. AI-native FTZ software goes further and prepares that work from your source data automatically, so operators review instead of rekey.

Get a recovery estimate

Why zones need dedicated software

A foreign-trade zone lets merchandise enter the United States without paying duty until it leaves the zone for U.S. consumption. Goods that are re-exported never pay U.S. duty. Manufacturers with production authority can pay duty at the finished-product rate when it is lower than the rate on the components.

Those benefits depend on records. CBP treats the zone operator as responsible for knowing, at any moment, what merchandise is in the zone, what status it holds, and where it went. That is why 19 CFR Part 146 requires an inventory control and recordkeeping system, and why most operators run specialized software rather than spreadsheets.

The program is large. According to the 86th Annual Report of the Foreign-Trade Zones Board, 199 zones were active in 2024, nearly $964 billion of merchandise was received into zones, and nearly 543,000 people worked in zone operations.

What FTZ software must do

RequirementWhat the software handlesReference
Inventory control and recordkeepingReceipts, movements, adjustments, removals, and an audit trail19 CFR 146.21–146.26
AdmissionPreparing the E-214 (CBP Form 214) to admit merchandise19 CFR 146.32
Zone statusPrivileged foreign, nonprivileged foreign, domestic, and zone-restricted19 CFR 146.41–146.44
Entry for consumptionWeekly estimates (3461) and Type 06 entry summaries (7501)19 CFR 146.63
Annual reconciliationThe operator's report within 90 days after the zone year ends19 CFR 146.25

Inventory control and recordkeeping

The ICRS is the core. It must account for every unit from admission to removal and tie each movement to its supporting documents. When CBP or an auditor asks where a quantity came from, the answer should come from the system, not from a reconstruction.

Admissions

Merchandise is admitted with an E-214. The software assembles it from the commercial invoice, bill of lading, and receiving record, then tracks the admission's lines as inventory layers.

Zone status

Status determines how duty is calculated when goods leave. Privileged foreign status locks the classification and rate at admission. Nonprivileged foreign status lets merchandise be classified and dutied in its condition at withdrawal, which is the basis of inverted-tariff savings. The software must keep status with each layer through every movement.

Weekly entry and removals

Operators approved for weekly entry file one estimate for the coming week and one Type 06 entry summary for what actually left, instead of one entry per shipment. The software has to know what was withdrawn, group it correctly, and flag when actual removals exceed the estimate. See our weekly entry guide for detail.

Annual reconciliation

Within 90 days after the end of the zone year, the operator prepares a reconciliation report and certifies it to the port director. Software that keeps a clean ledger all year turns this from a project into a report.

ICRS versus ERP

An ERP knows what the business owns. An ICRS knows what CBP needs to know: zone status, admission numbers, the link between each unit and its E-214, and the entry that removed it. Most operators run both. The FTZ system reads ERP and warehouse data and adds the customs layer on top. The quality of that connection decides how much rekeying the team does.

What AI-native FTZ software changes

Traditional FTZ software is a system of record. The operator downloads yesterday's data, matches receipts to shipments, keys admissions, and fixes exceptions, and the software stores the result.

AI-native FTZ software is built so that the system does the first pass. In Pax FTZ:

  • Source data from ERP, WMS, broker feeds, and documents is ingested and checked on arrival.
  • Inventory is reconciled against the source records, and differences are traced to the receipt, shipment, or adjustment behind them.
  • Conflicts between sources, such as a receipt quantity the invoice does not support, are flagged with the evidence and a proposed fix.
  • E-214 admissions and weekly entries are drafted with each field linked to its source record.
  • Consequential decisions, such as a status election or a filing, wait for an authorized person.

The operator's role shifts from assembling records to reviewing and deciding.

Ready to find out what you've been missing? Book a call with the Pax team.

Talk to an expert

Questions to ask when choosing FTZ software

  • Which filings does it prepare, and which does it transmit to CBP directly?
  • How does it get data from our ERP and WMS, and who maintains that mapping?
  • Can every quantity be traced back to a source record?
  • How does it handle zone status, inventory layers, and FIFO?
  • How is migration from our current system validated before go-live?

For a fuller checklist, see how to evaluate FTZ software.

Ready to find out what you've been missing? Book a call with the Pax team.

Talk to an expert

More resources like this one