What a standalone warehouse or ledger export loses: one freight claim read before and after its carrier and finance context

Short answer

A single-system export keeps one team's view and loses the reason the money moved. A warehouse export shows what shipped, when and in how many units, but not the claim, the carrier's offer or the write-off. A finance export shows a credit and a write-off with no link to a shipment or a cause. Read alone, each one leads a reviewer to a confident and wrong conclusion. The connected history explains the outcome, and the gap table below shows where each missing piece lives.

Visual briefFull-size diagram
A single shipment record shows four blank fields (claim filed, carrier paid, shortfall reason, days to resolve) that fill in as context pieces slide up from the carrier portal, the ERP and the AP memo: $6,200 claimed, $4,000 paid, $2,200 written off and 143 days.
Illustrative. The warehouse record is accurate but silent about the money until carrier and finance context is added.

This comparison is part of the shipment-to-credit-resolution guide. Here the same Illustrative case is read three times: as a warehouse row, as a ledger row, and as one joined history.

Before: the warehouse export row on its own

A fictional 410-person specialty food distributor ships nine handling units to a grocery chain under shipment S-5532. The carrier moves them on two PRO numbers. One unit is crushed in transit, and the consignee notes the damage on the delivery receipt and keeps only the sound goods.

What the warehouse export says about S-5532:

FieldValue in the export
ShipmentS-5532, nine units, shipped March 3
ScansNine units scanned out at the dock
StatusShipped
ExceptionsNone recorded on the warehouse side
ValueNot held

A reader of this row concludes that the shipment went out complete and nothing happened afterward. That is accurate for the dock and silent about everything after it. The warehouse system's job ended when the trailer doors closed, so it holds no delivery receipt, no claim and no money. Nothing in the row is wrong; the row simply stops before the story starts.

Before, the other way: the ledger export on its own

Now the finance view of the same case, from the ERP.

FieldValue in the export
Claim receivable$6,200 booked April 9
Credit received$4,000 posted August 30
Write-off$2,200 on September 12, memo "carrier claim balance"
Shipment referenceNone
Carrier claim numberTyped on the credit, not on the receivable

A reader of this row concludes that a carrier underpaid a claim by about a third and finance absorbed it. Which shipment, which unit, whether the carrier was right to pay less: none of that is in the ledger. A reviewer cannot tell whether the $2,200 reflects a weak claim, a missed deadline or a carrier that settled only one part of a split load.

After: the same case with carrier and finance context restored

Joined through the bill of lading (BOL) on the claim and the carrier claim number on the credit, the case reads as one history (Illustrative).

DateSourceWhat it adds
March 3Warehouse systemNine units shipped under S-5532
March 4Carrier portalLoad split across PRO numbers P-81 and P-82
March 6Carrier portalDelivery receipt on P-82 notes one crushed unit; consignee accepts the rest
April 9Carrier portal and ERP$6,200 claim filed against the BOL; receivable booked
August 30Carrier remittance and ERPCarrier pays $4,000 against P-82 only, citing its own claim number
September 12ERP and AP notes$2,200 written off; AP notes say the carrier treated freight charges on P-81 as outside the claim

Now the outcome has a cause. The carrier settled against the half of the split that carried the damaged unit, and the shortfall reflects a disagreement over what the claim covered. Resolution took 143 days from claim to credit. That is past the 120-day mark at which carrier claim regulations require a carrier to have paid, declined or made a firm offer, or else to have sent a written status explaining the delay, and to repeat that status every 60 days. Whether those status letters exist is itself a question for the claims lead. The filing side runs long too: a carrier may not set a claim-filing period shorter than 9 months, so a claim can be opened well after the warehouse has archived the shipment.

The gap table: what each export loses and where it lives

Question a reviewer would askWarehouse export aloneLedger export aloneWhere the context lives
What shipped, and when?YesNoWarehouse system
Which unit was damaged?NoNoDelivery receipt and carrier exception record
How was the load split?NoNoCarrier portal: PRO numbers listed against the BOL
Was a claim filed, and for how much?NoYes: $6,200Carrier portal and ERP receivable
What did the carrier pay, against what?NoPartly: $4,000, no shipmentCarrier remittance
Why was $2,200 written off?NoOnly a generic memoAP notes, claim correspondence or a coded reason field
How long did resolution take?NoPartly: booking to creditCarrier portal claim dates plus ERP posting dates
Did the carrier send status letters?NoNoClaims mailbox or portal correspondence

Two rows explain most lost context. The split row matters because the carrier pays against PROs while the shipper files against the shipment or BOL. The write-off row matters because the reason is often typed once, by one person, in a place no export reaches. The record chain names the key that would carry each piece, and the completeness checklist scores whether a company's history has it.

Describing the gap without opening a claim file

A partner does not need any of the rows above to describe a company's position. Ask each owner which columns of the gap table their system can fill, and from which year:

  • The warehouse operations manager: since when does the system hold the BOL beside each shipment ID?
  • The transportation or claims lead: does the portal list every PRO against the BOL, and are delivery receipts and status letters kept?
  • The AP or AR manager: is the carrier claim number recorded on credits, and is the write-off reason a coded field?

Answers such as "PRO lists from 2020, coded write-off reasons from 2023, delivery receipts unknown before 2021" are enough. The invoice side of carrier disputes is covered under freight audit exceptions, the reports that often start a claim under OS&D freight records, and the finance handling under AP exception handling and AR dispute resolution.

The company still has to meet the baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact: the CEO (in an owner-run company, usually the owner), with the CFO or COO involved, since the history spans warehouse, transportation and finance. 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. Unknown until SourceX reviews it: what carrier and customer contracts allow, how names and amounts would be de-identified, and what a buyer would want. Partners never handle the 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 your client's owners can say which columns of the gap table their systems fill, and from when, register as a partner, check who qualifies and read the terms before you make 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

Is a single-system export worthless?

No. A long, clean warehouse or finance history is still a record of real operations. The point is to describe honestly which questions it can answer on its own and which need context from another system.

Should the partner ask for the export to compare?

No. The owner of each system can say which fields exist and from which year. That description is enough for an introduction, and the records themselves stay inside the company.

Which missing context matters most?

Usually the reason for any shortfall between what was claimed and what was paid. Without it, the outcome is a number with no cause, which is the part of the story a reviewer most wants.

Sources

  1. govinfo.gov/content/pkg/CFR-2001-title49-vol4/pdf/CFR-20…
  2. uscode.house.gov/us/usc/t49/s14706
  3. refer.sourcex.si/terms

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