# Classification corrections: a worked exception | SourceX

Canonical: https://refer.sourcex.si/guides/classification-corrections-exception-examples
Last updated: 2026-11-04

The records that explain a classification correction are the ones that tell its story in order: the moment sales changed what a product was for, the analyst who asked, the broker who reasoned it through and cited a ruling, the director who said yes, the corrected filing and the fixed part record. A new code alone shows that something changed, never why. Below is one Illustrative story, a pump sold for a new purpose, told step by step with the person and the record behind each decision.

This story belongs to the [classification corrections hub](/guides/workflow-classification-corrections). Here the job is narrow: follow a single hard correction from start to finish so a partner can hear the same pattern in a client's own words.

## The case (Illustrative)

Fictional, not a real case or a completed deal. A 340-person family-owned company that imports industrial pumps has for years brought in one model under a duty provision tied to farm irrigation. Farmers bought it to move water across fields; nobody at the company thought about it much. In spring, a new sales manager wins orders from factories that want the same pump for general water transfer, and the product team updates the catalog. Nobody tells the trade compliance team. For a few months, shipments keep arriving under the old classification while the pump is increasingly sold for something else.

## Step by step: who noticed, who decided

### Step 1: the trigger

Because the old classification depends on how the pump is used, the change matters. Under 19 CFR 10.133, an actual-use claim needs the use intended at importation, the article so used, and proof of use within three years; 19 CFR 10.137 puts the burden of keeping use records on the company. Product management updates the pump's product master: new application, general industrial use, effective date noted. **Who decided:** the product manager, as a commercial decision. **Record:** the ERP product master change with its date. Nobody has thought about customs yet.

### Step 2: the question

A compliance analyst reviewing a monthly product-change report sees the new application and asks the customs broker whether the irrigation-use classification still applies. **Who decided:** the analyst, to raise it. The Customs reasonable care guidance puts the duty to classify with reasonable care on the importer of record, while Customs fixes the final classification, so raising the question is the company's job, not the broker's alone. **Record:** the email to the broker, naming the part number and the open entries.

### Step 3: the analysis

The broker's classification specialist compares candidate provisions and cites a published ruling on similar pumps from the agency's free public rulings database. The note concludes that the general-use provision fits the new application. **Who decided:** the licensed broker, on the classification question. **Record:** the broker platform note with the ruling number and reasoning.

### Step 4: the authorization

The compliance director reads the note and approves reclassification of open entries for the model and a change to future entries. **Who decided:** the compliance director, who holds authority to act for the company. **Record:** an approval email referencing the broker note.

### Step 5: the action, and the branch

Here the case forks by date. For entries still inside the window, the broker files a post summary correction, the electronic route to correct an ACE entry summary before liquidation, filed within 300 days of entry and at least 15 days before scheduled liquidation, with up to five reason codes and a free-text description. Older entries fall outside that route and go to whatever process the broker or trade counsel decides; this page does not give customs advice. **Record:** the revised entry lines with reason code and description, and a note on how older entries were handled.

### Step 6: the checked result

The corrections are accepted. The part master's duty-code field is updated so later entries use the new provision. **Who decided:** entry operations, confirming acceptance; product data, updating the master. **Record:** correction status in the customs software and the part master change.

## The chain as a decision log

Illustrative. The same case as the company would want to find it years later:

| Step | Record | System | Who decided | What it proves |
|---|---|---|---|---|
| 1. Trigger | Product master change, new application | ERP | Product manager | The stated use changed, with a date |
| 2. Question | Analyst email to broker | Email | Compliance analyst | Who noticed, and when |
| 3. Analysis | Broker note citing a ruling | Broker platform | Licensed broker | The reasoning, not just the answer |
| 4. Authorization | Approval email | Email | Compliance director | Who had authority to act |
| 5. Action | Post summary correction with reason code | Customs software | Broker, on approval | What changed, on which entries |
| 6. Result | Acceptance and part master update | Customs software and ERP | Entry operations, product data | The exception closed and stayed closed |

## Why steps 3 and 4 carry the value

Steps 1 to 6 together are a decision with an outcome. Steps 3 and 4 are what make it more than a log line: a qualified person reasons from product facts to a provision, cites an authority that can be checked, and a second person with authority accepts the reasoning before anything is filed. The branch at step 5 adds a rule-bound choice about the route.

That shape is what AI developers describe needing when they build systems meant to do real work: a trigger, evidence, a judgment, an approval and a verified result. [Why AI agents need work data](/proof/ai-agents-need-work-data) and the [exception handling guide](/guides/exception-handling-ai-agents-data) explain the demand, and [what GDPval is](/questions/what-is-gdpval) shows how real-task evaluations are built. The chain is only useful if each link survives; how the links join across ERP, email, broker platform and customs software is mapped in [classification corrections records across systems](/guides/classification-corrections-records-across-systems).

## Signals of similar corrections at a client

Phrases a trade systems integrator might hear from a compliance team:

- "Sales changed what the product is for, and nobody told us for months."
- "Our broker always cites a ruling in the note."
- "Reclassifications need the director's sign-off by email."
- "We corrected the open entries; the older ones went to counsel."
- "The part master didn't get updated, so it happened again."

Then ask four metadata questions: roughly how many corrections a year; whether broker notes stay attached to entries; whether approvals live in email or a system; and how many years each system holds. Do not ask for entries, part numbers or rulings.

The usual first contact is the compliance director; who can authorize a licensing discussion is covered in [who can license classification corrections records](/questions/who-can-license-classification-corrections-records). The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions. Buyer interest, the rights result for client-supplied material and any offer stay unknown until SourceX reviews the opportunity.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If an importing or brokerage client keeps chains like this one, with notes and approvals intact, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its decision-maker.

## Sources

- https://www.cbp.gov/trade/programs-administration/entry-summary/post-summary-correction
- https://www.ecfr.gov/current/title-19/chapter-I/part-10/subpart-A/subject-group-ECFR6e5353a8038b367/section-10.133
- https://refer.sourcex.si/terms
- https://www.cbp.gov/sites/default/files/assets/documents/2018-Mar/icprescare2017revision.pdf
