Usage-to-revenue-correction completeness scorecard: seven pass, partial or fail checks for billing advisors

Short answer

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.

Visual briefFull-size diagram
Seven usage-correction checks tick pass, partial or fail down the right while a stacked meter on the left adds one block per point and stops at 9 of 14.
Illustrative scoring for a fictional usage-billed software company. The score describes the trail, not its value.

It belongs to the usage-to-revenue-correction records guide. 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:

MarkPointsMeaning
Pass2The field or habit exists, and the owner can name the year it started
Partial1It exists for some years, some customers or some correction types, or relies on free text
Fail0It 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

#DimensionCheckQuestion for the ownerPassPartialFail
1CoverageYears of usage and invoicesSince when are usage records and invoices retrievable in billing?Five or more years, one system or documented migrationYears exist but an earlier billing tool was not migratedUnder two years, or unknown
2LinkageShared identifierCan you find the journal behind a 2023 usage credit?Subscription or contract number in a structured journal fieldCredit note number in memo text by conventionCustomer name only
3TimestampsThree dates keptWhen a contract changes mid-term, which dates does each system keep?Effective date, billing change date and posting period all recorded and joinableTwo of the threeOnly the billing change date
4GapsOriginal usage preservedWhen usage is wrong, is the original kept or replaced?Adjustment recorded beside the originalOriginal in logs or tickets onlyDeleted and re-added
5OutcomesReason capturedIs a reason required on every usage credit?Required reason code since a known yearFree text, sometimes blankNo reason recorded
6TimestampsLate correctionsDo usage credits ever post to a closed month, and how is that marked?Later-period journals reference the original periodAccountant knows which onesIndistinguishable from ordinary revenue changes
7LinkageRefund recordWhich system is the record of a refund, and do the two agree?One system of record, reconciledBoth, reconciled by handUnknown, 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.

#CheckAnswer heardMarkPoints
1Years of usage and invoicesBilling since 2018, one systemPass2
2Shared identifierSubscription ID on journals since 2021, customer name beforePartial1
3Three dates keptEffective date in the contract tool, billing date in billing, no joinPartial1
4Original usage preservedEngineers delete and re-add; tickets record most casesPartial1
5Reason capturedReason code required on credit notes since 2022Pass2
6Late correctionsJournals in a closed month carry a "prior period" referencePass2
7Refund recordWebhook gap in 2020; nobody sure which refunds were missedFail0
AllTotalSeven checks scoredSum9 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 shows the key that crosses each link, and the before-and-after comparison 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 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 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 covers the general trade-off). If the conversation started as a 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, check who qualifies and read the program terms before you introduce the finance lead.

  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

What total is good enough to introduce a company?

There is no threshold. A company scoring 5 of 14 with clear notes on which years hold together is a useful introduction. The scorecard shapes how you describe the records; SourceX's review decides scope.

Who answers the seven checks?

Usually the billing operations lead for checks 1, 3, 4 and 5, the revenue accountant or controller for checks 2 and 6, and sales operations or legal for the contract side of check 3. One 30-minute call with two of them is often enough.

Should I score from documents the client sends me?

No. Score from what the owners tell you. Partners do not receive invoices, credit notes, journals or contracts; counts, years and field names are enough.

Sources

  1. refer.sourcex.si/terms
  2. chargebee.com/docs/billing/2.0/subscriptions/subscriptions…
  3. docs.stripe.com/billing/subscriptions/usage-based/meters/con…
  4. chargebee.com/docs/payments/2.0/payment-gateways-and-confi…
  5. docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/sectio…

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