Periodic Monthly Statement 11th Workday Rules

Periodic Monthly Statement timing can be confusing when a daily statement is issued on the same day as the preliminary monthly statement. The key is to distinguish the month in which an entry is filed from the month in which its duties are consolidated and paid through ACE PMS.

How the Periodic Monthly Statement Cycle Works

Entry Activity and Payment Occur in Different Months

The Periodic Monthly Statement program generally allows eligible import duties and fees associated with one calendar month's entries to be consolidated for payment in the following month. This separation between entry activity and cash settlement is fundamental to understanding the PMS 11th workday.

For example, qualifying entries filed during January are generally included in the Periodic Monthly Statement paid in February. The January payment cycle, by contrast, covers qualifying entries from December. A January entry does not move into the January payment simply because its daily statement is generated before the January PMS payment date.

This structure is similar to a commercial billing cycle. Transactions accumulate during a defined period, and payment occurs after that period closes. Within ACE PMS, the preliminary monthly statement provides an opportunity to review the entries and estimated amount due before the scheduled payment and final statement processing.

The preliminary PMS is generally generated on the 11th workday of the payment month. Payment is then scheduled for the 15th workday, subject to the applicable annual PMS calendar. Weekends and federal holidays can create a substantial difference between calendar days and workdays, so compliance teams should not rely on recurring calendar dates.

A daily statement generated on the 11th workday remains part of the normal entry processing sequence. It does not retroactively join the preliminary PMS generated for the prior month's activity. Its applicable monthly cycle is determined by the underlying entry and statement timing, not merely by the coincidence of both statements appearing on the same date.

Applying the Rule to January 2026

Why a January 16 Daily Statement Belongs to February

For the January 2026 PMS cycle, the 11th workday was January 16, 2026, and the 15th workday payment date was January 23, 2026. The preliminary Periodic Monthly Statement generated on January 16 covered eligible prior-month activity. In practical terms, it consolidated qualifying December 2025 entries for payment on January 23.

An entry added to a daily statement dated January 16 would not ordinarily be added to that January monthly statement. It would instead flow into the February PMS cycle, with payment scheduled for February 23, 2026.

The timing can be illustrated as follows:

• A qualifying entry filed on December 31, 2025, could reach its daily statement during January and be included in the January PMS cycle.
• The preliminary January PMS would be available on January 16, 2026.
• The associated January PMS payment would occur on January 23, 2026.
• A qualifying entry with a January entry date and a daily statement dated January 16 would belong to the February PMS cycle.
• The February PMS payment date would be February 23, 2026.

The distinction matters because the January 16 daily statement and January 16 preliminary PMS perform different functions. The daily statement advances current entry activity through its processing timeline. The preliminary PMS provides a consolidated view of the prior month's eligible entries that are approaching payment.

Operational procedures should therefore avoid treating the 11th workday as an inclusive cutoff for the monthly statement generated that day. By the time the preliminary PMS is produced, the population for that payment cycle has generally already been established from the prior month's eligible entry activity.

Payment Controls and Late Payment Risk

Entry Date Changes Require Active Monitoring

The monthly cycle may appear predictable, but changes to entry data can create payment exceptions. If an entry date is changed, the entry may be reassigned to an earlier PMS period than personnel or the customs broker originally expected. A broker that monitors only the anticipated monthly statement could overlook the reassignment and allow the payment to become late.

Importers and brokers should reconcile the preliminary Periodic Monthly Statement against daily statement activity, entry dates, accepted dates, payment authorizations, and prior-cycle exceptions. The review should identify entries that moved between periods, were removed from PMS, or were not paid in the expected amount.

Useful ACE reporting fields typically include:

• Entry summary payment received date
• Entry date and release date
• Entry summary accepted date
• Payment authorized date
• Late payment indicator
• Summary paid indicator
• Estimated amount and paid amount
• Payment type code and description
• Periodic Monthly Statement month

These fields help distinguish an entry that is awaiting its normal PMS payment from one that has experienced a processing or authorization failure. The payment authorized date alone may not prove that funds were successfully received. Reconciliation should continue until the summary paid indicator, received date, and paid amount support the expected result.

Supplemental duty bills also require separate attention. When a supplemental bill relates to an entry originally paid through PMS, the amount generally must be paid through an accepted electronic method rather than assumed to roll automatically into a later monthly statement. Failure to use the required payment process can create delinquency exposure and may jeopardize continued PMS participation.

Clear ownership is essential. Brokers and importers should define who reviews the preliminary PMS, who authorizes payment, who confirms the debit, and who resolves rejected or reassigned entries before the deadline.

Building a Reliable ACE PMS Procedure

Use Calendar-Based Controls and Exception Reporting

A strong ACE PMS procedure should begin with the official workday calendar for each year. The compliance calendar should identify the preliminary statement date, payment date, internal review deadline, ACH authorization deadline, and escalation point for every month. Static instructions such as pay on the 15th of the month are inadequate because PMS uses workdays rather than ordinary calendar days.

The process should also separate three populations: prior-month entries approaching PMS payment, current-month entries accumulating for the next cycle, and exceptions requiring immediate investigation. This prevents a daily statement generated on the 11th workday from being mistaken for an addition to the preliminary PMS generated that same day.

A practical monthly workflow generally includes:

1. Reconcile daily statements throughout the entry month.
2. Confirm that eligible entries carry the intended PMS designation.
3. Review the preliminary PMS on the scheduled 11th workday.
4. Compare the statement to internal entry and duty accrual records.
5. Investigate changed dates, missing entries, payment discrepancies, and late-payment indicators.
6. Authorize payment with sufficient time to correct an ACH or account issue.
7. Confirm that the final statement and payment records agree.
8. Retain the statement, authorization, reconciliation, and exception resolution records.

Post-entry teams should also recognize that an entry designated for PMS is not necessarily considered fully paid when it is filed or placed on a daily statement. System recognition of final payment may occur later in the PMS cycle. This can affect the timing of a Post Summary Correction because a PMS entry generally must be recognized as truly paid before the correction can be accepted.

The best control is not a single cutoff rule. It is a documented reconciliation process that follows each entry from acceptance through statement assignment, payment authorization, and confirmed settlement.

Frequently Asked Questions

Is a Daily Statement Issued on the 11th Workday Included in That Day's Preliminary PMS?

Generally, no. A daily statement generated on the 11th workday reflects current entry processing, while the preliminary PMS generated that day consolidates eligible activity from the prior entry month. The daily statement entry normally belongs to the following PMS payment cycle.

Which PMS Includes an Entry on the January 16, 2026 Daily Statement?

A qualifying January entry appearing on the January 16, 2026 daily statement would generally be included in the February Periodic Monthly Statement. The scheduled February 2026 payment date was February 23. The January 23 payment covered qualifying prior-month entries.

Does the 11th Workday Mean the 11th Calendar Day?

No. PMS dates are based on workdays. Weekends and federal holidays are excluded when determining the applicable date, so the 11th workday may fall well after the 11th calendar day. Annual dates should be loaded into the organization's compliance calendar.

Can an Entry Date Change Affect the PMS Payment Month?

Yes. A corrected or changed entry date can shift an entry into a different statement period. Brokers and importers should monitor entry dates, PMS month fields, late-payment indicators, and payment status rather than relying solely on the initially expected payment month.

Is Payment Authorization the Same as Confirmed Payment?

Not necessarily. Authorization initiates the payment process, but compliance teams should confirm that the amount was received and applied. Payment received dates, paid amounts, summary paid indicators, ACH results, and final statement records should be included in the reconciliation.

When Can a PMS Entry Be Corrected Through a Post Summary Correction?

A PMS entry generally must be recognized as truly paid before a Post Summary Correction can be accepted. Because PMS delays settlement until the following month, post-entry teams may need to wait for payment processing and system recognition before submitting the correction.

How Stable Software Can Help

Supporting Broker-Led Post-Entry Services

Accurate PMS records can also support later duty recovery analysis by establishing when entries were paid and confirming the amounts collected. Stable Software provides DrawbackAI, flat-license duty drawback software that U.S. customs brokers can white-label for importer clients and use to file claims under their own filer codes.

Stable Software charges a flat software license and never takes a percentage of the importer's refund. This structure allows brokers to retain control of the client relationship, filing process, and economics of the drawback service. Customs brokers evaluating technology for expanding post-entry services can learn more about Stable Software's approach on the customs broker solutions page.

Resources