Integrations

Upload first. Connect your systems later.

Drag the files you already have, or one ZIP, into your account, or send them by SFTP. The agent sorts them by type and tells you what is missing.

Tell us your systems

About 3 minutes on a sample file. Your email and name open it. We never ask for your ACE login or bank details.

  • Your broker files⁠†
  • Read-only access
Demonstration file (synthetic data).⁠[1] The upload screen with one drop zone and the demonstration file's documents listed by type.Try the demo

Day one: upload

What can you send on day one?

You haveSend it as
Scanned or digital documentsPDF, TIFF, JPG or PNG
Spreadsheets and exportsXLSX, XLS or CSV
Text and word-processing filesTXT or DOCX
A folder of everythingOne ZIP file
  • ACE report exports

    From your ACE Portal account, run your entry summary reports, export them, and upload the files.

    If you filed CAPE

    If you filed CAPE, upload your CAPE reports too, such as ES-022 and REV-615.⁠[2] They let us check every entry for CAPE first.

  • Census AES export reports

    Census provides your export filings (EEI) by EIN through its ACE Export Reports.⁠[3] Run the reports and upload them.

    What you need first

    You need an ACE exporter account and a Certification of Authority, which Census vets first. If you already have an ACE import account, Census says you can see your AES trade reports.

    Census may give the exporter, or its authorized agent, the EEI it filed, for compliance and audit purposes, and proof of export for drawback is one of the official uses of EEI (15 CFR 30.60).⁠[4] We use your EEI only for your drawback claims.

  • From your broker

    Ask your broker for 7501 data, entry packets and broker statements, and upload them.

    If your broker sends records to us

    If your broker sends records to us directly instead, it needs your written consent first.⁠[5]

Why there is no ACE connection

CBP offers no public API that lets a third party pull your entry data, so there is no ACE connection for us to offer.⁠[6]

Anyone who asks for your ACE login to "connect" is asking for the kind of password CBP's fraud warning tells you to protect.⁠[7]

Catalog

Which systems can connect, and what works on day one?

Every system below works from day one, through files you export and upload. Direct connectors are built when a client or partner needs one.

Status labels

Available:
works from day one. No connector needed.
Custom engagement:
we can build it for you. How it works

Sealed runs take files through browser upload, which encrypts them before they leave your computer.

At launch, SFTP and connectors feed Standard runs only. A connector qualifies for Sealed only when it delivers files straight into a checked sealed machine.

What Sealed does not protect against

Customs data
SystemWhat we use from itDay oneDirect connection
ACE Portal (importer account)Entry summary lines, duty by HTS including Chapter 99, liquidation status, CAPE and refund reportsAvailable: upload report exportsNot offered. CBP provides no third-party connection, and we never use your login⁠[6]
Broker systems
SystemWhat we use from itDay oneDirect connection
Your broker's system (for example CargoWise or Magaya)⁠[8]7501 data, entry packets, broker statementsAvailable: your broker's CSV, XLSX or PDF exportsCustom engagement: a connector per platform, with your written consent to your broker⁠[5]
ERP and manufacturing
SystemWhat we use from itDay oneDirect connection
SAP S/4HANABills of materials, production orders, deliveries, billing documents, material movementsAvailable: export templateCustom engagement
Oracle NetSuiteExport invoices, item fulfillments, assemblies and bills of materials, inventoryAvailable: export templateCustom engagement: NetSuite REST and SuiteQL⁠[9]
Microsoft Dynamics 365 Business CentralItems, sales invoices and shipmentsAvailable: export templateCustom engagement: standard API; extra fields need a custom API⁠[10]
Microsoft Dynamics 365 Finance and OperationsItems, sales invoices, shipments, production bills of materialsAvailable: export templateCustom engagement
Sage IntacctInvoices and inventoryAvailable: CSV exportsCustom engagement: Sage Intacct REST API⁠[11]
Infor, Epicor, other Sage editions, QuickBooks EnterpriseInvoices and inventory; bills of materials in manufacturing editionsAvailable: CSV exportsCustom engagement, after we validate the system's interface
Export data
SystemWhat we use from itDay oneDirect connection
Census ACE Export Reports (AES)Your EEI by EIN: export date, Schedule B, quantity, value, destination, ITNAvailable: upload report exportsNot needed: Census delivers the reports to you⁠[3]
Forwarders and carriersBills of lading, air waybills, proof of delivery, EEI filed for youAvailable: uploadCustom engagement only. We have not verified carrier interfaces, so we promise none
3PL and warehouse systemsShipping orders, ship notices, inventoryAvailable: CSV files over SFTPCustom engagement: EDI files (856, 940, 945) over SFTP⁠[12]
E-commerce and returns
SystemWhat we use from itDay oneDirect connection
ShopifyOrders and returns: line items, quantities, statusAvailable: export filesCustom engagement: read-only, with Shopify's returns-read permission⁠[13]
Amazon (FBA)Customer returns, removals, inventory ledgerAvailable: report downloadsCustom engagement: Amazon's report API. Its inventory ledger detail covers 18 months, so older history comes from your own archives⁠[14]
Storage, email and SFTP
SystemWhat we use from itDay oneDirect connection
SFTPAny batch fileAvailable: key-based SFTP dropNot needed
Google DriveDocument archivesAvailable: uploadCustom engagement: one dedicated folder, read-only⁠[15]
Microsoft SharePoint and OneDriveDocument archivesAvailable: uploadCustom engagement: one folder, read-only
BoxDocument archivesAvailable: uploadCustom engagement: one folder you share, read-only⁠[16]
DropboxDocument archivesAvailable: uploadCustom engagement: app folder only⁠[17]
Email (Microsoft 365 or Gmail)7501s, invoices and AES confirmations in a mailboxAvailable: save attachments and uploadCustom engagement: read-only, one designated mailbox where the platform allows⁠[18]

Product names are trademarks of their owners. Listing a system means we can read its data. It does not mean its maker has reviewed, endorsed or partnered with us.

Get started

See the agent build a claim.

Run the demo on a sample file. About three minutes.

  1. 01

    Upload one quarter.

    Entry summaries, invoices and export records.

    WhoYou

  2. 02

    AI drafts your claim.

    It ties each export to its import, to the cent.

    WhoThe agent

  3. 03

    Your broker files. CBP pays you.

    The refund goes directly to your bank account.

    WhoA licensed broker

Your email and name open the demo. We never ask for your ACE login or bank details.

Book a discovery call
Ready now? Start a claim

Custom integrations

How does a custom integration work?

How long it takes

Storage folders and e-commerce returns are usually quickest. ERP connectors take longest: bills of materials and production records vary most between companies.

  1. Step 1. Request.

    You

    Tell us the system, the data you want us to read and roughly how many entries a year.

  2. Step 2. Scope and quote.

    Us

    We agree in writing what we read, with which access, and how we test, then quote a fixed price and timeline before work starts.

  3. Step 3. Grant read-only access.

    You

    You create a service account or app permission with read-only access.

  4. Step 4. Test.

    Us

    We build against a sample of your exports and compare the connector's output with your uploads for the same period. You approve the field mapping.

  5. Step 5. Go live.

    Us

    The connector feeds new records. Uploads keep working, so nothing waits on the connector.

Access

What access do we need, and what will we never ask for?

  • Read-only, and only what drawback needs: one storage folder, a read-only ERP service account, Shopify's returns-read permission or one mailbox where the platform allows.
  • You can switch it off. Revoke any access from your own system at any time. We then delete the stored credential.
  • Credentials kept apart. Connector credentials are stored encrypted in a secrets vault and never written to logs.
  • SFTP with keys, not passwords.
  • Never your ACE login or bank details. Not through an integration, and not any other way.
  • Your broker's records, with your written consent. We collect it before any broker connection.⁠[5]
  • Your export data, for your claims. We use your EEI only for your drawback claims.
The access claim, and how to check it
ClaimBacked byHow you checkLimits
Our connectors read only what drawback needsThe written scope for each connectorYour system's admin console shows the exact permissions grantedSome platforms cannot limit access to one mailbox or folder; the scope says so

Waitlist

Tell us your systems

The service opens to importers after launch. Join the waitlist, and tell us which systems hold your records.

What you want us to read
Entries a year
Processing mode
Your role

Free to join. We never ask for your ACE login or bank details.

Demo

Run the demo

Watch the agent turn a sample file into a claim folder. About 3 minutes.

We'll email you the link and add you to the waitlist. Unsubscribe anytime. We never ask for your ACE login or bank details.