Classification corrections history: what to inventory before a broker platform migration

Short answer

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.

Visual briefFull-size diagram
A timeline from the date of entry showing the clocks that still run when a broker platform cutover lands between years 2 and 3: the post summary correction window closes at 300 days, proof of actual use is due within 3 years, and entry records are kept for 5 years.
Illustrative entry timeline: the platform changes between years 2 and 3, while the correction and recordkeeping clocks keep running.

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, 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 (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. 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 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 classSystem todayYears heldOwnerMigration plan
Entry summaries and revised entriesOld broker platform8Entry operationsLast 5 years converted
Post summary correction filings with reason codesOld broker platform6Entry operationsConverted with entries
Broker notes on product factsOld broker platform notes8Classification teamFlattened into one text field
Ruling references cited per partClassification database10Classification teamCurrent parts only
Product specification changes from importersEmail, shared drive7Account managersOutside the project plan
Internal approvals to file a correctionEmail7Compliance directorOutside the project plan
Proof-of-use records for actual-use entriesImporter files, broker portal uploads5Importer, with broker copiesPortal 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.

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.

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, the logistics and warehousing page, the guide to logistics exceptions and their documented resolutions and the industries hub cover neighboring ground.

Go deeper on classification corrections

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, confirm the company against who qualifies, and read the program terms before you introduce the executive who can authorize the discussion.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does the five-year customs retention period mean the records can be licensed?

No. The retention period in 19 CFR 163.4 is an obligation to keep entry records; it says nothing about the right to license them. Licensing depends on who authored each record, the broker and importer agreements, and a rights review that SourceX runs after the introduction.

Can a trade systems integrator introduce the company if it only has technical access?

Yes, as the introducer, but technical access is not authority. The introduction should go to a decision-maker, usually through the compliance director, who can bring in counsel and finance.

Should we export the old broker platform before the introduction?

Only what the company already decides to keep for its own reasons and with the required authority. Do not create copies for a licensing discussion. Describe the records at metadata level and let SourceX review them first.

Sources

  1. cbp.gov/trade/programs-administration/entry-summary/…
  2. ecfr.gov/current/title-19/chapter-I/part-163/section-…
  3. rulings.cbp.gov
  4. ecfr.gov/current/title-19/chapter-I/part-10/subpart-A…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment