Post Entry Audit Program: Build a Monthly Self-Review That Catches Errors

Key Points

• A structured monthly self-review of ACE entry data is one of the most effective ways to demonstrate reasonable care and catch classification, valuation, and special-program errors before CBP does.
• Post Summary Corrections (PSCs) are available only before liquidation and are the lowest-friction correction path for errors discovered early.
• Protests must generally be filed within 180 days of liquidation; missing that window forecloses most administrative refund remedies.
• A voluntary prior disclosure filed before CBP initiates a formal inquiry can substantially reduce penalty exposure for fraud or gross negligence under the penalty statute.
• Systematic, documented self-review is itself evidence of reasonable care, which is a legal standard every importer must meet on every entry.

On this page

1. What a post entry audit program is and why it matters
2. Building a monthly ACE-data self-review: sampling approach
3. Error logging: what to capture and how to categorize errors
4. Choosing the right correction path: PSC, protest, or prior disclosure
5. Integrating the program into a broader reasonable-care framework
6. What importers should do
7. Key references

A post entry audit program is a recurring internal process in which an importer, broker, or compliance team pulls a sample of filed entry summaries, compares them against source documents and classification logic, logs every discrepancy, and routes each error to the appropriate correction mechanism. Done monthly on ACE data, it converts reactive error discovery into a managed, documentable compliance function.

The links in this article go to the primary documents: the proclamations, Federal Register notices, and official tariff schedule pages themselves. Read the source.

What a Post Entry Audit Program Is and Why It Matters

CBP's Automated Commercial Environment (ACE) records every entry summary your company or clients have filed. That data is also available to CBP's targeting and audit functions. Running your own periodic review of that same data lets you find errors on your timeline rather than CBP's.

The practical stakes are straightforward:

• Overpayments erode margins and can only be recovered within strict time limits.
• Underpayments create penalty exposure, and the severity of penalties scales with culpability (negligence, gross negligence, or fraud).
• Special-program errors, such as misapplied free-trade-agreement claims or incorrect special-tariff-number declarations, can trigger both duty liability and origin-verification inquiries.

Beyond the financial math, a documented self-review program is direct evidence of reasonable care, the legal standard that every importer must satisfy on every transaction under the Customs Modernization Act.

Building a Monthly ACE-Data Self-Review: Sampling Approach

No compliance team can manually verify every line of every entry. The goal is a statistically defensible sample that surfaces systemic issues, not a 100% audit.

Define your universe

Start by segmenting entries into risk tiers. High-risk tiers typically include:

• High-duty-rate HTS chapters and subheadings
• Entries claiming FTA preferential treatment or special tariff programs
• Entries subject to Section 232, Section 301, or other special-measure duties where additional HTS numbers must be declared
• AD/CVD-covered merchandise
• New suppliers, new countries of origin, or new product lines introduced in the review period

Sample size and selection

A common starting framework is to review 100% of entries in the highest-risk tier and a random 10 to 20 percent sample from lower-risk tiers. If the high-risk tier is very large, a statistically valid random sample (typically 30 to 60 entries, depending on universe size and acceptable confidence level) is acceptable, provided the methodology is documented. Rotate selection within random tiers so the same entries are not repeatedly reviewed.

Data pull mechanics in ACE

ACE reports allow filtering by entry date, port, HTS number, country of origin, and entered value. Pull entry summary data directly from ACE or your broker's ACE-connected system. Match each sampled entry summary against the commercial invoice, packing list, bill of lading, and any applicable rulings or binding determinations on file.

Error Logging: What to Capture and How to Categorize Errors

A log that simply notes "classification error" is not useful for systemic correction. Capture the following fields for each discrepancy found:

• Entry number and line number
• Filed HTS subheading and correct HTS subheading
• Filed value or quantity and correct value or quantity
• Duty impact (overpayment or underpayment, in dollars)
• Root cause: importer error, broker error, data-entry error, ruling misapplication, or ambiguous classification
• Liquidation status and liquidation date
• Proposed correction path (see next section)
• Assigned owner and target resolution date

Categorizing by root cause is critical. If 80 percent of errors trace back to a single supplier's invoices lacking required country-of-origin detail, the fix is upstream, not entry-by-entry corrections. Aggregate the log monthly and review for patterns before deciding on correction strategy.

Choosing the Right Correction Path: PSC, Protest, or Prior Disclosure

The correction mechanism that applies to a given error depends primarily on two factors: when the error was discovered relative to liquidation, and the nature and severity of the error.

Post Summary Correction (PSC)

A PSC allows an importer or broker to amend a filed entry summary after acceptance but before liquidation. PSCs are the preferred correction path for most routine errors discovered through self-review because they are electronically filed in ACE, they do not require CBP to initiate a separate action, and they reset the liquidation clock for the corrected data elements. PSCs can be used to correct HTS classifications, entered values, quantities, special-program claims, and most other entry-summary data fields. Note that not every entry type or data element is PSC-eligible; review the applicable CBP ACE guidance and any active CSMS messages before filing. For current PSC processing rules and restrictions, see our article on CBP post summary correction processing modifications.

Protest

Once an entry liquidates, the PSC window closes. The primary administrative remedy is a protest filed under 19 U.S.C. 1514. Protests must generally be filed within 180 days of the date of liquidation. A protest can contest the classification, appraisement, rate of duty, or other CBP decision on the liquidated entry. Protests that result in additional duty owed are treated differently from protests seeking refunds; both paths require accurate documentation of the correct treatment and the basis for the challenge. Missing the 180-day deadline is almost always fatal to the administrative remedy, making timely liquidation monitoring a core function of any self-review program.

Prior Disclosure

When self-review uncovers a pattern of underpayments that could be attributed to gross negligence or fraud, or when the dollar magnitude is material, a voluntary prior disclosure under 19 U.S.C. 1592(c)(4) may be the appropriate path. A prior disclosure, filed before CBP has initiated a formal investigation, significantly limits the penalty that CBP can assess. The disclosure must identify the merchandise, the violation, and the correct duty, and it must be accompanied by or followed promptly by tender of the unpaid duties and interest. Prior disclosure is not a routine self-correction tool; it is a structured legal filing. However, a well-run audit program that catches a systemic issue early, before a CBP inquiry begins, is precisely the scenario in which prior disclosure provides the greatest protection.

Severity framework

A practical decision rule for routing errors:

• Isolated, pre-liquidation, low dollar value: PSC
• Post-liquidation, refund due to importer: Protest within 180 days of liquidation
• Post-liquidation, duty owed to CBP, non-systemic: Amended protest or voluntary tender with documentation
• Systemic underpayment pattern, material dollars, or potential fraud indicator: Evaluate prior disclosure with legal counsel before taking any other action

Integrating the Program into a Broader Reasonable-Care Framework

A post entry audit program does not stand alone. It should be one layer of a compliance architecture that also includes:

• Pre-entry classification review for new products, new suppliers, and new tariff-measure applicability
• Recordkeeping discipline aligned with the records CBP can demand under the (a)(1)(A) list, described in detail in our article on the CBP (a)(1)(A) list
• Tariff-alert monitoring so that rate changes, new special-measure HTS numbers, or quota openings are captured before entries are filed, not discovered in the monthly review
• Written procedures documenting how the self-review is conducted, who conducts it, and how errors are escalated and resolved

The written procedures matter because CBP's informed-compliance framework, which informs how CBP assesses culpability in penalty cases, explicitly credits importers who have documented processes for verifying their entries. For a deeper look at how informed compliance and enforced compliance interact, see our article on informed compliance at CBP.

Store the completed monthly review logs, the sample selection methodology, and all correction filings in your recordkeeping system. CBP's general records-retention requirement runs five years from entry date for most transaction records. Audit program documentation should be retained at least as long as the underlying entries.

What Importers Should Do

• Schedule a standing monthly review. Pull ACE entry data within the first week of each month covering the prior month's entries, apply your risk-tiered sampling methodology, and complete the error log before entries in the sample approach liquidation.
• Monitor liquidation dates actively. Set calendar alerts so that errors discovered after liquidation are routed to protest before the 180-day deadline under 19 U.S.C. 1514 expires.
• Escalate systemic patterns immediately. If the error log shows the same root cause across multiple entries and periods, treat it as a potential prior-disclosure situation and evaluate it before filing any additional corrections.
• Document everything. The log, the methodology, the correction filings, and the resolution outcomes are your evidence of reasonable care if CBP ever conducts a focused assessment or penalty proceeding.

Key References

• 19 U.S.C. 1592 - Penalties for fraud, gross negligence, and negligence in entry; prior disclosure provision at subsection (c)(4)
• 19 U.S.C. 1514 - Protest of CBP decisions; 180-day filing deadline after liquidation
• CBP ACE Features and Reports - Entry summary data access, PSC filing, and ACE account management
• CBP ACE Program Overview - Automated Commercial Environment program documentation
• Harmonized Tariff Schedule of the United States (USITC) - Official HTS for classification verification
• Federal Register - Source for special-measure tariff notices, AD/CVD orders, and quota announcements
• CBP Post Summary Correction Processing Modifications - Current PSC eligibility rules and processing changes
• CBP (a)(1)(A) List: Records CBP Can Demand on Request - Recordkeeping obligations tied to the self-review document retention requirement
• Importer Reasonable Care: What the Mod Act Actually Requires - Legal standard that a self-review program helps satisfy
• Informed Compliance CBP: How It Works and What It Demands - How CBP uses informed compliance in penalty and audit contexts