Dispute-to-evidence-packet completeness scorecard: ten metadata checks with pass, partial and fail marks

Short answer

A dispute-to-evidence-packet trail breaks in four places: identifiers that do not carry from one system to the next, timestamps that record when a case closed rather than when a promise was made, policies kept only in their current version, and outcomes stored without the packet that produced them. The worst single break is delivery proof that covers a replacement order instead of the disputed one. The scorecard below lets you mark each check pass, partial or fail from a conversation, without seeing a record.

Visual briefFull-size diagram
Ten dispute-trail checks, from coverage and order linkage to packets kept and outcomes, tick pass, partial or fail while a vertical meter rises to 15 of 20 points.
Illustrative scoring for a fictional retailer. A score describes the trail; it does not predict acceptance.

It belongs to the dispute-to-evidence-packet records guide. If you want to see what a gap looks like in a single case first, read the sibling before-and-after walkthrough.

How to use the scorecard in one call

Book 30 to 45 minutes with whoever builds dispute responses, plus the customer service and warehouse leads if possible. Ask each check's question as written. Mark it from the answer, not from what you hope is true. Write "unknown" in your notes when nobody can answer; unknown scores as fail until someone confirms otherwise.

Each mark is worth points: pass 2, partial 1, fail 0. Ten checks give a maximum of 20. The total is a description of the trail, not a forecast of anything.

The ten checks, each answerable from metadata

#CheckMetadata questionPassPartialFail
1CoverageSince which year are disputes retrievable, and in which tool?Five or more years in one tool or a documented migrationYears exist but split across tools with a gapUnder two years, or unknown
2Volume by reasonCan disputes be counted by reason category?Counts by category availableTotal count onlyNo count
3Order linkageDoes every dispute carry the order number the warehouse uses?Same order number in both systemsDifferent formats that a lookup can mapNo shared key
4Replacement linkWhen a replacement ships, where is the original order number stored?Structured "replaces order" fieldCRM note or agent memoryNot recorded
5Contact timestampsCan you see when a customer first contacted you, not just when the case closed?Open date and each message time keptClose date onlyNo contact history
6Promise timestampsCan you see the date a refund or replacement was promised?Promise recorded with a dateShipping date onlyNeither
7Delivery proofFor a disputed order, can tracking and delivery status be retrieved years later?Tracking stored with shipment, retrievableTracking stored, carrier history expiredNot stored
8Policy versionsCould you show the returns or delivery policy as it read on an order date?Dated versions keptSome archived copiesCurrent page only
9Packets keptIs each submitted packet saved and linked to its dispute ID?Saved and linkedSaved in a drive without IDsNot kept
10OutcomesIs won, lost or accepted recorded against every dispute?Recorded for allRecorded for some yearsNot recorded

Check 9 matters more than it looks. Stripe's documentation says a merchant gets one opportunity to respond and cannot edit the response afterward, so the packet as sent is the only record of what the merchant argued. A company that keeps outcomes but discards packets knows the score without the play.

Check 7 tests the evidence Stripe's best-practice guidance highlights for physical goods: proof of shipment and delivery with the full address, arranged chronologically. Check 8 tests whether the company could show its terms as they read on the order date. If the company cannot retrieve either years later, the trail ends before the reasoning does.

The replacement-order test, scored three ways

Check 4 deserves its own conversation. Ask: "If a customer disputes an order you already replaced, how does your team build the packet?" The answer usually falls into one of three groups.

  1. Structured link (pass). The replacement carries a field that points to the original order, and the packet tool follows it. The trail holds from the year the field was introduced; note that year.
  2. A person who knows (partial). A payments specialist searches the CRM, finds the note and writes the explanation. The records exist, but the reasoning lives in one team's habits. This is common, and saying so honestly helps SourceX scope the review.
  3. No link (fail). Replacements are created as fresh orders and nobody connects them. The company may still hold years of disputes and outcomes, but the delivery side of the chain is unreliable.

All three can be worth an introduction. The mark changes how you describe the records, not whether the company may qualify.

A completed scorecard (Illustrative)

A fictional 410-person home appliance retailer, scored in one call with its payments lead and customer service manager. All values are invented.

#CheckAnswer heardMarkPoints
1CoverageDisputes in one tool since 2018Pass2
2Volume by reasonCounts by category in the tool's reportsPass2
3Order linkageSame order number everywherePass2
4Replacement linkAgents type the original order in the case notePartial1
5Contact timestampsEvery message time kept in the helpdeskPass2
6Promise timestampsOnly the replacement ship datePartial1
7Delivery proofTracking stored; carrier history older than two years not retrievablePartial1
8Policy versionsCurrent policy page onlyFail0
9Packets keptSaved in a shared drive by dispute ID since 2020Pass2
10OutcomesRecorded for every disputePass2
AllTotalTen checks scoredSum15 of 20

How a partner would summarize it: "Eight years of disputes with outcomes and packets from 2020; replacements linked by CRM note only; no policy history." That sentence is more useful to SourceX than the number. For the B2B version of the same exercise, see accounts receivable dispute resolution records; for how long support history is typically kept, see how long to keep support tickets.

Before the introduction: owners, authority and what stays open

The scorecard names the system owners for you: payments or finance for checks 1, 2, 9 and 10; customer service for checks 4 to 6; operations for check 7; ecommerce or legal for check 8. None of them is the person who can authorize a licensing discussion. That is the CEO (in an owner-run company, the owner), though the CFO or COO may sponsor the introduction.

Confirm the company baseline: 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. The company fit checker covers the same basics.

What stays unknown until SourceX reviews it: what processor, card network and carrier terms allow, how customer details would be removed, which years a buyer wants and what the company would be paid. Partners never ask for or handle dispute rows, packets or case notes. If a system change is planned, the ERP replacement handoff checklist helps time the conversation before old records are archived.

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.

Once you can describe the company's trail in one honest sentence from its scorecard, register as a partner, confirm the basics on who qualifies and read the program terms before you introduce the CEO.

  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

What score is good enough to introduce a company?

There is no threshold. The scorecard tells you how to describe the trail honestly, not whether SourceX or a buyer will want it. A low score with a clear explanation is a better introduction than a high score that turns out to be guessed.

Who should answer the scorecard questions?

Usually the payments or chargebacks lead for the dispute rows, the customer service lead for CRM rows and an operations manager for delivery rows. One conversation with all three is ideal; none of them needs to open a record.

Do I send the completed scorecard to SourceX?

You can summarize it in your introduction in your own words, with the sponsor's agreement. It should contain counts, years, systems and marks only, never order numbers, customer names or packet contents.

Sources

  1. refer.sourcex.si/terms
  2. docs.stripe.com/disputes/responding
  3. docs.stripe.com/disputes/best-practices
  4. docs.stripe.com/disputes/reason-codes-defense-requirements

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