Automated In-Bond Processing Documentation: A Compliance Guide

In-bond processing is a specific U.S. Customs and Border Protection mechanism. It allows imported merchandise to move through the United States, by ocean, rail, truck, or air, without formal customs entry or duty payment until it reaches its final port of arrival or is exported. This guide covers what CBP's automated in-bond process requires, the deadlines and penalties involved, and where accurate document data extraction fits into meeting them.

The document layer sits upstream of every filing. DeepRead's overview of AI document processing in logistics shows how shipping paperwork is read at volume.

What In-Bond Processing Is

In-bond cargo is merchandise that has not yet been formally entered for consumption, meaning duties have not been paid or the entry process completed, but that is transported through the U.S. under a CBP-approved bond covering it in transit. Carriers, warehouses, cartmen, and container stations handling this cargo must obtain an Activity Code 2 (C2) custodial bond under 19 CFR 113.63, and the movement, with its eventual arrival, export, or diversion, must be reported to CBP electronically.

CBP's document describes three primary movement types:

• Immediate Transportation (IT, type 61): cargo moves to another U.S. port for entry.
• Transportation and Exportation (T&E, type 62): cargo moves through the U.S. and is exported from another port.
• Immediate Exportation (IE, type 63): cargo is exported from the port where it arrived.

The official guidance is CBP's Office of Field Operations Automated In-Bond Processing Business Process Document, described as a living document that will evolve with regulations and the ACE system. The public version on CBP.gov is still Version 2.1, dated July 26, 2019, and later changes arrive through CSMS notices, so check CBP.gov for current guidance instead of relying on a static summary.

CBP's Mandate: Full Automation Through ACE

CBP's Office of Field Operations is committed to full automation of the in-bond process, and this is already enforced. The key dates from CBP's documents and notices:

• September 28, 2017: the revised in-bond rules (19 CFR Part 18) were published in the Federal Register, effective November 27, 2017.
• July 2, 2018: mandatory electronic creation of in-bond transactions took effect.
• August 6, 2018: electronic reporting of arrivals, exports, and diversions became mandatory, but enforcement was postponed, partly because of a government funding hiatus.
• July 29, 2019: enforcement began. CBP announced it in CSMS #38731726, stating that all in-bond exports, arrivals, and diversions must be reported electronically through ACE and that it no longer accepts paper copies of CBP Form 7512 for arrival and export functionality. An ACE edit rejects the arrival if the actions are not performed.

There are real exceptions. Air manifest in-bonds are exempt, trade members can still request manual posting by CBP for air shipments, and pipeline and truck shipments transiting the U.S. from Canada keep the paper process. Paper Form 7512 also still appears in audit situations such as bonded warehouse and foreign trade zone withdrawals, and some ports may ask for a copy at arrival or export. None of this changes the electronic reporting requirement. CBP also cautions trade parties not to drop the form from shipping documents until their business partners confirm they no longer need it.

CBP-approved systems for electronic in-bond filing include the ACE manifest and portal routes and QP/WP, an ABI-hosted system available to carriers and non-carriers, with "QP" handling the application function and "WP" handling arrival and export reporting.

Key Regulatory Requirements and Deadlines

• Two-business-day arrival reporting. Carriers must report the arrival of in-bond merchandise within two business days of reaching the port of destination or exportation, through a CBP-approved EDI system.
• FIRMS code on every arrival. The arrival report must include the FIRMS code of the physical location of the merchandise. Since August 10, 2024, ACE validates that the code is provided, valid, active, and within the arrival port, and does not transmit arrivals that fail, according to CBP's Trade Information Notice on FIRMS validation. This applies to all modes except air.
• 30-day standard transit time. In-bond cargo must reach its destination within 30 days, with 60 days for barge shipments. Extensions are requested from the port director, not electronically, and filing a new application does not extend the original time.
• Electronic diversion approval. Carriers must electronically request and receive CBP's permission before diverting in-bond merchandise to a different port, not divert first and report afterward. Diversion does not transfer bond liability.
• A separate process for agricultural permits. The in-bond application in ACE does not govern the Agriculture permit process. Cargo moving on a USDA permit must follow the routing the permit directs and may not be diverted, though electronic creation of the in-bond is still required.
• HTS numbers. 19 CFR 18.1 calls for the six-digit HTSUS number in the in-bond application. CBP's 2019 document said the element was not yet enforced, so confirm the current ACE edits in the CATAIR In-Bond guide.
• CTPAT is separate. The Customs-Trade Partnership Against Terrorism is a voluntary CBP security program. If your operation participates, its minimum security criteria apply alongside, not instead of, the in-bond reporting requirements.
• eBond for the underlying customs bond. CBP's eBond, launched January 3, 2015, is an electronic mechanism for sureties and surety agents to submit Single Transaction Bonds, Continuous Bonds, and Bond Riders to ACE via EDI. It is required for certain ACE transactions, though CBP's bond rules still allow Form 301 bonds to be scanned and emailed or faxed outside eBond.

Teams that file at volume will find that the document intake is the part that stops scaling first. DeepRead's guide to scaling unstructured document processing covers how to move from a pilot to production volume.

What Happens When Reporting Is Late or Wrong

Enforcement is not automatic. According to CBP's FAQ, Notices of Liquidated Damages are issued manually, and CBP typically begins by requesting an audit report and working toward reconciliation. Failing to report arrival, or the FIRMS code, within the prescribed period is an irregular delivery. The party whose bond is obligated is liable for shortages, irregular delivery, and non-delivery, with any loss at the destination presumed to have occurred in that party's possession unless conclusive evidence shows otherwise.

If there is a loss of duty, such as a shipment diverted to domestic use, the claim is typically based on the loss of duty or the value of the merchandise, and it can rise to the full value if CBP determines the violation arose from fraud. If there is no loss of duty, CBP's FAQ cites fixed penalties of roughly $1,000 to $2,000 for a first violation and $2,000 to $10,000 for multiple or repeated violations. Those figures come from the 2019 FAQ, so confirm the current amounts with CBP or your customs counsel. A fraud finding means materially higher exposure than a compliance lapse.

Because the burden often falls on proving what happened and when, audit trails and review steps that make late or wrong filings easier to trace matter. They are among the features covered in DeepRead's guide to document workflow automation.

Where Bill of Lading Data Extraction Fits

CBP's own documentation states that all in-bond entry data is derived from the Bill of Lading. The accuracy of the underlying BOL data therefore determines the accuracy of the in-bond entry, and given the tight, mandatory reporting windows, manual re-keying of BOL data into an in-bond submission is exactly where errors or delays create compliance exposure.

CBP's concordance table, which maps the old paper Form 7512 to ACE and QP/WP data elements, names the values a BOL extraction step needs to capture:

• The in-bond number and entry type (IT, T&E, or IE).
• Census Schedule D port codes, for the first U.S. port of unlading and the U.S. port of destination or exportation.
• Schedule K codes for the foreign port of lading and, for exports, the foreign destination.
• The consignee name, which must match the bill of lading, and the master or house bill number, plus container numbers.
• The quantity, in the smallest exterior packing unit, with the description, marks and numbers, and seal numbers.
• Gross weight and value, with net weight in a separate record.
• The Harmonized Tariff Schedule number, reported at a minimum of six positions where required.

Reading these fields accurately from a BOL, before they feed an ACE or QP/WP submission, is a direct and CBP-relevant use of document automation. DeepRead's guide to structured data extraction explains how schema-driven extraction turns a shipping document into fields like these.

DeepRead's role here is narrow. It is a document extraction API, not a customs filing system, ACE interface, or bonded-carrier platform, and it does not connect to ACE, eBond, or QP/WP, which remain CBP's required systems for the actual filing. Extract returns the fields you define from a BOL, each with its page, bounding box, and source text, and marks uncertain values needs_review with a reason so a person can check them before filing. It is priced at $15 per 1,000 pages for Extract and $35 for Deep Extract, with 2,000 free pages a month. DeepRead has published a vendor-run extraction benchmark, but it contains no bills of lading or customs documents, so run your own sample of BOLs before relying on any accuracy figure.

What to Confirm Before Relying on Any Automation Here

• Current CATAIR compliance. Technical guidance for processing electronic in-bonds in ACE lives in the CBP and Trade Automated Interface Requirements (CATAIR) Implementation Guide: In Bond, not the business process document alone. Confirm any system or integration against CATAIR directly.
• Which system your process uses. ACE and QP/WP are both valid but distinct, so confirm which one your carrier or broker relationship is built on before assuming integration compatibility.
• Hard deadlines. The two-business-day reporting window is not a guideline, and the arrival must carry a valid FIRMS code. Build any BOL-to-in-bond pipeline with those as firm constraints.
• Corrections. CBP's 2019 document says there is no amendment function, so a correction means deleting the in-bond and re-adding it with the same number. Confirm whether that has changed.
• Agricultural permit shipments. They follow a separate routing process, so confirm this does not apply before assuming standard ACE in-bond handling covers your cargo.
• CTPAT status, if applicable, since its security criteria run alongside the electronic reporting requirements.

Conclusion

Automated in-bond processing is a CBP-mandated electronic requirement, not an optional efficiency upgrade. Since July 2019, CBP no longer accepts paper CBP Form 7512 for arrival and export reporting (with air manifest in-bonds excepted), and the reporting rules, including the two-business-day arrival deadline, the FIRMS code, and prior approval for diversion, carry escalating penalty exposure.

CBP's own documentation confirms in-bond entry data is derived directly from the Bill of Lading, which is where accurate document extraction has a narrow role: feeding correct data into a submission process that still runs through CBP's required systems (ACE, eBond, QP/WP), not replacing them.

Frequently Asked Questions

What does "in-bond" mean in customs and freight terminology?

It refers to imported merchandise moving through the United States without formal customs entry or duty payment until it reaches its final port of arrival or is exported, covered during transit by a CBP-approved bond.

Can CBP Form 7512 still be submitted on paper?

For arrival and export reporting, no. Since enforcement began on July 29, 2019 (CSMS #38731726), CBP no longer accepts paper copies for those functions. Exceptions include air manifest in-bonds, pipeline and Canada-transit trucks, and audit situations such as bonded warehouse and foreign trade zone withdrawals, where ports may still ask for paper. Electronic reporting remains required.

What is a FIRMS code, and is it required?

A FIRMS code identifies the specific facility or location where in-bond merchandise is held. Since August 10, 2024, ACE does not transmit in-bond arrivals without a valid, active FIRMS code within the arrival port, for all modes except air.

What happens if an in-bond arrival is not reported on time?

CBP reviews the matter and issues Notices of Liquidated Damages manually. If there is a loss of duty, the claim is typically based on the loss of duty or merchandise value, rising to the full value if fraud is involved. If there is no loss of duty, CBP's FAQ cites fixed penalties of roughly $1,000 to $2,000 for a first violation and $2,000 to $10,000 for repeated ones. Confirm current amounts with CBP.

What is the difference between ACE and QP/WP for in-bond applications?

Both are CBP-approved electronic routes for in-bond filing. ACE is CBP's primary automated system, usable alongside manifest information. QP/WP is an ABI-hosted alternative available to both carriers and non-carriers, with "QP" handling applications and "WP" handling arrival and export reporting.

What is CTPAT, and how does it relate to in-bond processing?

CTPAT (Customs-Trade Partnership Against Terrorism) is a voluntary CBP security program that sets minimum supply chain security criteria. It is separate from the in-bond reporting rules, so a participant's CTPAT obligations apply alongside the electronic reporting requirements.