# Shipment-to-credit metadata packet | SourceX

Canonical: https://refer.sourcex.si/guides/chain-shipment-to-credit-resolution
Last updated: 2026-11-04

A referral partner can describe a company's shipment-to-credit history from metadata alone: which system records the dispatch scan, where the carrier claim lives, which ledger records the credit, how many claims a year, which reference ties them together, and who owns each step. No claim file or invoice changes hands. The case to test before introducing is a claim that references a shipment the carrier or warehouse later split, because that is where credits stop matching their claims.

## A worked case: six pallets, one claim, two pro numbers (Illustrative)

A fictional 340-person distributor ships six pallets to a retailer. At the cross-dock, one pallet is damaged, broken down and rebuilt. Under the GS1 standard a new Serial Shipping Container Code (SSCC) is assigned when a logistic unit is broken down and repacked, so the warehouse now holds five original pallet IDs and one new one. The carrier moves the freight on two pro numbers. The retailer refuses the rebuilt pallet.

| Step | System | Record | Reference it carries |
|---|---|---|---|
| Dispatch | WMS | Six pallets scanned out, each with an SSCC | Shipment ID S-1180, six SSCCs |
| Repack | WMS | One pallet rebuilt; new SSCC assigned | New SSCC; link to the old one only if the WMS stores it |
| Transit | Carrier portal | Freight split across pro numbers P-1 and P-2 | Bill of lading number |
| Exception | Carrier portal | Rebuilt pallet refused at delivery | P-2 only |
| Claim | Carrier portal | $4,800 claim filed against shipment S-1180 | Shipment ID and bill of lading, not P-2 |
| Settlement | Carrier portal and email | Carrier offers $3,000 against P-2 | P-2 and the carrier's claim number |
| Credit | ERP | $3,000 credit received; $4,800 claim receivable | Claim number typed by AP, if at all |
| Close | ERP | $1,800 written off | Journal entry with a free-text memo |

Nothing here is unusual, and every system did its job. The problem is that each system kept its own reference. The rest of this page asks which links survive.

## What metadata can a referral partner collect about shipment-to-credit-resolution without reading private content?

Counts, ranges, field names, link status and owners. The packet below is a starting form for a logistics finance advisor talking with a controller or claims lead.

### Metadata packet (Illustrative)

| Field | WMS (dispatch scan) | Carrier portal (claim) | ERP (credit) |
|---|---|---|---|
| Object types | Shipments, pallets with SSCCs, scans, repacks | Claims, status updates, settlement offers | Claim receivables, credits, write-offs |
| Date range | 2017 to today | 2020 to today; earlier claims by email | 2015 to today |
| Approximate volume | About 1.2 million shipments | About 2,600 claims | About 2,400 claim credits |
| Shared reference | Shipment ID and bill of lading | Bill of lading; carrier claim number | Claim number typed by AP since 2021 |
| Split or repack link | Old SSCC stored after repack? Unknown | Pro numbers per split listed? Unknown | Not held |
| Step owner | Warehouse operations manager | Transportation claims lead | Accounts payable manager |
| Retention rule | No purge known | Portal access ends with carrier contract | Seven-year finance policy |
| Planned change | WMS upgrade next year | None | ERP replacement under review |

For U.S. interstate motor freight, two legal clocks explain why the claim step can stay open for months. A carrier may not set less than 9 months for filing a claim, or less than 2 years for suing after it disallows one (49 U.S.C. 14706). Once a claim is received, the carrier must pay, decline or make a firm settlement offer within 120 days, or report the status in writing and repeat that every 60 days (49 CFR 370.9). That status trail is what the portal and email hold before any credit reaches the ERP.

Note the retention row for the carrier portal. If claim history lives on a carrier's site, the company may lose access when a contract ends, which makes its own copies matter. A planned ERP replacement is a similar real deadline; the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) covers what to ask.

## Who can authorize the conversation, and what stays unknown

Shipment-to-credit history spans warehouse, transportation and finance, so the sponsor is usually a CFO, COO or owner. A claims lead can describe the process but rarely has authority to license finance records.

Before you introduce, confirm:

- The company has 50+ full-time employees at peak, contractors excluded, and a documented operating history.
- It owns the records or has the right to license them; records held for 3PL clients may belong to those clients.
- A named decision-maker will take a first call.
- 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.

What stays unknown until SourceX reviews it: which records a buyer would want, how customer and carrier contracts limit use, how names and addresses would be removed, and what the company would be paid. You never handle raw records. For sector context see [introducing logistics and warehousing businesses](/guides/how-advisors-introduce-logistics-and-warehousing-clients-to-a-data-licensing-opportunity), [logistics exceptions and their resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions) and the [systems hub](/systems).

## Go deeper on shipment-to-credit-resolution records

- [How to link dispatch scans, carrier claims and ERP credits](/guides/shipment-to-credit-resolution-record-linkage): a guide to the references that join WMS, carrier portal and ERP records.
- [Shipment-to-credit-resolution completeness checklist](/resources/shipment-to-credit-resolution-completeness-checklist): a checklist of the breaks that leave a claim trail incomplete.
- [What a single-system claims or ERP export leaves out](/guides/shipment-to-credit-resolution-missing-context): a guide to the context lost when only one system is exported.

## 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 controller can name the claim key and say from which year it links all three systems, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before making the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://www.gs1.org/standards/id-keys/sscc
- https://www.govinfo.gov/content/pkg/CFR-2001-title49-vol4/pdf/CFR-2001-title49-vol4-sec370-9.pdf
- https://uscode.house.gov/us/usc/t49/s14706/
