Classification corrections records across systems: a system map of entries, notes, rulings and approvals

Short answer

Rebuilding a classification correction across systems needs identifiers that each system shares with the next: entry number plus line, part number, ruling number and timestamps that sort correctly. Four systems are involved: ERP product master, mailboxes, broker platform and ACE filing software. Each stores one piece in its own fields. Without common identifiers, a single correction splits into four records that no query can reconnect. Below is the field-level map, then one Illustrative join.

Visual briefFull-size diagram
Four system lanes, ERP product master, email, broker platform and ACE filing software, with six records of one correction linked in order by keys: part number, entry list, note reference, entry number and part number again.
Illustrative: four systems and the keys that let one correction be read as a single chain.

This system map is part of the classification corrections hub. It is a reference for trade systems integrators: which field in which system, which identifier joins it, and which administrator to ask.

The system map: record, system, key, owner

Owners vary between importing companies and brokerages; these are typical for a company working with an outside broker.

RecordSystemLinking key it carriesTypical owner
Product application or specification changeERP product masterPart number, effective dateProduct management
Duty-code field on the partERP or classification databasePart number, HTS code, ruling referenceTrade compliance
Analyst question to the brokerEmailPart number or model; entry numbers if typedCompliance analyst
Broker classification noteBroker platform notesEntry number, part number, ruling numberLicensed broker
Approval to correctEmail, sometimes a workflow toolReference to the note; entry listCompliance director
Revised entry with reason codeCustoms software (ACE filing)Entry number, line number, original and revised HTS, reason codeEntry operations
Acceptance statusCustoms softwareEntry number, status dateEntry operations

On the customs side the structure is fixed by U.S. Customs and Border Protection. The Entry Summary Create/Update CATAIR marks a filing as a post summary correction and carries separate tables of header and line reason codes. The agency's post summary correction guidance allows up to five reason codes at header or line level, plus a free-text description. The free text is where a broker can put the ruling number, which turns the entry into a joinable record.

Five keys and how each one fails

KeyCustoms software fieldEmail or notes fieldHow the join fails
Entry and lineEntry number, line number, original and revised HTSEntry number in the subject or bodyThreads that mention "last month's entries" with no number
PartPart number on the entry linePart number or model in the analyst emailMarketing names that differ from the part master
Authority citedRuling number in the correction description, if enteredRuling number in the broker noteRulings later modified or revoked
ReasonCorrection reason codeFree-text explanation in the approvalCodes that do not match the narrative
ChronologyFiled date and statusSent dates on question, analysis and approvalApproval dated after filing

A further wrinkle: when the agency reverts a post summary correction, the CATAIR notes that the entry summary returns to the last accepted version, which may not be the original. A company reconstructing history needs the version sequence, not just the latest state.

One correction joined across four systems (Illustrative)

A different fictional case from the one on the exception examples page, so the join can be seen on its own: a 410-person company that imports commercial LED light fixtures whose engineering team swapped the driver in fixture L-118 for one with a built-in occupancy sensor. The composition change raised a classification question. All values are invented.

OrderSystemRecordKeys it carriesJoins to
1ERPEngineering change notice: new driver with sensor, effective in MarchPart L-118, effective dateEmail by part number
2EmailEngineer flags the change to trade compliance, listing nine open entriesPart L-118, entry listBroker note by entry list
3Broker platformNote comparing two provisions for the revised fixture, citing a rulingEntry numbers, part L-118, ruling numberApproval by note reference
4EmailCompliance director approves correcting the open entriesNote reference, entry listFilings by entry number
5ACE filing softwareRevised lines with line reason code; ruling number in the descriptionEntry and line, revised HTS, reason codeRuling by number; ERP by part
6ERPDuty-code field on L-118 updated, linked to the change noticePart L-118, new HTSCloses the loop

Read in order, the six rows tell the whole story. Remove the entry list from row 2 or the ruling number from row 5 and the chain falls apart into pieces nobody can reconnect with confidence.

Checking a cited ruling without opening any files

The ruling row is a useful quality check that needs no access to company records. The agency's public rulings database, CROSS, links a ruling to later rulings that modified or revoked it, so the company can confirm what each cited ruling meant on the date of the note. A partner can suggest that check; the company runs it. The tariff classification consultant guide covers how advisors already use rulings with clients.

What a platform cutover does to the joins

Entry lines usually survive a platform change, because nobody wants to lose filed entries. The joins are what break. If a new broker platform imports entry lines but flattens notes into one undated field, row 3 loses its entry links. If the mail archive moves on a different schedule, rows 2 and 4 drift away. The integrator can flag both in the cutover plan without touching record content; an email platform migration covers the mailbox side, and tariffs and middle-market distress explains why these records are under pressure now.

Export capability varies by platform, version and contract, so the company should confirm with its own administrators what history each system can produce. 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. Product facts and proof-of-use records often come from importing clients, so rights are layered; buyer interest, the rights result and any offer stay unknown until SourceX reviews the opportunity. The referral brief template puts the map on one page.

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 a company's systems still carry the entry, part and ruling keys that join its corrections, register as a partner, check the company on who qualifies and read the program terms before introducing the compliance director.

  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

Which key matters most?

The entry number with line number. It anchors the customs record, and every other record has to point back to it. Email that says only 'the fixture entries' cannot be joined reliably.

Why check rulings in CROSS if the broker note already cites one?

Because rulings can be modified or revoked later. CROSS links a ruling to those later rulings, so the company can confirm what the cited ruling meant on the date of the note without anyone outside opening the files.

Can a trade systems integrator build the joins for the company?

The integrator can describe which keys exist and flag cutover risks in the project plan. Building or exporting joined datasets for a licensing discussion waits until the company decides to talk and SourceX has reviewed rights.

Sources

  1. cbp.gov/trade/programs-administration/entry-summary/…
  2. cbp.gov/sites/default/files/2026-05/ace_catair_entry…
  3. refer.sourcex.si/terms
  4. rulings.cbp.gov

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