This scorecard is part of the shipment-to-credit-resolution guide. Use it after the company has described its systems, and before you describe the opportunity to anyone else.
Scoring rules
Give each check 2 points for a pass, 1 for a partial and 0 for a fail or unknown. Ten checks make 20 points. Convert to a percentage if that helps the conversation, but keep the per-check marks: a reviewer learns more from "linkage fails before 2021" than from a single number.
Three rules keep the score honest:
- Score from metadata only. Field names, date ranges, counts, settings and owners. If answering a check would require reading a claim, mark it unknown.
- Date every pass. A check that passes only from 2021 is a pass from 2021 and a fail before it. Record the year.
- Name the owner. Each answer should come with the role that gave it, so SourceX knows whom to ask later.
The ten checks
| Check | Area | How to check at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1. System overlap | Coverage | Ask the years held in the warehouse system, the claims portal and the ledger | All three overlap for 3+ years | Overlap under 3 years | One system has no history for the period |
| 2. Claim volume | Coverage | Ask roughly how many carrier claims are filed a year | Known within a range | Known only for recent years | Unknown |
| 3. Anchor key on claims | Linkage | Ask which reference the claims team types on every claim | Bill of lading or shipment ID on every claim | On most claims | Varies by person |
| 4. Split listing | Linkage | Ask whether the portal lists every PRO number against the bill of lading | Always | For some carriers | Never |
| 5. Claim number on credits | Linkage | Ask what number AP records when a carrier pays | Company and carrier claim numbers both | Carrier number only | Neither |
| 6. Claim dates | Timestamps | Ask which dates are fields: filed, acknowledged, offered, paid | All four | Filed and paid only | Paid date only |
| 7. Status history | Timestamps | Ask whether the portal keeps past statuses or only the latest | Full history | Latest status plus notes | Latest only |
| 8. Amounts agree | Outcomes | Ask whether claimed, offered, paid and written-off amounts are separate fields | All four, never netted | Separate, but carriers sometimes net claims against open freight bills | Only the credit amount |
| 9. Shortfall reason | Outcomes | Ask how a write-off of an unpaid balance is recorded | Coded reason field | Free-text memo | No reason recorded |
| 10. Declared gaps | Gaps | Ask what history sits outside the systems: email, a former carrier's portal, a retired ERP | Gaps named with years | Gaps suspected, not dated | Nobody can say |
Check 4 is where repacked units also show up. GS1 assigns a new Serial Shipping Container Code when a logistic unit is broken down and repacked, so a company should also be asked whether its warehouse system keeps the old code beside the new one. Score that inside check 4 rather than adding a check.
The split-shipment test
One case tests most of the scorecard at once: a carrier claim that references a split shipment. The claim names the original shipment and its bill of lading. The carrier moved the freight on two PRO numbers and pays against one of them. An AP clerk matching the credit cannot tell whether it settles the whole claim, part of it, or a different claim on the same lane.
Ask the claims lead to walk through how such a claim would be traced today, in general terms:
| Step in the trace | Which check it exercises | What a complete answer sounds like |
|---|---|---|
| Find the claim from the credit | 5 | "Our claim number is on every carrier credit since 2021" |
| Find both PROs from the claim | 4 | "The portal lists every PRO under the bill of lading" |
| Tell whether the payment covers both | 8 | "Offered and paid amounts are separate fields" |
| Explain any balance | 9 | "Write-offs use a reason code from a fixed list" |
Multiply that case by a few hundred claims a year and the difference shows. A company that fails checks 4 and 5 has a record of every step but no reliable join for many of them.
Why claim timing stretches the trail
Two timing rules explain why claim records accumulate over months and why checks 6 and 7 matter. A carrier may not set a claim-filing period shorter than 9 months. Carrier claim regulations then require the carrier to pay, decline or make a firm compromise offer within 120 days of receiving a claim, or else send a written status with the reason for delay and repeat it every 60 days while the claim is pending. A single claim can sit open across quarters, through staff changes and sometimes through a system change. If the portal keeps only the latest status, the trail of those letters and offers is gone, which is why status history earns its own check.
A filled scorecard (Illustrative)
A fictional 520-person housewares importer that files about 1,800 carrier claims a year, scored from a 40-minute call with its controller and claims lead.
| Check | Mark | Points | Note |
|---|---|---|---|
| 1. System overlap | Pass | 2 | All three systems overlap from 2018 |
| 2. Claim volume | Pass | 2 | About 1,800 a year |
| 3. Anchor key on claims | Pass | 2 | Bill of lading on every claim |
| 4. Split listing | Partial | 1 | Two of five main carriers list every PRO |
| 5. Claim number on credits | Fail | 0 | Neither number on credits before 2021; both since |
| 6. Claim dates | Pass | 2 | Four date fields in the portal |
| 7. Status history | Partial | 1 | Latest status plus free-text notes |
| 8. Amounts agree | Pass | 2 | Separate fields; no netting reported |
| 9. Shortfall reason | Partial | 1 | Coded since 2023, memo before |
| 10. Declared gaps | Pass | 2 | Pre-2018 claims in a shared mailbox |
| Total | 6 pass, 3 partial, 1 fail | 15 of 20 | 75% complete |
The useful output is the sentence it produces: "Strong from 2021 on, linkage partial before; status history partly in notes; reason codes from 2023." That sentence can go into an introduction. The record chain shows how the keys behind checks 3 to 5 connect, and the missing-context comparison shows what a reader loses when they fail.
Before you introduce
The scorecard describes the trail; it does not qualify the company. Confirm the baseline too: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Since the trail spans warehouse, transportation and finance, that contact is the CEO (in an owner-run company, usually the owner) rather than the claims lead who answered the checks. 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: whether carrier and customer contracts allow licensing, how names, addresses and amounts would be de-identified, which years a buyer would want and what the company would be paid. Partners score from metadata and never handle claim files or remittances. Related finance records are described under AR dispute resolution and AP exception handling; freight audit and payment companies often hold the invoice side, and an ERP replacement handoff checklist helps when a system change is coming.
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 your scorecard produces a dated sentence the company's owners agree with, register as a partner, check who qualifies and read the terms before you introduce the decision-maker.