Do a client's state repair records qualify? A billing repair scorecard for introducers

Short answer

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.

Visual briefFull-size diagram
A half-circle gauge with weak, borderline and strong zones; as eight criteria are ticked on the right, the needle swings and settles in the strong zone for a fictional 260-person HR software company, with the two must-have criteria marked.
Illustrative rating for a fictional HR software company's billing repairs. A conversation aid, not SourceX's review.

This scorecard is part of the guide to state repair in an ordinary workflow, 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.

CriterionStrongBorderlineWeakWho usually answers
1. Company size50 or more full-time employees at peak, contractors excludedClose to 50, or many contractorsClearly under 50 full-timeOwner or HR
2. History and event retentionSeveral years of billing events copied into the company's own databaseCopies started recently, or a billing migration cut historyOnly what the billing tool keepsBilling engineer or finance systems lead
3. Rights to licenseThe company owns its billing, CRM and support recordsVendor or customer contract terms not yet checkedRecords belong to a client or resellerCFO or counsel
4. English share (outside the U.S., Canada and the EU)At least 70% of tickets, notes and order forms in EnglishMixed, share unknownMostly another languageSupport director
5. Repair volumeA named routine fix, with a rough monthly countRepairs happen, but nobody counts themToo rare to describeBilling operations lead
6. Written target (must-have)Signed order form or contract stored in the CRM for each accountOrder forms for new deals onlyIntended state lives in people's memoryRevenue operations
7. Before-and-after values (must-have)Change events or field history keep previous and new valuesTicket notes list old and new values by handOnly the current state survivesBilling engineer
8. Ticket-to-event linkageEach repair ticket names the account or subscription IDIDs sometimes, matched by date otherwiseRepairs done with no ticketSupport 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.

ResultRuleWhat to do
Strong fitCriteria 6 and 7 strong, nothing weakIntroduce the CFO or COO
Borderline fitCriteria 6 and 7 at least borderline, one or two others weak or borderlineIntroduce, naming the weak criteria plainly
Weak fitCriterion 6 or 7 weak, or criterion 1 or 3 weakHold; 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 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.

Criterion260-person HR software company140-person managed print provider90-person reseller in India
1. Company sizeStrongStrongStrong
2. History and retentionStrong: events copied since 2021Borderline: billing migration in 2024Weak: tool defaults only
3. RightsStrongStrongWeak: reseller contracts unclear
4. English shareStrong (U.S.)Strong (EU, English contracts)Borderline: share unknown
5. Repair volumeStrong: about 30 plan-change fixes a monthBorderline: not countedWeak
6. Written targetStrong: order form on every accountStrongBorderline: new deals only
7. Before-and-after valuesStrong: field history keptBorderline: ticket notes onlyWeak
8. LinkageBorderline: IDs on most ticketsStrongWeak
ResultStrong fitBorderline fitWeak 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 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, and the wider approach in the 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; other record families are listed under 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, check who qualifies, and read the terms before introducing the CFO or COO.

  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

Why are only two criteria must-haves?

Without a written target, nobody can say what the account should have looked like; without before and after values, nobody can say what the repair changed. Weakness elsewhere reduces how many repairs are usable, but these two decide whether any repair can be checked at all.

Does a company that does not use Stripe qualify?

Billing platform does not matter. Stripe is used here because its public documentation describes events, entitlements and retention clearly. The same questions apply to any billing, ERP or provisioning system.

Should I ask the billing team to export a sample repair?

No. Partners never request or handle customer records. Ask whether the fields exist and how far back they go, and leave record review to SourceX under an agreement with the company.

Sources

  1. docs.stripe.com/billing/entitlements
  2. support.stripe.com/questions/stripe-event-retention-period
  3. docs.stripe.com/billing/subscriptions/upgrade-downgrade
  4. 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