# Classification corrections across systems | SourceX

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

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.

This system map is part of the [classification corrections hub](/guides/workflow-classification-corrections). 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.

| Record | System | Linking key it carries | Typical owner |
|---|---|---|---|
| Product application or specification change | ERP product master | Part number, effective date | Product management |
| Duty-code field on the part | ERP or classification database | Part number, HTS code, ruling reference | Trade compliance |
| Analyst question to the broker | Email | Part number or model; entry numbers if typed | Compliance analyst |
| Broker classification note | Broker platform notes | Entry number, part number, ruling number | Licensed broker |
| Approval to correct | Email, sometimes a workflow tool | Reference to the note; entry list | Compliance director |
| Revised entry with reason code | Customs software (ACE filing) | Entry number, line number, original and revised HTS, reason code | Entry operations |
| Acceptance status | Customs software | Entry number, status date | Entry 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

| Key | Customs software field | Email or notes field | How the join fails |
|---|---|---|---|
| Entry and line | Entry number, line number, original and revised HTS | Entry number in the subject or body | Threads that mention "last month's entries" with no number |
| Part | Part number on the entry line | Part number or model in the analyst email | Marketing names that differ from the part master |
| Authority cited | Ruling number in the correction description, if entered | Ruling number in the broker note | Rulings later modified or revoked |
| Reason | Correction reason code | Free-text explanation in the approval | Codes that do not match the narrative |
| Chronology | Filed date and status | Sent dates on question, analysis and approval | Approval 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](/guides/classification-corrections-exception-examples), 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.

| Order | System | Record | Keys it carries | Joins to |
|---|---|---|---|---|
| 1 | ERP | Engineering change notice: new driver with sensor, effective in March | Part L-118, effective date | Email by part number |
| 2 | Email | Engineer flags the change to trade compliance, listing nine open entries | Part L-118, entry list | Broker note by entry list |
| 3 | Broker platform | Note comparing two provisions for the revised fixture, citing a ruling | Entry numbers, part L-118, ruling number | Approval by note reference |
| 4 | Email | Compliance director approves correcting the open entries | Note reference, entry list | Filings by entry number |
| 5 | ACE filing software | Revised lines with line reason code; ruling number in the description | Entry and line, revised HTS, reason code | Ruling by number; ERP by part |
| 6 | ERP | Duty-code field on L-118 updated, linked to the change notice | Part L-118, new HTS | Closes 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](/guides/tariff-classification-consultant) 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](/guides/an-email-platform-migration) covers the mailbox side, and [tariffs and middle-market distress](/guides/tariffs-middle-market-distress-2026) 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](/resources/classification-corrections-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](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing the compliance director.

## Sources

- https://www.cbp.gov/trade/programs-administration/entry-summary/post-summary-correction
- https://www.cbp.gov/sites/default/files/2026-05/ace_catair_entry_summary_create-update_ae-ax_2025-11-01_rev_109_508c_2.pdf
- https://refer.sourcex.si/terms
- https://rulings.cbp.gov/
