What is ABI Software? Automated Broker Interface Explained (2025)
ABI (Automated Broker Interface) software is CBP-certified technology that connects directly to U.S. Customs and Border Protection's Automated Commercial Environment (ACE)—the system CBP uses to process trade data—so importers can file customs entries and Importer Security Filings (ISF) electronically. Any importer of record can use ABI software to self-file their own entries, or route filings through a licensed customs broker instead. Which path makes sense depends on your entry volume, in-house expertise, and how much control you want over the filing process, which is exactly what this guide walks through.
What Is ABI Software, Exactly?
From Paper Manifests to Electronic Filing
Before ABI existed, customs entries moved on paper—stacks of forms hand-carried or mailed to CBP ports, processed by clerks, and prone to the kind of delays that stall cargo on the dock. CBP built the Automated Broker Interface in the 1980s to let brokers and importers transmit entry data electronically instead, and the program has expanded steadily ever since. Today, ABI is the standard method for filing commercial entries, and CBP has all but retired paper-based alternatives for routine cargo.
ABI software isn't a single CBP-owned application. It's a category: any software product that has been certified by CBP to communicate with its systems using the required data formats and transmission protocols. Strix's platform is one example. There are others on the market, ranging from broker-only tools to importer-facing self-filing platforms, and they vary widely in usability, automation, and the level of support behind them.
CBP puts every ABI software product through a certification process before it can transmit live data—vendors have to demonstrate their system correctly formats and validates entry data across a range of test scenarios before CBP turns on production access. That certification is why "ABI-certified" is a meaningful claim rather than marketing language: it means CBP has actually tested the software's connection to ACE, not just that the vendor built a form that looks like an entry. Filers submit through ABI across all U.S. ports, and CBP processes millions of shipments through the system every year, from small parcel entries to complex multi-line commercial shipments.
How ABI Connects to CBP's ACE System
ACE (Automated Commercial Environment) is CBP's primary trade processing system—the "single window" through which every customs entry, ISF filing, and most trade documents must pass. ABI software is the interface layer that sits between your business systems and ACE. When you submit an entry through ABI software, it packages your shipment data into the electronic format ACE requires, transmits it, and relays CBP's response back to you in something close to real time.
That response loop matters. ACE validates entries against CBP's rules as they arrive, flagging missing data, HTS (Harmonized Tariff Schedule) classification issues, or bond problems within minutes rather than days. Well-built ABI software surfaces those validation messages in plain language, so you can fix an issue before it becomes a hold at the port. Poorly built software just forwards CBP's raw error codes and leaves you to decode them—one of the biggest practical differences between platforms that otherwise all claim "ACE integration."
What Data Actually Moves Through ABI Software
Every entry transmitted through ABI carries a defined set of data elements CBP requires before it will release cargo: importer of record number, HTS classification for each line item, country of origin, entered value, bond information, and any flags for partner government agency (PGA) review—products regulated by the FDA, USDA, EPA, or similar agencies. Get any one of these wrong, and ACE either rejects the entry outright or holds it for manual review, both of which slow your cargo down.
This is where ABI software earns its keep. A basic ABI connection just transmits whatever data you type into it, leaving you to catch errors the hard way—through a CBP rejection notice. Stronger platforms validate each data element against CBP's current rules before transmission: confirming your HTS code is active and correctly formatted, checking that your bond covers the entered value, and flagging PGA requirements tied to your product's classification before you submit rather than after CBP does. That difference alone can be the gap between a same-day release and a multi-day hold at the port.
Who Can Self-File Using ABI Software?
Self-Filing Is Legal for Any Importer of Record
A common misconception is that only licensed customs brokers can file entries. That's not true. Any importer of record has the legal right to file its own customs entries directly with CBP—the requirement is that the filing be done by an employee of the importing company, not an outside contractor who isn't a licensed broker. This is why self-filing has become a realistic option for companies with steady import volume and someone on staff willing to own the process, not just the largest multinationals.
ISF filings work a bit differently: CBP allows a single ABI account and filer code to submit ISF data across multiple EINs, which is useful for companies managing imports for related entities. Customs entry filing is stricter—entry filing is considered "customs business," and that work has to be performed by an employee of the actual importer of record, or by a licensed broker acting on the importer's behalf.
Filer Codes: Your Entry Point to ACE
Every party authorized to file through ABI—whether an importer self-filing or a customs brokerage—needs a filer code: a short alphanumeric identifier CBP assigns that ties every transmission back to a specific filer. Strix files under filer code 8ND, for example, which is how CBP and the trade community track our submissions across the millions of shipments processed through ACE each year.
Getting a filer code means applying to CBP and pairing it with ABI software that's certified to transmit on your behalf. This is usually the point where importers realize self-filing isn't just "buying software"—it's taking on the compliance responsibility, recordkeeping, and CBP relationship that a broker would otherwise carry for you. That's not a reason to avoid it, but it is the honest trade-off self-filers accept in exchange for lower per-entry costs.
What Self-Filing Requires From Your Team
Before committing to self-filing, it's worth being honest about what it takes internally. You'll need someone who can commit real time each week to reviewing commercial invoices, verifying HTS classifications, and confirming country-of-origin documentation—this isn't a task you hand to whoever has a spare hour. You'll also need a customs bond in place, since CBP requires one regardless of who files the entry, and a process for keeping entry records for the legally required retention period.
None of this is unusual or especially hard for companies that already have organized import documentation, but it is a real commitment, not just a software subscription. Companies that import inconsistently, or that lack anyone with customs experience, often find it faster to start with full-service brokerage and revisit self-filing once volume justifies building that internal capability. There's no penalty for changing your mind later—Strix clients move between self-filing and brokerage as their needs shift, sometimes entry by entry.
Self-Filing vs. Full-Service Brokerage: The Economics
What Self-Filing Actually Costs
With Strix, self-filing runs $30 per entry. That price covers ABI-certified software with ACE integration, built-in validation, and access to licensed broker support when a filing gets complicated—not just a bare-bones transmission tool. For companies that import consistently and have someone comfortable owning classification, valuation, and documentation review, self-filing can meaningfully lower per-entry cost without asking you to build compliance expertise from scratch.
The trade-off is time and accountability. Someone on your team needs to gather commercial invoices, verify HTS codes, confirm country of origin, and review each entry before it goes to CBP. Good ABI software reduces that workload through automation and validation, but it doesn't eliminate the underlying responsibility—you're still the importer of record, and CBP holds you accountable for accuracy regardless of who clicks "submit."
What Full-Service Brokerage Costs
Full-service brokerage with Strix runs $100–$250 per entry, depending on complexity, entry type, and the level of hands-on support required. A licensed customs broker manages the entire filing on your behalf: classification review, entry preparation, submission, and follow-up if CBP has questions. For companies without the internal bandwidth to own compliance, or those dealing with complex products, multiple partner government agency (PGA) requirements, or unfamiliar trade lanes, that added cost buys expertise you'd otherwise have to build in-house.
Running the Numbers on Your Volume
The math tends to favor self-filing as volume grows, and brokerage as complexity grows—those two variables don't always point the same direction. A company filing 50 entries a month at $30 self-filing spends $1,500 monthly versus $5,000–$12,500 at brokerage rates; over a year, that gap can run into six figures. But a company filing five complex entries a month involving anti-dumping duties, Section 301 tariffs, or multiple PGAs may find that a licensed broker's expertise prevents costly classification errors that would far outweigh the per-entry savings of filing alone.
Consider a Bozeman-based outdoor gear importer bringing in roughly 40 entries a month on well-established product lines from two long-term suppliers. At full-service brokerage rates, that's $4,000–$10,000 a month; self-filing at $30 per entry drops that to $1,200 a month, a savings of roughly $34,000–$106,000 a year. That importer already has clean product data, a compliance-minded operations manager, and consistent country-of-origin documentation—exactly the conditions where self-filing tends to work well. A newer importer bringing in the same volume but sourcing from five new suppliers across three countries, with product lines still being classified for the first time, faces a different calculation: the risk of a misclassified HTS code or a missed PGA requirement can cost far more than the brokerage fee it was meant to avoid.
Many importers land somewhere in between: self-filing routine, well-understood shipments while routing anything unusual—new products, new suppliers, new countries of origin—to a broker for review. Strix's dual-service model exists specifically for that reality; you're not locked into one path for every entry.
What to Look for in ABI Software
ACE Certification and CBP Compliance
Start with the basics: is the software actually ABI-certified, and does it maintain direct ACE integration rather than relying on a third-party intermediary? Ask how the vendor handles CBP's periodic ACE updates and rule changes—software that lags behind CBP's requirements creates compliance risk you don't want to inherit. You should also confirm the provider holds its own filer code and can show a track record of filings across U.S. ports, not just a demo environment.
Automation and Validation
The best ABI platforms catch problems before CBP does. Look for software that validates HTS codes, checks bond sufficiency, flags missing PGA data, and confirms entry math before transmission—not software that simply forwards whatever you type and waits for CBP to reject it. Automation around recurring shipments, saved supplier and product profiles, and duty calculation can turn a 30-minute entry into a five-minute one once your data is set up correctly.
Support When You Need It
Even confident self-filers eventually hit an entry that doesn't fit the standard pattern—an unfamiliar HTS classification, a PGA hold, or a CBP query that needs a fast, accurate response. Software alone can't resolve those situations; you need access to licensed customs brokers who can step in. Strix pairs self-filing software with support from licensed, ABI-certified brokers, available Monday–Friday, 6:00 AM–6:00 PM Mountain Time, so self-filers aren't left guessing on the entries that actually get complicated.
Recordkeeping and Audit Trail
CBP can request records supporting any entry for years after filing, so your ABI software should keep a complete, retrievable history of every submission—not just a snapshot of the current status. Look for platforms that store the underlying commercial invoices, classification decisions, and CBP correspondence alongside each entry, rather than requiring you to reconstruct that history from email threads if an audit request arrives.
Common ABI Filing Mistakes to Avoid
Self-filing through ABI software removes the broker as a middleman, but it doesn't remove the risk of the mistakes brokers are trained to catch. A few show up more often than others.
Missing or Late PGA Data
Products regulated by agencies like the FDA or USDA need specific data flags before ACE will release them, and that data has to be accurate at the moment of filing—not added after the fact. Importers new to a product category often don't realize a PGA flag applies until CBP holds the shipment, which turns a routine entry into a multi-day delay. Good ABI software checks for known PGA triggers based on your HTS classification before you submit.
Treating ISF and Entry Data as Separate Problems
ISF (Importer Security Filing) data and customs entry data describe the same shipment, and CBP checks them against each other. A manufacturer name, bill of lading number, or HTS code that doesn't match between your ISF and your entry raises questions CBP will want answered, sometimes with a penalty attached. Filing both through the same platform, ideally with shared data, reduces the chance of a mismatch. For a full breakdown of ISF-specific pitfalls, see our guide to ISF filing best practices.
Underestimating Bond Coverage
Your customs bond has to cover the value and duty of the entries you're filing, and it's easy to outgrow a bond without noticing—particularly if your import volume or product values increase mid-year. An insufficient bond can stall an entry at exactly the wrong moment. Review your bond coverage against your actual import volume at least annually, and sooner if you add a high-value product line.
Ignoring Software Validation Warnings
Every validation warning your ABI software surfaces exists because CBP has rejected similar entries before. Importers under deadline pressure sometimes override or ignore these warnings to get a filing out the door, only to have CBP reject it anyway—now with less time to fix it. Treat validation warnings as CBP's rules speaking in advance, not as noise to work around.
How Strix's ABI Software Works
Strix has been filing customs entries since 2006, and our platform reflects two decades of watching where self-filers actually get stuck. The software is ABI-certified with direct ACE integration, covers all U.S. ports, and handles the core filing types importers need most: ISF filing, customs entries, and Post Summary Corrections (PSC), which amend an entry after it's been filed. Every filing runs under our own filer code, 8ND, giving CBP a consistent record of our submissions across the millions of shipments processed on the platform.
What differentiates Strix from a bare-bones ABI tool is the model underneath it. Self-filers on our software still have access to licensed customs brokers for entries that need a second set of eyes—a benefit-of-the-doubt review before submission, or hands-on help if CBP flags something after the fact. That's the logic behind pricing self-filing at $30 per entry: you get certified, validated software plus a safety net, not just a transmission pipe. For companies that decide they'd rather hand off filing entirely, our full-service brokerage team takes over at $100–$250 per entry, using the same ACE-integrated infrastructure.
Because both paths run on the same platform, moving between them isn't a system migration—it's a conversation about which entries need which level of support this month. That flexibility matters more than most importers expect once volume or product mix starts to shift.
Frequently Asked Questions
Is ABI software the same as ACE?
No. ACE is CBP's trade processing system—the destination. ABI software is the certified technology that connects to ACE and transmits your filing data to it. You can't file directly into ACE without ABI-certified software or a broker who has it.
Can I self-file customs entries without a broker?
Yes. Any importer of record can self-file customs entries, as long as the filing is done by an employee of the importing company rather than an outside, unlicensed party. You'll need ABI-certified software and your own CBP-assigned filer code.
Do I need a filer code if I use a broker?
No. When a licensed broker files on your behalf, the entry is submitted under the broker's filer code, not yours. You only need your own filer code if you're self-filing.
Is self-filing cheaper than using a broker?
Usually, on a per-entry basis—Strix's self-filing runs $30 per entry versus $100–$250 for full-service brokerage. Whether it's cheaper overall depends on your volume and how much internal time compliance work takes, since self-filing shifts responsibility (and staff hours) onto your team.
What happens if I make a mistake on a self-filed entry?
You can typically correct it with a Post Summary Correction (PSC) before the entry liquidates. Mistakes are also exactly the situation where having licensed broker support behind your self-filing software—rather than software alone—makes a practical difference.
How long does it take to set up ABI self-filing?
Most importers can be filing within a few weeks of signing up, though the exact timeline depends on how quickly you can supply bond information, EIN documentation, and product data. Strix handles the CBP-facing setup steps; your team's main job is getting historical product and supplier data organized.
Does ABI software handle ISF filings too?
Yes—most ABI platforms, including Strix's, handle both ISF and customs entry filing, since both are submitted through ACE. Filing them on the same platform helps keep manufacturer, shipper, and HTS data consistent between the two, which reduces the mismatches that trigger CBP scrutiny.
Conclusion
ABI software is the electronic bridge between your business and CBP's ACE system, and understanding how it works is the first real step toward deciding whether self-filing fits your operation. The legal right to self-file has existed for any importer of record for years; what's changed is that certified software has made it practical for more companies to exercise that right without sacrificing accuracy or support. Whether self-filing at $30 per entry or working with a licensed broker at $100–$250, the right choice comes down to your volume, your team's bandwidth, and how much of the compliance workload you want to own directly.
For a deeper look at one of the filing types ABI software handles, see our ISF filing guide and our post on ISF filing best practices. If HTS classification is the piece slowing you down, our HTS classification guide walks through the 10-digit system in detail. And for definitions of the terms in this guide—ABI, ACE, filer code, and more—our customs glossary is a quick reference.
Choose the Filing Model That Fits Your Business
See how Strix's ABI-certified software compares to full-service brokerage, and get pricing for your actual entry volume.
Explore self-filing software or talk to our brokerage team about full-service filing. You can also review current pricing for both models before you decide.