# Chargeback evidence trail completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/dispute-to-evidence-packet-completeness-checklist
Last updated: 2026-11-04

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.

It belongs to the [dispute-to-evidence-packet records guide](/guides/chain-dispute-to-evidence-packet). If you want to see what a gap looks like in a single case first, read the sibling [before-and-after walkthrough](/guides/dispute-to-evidence-packet-missing-context).

## 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

| # | Check | Metadata question | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1 | Coverage | Since which year are disputes retrievable, and in which tool? | Five or more years in one tool or a documented migration | Years exist but split across tools with a gap | Under two years, or unknown |
| 2 | Volume by reason | Can disputes be counted by reason category? | Counts by category available | Total count only | No count |
| 3 | Order linkage | Does every dispute carry the order number the warehouse uses? | Same order number in both systems | Different formats that a lookup can map | No shared key |
| 4 | Replacement link | When a replacement ships, where is the original order number stored? | Structured "replaces order" field | CRM note or agent memory | Not recorded |
| 5 | Contact timestamps | Can you see when a customer first contacted you, not just when the case closed? | Open date and each message time kept | Close date only | No contact history |
| 6 | Promise timestamps | Can you see the date a refund or replacement was promised? | Promise recorded with a date | Shipping date only | Neither |
| 7 | Delivery proof | For a disputed order, can tracking and delivery status be retrieved years later? | Tracking stored with shipment, retrievable | Tracking stored, carrier history expired | Not stored |
| 8 | Policy versions | Could you show the returns or delivery policy as it read on an order date? | Dated versions kept | Some archived copies | Current page only |
| 9 | Packets kept | Is each submitted packet saved and linked to its dispute ID? | Saved and linked | Saved in a drive without IDs | Not kept |
| 10 | Outcomes | Is won, lost or accepted recorded against every dispute? | Recorded for all | Recorded for some years | Not 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.

| # | Check | Answer heard | Mark | Points |
|---|---|---|---|---|
| 1 | Coverage | Disputes in one tool since 2018 | Pass | 2 |
| 2 | Volume by reason | Counts by category in the tool's reports | Pass | 2 |
| 3 | Order linkage | Same order number everywhere | Pass | 2 |
| 4 | Replacement link | Agents type the original order in the case note | Partial | 1 |
| 5 | Contact timestamps | Every message time kept in the helpdesk | Pass | 2 |
| 6 | Promise timestamps | Only the replacement ship date | Partial | 1 |
| 7 | Delivery proof | Tracking stored; carrier history older than two years not retrievable | Partial | 1 |
| 8 | Policy versions | Current policy page only | Fail | 0 |
| 9 | Packets kept | Saved in a shared drive by dispute ID since 2020 | Pass | 2 |
| 10 | Outcomes | Recorded for every dispute | Pass | 2 |
| All | Total | Ten checks scored | Sum | 15 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](/data-types/accounts-receivable-dispute-resolution-process); for how long support history is typically kept, see [how long to keep support tickets](/questions/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](/tools/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](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) 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](/register), confirm the basics on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the CEO.

## Sources

- https://refer.sourcex.si/terms
- https://docs.stripe.com/disputes/responding
- https://docs.stripe.com/disputes/best-practices
- https://docs.stripe.com/disputes/reason-codes-defense-requirements
