When an ACE report contains payment types 2, 6, 7, and 8, the variation is usually intentional rather than an error. Understanding ACE ACH payment types allows customs brokers and importers to identify who controls each statement, whether payment follows a daily or monthly cycle, and which party funds the duty withdrawal.
What ACE ACH Payment Type Codes Mean
Statement Ownership and Payment Timing
ACE payment type codes identify how entry summaries are grouped into statements and whether the statement belongs to a broker or importer. They also distinguish daily statement processing from Periodic Monthly Statement, commonly called PMS. The code is therefore more than an ACH designation. It reflects the statement structure, payment timing, and party responsible for authorizing the withdrawal.
| Payment Type | Statement Owner | Timing | General Use |
|---|---|---|---|
| 2 | Broker | Daily | Broker batches entries, potentially for multiple importers, and funds the statement |
| 3 | Importer | Daily | One importer funds its own daily statement through its ACH account |
| 6 | Broker | Periodic monthly | Broker batches PMS entries, potentially for multiple importers, and funds the monthly statement |
| 7 | Importer | Periodic monthly | Importer funds a PMS statement associated with an importer number and subdivision suffix |
| 8 | Importer | Periodic monthly | Importer funds a PMS statement without a subdivision suffix |
Types 2 and 6 are broker statement arrangements. A broker statement can generally include entries for multiple importers. Because the broker makes the customs duty payment, the broker typically recovers that outlay through its billing process.
Types 3, 7, and 8 are importer statement arrangements. Each statement is associated with a specific importer account structure, and the importer generally pays through its own ACH account. The broker therefore does not ordinarily advance those duties or include them as a reimbursable outlay.
The key difference between types 7 and 8 concerns importer account identification. Type 7 supports an importer statement with a subdivision suffix, while type 8 applies without that suffix. Both are PMS types and can support a consolidated monthly payment process.
Choosing Between Daily and Monthly Statements
Aligning the Statement Type With Treasury Policy
Organizations that prefer a monthly customs duty withdrawal will generally use a PMS arrangement represented by payment type 6, 7, or 8. The appropriate type depends on whether the broker or importer owns and funds the statement, as well as how the importer account is configured in ACE.
Payment type 6 may be suitable when the broker manages the statement and advances duties for its clients. This arrangement can simplify payment administration for importers, but it increases the broker's cash outlay, credit exposure, reconciliation burden, and need for prompt client reimbursement. Brokers should establish clear credit policies and monitor unrecovered duty advances separately from brokerage service charges.
Payment types 7 and 8 are generally preferable when an importer wants customs duties withdrawn directly from its own bank account. Direct importer payment reduces broker outlay and gives the importer's treasury team greater control over cash movement. The importer must maintain accurate ACH authorization information and ensure that sufficient funds and internal approvals are available when the monthly statement is paid.
PMS Does Not Change the Underlying Entry Obligations
Periodic Monthly Statement consolidates eligible entries into a monthly payment cycle. It does not eliminate entry-level compliance responsibilities, change declared duty liability, or replace the need to review individual entry summaries. Importers and brokers must still verify classification, valuation, origin, special tariff treatment, and other data affecting duty.
Monthly payment also requires appropriate PMS designation and account setup. A treasury preference for one monthly withdrawal does not automatically convert daily statements into PMS statements. The filer, importer, and payment account must be configured consistently before eligible entries can follow the intended monthly cycle.
A practical policy should define which importers use broker-funded statements, which use importer ACH, and whether subdivision suffixes are required. That policy should then be reflected in filing instructions, client onboarding records, ACH authorizations, and post-entry review procedures.
Reading and Validating ACE Statement Reports
Why Multiple Payment Types Appear in One Report
An ACE report can legitimately display several payment types when it covers a mixed portfolio of entries. A broker may have some clients on daily broker statements, others on broker-funded PMS, and still others paying through their own ACH accounts. The appearance of types 2, 6, 7, and 8 together does not by itself indicate inconsistent processing.
Reviewers should analyze payment types alongside the importer number, subdivision suffix, statement number, statement date, filer code, payment status, and entry summary number. This makes it possible to determine whether each entry followed the intended client payment arrangement. Payment type should not be reviewed as an isolated field.
Controls for Statement Generation Problems
ACE statement generation problems can occasionally produce duplicate, outdated, or otherwise invalid statements. For example, a system issue on October 28 and 29, 2026 generated erroneous statements for some entry summaries, including duplicates and statements carrying July dates. ACH authorization attempts against invalid statement numbers were rejected.
When statement information appears unusual, filers should use the REV-104 Daily Statement Entry Summary List report to identify valid statement numbers before authorizing payment. A strong validation process should include the following steps:
- Confirm that the statement number appears on the current REV-104 report.
- Match the payment type to the expected broker or importer payment arrangement.
- Compare the statement date and entry population against filing records.
- Investigate duplicates, unexpected historical dates, or unexplained changes in statement ownership.
- Confirm that the ACH account belongs to the party responsible for funding that statement type.
- Retain evidence of review and payment authorization for audit support.
ACE Portal users should also recognize that ACH Refund Authorization is located under the Financial Transactions header within the Importer sub-account. Current ACH data is retrieved automatically in that area. Although refund authorization is distinct from statement payment, accurate financial account administration supports both processes and reduces avoidable payment delays.
- CBP issued CSMS #70329550 on October 30, 2026, addressing an ACE statement generation issue on October 28 and 29, 2026. Some filers received erroneous statements (including ones dated July 29 or 30) or duplicates for certain entry summaries submitted October 23, 27, or 28. Invalid statements should be ignored, as ACH authorization attempts will be rejected. Filers must use the REV-104 Daily Statement Entry Summary List report to confirm valid statement numbers before processing payments that display mixed types such as 2, 6, 7, and 8.
- Effective October 29, 2026, CBP updated the ACE Portal Importer sub-account by placing the ACH Refund Authorization function under a new Financial Transactions header tab. The portal now automatically retrieves current ACH data, removing the prior manual Get Info/Refresh button. This change supports ongoing statement and refund processing tied to ACH.
- No regulatory or policy updates specifically altering ACH payment type codes 2, 6, 7, or 8 occurred in the past 30 days. CBP's ACE CATAIR Daily Statement documentation continues to define type 2 as daily broker batching by entry number, type 6 as periodic broker, type 7 as periodic importer with subdivision suffix, and type 8 as periodic importer without suffix (types 6-8 require PMS designation). Treasury preference for monthly withdrawals remains supported via types 6, 7, and 8.
Frequently Asked Questions
Is Payment Type 8 a Daily Importer Statement?
No. Payment type 8 generally represents a periodic importer statement without a subdivision suffix. It is associated with PMS rather than daily statement processing. Payment type 3 is the daily importer statement type, while type 7 is the periodic importer type used with a subdivision suffix.
Which Payment Types Support Monthly Duty Withdrawals?
Payment types 6, 7, and 8 are generally associated with Periodic Monthly Statement. Type 6 is broker-funded, while types 7 and 8 are importer-funded. The correct selection depends on ACH ownership, importer account structure, PMS eligibility, and the commercial agreement between the importer and broker.
Why Would Types 2 and 6 Appear for the Same Importer?
An importer may have entries processed under different statement cycles because of eligibility, filing instructions, account configuration, timing, or operational exceptions. Type 2 indicates a daily broker statement, while type 6 indicates a periodic broker statement. Repeated unexpected differences should be investigated rather than assumed to be normal.
Does an Importer-Funded Statement Mean the Broker Never Bills Duties?
Generally, yes. When the importer pays CBP directly through its own ACH account, the broker has no duty outlay to recover. The broker may still invoice brokerage, freight, disbursement, or other agreed charges, but customs duties should not ordinarily appear as a broker-funded reimbursement.
Can a Payment Type Be Changed After Filing?
The available correction path typically depends on the entry's status, statement generation, payment authorization, and ACE processing stage. Filers should identify incorrect payment instructions as early as possible and coordinate changes with the importer and treasury personnel. Once payment processing has advanced, cancellation or correction options may be more limited.
How Stable Software Can Help
Support a More Profitable Broker Technology Strategy
Accurate statement controls protect cash flow, but customs brokers can also create value by helping importers recover eligible duties after export or destruction. Stable Software provides DrawbackAI for customs brokers, a flat-license duty drawback platform that brokers can white-label for importer clients and use to file claims under their own filer code.
Stable Software charges a flat software license and never takes a percentage of the refund. This structure allows brokers to retain control of their client relationships and service economics without surrendering part of an importer's recovery to the software provider. Brokers evaluating how duty drawback can complement entry filing, payment management, and post-entry services can explore the platform as part of a broader customs technology strategy.
Resources
| Type | Resource |
|---|---|
| Source | Primary source |



