# Usage correction trail completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/usage-to-revenue-correction-completeness-checklist
Last updated: 2026-11-04

A usage-to-revenue-correction trail breaks in predictable places: credit notes and journals with no shared subscription or contract number, three dates (contract effective, billing change, posting period) that nobody records together, original usage overwritten by the correction, credits with no required reason, and corrections posted months after the usage they fix. The hardest case is a contract amendment whose effective date falls before billing could apply it. This scorecard marks each check pass, partial or fail without seeing a record.

It belongs to the [usage-to-revenue-correction records guide](/guides/chain-usage-to-revenue-correction). Fill in that guide's metadata packet first; then use these seven checks to judge how much of the trail a reviewer could actually follow.

## Marking rules for a billing correction trail

Each check is one question to the person who owns that part of the trail. Mark what you hear:

| Mark | Points | Meaning |
|---|---|---|
| Pass | 2 | The field or habit exists, and the owner can name the year it started |
| Partial | 1 | It exists for some years, some customers or some correction types, or relies on free text |
| Fail | 0 | It does not exist, or nobody can say; unknown counts as fail until confirmed |

Seven checks give 14 points. The total is shorthand. What you take into the introduction is one sentence per weak check saying which years it affects.

## Seven checks across coverage, linkage, dates, outcomes and gaps

| # | Dimension | Check | Question for the owner | Pass | Partial | Fail |
|---|---|---|---|---|---|---|
| 1 | Coverage | Years of usage and invoices | Since when are usage records and invoices retrievable in billing? | Five or more years, one system or documented migration | Years exist but an earlier billing tool was not migrated | Under two years, or unknown |
| 2 | Linkage | Shared identifier | Can you find the journal behind a 2023 usage credit? | Subscription or contract number in a structured journal field | Credit note number in memo text by convention | Customer name only |
| 3 | Timestamps | Three dates kept | When a contract changes mid-term, which dates does each system keep? | Effective date, billing change date and posting period all recorded and joinable | Two of the three | Only the billing change date |
| 4 | Gaps | Original usage preserved | When usage is wrong, is the original kept or replaced? | Adjustment recorded beside the original | Original in logs or tickets only | Deleted and re-added |
| 5 | Outcomes | Reason captured | Is a reason required on every usage credit? | Required reason code since a known year | Free text, sometimes blank | No reason recorded |
| 6 | Timestamps | Late corrections | Do usage credits ever post to a closed month, and how is that marked? | Later-period journals reference the original period | Accountant knows which ones | Indistinguishable from ordinary revenue changes |
| 7 | Linkage | Refund record | Which system is the record of a refund, and do the two agree? | One system of record, reconciled | Both, reconciled by hand | Unknown, or known gaps |

## Scoring a fictional usage-billed company (Illustrative)

A fictional 300-person observability software company bills usage monthly, collects through a payment gateway and closes its books in NetSuite. Answers and marks are invented.

| # | Check | Answer heard | Mark | Points |
|---|---|---|---|---|
| 1 | Years of usage and invoices | Billing since 2018, one system | Pass | 2 |
| 2 | Shared identifier | Subscription ID on journals since 2021, customer name before | Partial | 1 |
| 3 | Three dates kept | Effective date in the contract tool, billing date in billing, no join | Partial | 1 |
| 4 | Original usage preserved | Engineers delete and re-add; tickets record most cases | Partial | 1 |
| 5 | Reason captured | Reason code required on credit notes since 2022 | Pass | 2 |
| 6 | Late corrections | Journals in a closed month carry a "prior period" reference | Pass | 2 |
| 7 | Refund record | Webhook gap in 2020; nobody sure which refunds were missed | Fail | 0 |
| All | Total | Seven checks scored | Sum | 9 of 14 |

What the partner writes in the introduction: "Six years of usage billing; reason codes from 2022 and subscription IDs on journals from 2021; effective dates kept but not joined to billing; refund records uncertain for 2020." A reviewer can plan from that sentence.

The companion [record-chain guide](/guides/usage-to-revenue-correction-record-linkage) shows the key that crosses each link, and the [before-and-after comparison](/guides/usage-to-revenue-correction-missing-context) shows what a reader gets wrong when only one export is available.

## The effective-date test, scored

Check 3 carries the case that matters most. Ask one question: "When a customer signs an amendment that takes effect before billing can apply it, where do you record the difference?"

Chargebee permits backdating only within the current billing term and does not backdate the invoice, so an amendment entered after the term rolls over cannot correct the closed period. The difference has to travel as a credit. Three answers are common, and each maps to a mark.

1. **A credit note with a reason code and the contract number (pass).** The trail holds from the year this became routine. Note that year.
2. **A credit note with free text (partial).** The trail exists but needs a person to interpret each correction.
3. **A spreadsheet the controller keeps (fail for check 3, partial for check 5 at best).** The reasoning lives outside every system, which SourceX's review would need to account for.

On the ledger side, NetSuite reversing entries are exact opposites of the original journal and stay linked to it. A correction posted as a fresh journal in a later period has no such link, which is what check 6 tests.

### Why check 4 can fail where owners expect a pass

Two vendor behaviors make overwritten usage common. Chargebee's backdating documentation notes that when a subscription change is backdated, metered usage recorded after the backdated date is deleted. Stripe's meter documentation says a meter event can be canceled only within 24 hours of being sent, and canceling usage already on a finalized invoice does not change that invoice. Either way, the billing tool may no longer show what the meter originally said. The anomaly survives only in a log, a ticket or a spreadsheet, so ask where.

### Why check 7 needs a direct question

Chargebee's Stripe gateway documentation says Stripe webhooks are needed for refunds and disputes. A period of misconfigured webhooks leaves refunds in the payment processor with no matching update in billing. Owners usually know whether that happened; they rarely volunteer it.

## Before you introduce: owners and open questions

The checks name the owners: billing operations for usage, credits and refunds; the revenue accountant or controller for journals and closed-period corrections; sales operations or legal for amendments. The person who can authorize a licensing conversation is above them: the CEO, who in an owner-run company is usually the owner. A [portfolio review handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-a-portfolio-review) helps if the company sits in an investor's portfolio.

Confirm the company baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records 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) runs the same basics.

Unknown until SourceX reviews it: what customer contracts allow, how customer names and amounts would be removed, which years a buyer wants, and what the company would be paid and how (the [one-time payment versus royalties comparison](/compare/one-time-payment-vs-royalties-data-licensing) covers the general trade-off). If the conversation started as a [revenue leakage audit](/guides/revenue-leakage-audit), keep the introduction separate from that engagement.

## 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 the scorecard gives you a one-sentence account of which correction years hold together, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the finance lead.

## Sources

- https://refer.sourcex.si/terms
- https://www.chargebee.com/docs/billing/2.0/subscriptions/subscriptions-actions-backdating
- https://docs.stripe.com/billing/subscriptions/usage-based/meters/configure
- https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/stripe
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1471552.html
