ABI & CATAIR for Duty Drawback
Updated March 2026 · 12 min read
The Automated Broker Interface (ABI) is CBP's electronic system for processing trade transactions, including duty drawback claims. The CATAIR (Customs and Trade Automated Interface Requirements) defines the record formats, data elements, and transmission protocols for ABI. This guide covers how ABI and CATAIR apply specifically to drawback filing.
What is ABI?
The Automated Broker Interface (ABI) is the electronic data interchange system that connects the trade community to CBP's Automated Commercial Environment (ACE). All duty drawback claims must be filed electronically through ABI — there is no paper filing option.
ABI participants include customs brokers, importers, carriers, and software providers who have been certified to transmit data to CBP. To file drawback through ABI, you need either:
- Your own ABI connection (requires CBP certification and testing)
- A licensed customs broker who files on your behalf through their ABI connection
- Software that generates ABI-compliant files for submission through a certified connection
DutyDrawback.ai generates ABI-compliant drawback files that meet all CATAIR specifications. You can submit these files through your broker's ABI connection or your own.
What is CATAIR?
CATAIR (Customs and Trade Automated Interface Requirements) is CBP's technical specification document that defines the data formats for all ABI transactions. For drawback, the relevant CATAIR chapter specifies:
- Record types and their structure (fixed-length or delimited fields)
- Required and optional data elements for each record type
- Valid codes and values for each field
- Business rules and validation logic
- Transmission protocols and response handling
CATAIR is updated periodically by CBP as regulations change. The TFTEA modernization (effective February 2018) required significant CATAIR updates for drawback — including new provision codes, updated matching rules, and revised record formats.
ABI Drawback Record Types
Drawback claims in ABI use the DE record type for submission and the DX record type for CBP's response. The DE contains all claim data, and the DX returns the acceptance or rejection with error codes.
Drawback Entry (Submission)
The drawback entry type used to submit a drawback claim to CBP through ABI. The DE record contains all claim data including the header, import entry references, export documentation, and supporting information required for CBP to process the drawback claim.
Key fields: Claim number, provision code, filer code, drawback office, import entry references, export documentation, duties claimed
Drawback Response
The response type returned by CBP after processing a DE submission. A DX record contains either the claim acceptance confirmation or a rejection with specific error codes identifying the issues that need to be corrected before resubmission.
Key fields: Claim status (accepted/rejected), error codes, error descriptions, claim number, disposition details
ABI Drawback Filing Flow
- Generate ABI records — Create the DE (Drawback Entry) record containing all claim data: import entry references, export documentation, and supporting information.
- Validate format — Verify all records conform to CATAIR specifications: field lengths, valid codes, required elements, and business rule compliance.
- Transmit to CBP — Send the records through an ABI-certified connection. CBP returns an acknowledgment with a drawback claim number.
- Handle DX responses — CBP returns a DX response containing either the claim acceptance or a rejection with error codes that identify the specific issues (see our Drawback Error Reference).
- Track liquidation — Monitor the claim through CBP's review process until final liquidation and refund issuance.
Common ABI Challenges for Drawback
Certification & Testing
Getting ABI-certified for drawback requires passing CBP's conformance testing — submitting test claims that demonstrate your software correctly generates all required record types. This can take months and requires deep knowledge of CATAIR specifications.
CATAIR Updates
CBP periodically updates CATAIR requirements. Staying current requires monitoring CBP's CSMS (Cargo Systems Messaging Service) for announcements and updating your software accordingly. Missing an update can cause claim rejections.
Data Mapping
Translating your internal trade data into CATAIR-compliant ABI records requires precise mapping. Each field has specific formatting requirements, valid value ranges, and conditional logic that depends on the provision code and claim type.
How DutyDrawback.ai Handles ABI
- ✔Automatic ABI file generation — Upload your import/export data and the platform generates CATAIR-compliant records for all supported provision codes (51-60, 76).
- ✔Built-in validation — Every record is validated against CATAIR specifications before you download the files. Field lengths, valid codes, required elements, and business rules are all checked automatically.
- ✔Current with CATAIR updates — The platform tracks CBP's CATAIR changes so your files are always compliant with the latest specifications.
- ✔Full audit trail — Every generated record includes a complete audit trail linking back to the source import and export data, making CBP audits straightforward.
- ✔No ABI certification required — You don't need your own ABI connection. DutyDrawback.ai generates the files; your broker or ABI service provider handles transmission.
Skip the ABI Complexity
DutyDrawback.ai generates ABI-compliant CATAIR files automatically. No certification required.
See How it Works