This system map is part of the usage billing corrections guide. The guide explains what a correction is and which records prove each part of it. This page does one job: it shows where each record is stored, which identifier carries the case from one system to the next, and what a fully joined case looks like.
Five systems, one correction
A usage billing correction rarely lives in one product. A typical mid-size software company spreads it across:
- The billing engine, which receives meter events, rates them against the price in force and produces invoices and credit notes.
- The CRM, where account teams record contract amendments, plan upgrades and negotiated terms.
- The support desk, where the customer's finance team raises the dispute.
- An approval tool or inbox, where finance operations agrees the corrected amount. In many companies this is still email or chat.
- The general ledger, which receives the posted invoice and credit. It confirms the money moved but rarely explains why.
Each system has a different owner, so a cross-system history is also a question of who holds what. The cross-system data value guide explains why joined records across tools are worth more than any single export.
The system map: record, linking key and owner
| System | Record it holds | Key it must carry to join the next record | Usual owner |
|---|---|---|---|
| Billing engine | Meter events for each period | Subscription ID and billing period | Product engineering, billing operations |
| CRM | Contract amendment or plan change | Subscription ID or contract number shared with billing | Revenue operations |
| Billing engine | Invoice and its usage line | Invoice number and subscription ID | Billing operations |
| Support desk | Dispute case | Invoice number recorded on the case | Customer support |
| Approval tool or email | Credit approval with calculation | Case number in the approval | Finance operations head |
| Billing engine | Credit note | Case number or approval ID in metadata or memo | Billing operations |
| General ledger | Posted invoice and credit | Invoice and credit note numbers | Controller |
Two documented behaviors make the plan-change and credit rows matter. Stripe's documentation says that changing a subscription's price or quantity mid-period creates prorations by default, so a disputed proration points back to one specific subscription change. And once an invoice is finalized, most amounts cannot be edited; a credit note reduces it without voiding it and carries one of four reason codes plus a memo and optional internal metadata. The metadata field is where a case or approval reference can travel, if the company chose to put it there.
StripeOne fully joined case, key by key (Illustrative)
A fictional 180-person data API company bills monthly for requests above an allowance. All identifiers and events are invented.
| Hop | From | To | Key carried | Result |
|---|---|---|---|---|
| 1 | Meter events for SUB-0417, March | Invoice INV-2291 usage line | SUB-0417, March period | Joined by ID |
| 2 | CRM amendment AMD-0088 (plan upgrade raising the allowance, effective 12 March) | SUB-0417 plan change | Contract number on both | Joined by ID |
| 3 | INV-2291 | Support case CASE-5520 | Invoice number on the case | Joined by ID |
| 4 | CASE-5520 | Credit approval in finance inbox | Case number in subject line | Joined, but only by text search |
| 5 | Credit approval | Credit note CN-0093 against INV-2291 | Case number in credit note metadata | Joined by ID |
| 6 | CN-0093 | Ledger entry | Credit note number | Joined by ID |
What the joined case shows: the upgrade was signed in the CRM on 12 March, but the higher request allowance was not applied to the subscription until April, so March usage between the old and new allowance was billed as overage. The customer disputed, finance recalculated, approved a credit and recorded the case number in the credit note. Every hop but one joins by an identifier. Hop 4 depends on someone having typed the case number into an email subject.
The ARR bridge guide shows how corrections like this one later surface as contraction or credits in revenue reporting.
Where the keys usually break
- Raw usage is gone. If meter events are aggregated before billing and the raw events are not kept, hop 1 cannot be tested. Stripe's meter events API accepts event timestamps only within the past 35 calendar days, so usage found to be wrong later is usually settled as a credit rather than re-recorded, which makes the credit decision the main surviving evidence.
- Amendments without history. If the CRM field that holds the plan or allowance was changed without field history switched on, nobody can show when it changed. Salesforce notes that field history tracking records old value, new value, who and when, but starts only once enabled and is not retroactive.
- Cases logged to the account, not the invoice. Hop 3 then needs a match by date.
- Approvals in chat. Hop 4 is the most common break. An approval that names the customer but not the case or invoice can only be matched by amount and date.
- Credit notes with a reason code only. Four codes cannot hold the reason, so without a reference in metadata the "why" never reaches the billing engine.
SalesforceThe twenty-case trace count
Ask billing operations to pick twenty credit notes issued at least a year ago, at random, and report three numbers: how many trace from credit note back to meter events entirely by ID, how many need one match by date or amount, and how many break. Ask which hop fails most often. Ask for counts only, never invoices or customer names. SourceX publishes no benchmark for a good result; the counts give its review an honest starting point. A revenue leakage audit uses a similar sample, but to find lost revenue rather than to test whether the evidence joins.
What the map does and does not establish
The map describes where records sit and whether they join. It does not establish who may license them. That depends on the systems' owners, the company's customer contracts and an executive with authority; the decision tree on who can license these records covers it, and the referral brief template records the trace count in a form an executive can read.
The company needs 50+ full-time employees at peak (contractors excluded), a 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 90% of the data is in English. Unknown until SourceX reviews it: buyer interest, what customer agreements allow, de-identification of customer names and amounts, and any offer. Partners sign the Channel Partner Agreement before submitting introductions. A similar invoice-to-correction chain in logistics is on the freight audit exceptions page.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the twenty-case count shows most corrections joining from credit note to meter events by ID, register as a partner, check the company against who qualifies and read the program terms before you make the introduction.