Shipment-to-credit-resolution records: a sample metadata packet from WMS scan to carrier claim to ERP credit

Short answer

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.

Visual briefFull-size diagram
A branching flow shows one six-pallet shipment splitting into two carrier pro numbers after a pallet is repacked under a new SSCC, a $4,800 claim filed against the original shipment, and a $3,000 credit in the ERP that matches only one branch, leaving $1,800 unexplained.
Illustrative. The claim names the original shipment, the carrier pays against one half of the split, and the ERP cannot tell which.

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.

StepSystemRecordReference it carries
DispatchWMSSix pallets scanned out, each with an SSCCShipment ID S-1180, six SSCCs
RepackWMSOne pallet rebuilt; new SSCC assignedNew SSCC; link to the old one only if the WMS stores it
TransitCarrier portalFreight split across pro numbers P-1 and P-2Bill of lading number
ExceptionCarrier portalRebuilt pallet refused at deliveryP-2 only
ClaimCarrier portal$4,800 claim filed against shipment S-1180Shipment ID and bill of lading, not P-2
SettlementCarrier portal and emailCarrier offers $3,000 against P-2P-2 and the carrier's claim number
CreditERP$3,000 credit received; $4,800 claim receivableClaim number typed by AP, if at all
CloseERP$1,800 written offJournal 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)

FieldWMS (dispatch scan)Carrier portal (claim)ERP (credit)
Object typesShipments, pallets with SSCCs, scans, repacksClaims, status updates, settlement offersClaim receivables, credits, write-offs
Date range2017 to today2020 to today; earlier claims by email2015 to today
Approximate volumeAbout 1.2 million shipmentsAbout 2,600 claimsAbout 2,400 claim credits
Shared referenceShipment ID and bill of ladingBill of lading; carrier claim numberClaim number typed by AP since 2021
Split or repack linkOld SSCC stored after repack? UnknownPro numbers per split listed? UnknownNot held
Step ownerWarehouse operations managerTransportation claims leadAccounts payable manager
Retention ruleNo purge knownPortal access ends with carrier contractSeven-year finance policy
Planned changeWMS upgrade next yearNoneERP 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 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, logistics exceptions and their resolutions and the systems hub.

Go deeper on shipment-to-credit-resolution records

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, check the company against who qualifies and read the program terms before making the introduction.

  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

Do I need claim files or invoices to describe the chain?

No. Claim counts per year, the fields used to reference a shipment, the date ranges in each system and who owns claims are enough. Claim correspondence, photos, customer names and amounts stay inside the company.

Does SourceX integrate with a particular WMS, carrier portal or ERP?

This page names system types only to show where records usually sit. It does not describe a SourceX connector. If the company proceeds, it decides what to share under a signed agreement, and SourceX reviews rights and preparation from there.

Is a shipper with a few hundred claims a year worth introducing?

Possibly, if the history is long and the company meets the size and rights tests. A smaller claim volume with clean links can be more useful than a large one where credits cannot be matched. Describe what exists and let SourceX decide scope.

Sources

  1. refer.sourcex.si/terms
  2. gs1.org/standards/id-keys/sscc
  3. govinfo.gov/content/pkg/CFR-2001-title49-vol4/pdf/CFR-20…
  4. uscode.house.gov/us/usc/t49/s14706

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