Cervo AI

The Automated Broker Interface is the backbone of every customs entry filed in the United States. Every 7501, every ISF, every PGA message set - all of it flows through an ABI on its way to ACE. Yet for many brokerages, ABI integration remains one of the least understood and most frustrating parts of their technology stack. This guide covers what ABI is, how the major systems work, what to consider when evaluating integrations, and how modern automation tools layer on top of ABI to make entry processing faster and more accurate.

What is an ABI?

The Automated Broker Interface, or ABI, is the electronic data interchange system that U.S. Customs and Border Protection operates for receiving and processing customs entry data. Licensed customs brokers, importers, and other authorized filers use ABI-certified software to transmit entry summaries, entry/entry summary combinations, PGA data, and other required information directly to CBP through the Automated Commercial Environment (ACE).

ABI replaced the paper-based filing process that brokers used for decades. Instead of physically delivering entry documents to the port, brokers transmit structured electronic messages that contain all the data CBP needs to assess duties, taxes, and fees, run risk assessments, and coordinate with Partner Government Agencies.

Key functions that flow through ABI include:

Entry filing. Formal entries (type 01, 11, etc.), informal entries, FTZ entries, and warehouse entries are all transmitted through ABI.
Entry summary data. Line-level detail including HTS codes, values, quantities, country of origin, and duty calculations.
PGA message sets. Electronic data required by FDA, APHIS, EPA, CPSC, TTB, and other agencies that regulate imported goods.
CBP responses. Status messages, rejection notices, liquidation data, quota status, and other feedback from CBP flow back to the broker through ABI.
Duty payments. ACH and statement processing for duty, tax, and fee payments.

If you are a customs broker in the United States, your ABI system is not optional - it is the pipeline through which your entire business operates.

Why ABI Integration Matters

For most brokerages, ABI integration is not just about being able to file entries. It is about how efficiently and accurately data moves from commercial documents to a filed entry. The quality of your ABI integration directly affects:

Speed. A well-integrated workflow means data flows from document intake to filed entry with minimal manual rekeying. A poorly integrated one means entry writers are copying data between systems, introducing delays at every step.
Accuracy. Every manual data transfer is an opportunity for error. Mistyped HTS codes, incorrect values, wrong manufacturer IDs - these errors trigger CBP rejections, holds, and potential penalties. Tight integration reduces these handoff errors.
Compliance. ABI integration is not just about getting data into the system - it is about getting the right data in the right format. have strict formatting requirements. Chapter 99 codes must be applied correctly. AD/CVD case numbers must match active orders. Integration quality determines whether these compliance requirements are met consistently.
Scalability. Brokerages that rely on manual data entry hit a ceiling. You can only hire so many entry writers. Strong ABI integration - particularly when combined with automation - lets you handle more entries without proportionally increasing headcount.

Major ABI Systems in the Market

We are partnering with three ABI platforms that dominate the U.S. customs brokerage market. Each connects to CBP's ACE system and handles electronic entry filing, but they differ significantly in architecture, user experience, data structures, and integration capabilities.

Descartes NetCHB

NetCHB is a web-based customs brokerage platform that has gained adoption among small to mid-sized brokerages. Built on modern web technologies, NetCHB offers a more contemporary user interface than some legacy systems and includes entry filing, classification tools, and compliance features.

NetCHB's key advantage is its modern architecture. As a cloud-native platform, it tends to be more flexible for integrations and can accept data through APIs more readily than older, on-premise systems. It also offers a lower barrier to entry for smaller brokerages that need ABI capability without the overhead of an enterprise platform.

For integration purposes, NetCHB provides API access that allows external systems to create entries, push line-level data, and retrieve filing status. This modern API-first approach makes it a natural fit for brokerages that want to layer automation tools on top of their filing system.

CargoWise

CargoWise, developed by WiseTech Global, is the most widely used ABI system among large and mid-sized customs brokerages. It is a comprehensive logistics platform that includes customs brokerage, freight forwarding, warehousing, and transportation management in a single integrated system.

For customs filing specifically, CargoWise handles entry creation, HTS management, duty calculation, PGA data, and CBP response processing. Its strength is breadth - it covers the full lifecycle of a shipment from booking through final delivery. Its challenge is complexity. CargoWise has a steep learning curve, and its data model can be rigid, making it difficult to customize workflows or integrate with external tools without significant configuration work.

CargoWise uses its own proprietary data formats and APIs. Integrating external data sources - whether from importer systems, document processing tools, or compliance databases - typically requires working within CargoWise's integration framework, which includes eHub for EDI-style integrations and a set of web APIs for programmatic access.

Descartes OneView

Descartes OneView is a dedicated customs management platform that many mid-market brokerages rely on for ABI filing. Originally built specifically for customs brokerage operations, OneView focuses on entry processing, classification, and compliance without the freight forwarding and logistics modules that come with broader platforms.

OneView's strengths are its customs-specific functionality and its relatively streamlined interface for entry creation. It handles formal and informal entries, PGA filing, AD/CVD processing, and quota management. Many brokers appreciate its focused approach - it does customs well without trying to be an everything platform.

On the integration side, OneView provides data import and export capabilities that allow external systems to push entry data in. The specific integration methods and data formats vary depending on the deployment, but the platform is generally receptive to structured data feeds from upstream systems.

Key Integration Considerations

Whether you are evaluating a new ABI system or looking to integrate automation tools with your existing one, several factors determine the success or failure of the integration.

Data Mapping

Every ABI system has its own data model. Field names, data types, required versus optional fields, and validation rules all differ between platforms. A successful integration requires precise mapping between the source data (commercial documents, importer records, classification databases) and the ABI system's expected format.

This is more complex than it sounds. A single customs entry can contain dozens of data fields per line item: HTS code, description, value, quantity in multiple units, country of origin, manufacturer ID, AD/CVD case numbers, Chapter 99 codes, and PGA-specific fields. Each of these must land in the correct field in the correct format, or the entry will reject.

Entry Type Support

Not all integrations need to cover every entry type, but you should understand which types your integration will handle. Formal consumption entries (type 01) are the most common, but your brokerage likely also files warehouse entries (type 21), FTZ entries (type 06), temporary imports (type 23), and others. Each entry type has different data requirements, and your integration needs to account for these differences.

PGA Filing

Partner Government Agency data is one of the most complex parts of ABI integration. Each PGA has its own set of required fields, product codes, processing codes, and conditional logic. FDA alone has hundreds of product codes, each with different data requirements. APHIS requires specific permit numbers and treatment information. CPSC has its own electronic filing requirements that continue to expand.

Your ABI integration must handle PGA data at the line-item level, correctly associating the right PGA codes and data elements with each product on the entry. A generic integration that only handles basic entry data without PGA support will leave your entry writers manually keying in the most error-prone part of the filing.

ABI Response Handling

Filing an entry is only half the conversation. CBP sends responses back through ABI - acceptance confirmations, rejection notices, requests for additional information, liquidation notices, and quota status messages. A complete integration must capture and process these responses, routing them to the right people and systems.

This is where many integrations fall short. They focus on pushing data into the ABI but do not adequately handle the return flow. Rejected entries need to be flagged immediately so they can be corrected and refiled. Liquidation data needs to flow into accounting systems. Quota messages need to trigger alerts for time-sensitive filings.

Error Reconciliation

When something goes wrong - and in customs, something always goes wrong - your integration needs to support efficient error resolution. This means clear error messages that identify which field failed validation, the ability to correct and refile without re-entering the entire entry, and audit trails that show what data was submitted and when.

The best integrations provide pre-submission validation that catches errors before the entry is transmitted to CBP. This is far better than waiting for a CBP rejection, which adds time to every correction cycle.

Challenges with ABI Integration

Even with a clear understanding of the requirements, ABI integration is not straightforward. Several challenges consistently trip up brokerages and technology providers.

Different Systems, Different Data Formats

There is no universal standard for how ABI systems accept external data. CargoWise has its integration framework. OneView has its own data import format. NetCHB has its API. If you are building a tool that needs to work across multiple ABI platforms - or if your brokerage operates on more than one system - you are dealing with multiple integration targets, each with its own quirks.

This is a particularly acute challenge for brokerages that have grown through acquisition. It is common to find a single organization running two or three different ABI systems across different offices, each with different workflows and data conventions.

Keeping Up with CBP Changes

CBP regularly updates ACE requirements, adds new PGA message set fields, modifies entry type rules, and changes tariff program requirements. Each of these changes can affect ABI integrations. A new Chapter 99 code might require a new field mapping. A PGA rule change might alter the conditional logic for when certain data elements are required.

Brokerages that manage their own integrations must monitor CBP's CSMS messages and ACE updates continuously, then adjust their data mappings and validation rules accordingly. This is an ongoing maintenance burden that never goes away.

CERT Environment Testing

CBP maintains a Certification (CERT) environment where brokers can test their ABI transmissions before going live. Any new integration or significant change to an existing integration should be validated in CERT first. However, CERT testing has its own challenges: the environment does not perfectly mirror production, test data must be carefully constructed to exercise all code paths, and CERT response times do not always reflect real-world performance.

Thorough CERT testing is essential but time-consuming. Skipping it - or rushing through it - is one of the most common causes of integration failures in production.

Security and Compliance Requirements

ABI data includes sensitive information: importer identification numbers, bond data, transaction values, and proprietary supply chain details. Any integration that touches this data must meet CBP's security requirements and, increasingly, the expectations of importers who demand SOC 2 compliance and data encryption from their service providers.

The Role of Automation Layers on Top of ABI

Here is the fundamental reality of ABI systems: they are filing platforms, not intelligence platforms. Your ABI system is excellent at transmitting structured data to CBP and processing the responses. It is not designed to read a commercial invoice, determine the correct HTS classification, check whether a product triggers AD/CVD duties, or verify that all PGA data elements are present and correct.

That is why a growing number of brokerages are adopting automation tools that sit on top of their existing ABI systems. These tools do not replace the ABI - they make it smarter by handling the upstream work that determines what data goes into the filing.

Modern automation layers typically handle several functions:

Document extraction. AI-powered tools read commercial invoices, packing lists, bills of lading, and other trade documents to extract the data fields needed for entry creation. This eliminates the manual data entry that slows down every entry.
. Automated classification engines analyze product descriptions, material compositions, and intended use to suggest or assign HTS codes. This is especially valuable for brokerages handling diverse commodities where entry writers cannot be experts in every product category.
Compliance screening. Automated checks for AD/CVD scope, Section 232 applicability, Section 301 coverage, IEEPA duties, and other trade program requirements. These checks happen before the entry is filed, catching issues that would otherwise result in CBP rejections or post-entry audits.
. Automatic identification of applicable PGAs based on HTS codes, with pre-population of known product data from a parts library. This addresses one of the most error-prone aspects of entry filing.
Duty calculation. Automated calculation of duties across stacking tariff programs - base duty rate plus Section 232, plus Section 301, plus IEEPA, plus any AD/CVD deposits. You can model these calculations using tools like the to understand the total landed cost before filing.
Data validation. Pre-submission checks that verify all required fields are present, formats are correct, and values fall within expected ranges - catching errors before they become CBP rejections.

The critical point is that these automation layers work with your ABI system, not instead of it. Your entry writers still use the ABI they know. Your filing infrastructure stays in place. The automation simply ensures that the data flowing into the ABI is more accurate, more complete, and produced faster than manual processes can achieve.

How Cervo Integrates with ABI Systems

Cervo is built to sit on top of your existing ABI system - whether that is CargoWise, OneView, or NetCHB. Cervo is not an ABI, and it is not replacing your ABI. It is an automation layer that handles the upstream work of turning commercial documents into validated, draft-ready 7501s, then pushes that data into your ABI for transmission to CBP. Brokers connect their ABI once - a one-time authentication with CargoWise, OneView, or NetCHB - and from that point forward, pushing an entry is a single click. No re-authentication, no re-configuration for each filing.

Here is how the workflow operates:

Document intake. Commercial invoices, packing lists, bills of lading, and other trade documents are uploaded to Cervo - either manually, via email forwarding, or through API integration with your TMS or importer portals.
Data extraction. Cervo's reads and extracts all relevant data fields from the commercial documents: product descriptions, quantities, values, manufacturer information, country of origin, and more.
Classification. Using extracted product data combined with the broker's , Cervo assigns or suggests HTS codes for each line item. For known products, the classification is automatic. For new products, Cervo provides ranked suggestions with supporting rationale.
Compliance checks. Cervo screens every line item against active tariff programs (Section 232, 301, IEEPA), AD/CVD orders, denied party lists, and PGA requirements. Any issues are flagged for review before filing.
Data validation. All entry data is validated against the target ABI system's requirements - correct formats, required fields populated, values within expected ranges, Chapter 99 codes properly applied.
ABI push. Once the entry writer is satisfied with the AI-extracted data, they click one button to push everything into their ABI. The draft-ready 7501 is pushed directly into the broker's ABI system - in CargoWise, this means populating the customs declaration fields through the integration framework. In OneView, data flows into the entry creation workflow. In NetCHB, entry data is created through the platform's API.
Response monitoring. After filing, Cervo tracks CBP responses that come back through the ABI, flagging rejections or requests that need attention.

The result is that your entry writers spend less time on data entry and more time on judgment calls - reviewing flagged compliance issues, handling exceptions, and managing importer relationships. The routine work of extracting data from documents, looking up HTS codes, and populating entry fields is handled by the automation layer before it ever reaches the ABI. When everything looks right, the entry writer clicks "push" and the draft-ready 7501 flows into the ABI - no manual rekeying, no switching between systems.

Because Cervo integrates with multiple ABI platforms, brokerages that operate on more than one system can standardize their upstream workflow. Documents are processed the same way regardless of which ABI system will handle the filing - the integration layer handles the translation into each platform's specific data format.

Choosing the Right Integration Approach

If you are evaluating how to improve your ABI workflow, the decision comes down to two fundamentally different approaches:

Replace your ABI system. This means migrating to a new platform, retraining your team, transferring bonds, and rebuilding all of your workflows. It is a major undertaking that typically takes 6 to 12 months and carries significant operational risk during the transition. The upside is that you get a clean start with a more modern platform. The downside is the disruption, cost, and the reality that the new ABI system still will not handle document extraction, classification, or compliance screening on its own.

Layer automation on top of your existing ABI. This approach keeps your current filing infrastructure in place and adds an automation layer that handles the upstream work. Implementation is typically measured in weeks, not months. Your team keeps using the ABI they already know, and the automation fills in the gaps that the ABI was never designed to handle. This is the approach Cervo takes, and it is the approach we see delivering the fastest ROI for brokerages of all sizes.

For most brokerages, the second approach is the pragmatic choice. Your ABI system works. Your team knows it. Your bonds, permits, and CBP certifications are all tied to it. What you need is not a new filing system - you need smarter, faster data flowing into the system you already have.

Frequently Asked Questions

What is the Automated Broker Interface (ABI)?

The Automated Broker Interface is CBP's electronic system that allows licensed customs brokers, importers, and other filers to transmit customs entry data directly to the Automated Commercial Environment (ACE). ABI handles entry filings, duty calculations, PGA data, and electronic responses from CBP - replacing what was once a paper-based process.

What are the major ABI systems used by customs brokers?

The three most widely used ABI systems in the U.S. customs brokerage market are CargoWise (by WiseTech Global), Descartes OneView, and NetCHB. Each platform connects to CBP's ACE system and handles electronic entry filing, but they differ in architecture, data formats, and integration capabilities.

Can I use automation tools without replacing my ABI system?

Yes. Modern automation platforms are designed to layer on top of your existing ABI system, not replace it. Tools like Cervo integrate with CargoWise, OneView, and NetCHB to handle document extraction, HTS classification, compliance screening, and data validation - then push the validated data into your ABI for filing. Your team keeps using the same ABI they already know.

How long does an ABI integration typically take?

The timeline depends on the type of integration. Replacing an ABI system entirely can take 6 to 12 months including data migration, CERT testing, and user training. Integrating an automation layer on top of an existing ABI is much faster - typically 2 to 4 weeks - because the core filing infrastructure stays in place and only the data pipeline changes.

Cervo's ABI Integration Guide: What Customs Brokers Need to Know