Confirming whether a customs broker submitted a post summary correction requires more than running a standard ACE report. The ACE Entry Summary Version Number is available within the reporting universe, but importers generally must customize an ES-001, ES-002, or ES-003 report to display it alongside other useful PSC data.
Which ACE Report Shows the Entry Summary Version Number?
The Entry Summary Reports universe makes the version number available to all three major ACE import reports: ES-001, ES-002, and ES-003. However, the field is generally not displayed in the standard report layout. A user must modify an existing report or create a custom report that includes the relevant data object.
Choosing Between ES-001, ES-002, and ES-003
The best report depends on the level of analysis required. ES-001 can support a broader entry summary review, while ES-002 and ES-003 provide more detailed data suitable for investigating changes at the entry or line level. Many compliance teams modify ES-003 because it can combine entry summary information with additional correction-related fields in a practical monitoring report.
The field to add is typically labeled Entry Summary Version Number. Within the ACE report editor, users can search for terms such as “version,” “PSC,” or “Post Summary Correction” to locate related data objects. If a broker files a post summary correction, the entry summary version will generally progress from version 1 to version 2. Subsequent changes may produce additional versions, depending on how the transaction is processed.
A CBP-originated adjustment may appear differently, such as a decimal version like 1.01. For that reason, the version number should not be treated as the only evidence of a broker-filed PSC. It is most useful when evaluated with the PSC indicator, filer information, submission date, update timestamp, and entry summary status.
How to Customize an ACE PSC Report
An effective ACE PSC report begins with one of the standard entry summary reports and adds correction-specific data objects. Users generally need appropriate ACE reporting access and permission to edit or save custom reports. The available fields may vary based on the report universe, account permissions, and periodic changes to ACE.
Add the Entry Summary Version and PSC Fields
The first step is to open ES-001, ES-002, or ES-003 in the ACE reporting environment and select the option to modify the report. Rather than changing a shared operational report, compliance teams should typically save a separate custom copy with a clear name, such as “PSC Monitoring Report” or “Entry Summary Revision Review.”
At minimum, the customized report should include:
- Entry number
- Entry summary status
- Entry summary version number
- Entry summary update date
- Entry summary update time
- Post Summary Correction indicator
- PSC submission date
- PSC filer name
- PSC reason or reason code
- Protest status and protest number
- Bill amount and refund amount
The PSC Indicator helps identify whether a post summary correction has been associated with the entry. The PSC Submission Date provides stronger operational confirmation of when the correction entered the system. If the date is blank, the available ACE data may not reflect a submitted PSC, even when internal correspondence suggests that correction work is underway.
Detailed reports can also expose PSC information at the line level. Line-level reason codes are particularly useful when reviewing classification, valuation, origin, duty, or other changes affecting only part of an entry. Filters should be configured carefully so they do not unintentionally exclude corrected versions, inactive records, or entries outside a narrow date range.
How to Verify That a Broker Submitted a PSC
No single ACE field should generally serve as the entire control for confirming post-entry activity. A well-designed review compares multiple data points and distinguishes between a correction prepared by the broker, a correction transmitted to CBP, and a correction reflected in ACE reporting.
Read the Version Number in Context
An original entry summary commonly appears as version 1. When a broker submits a correction, the Entry Summary Version Number will typically change to version 2. If further corrections occur, later version numbers may appear. Decimal versions may indicate updates initiated or processed differently, including certain CBP actions, so they require additional investigation.
Compliance teams should confirm PSC activity by reviewing the version number with the following fields:
- PSC Indicator: Shows whether ACE identifies the entry as having PSC activity.
- PSC Submission Date: Indicates when the correction was submitted or recorded.
- PSC Filer Name: Helps establish which party filed the correction.
- Entry Summary Update Date and Time: Shows when the record most recently changed.
- PSC Reason: Explains the reported basis for the correction when available.
- Entry Summary Status: Provides context on the entry’s current processing state.
These fields should then be reconciled against broker instructions, internal approval records, revised duty calculations, and expected financial outcomes. Bill and refund amounts can help identify whether the correction generated an additional duty obligation or anticipated refund.
A repeatable control should also flag entries for which a PSC was requested internally but no submission date appears within the expected service period. Exception-based monitoring is more reliable than manually reviewing every entry and allows trade compliance teams to focus on missing submissions, unexpected correction reasons, or version changes that were not authorized.
Frequently Asked Questions
Is There a Standard ACE Report That Automatically Displays the Version Number?
The Entry Summary Version Number is generally available as a data object rather than a default column in a standard report. Users typically need to modify ES-001, ES-002, or ES-003 and add the field. Saving the revised layout as a custom report makes it easier to repeat the review without rebuilding the report each time.
What Does Version 2 Mean in an ACE Entry Summary Report?
Version 2 commonly indicates that the original entry summary has been revised, often through a post summary correction. It should not be interpreted in isolation, however. The PSC indicator, submission date, filer name, update timestamp, and correction reason should be reviewed to determine who made the change and why.
Can an ACE Report Show Who Filed the Post Summary Correction?
A customized report can generally include the PSC Filer Name or a comparable filer-related field when it is available in the selected reporting universe. This information helps determine whether the importer’s broker or another authorized party submitted the correction. It should be reconciled with broker confirmations and internal authorization records.
Why Is the PSC Submission Date Blank?
A blank PSC date may mean that no post summary correction has been submitted or recorded for the entry. It may also result from report filters, field selection, timing, access permissions, or the way the correction was processed. Users should refresh the report, confirm the entry number and date range, and review related version and status fields before escalating the discrepancy.
Should ES-001, ES-002, or ES-003 Be Used for PSC Monitoring?
All three can generally display the Entry Summary Version Number after customization. The appropriate choice depends on the required detail. ES-003 is often useful for operational monitoring, while detail-oriented reports may be preferable when compliance teams need line-level PSC flags and reason codes. Organizations should select one consistent report design for recurring controls.
Does a Version Change Always Confirm a Broker-Filed PSC?
Not necessarily. Certain CBP changes or other record updates may produce a different version pattern, including decimal values. A version change confirms that the entry summary record changed, but it does not always establish the source or purpose of the change. Supporting PSC fields and transaction records provide the necessary context.
How Stable Software Can Help
Strengthen Post-Entry Oversight
ACE reporting provides essential government data, but compliance teams still need a dependable process for matching corrections to broker requests, approvals, deadlines, and financial results. Stable Software helps importers and customs brokers streamline trade operations, centralize critical entry information, and reduce the manual effort involved in identifying exceptions.
By connecting post-entry workflows with structured operational data, organizations can improve accountability for PSC submissions, version changes, refund opportunities, and additional duty exposure. This creates a stronger audit trail while allowing experienced personnel to focus on higher-risk discrepancies rather than routine report manipulation. Learn more about modernizing customs and compliance operations at Stable Software.
