# State repair review packet: contents list | SourceX

Canonical: https://refer.sourcex.si/resources/state-repair-review-packet
Last updated: 2026-11-04

A state repair review packet is seven short documents, prepared by the company in this order: a task statement, a note on where the intended state lives, the signals that show the broken state, the actions staff are allowed to take, an acceptance check written in advance, volume and span counts, and rights notes. Each describes records the company holds; none contains a customer account. The packet lets SourceX judge one class of repairs before any agreement.

The packet belongs to the guide to [state repair in an ordinary workflow](/guides/concept-state-repair), which follows a subscription moved to the wrong plan and restored. Partners do not build or hold it. It is set out here so an introducer can tell a billing or finance lead, accurately, what preparing for a review involves.

## The contents list, in assembly order

The order runs from what the job is, through how a broken account is recognized and fixed, to how each repair is judged and who may license the records.

| Order | Document | What it shows | Prepared by | Typical length |
|---|---|---|---|---|
| 1 | Task statement | The repair job in one or two sentences | Billing operations lead | A paragraph |
| 2 | Target source note | Which system holds the intended plan, seats and term | Revenue operations | Half a page |
| 3 | Broken-state signals | The events and fields that reveal the error | Billing engineer | A short list |
| 4 | Allowed actions | What staff may change, and the limits that need approval | Finance controller | A short list |
| 5 | Acceptance check | The fixed pass-or-fail test for every repair | Finance and billing together | Four to six lines |
| 6 | Volume and span | Repairs per month, retention, migration dates | Billing engineer | A table |
| 7 | Rights and sensitivity notes | Personal data present, contract limits | Counsel or the CFO | Half a page |

The acceptance check sits fifth on purpose. It can only be written once the target, the signals and the allowed actions are agreed, and the counts in document 6 are then counts of repairs that could be tested against it.

## Each document, filled in for one repair class (Illustrative)

**Illustrative and fictional.** A 210-person project-management software company sells a Team plan, priced per seat, with seven features. Its most common repair: a customer's subscription moved to the wrong plan or seat count during an upgrade or a billing-cycle change.

**1. Task statement.** "Restore a subscription to the plan, quantity and features on the signed order form, and clear any charges or credits the error created."

**2. Target source note.** "The signed order form is stored in the CRM on the account record. For accounts opened before 2021, the contract sits in the contract repository and is linked by account number." A note like this is where the company decides which system is authoritative for each field; the live explainer on [what a system of record is](/questions/what-is-a-system-of-record) is useful background.

**3. Broken-state signals.** Subscription update events with previous values; entitlement summary events; a support ticket reporting lost access. Stripe's entitlements documentation describes an event sent whenever a customer's active entitlements change, which is the kind of signal this document names. Another is quantity: Stripe's guide notes that updating a price resets quantity to 1 unless the existing quantity is sent, so "quantity fell to 1" is a known signature of this error.

**4. Allowed actions.** Price and quantity correction; proration credit; goodwill credit up to a set limit; escalation to the finance controller above it.

**5. Acceptance check.** Written out in the next section.

**6. Volume and span.** About 18 repairs a month; full events kept by the billing tool for 30 days, which matches what Stripe's support documentation describes, with internal event storage since March 2023; one billing migration in 2020.

**7. Rights and sensitivity notes.** Customer names and admin contacts, contracted prices, employee identifiers in ticket notes; reseller agreements for one region to be checked.

## The acceptance check, applied to two repairs (Illustrative)

A repair passes only if all five conditions hold:

1. Active features equal the order form.
2. Subscription quantity equals contracted seats.
3. The next invoice preview equals contracted price times quantity, with no stray proration.
4. The customer's admin confirmed access in the ticket.
5. The person who approved any credit is recorded.

Two fictional repairs from the same company, each for a 25-seat Team account at $36 a seat:

| Condition | Repair A | Repair B |
|---|---|---|
| Features match order form | Pass: seven of seven | Pass: seven of seven |
| Quantity matches contract | Pass: 25 seats | Pass: 25 seats |
| Invoice preview correct | Pass: $900, no proration left | Fail: a stray $310 proration credit still reduces the $900 |
| Customer confirmed access | Pass | Pass |
| Credit approver recorded | Not applicable: no credit | Pass: controller named for a $50 goodwill credit |
| Result | Passes | Fails: repair half done |

Repair B looks fixed to the customer and to support. Only the invoice condition catches it. Stripe's documentation says prorations are created by default on a price change, which is why the check names the invoice rather than the account screen. The check is what turns the packet from a description into something a buyer can test, case by case.

## What stays out of the packet

The packet carries descriptions and counts. It does not carry:

- customer names, account numbers or contract prices for real accounts;
- exports, screenshots or log extracts;
- employee names, beyond the roles that prepare each document;
- any promise about how many repairs will pass.

Record-level work comes later, under SourceX's agreement with the company, after de-identification and rights review. If the owner wants to prepare for that conversation, the list of [questions to ask before licensing company data](/resources/questions-to-ask-before-licensing-company-data) is a good start.

## After the packet: what review settles

SourceX uses the packet to decide whether a review is worth scoping and what it should test. The review then settles what the packet cannot: the real share of passing repairs, the de-identification needed, vendor and reseller contract limits, and whether a buyer wants this task type.

The company itself must meet the program basics: 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.

Before a packet is worth discussing, a client should rate well on the [state repair qualification scorecard](/questions/does-state-repair-data-qualify); the [state repair evidence gaps](/questions/state-repair-evidence-gaps) page shows how to describe what document 6 will reveal. Portfolio teams reviewing subscriptions can pair this with [SaaS renewal management](/guides/saas-renewal-management-portfolio-companies).

## 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 the billing lead says the company could write documents 1 to 7 from what it already knows, [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://docs.stripe.com/billing/subscriptions/upgrade-downgrade
- https://support.stripe.com/questions/stripe-event-retention-period
- https://refer.sourcex.si/terms
