# State repair records: qualification scorecard | SourceX

Canonical: https://refer.sourcex.si/questions/does-state-repair-data-qualify
Last updated: 2026-11-04

Rate a client's billing repair records on eight criteria: headcount, operating history and event retention, rights, English share where it applies, how often repairs happen, whether the intended state is written down outside the system that broke, whether before and after values are stored, and whether tickets link to the change events. Two are must-haves: the written target and the before-and-after values. Both strong and nothing weak means a strong fit.

This scorecard is part of the guide to [state repair in an ordinary workflow](/guides/concept-state-repair), which follows one subscription moved to the wrong plan and put back. That guide explains what a repair record is. This page is a rating sheet for a short call with the head of billing operations or the finance lead, kept to answers rather than files.

## Eight criteria, three possible answers each

Mark the answer closest to what the client says. The last column names who usually knows.

| Criterion | Strong | Borderline | Weak | Who usually answers |
|---|---|---|---|---|
| 1. Company size | 50 or more full-time employees at peak, contractors excluded | Close to 50, or many contractors | Clearly under 50 full-time | Owner or HR |
| 2. History and event retention | Several years of billing events copied into the company's own database | Copies started recently, or a billing migration cut history | Only what the billing tool keeps | Billing engineer or finance systems lead |
| 3. Rights to license | The company owns its billing, CRM and support records | Vendor or customer contract terms not yet checked | Records belong to a client or reseller | CFO or counsel |
| 4. English share (outside the U.S., Canada and the EU) | At least 70% of tickets, notes and order forms in English | Mixed, share unknown | Mostly another language | Support director |
| 5. Repair volume | A named routine fix, with a rough monthly count | Repairs happen, but nobody counts them | Too rare to describe | Billing operations lead |
| 6. Written target (must-have) | Signed order form or contract stored in the CRM for each account | Order forms for new deals only | Intended state lives in people's memory | Revenue operations |
| 7. Before-and-after values (must-have) | Change events or field history keep previous and new values | Ticket notes list old and new values by hand | Only the current state survives | Billing engineer |
| 8. Ticket-to-event linkage | Each repair ticket names the account or subscription ID | IDs sometimes, matched by date otherwise | Repairs done with no ticket | Support operations |

Criterion 4 applies only outside the U.S., Canada and the EU; elsewhere, mark it strong. 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.

## How the two must-haves decide the result

Read criteria 6 and 7 first, then the rest.

| Result | Rule | What to do |
|---|---|---|
| Strong fit | Criteria 6 and 7 strong, nothing weak | Introduce the CFO or COO |
| Borderline fit | Criteria 6 and 7 at least borderline, one or two others weak or borderline | Introduce, naming the weak criteria plainly |
| Weak fit | Criterion 6 or 7 weak, or criterion 1 or 3 weak | Hold; repairs cannot yet be checked or licensed |

The reasoning is simple. A repair is evidence only if a reviewer can compare three states: intended, broken and restored. The order form supplies the first. The stored previous and new values supply the other two. Without either, a repair is a story told after the fact.

Criterion 2 matters more than it looks. Stripe's support documentation says events from the last 30 days are fully available through the API, while older events show only a summary. A company that relied on the billing tool alone can prove last month's repairs in detail and little before that. Stripe's entitlements guide recommends storing active entitlements in the company's own database, and a team that followed that advice may hold years of feature history without realizing it. The gap guide on [record gaps that make state repair hard to assess](/questions/state-repair-evidence-gaps) goes through retention and the other weak points in detail.

## Three billing teams, rated from conversation (Illustrative)

All three companies are fictional; each rating came from answers, not files.

| Criterion | 260-person HR software company | 140-person managed print provider | 90-person reseller in India |
|---|---|---|---|
| 1. Company size | Strong | Strong | Strong |
| 2. History and retention | Strong: events copied since 2021 | Borderline: billing migration in 2024 | Weak: tool defaults only |
| 3. Rights | Strong | Strong | Weak: reseller contracts unclear |
| 4. English share | Strong (U.S.) | Strong (EU, English contracts) | Borderline: share unknown |
| 5. Repair volume | Strong: about 30 plan-change fixes a month | Borderline: not counted | Weak |
| 6. Written target | Strong: order form on every account | Strong | Borderline: new deals only |
| 7. Before-and-after values | Strong: field history kept | Borderline: ticket notes only | Weak |
| 8. Linkage | Borderline: IDs on most tickets | Strong | Weak |
| Result | Strong fit | Borderline fit | Weak fit |

The managed print provider is the instructive case. Its repairs are well documented by people rather than systems: technicians write old and new values into tickets. That keeps it borderline rather than weak, and its migration date tells SourceX exactly where the reliable history begins.

## The five questions behind the ratings

Five questions, asked of the billing or finance lead, fill most of the scorecard.

1. **Which kinds of mistaken change happen often enough to have a routine fix?** Wrong plan, wrong seat count, a missed discount, access applied to the wrong account. Ask for a rough monthly count (criterion 5).
2. **Is the intended state written down somewhere other than the system that broke?** An order form in the CRM gives the repair a target that does not depend on memory (criterion 6). The live explainer on [what a system of record is](/questions/what-is-a-system-of-record) helps when the answer is "it depends which field."
3. **Are before and after values stored for each change?** Change events with previous values, a field history, or a ticket note that lists both (criterion 7). Some changes create collateral effects worth asking about: Stripe's documentation says updating a subscription's price resets the quantity to 1 unless the existing quantity is included, and prorations are created by default.
4. **How long are those events kept, and are copies stored internally?** This decides how many repairs are still provable (criterion 2).
5. **Who owns the billing and support records, and who can authorize a licensing discussion?** The CFO or COO usually owns the records; the CEO authorizes (criterion 3).

If question 2 or 3 gets a "no," the company may still hold useful workflow data, just not repair records a buyer would test.

## Who answers, and what a score leaves open

The billing operations lead answers criteria 5 to 8; a billing engineer knows retention; the CFO or COO owns the rights question, and the CEO can authorize a licensing discussion. The company-level basics are covered in the [company qualification checklist](/resources/company-qualification-checklist), and the wider approach in the [business introducer guide to operational data licensing](/guides/a-business-introducer-guide-to-operational-data-licensing).

A score cannot show how many repairs pass an acceptance check, how customer names and pricing will be de-identified, whether billing or support vendor terms limit use, or whether any buyer wants this task type. SourceX measures those in review with the company. Discovery stays at metadata level: which billing tool, roughly how many repairs a month, how far back, and who owns them. What the company prepares once a review starts is set out in the [state repair review packet](/resources/state-repair-review-packet); other record families are listed under [data types](/data-types).

## 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 a client scores strong on the written target and the before-and-after values and weak on nothing, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before introducing the CFO or COO.

## Sources

- https://docs.stripe.com/billing/entitlements
- https://support.stripe.com/questions/stripe-event-retention-period
- https://docs.stripe.com/billing/subscriptions/upgrade-downgrade
- https://refer.sourcex.si/terms
