# Classification corrections: migration inventory | SourceX

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

Before a broker platform migration, inventory the record classes behind each classification correction: ruling references, broker notes, revised entries and the product facts that changed. Note the years each system covers, who owns each class, which records are still inside a customs clock, and the date old-platform access really ends. Keep the inventory at metadata level. The compliance director can usually supply it; the introduction goes to the executive with authority to discuss licensing.

## What is a classification correction, and why does its history matter?

A classification correction is a change to the tariff classification declared on an entry after the fact: a broker or importer finds that a product belongs under a different heading, often because its declared use, composition or a ruling changed. For entries not yet liquidated, the usual U.S. route is a [post summary correction](https://www.cbp.gov/trade/programs-administration/entry-summary/post-summary-correction), filed electronically within 300 days of entry and at least 15 days before scheduled liquidation, with up to five reason codes and a free-text explanation.

The corrected entry is only the last record in the chain. The reasoning sits upstream: the broker note recording what the product actually is, the ruling number checked in [CROSS](https://rulings.cbp.gov/) (which also links a ruling to later rulings that modified or revoked it), the product specification that changed, and the approval to file. For goods entered under actual-use provisions, the importer must also show the article was used as declared, with [proof furnished within 3 years](https://www.ecfr.gov/current/title-19/chapter-I/part-10/subpart-A/subject-group-ECFR6e5353a8038b367/section-10.133). Years of these chains show how a trade compliance team reasons about products, which is why they deserve an inventory before the software that holds them changes.

## What should be inventoried before a broker platform migration affects classification corrections history?

Inventory the chain, not just the entries. A migration usually carries entry data forward, because entry records relating to an entry are generally kept for [five years from the date of entry](https://www.ecfr.gov/current/title-19/chapter-I/part-163/section-163.4) whichever platform holds them. The reasoning around a correction often lives in the old platform's notes and attachments and in email, and those are the parts most likely to be left behind or flattened into a single comment field.

The register below is an Illustrative inventory for a fictional 260-person customs brokerage moving its entry-writing platform. Each cell is metadata.

| Record class | System today | Years held | Owner | Migration plan |
|---|---|---|---|---|
| Entry summaries and revised entries | Old broker platform | 8 | Entry operations | Last 5 years converted |
| Post summary correction filings with reason codes | Old broker platform | 6 | Entry operations | Converted with entries |
| Broker notes on product facts | Old broker platform notes | 8 | Classification team | Flattened into one text field |
| Ruling references cited per part | Classification database | 10 | Classification team | Current parts only |
| Product specification changes from importers | Email, shared drive | 7 | Account managers | Outside the project plan |
| Internal approvals to file a correction | Email | 7 | Compliance director | Outside the project plan |
| Proof-of-use records for actual-use entries | Importer files, broker portal uploads | 5 | Importer, with broker copies | Portal uploads not converted |

Then confirm four facts:

1. Which record classes exist, and which link to an entry number and part number?
2. How many years each system covers, as the system shows it, not as people remember it.
3. Who administers the broker platform, the classification database, the mail archive and the product master.
4. The date read access to the old platform ends under the vendor contract.

Two limits keep this honest. The retention obligation is separate from any licensing question; it explains why some records must survive, not who may license them. And a partner never recommends keeping data the company has no authority or reason to keep. Email-side retention during a change is covered in [an email platform migration](/guides/an-email-platform-migration).

## Work through one correction the migration could orphan

Take an Illustrative product whose declared use changed after import. The broker note records the new use, the classifier checks a ruling in CROSS, and a post summary correction files the revised heading. After migration, the revised entry survives because entry data converts; the note becomes an undated line of text, the ruling reference survives only if the part is still active, and the importer's specification change sits in an account manager's mailbox. Anyone reading the new system sees a heading changed with no reason attached. The detailed case walk-through is on the exception examples page linked below; for the inventory, the question is whether each link in that chain has a home after cutover.

## Ask the compliance director about coverage and rights

The compliance director, or the licensed customs broker who supervises classification, knows where notes, rulings and approvals live and can say what the cutover carries. Authority to discuss licensing sits with the CEO, with the COO or general counsel advising. Ownership is layered in this sector: the brokerage writes the notes and filings, but the product facts and proof-of-use records often come from importer clients, whose agreements decide what may be reused. SourceX's rights review settles those questions; see [why data rights matter](/proof/why-data-rights-matter).

The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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, and the first valid introduction within the 90-day window is credited when the company submits a verified application.

Unknown until SourceX reviews it: buyer interest in this record type, the rights result for each importer's material, the de-identification required and any offer. The [tariff classification consultant guide](/guides/tariff-classification-consultant), the [logistics and warehousing page](/industries/logistics-and-warehousing), the guide to [logistics exceptions and their documented resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) and the [industries hub](/industries) cover neighboring ground.

## Go deeper on classification corrections

- [Classification corrections referral brief template](/resources/classification-corrections-referral-brief-template): a metadata-only brief to fill in, with one completed Illustrative example.
- [Classification corrections exception examples](/guides/classification-corrections-exception-examples): one hard correction case worked step by step.
- [Classification corrections records across systems](/guides/classification-corrections-records-across-systems): a system map with the keys that join entry, note and ruling.
- [Who can license classification corrections records](/questions/who-can-license-classification-corrections-records): a decision tree from record owner to authorized signer.

## 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 the cutover plan converts entries but not the notes, rulings and approvals behind years of corrections, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the executive who can authorize the discussion.

## Sources

- https://www.cbp.gov/trade/programs-administration/entry-summary/post-summary-correction
- https://www.ecfr.gov/current/title-19/chapter-I/part-163/section-163.4
- https://rulings.cbp.gov/
- https://www.ecfr.gov/current/title-19/chapter-I/part-10/subpart-A/subject-group-ECFR6e5353a8038b367/section-10.133
- https://refer.sourcex.si/terms
