# State repair evidence gaps: a gap analysis | SourceX

Canonical: https://refer.sourcex.si/questions/state-repair-evidence-gaps
Last updated: 2026-11-04

Billing repairs are hard to assess when one of six kinds of evidence is missing: a written target, stored before-and-after values, event history older than the billing tool keeps, proof the person making the change was allowed to, the product version that defined the plan at the time, and a check that the next invoice came out right. Time is usually the biggest gap. None ends the conversation; each changes how many repairs can be used.

This gap analysis is part of the guide to [state repair in an ordinary workflow](/guides/concept-state-repair), where a customer loses two features after a wrong plan change and a billing specialist restores them. Here the question is narrower: across a company's history of such fixes, which records would a review expect, which do companies usually keep, and how should an introducer describe the difference without overselling.

## The evidence a repair review looks for

A review treats each repair as three states and the steps between them. Six kinds of evidence let it rebuild those states without relying on anyone's memory.

| Expected evidence | Question it answers |
|---|---|
| Written target | What should the account have looked like? |
| Before-and-after values | What exactly did the error change, and what did the fix change back? |
| Event history beyond 30 days | Can older repairs be rebuilt, not only last month's? |
| Permission record | Was the person who made each change allowed to make it? |
| Plan or feature-list version | What did "Business plan" include on the date of the error? |
| Outcome check | Did the next invoice and the customer's access confirm the fix? |

Each one closes a different door to doubt. With all six, a reviewer can mark a repair pass or fail. With four or five, the repair is still informative but carries a stated uncertainty.

## Expected against usual: the gap table

The pattern below reflects how subscription billing stacks are commonly set up, not a survey of companies.

| Evidence | What companies usually keep | What usually goes missing | Effect on the review |
|---|---|---|---|
| Written target | Order forms for most new contracts | Order forms for older or renewed accounts | Restored state cannot be checked against an agreement |
| Before-and-after values | Recent change events with previous values | Values on fixes made directly in an admin screen | The repair's steps cannot be rebuilt |
| Event history | The billing tool's own retention window | Full events older than that window | Older repairs show only a summary |
| Permission record | The change itself and a user name | Whether that user held the right role, especially under a shared login | A breach cannot be told apart from an authorized fix |
| Plan version | Today's plan catalog | The feature list as it stood on past dates | "Six features" means different things on different dates |
| Outcome check | Ticket status "solved" | A comparison of the next invoice with the contract | A leftover proration may mean the fix was half done |

## The retention gap and the other four

**Time.** Stripe's support documentation says events from the last 30 days are fully available through the API and older events show only a summary. A repair from last year can be shown in full only if the company stored its own copy or wrote the values into a ticket. Stripe's entitlements guide recommends storing active entitlements in the company's own database; a company that followed it may hold a much longer feature history than the billing tool shows.

**No written target.** If the order form is missing, the "restored" state is just the state someone chose. It cannot be tested.

**Missing permissions.** The log shows a price change but not whether the person making it was allowed to. Repairs made under a shared admin login are the usual cause.

**Versions that moved.** The product's feature list changed between the error and the fix, so a reviewer cannot tell which features the customer was owed on each date without a dated catalog.

**Unproven outcome.** The account looks right, but nobody checked the next invoice. Stripe's guide to upgrades and downgrades says prorations are created by default when a price changes, so a correction can leave credits or charges behind unless someone confirms the invoice afterwards.

Field history inside CRM and ERP tools has its own retention rules; the companion guide to [state repair records in CRM and ERP systems](/guides/state-repair-training-data-enterprise) covers those.

## Ten repairs at a payroll software company (Illustrative)

**Illustrative and fictional.** A 300-person payroll software company fixes wrong plan and seat changes about 25 times a month. The introducer asks the head of billing operations one question per row: out of every ten repairs over the last three years, roughly how many keep this evidence?

| Evidence | Owner's estimate, out of 10 | Why it falls short |
|---|---|---|
| Written target | 9 | Contracts signed before 2022 sit in a shared drive, unlinked |
| Before-and-after values | 7 | Some fixes are made directly in the admin screen |
| Event history beyond 30 days | 3 | Internal event storage began only last year |
| Permission record | 6 | Two billing staff shared one admin login until 2024 |
| Plan version | 2 | The plan catalog is edited in place |
| Outcome check | 5 | Finance checks the next invoice only for accounts over a set size |

Read across, the strongest group is last year's repairs: targets, values and full events are mostly present there, and the gap sits in plan versions. That is a coherent, describable slice. The older repairs carry targets and ticket notes but little else, so they are better described as context than as checkable cases.

## Wording the gaps honestly

| Instead of | Say |
|---|---|
| "We keep everything." | "Full billing events from last year onward; summaries before that." |
| "Every repair is documented." | "About seven in ten fixes keep old and new values." |
| "Only authorized staff make changes." | "Named logins since 2024; one shared login before." |
| "We always verify." | "Finance checks the next invoice for larger accounts." |

Give years and rough shares, and note who gave each answer. A company that names its gaps reads as more credible than one that claims a perfect archive, and SourceX can scope a review around a known boundary.

## Who holds the missing pieces, and what stays unknown

Revenue operations usually holds order forms; a billing engineer knows event storage; support operations owns tickets; product management owns the plan catalog; finance owns invoice checks. Authority to discuss licensing normally rests with the CFO, COO or CEO.

Gaps do not change the company test: 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.

Unknown until SourceX reviews it: the real share of usable repairs, the de-identification needed, any vendor contract limits, and whether a buyer wants this task type. To rate a client before raising gaps at all, use the [state repair qualification scorecard](/questions/does-state-repair-data-qualify); for what a review asks the company to prepare, see the [state repair review packet](/resources/state-repair-review-packet). Portfolio teams already auditing subscriptions can pair this with [SaaS renewal management](/guides/saas-renewal-management-portfolio-companies), and the failure side of agents is covered in [why AI agents fail](/questions/why-ai-agents-fail).

## 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 can describe the gaps in years and shares, as above, [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms) before introducing the CFO or COO with that description attached.

## Sources

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