Support-to-credit completeness scorecard: eight checks on the ticket, credit note and ledger trail

Short answer

A support-to-credit trail breaks where a service credit loses its reason on the way from the help desk to the books: a credit note that carries no ticket ID, a ledger memo that carries no credit note ID, an approval timestamp that comes after the credit, a credit policy with no version history, or an outcome nobody records. A case that often breaks is a partial credit that leaves the invoice open. This scorecard lets you mark each check pass, partial or fail from one conversation.

Visual briefFull-size diagram
Eight support-to-credit checks, from ticket coverage to outcome after credit, tick pass, partial or fail in two columns while a horizontal meter fills to 11 of 16 points.
Illustrative scoring for a fictional managed hosting provider. The score describes the trail; it does not predict acceptance.

This resource belongs to the support-to-credit records guide, which covers the metadata packet itself. Use the scorecard after the packet, when you want to know how much of the trail actually holds together.

Scoring rules before the call

Book 30 minutes with the people who run support, billing and receivables. Read each check's question aloud and mark the answer you hear, not the answer you expect. Three marks are possible:

  • Pass (2 points): the company describes the link or field and can say since when it exists.
  • Partial (1 point): the link exists for some years, some teams or some credit types, or depends on someone typing it by hand.
  • Fail (0 points): the link does not exist, or nobody present can say. Unknown scores as fail until someone confirms otherwise.

Eight checks give a maximum of 16 points. Write one sentence of notes per check. The notes are worth more than the total, because they tell SourceX which years and which credit types read as a chain.

The eight checks, answered at metadata level

#CheckQuestion for the ownerPassPartialFail
1Ticket coverageSince what year can a credit request ticket still be opened?Five or more years in one help desk or a documented migrationYears exist but an old help desk was not migratedUnder two years, or unknown
2Decision markerHow does a ticket show that a credit was approved?Required field or form since a known yearA tag some agents applyOnly the agent's reply text
3Ticket to credit noteDoes a credit note carry the ticket ID?Stored in a structured field on every credit noteTyped into a memo some of the timeOnly the invoice number is shared
4Credit note to ledgerDoes the ledger credit memo carry the credit note ID?Synced or required reference fieldMemo text by conventionMatched by amount and date only
5Timestamp orderIs the approval time recorded before the credit note time?Approval and issue both dated, approval firstDated, but some credits issued before approvalCredits also issued from chat or email with no ticket
6Partial-credit invoicesWhat happens to the rest of an invoice after a partial credit?Open balance has a recorded reason and ownerAssistant controller knows, nothing recordedOpen balances look like ordinary unpaid invoices
7Policy versionCan you show the credit policy as it read on an approval date?Versioned policy with dated changesA few archived copiesCurrent document only
8Outcome after creditIs it recorded whether the customer renewed, paid the rest or left?Outcome linked to the account and the creditOutcome in a CRM nobody links to ticketsNot recorded

Checks 3 and 4 are where trails often thin out. Stripe lets a company store custom key-value metadata on its objects and suggests storing an external object's ID there, so a ticket ID on a credit note is possible, but only if someone built it. NetSuite can apply a customer credit memo automatically to the oldest open invoice or to one chosen on the Apply subtab, which is why check 4 has a follow-up: which method does the team use? Automatic application can attach a credit to an invoice the ticket never discussed.

Check 2 is usually the strongest. Zendesk ticket audits are a read-only history of every ticket update, field changes and tag changes included, so if a required "credit approved" field exists, the moment it was set is normally kept.

Check 6 in depth: a partial credit on an open invoice

This check deserves its own two minutes because it produces a record that looks wrong even when everything went right. Stripe's documentation explains the mechanics: a credit note on an open invoice reduces the amount due, and the invoice moves to paid only when the balance reaches zero. On a paid invoice, the amount due does not change and the money goes back as a refund, a customer balance credit or a refund outside Stripe.

So a $300 service credit on an invoice with $700 still due leaves $400 open. Months later, anyone reading only the receivables aging sees a $400 balance that looks like a collections problem. Ask: "When a credit reduces an invoice but does not close it, where is that recorded?" Answers fall into three marks.

  1. Pass. The open balance carries a reason code or a note referencing the ticket, and the collections owner can filter credited invoices.
  2. Partial. "The assistant controller knows." The records exist, but the reasoning lives with one person, which SourceX's review would need to account for.
  3. Fail. Credited invoices sit among ordinary unpaid ones with no marker. The help desk and billing history may still be valuable, but the ledger end of the trail cannot explain itself.

No mark here disqualifies a company. It changes how you describe the records.

Scored example: a 180-person managed hosting provider (Illustrative)

A fictional managed hosting provider issues outage credits through its help desk. All answers and marks are invented to show how a filled scorecard reads.

#CheckAnswer heardMarkPoints
1Ticket coverageHelp desk since 2017, earlier tickets lost in a migrationPass2
2Decision markerRequired "credit approved" field since 2021, a tag before thatPass2
3Ticket to credit noteBilling types the ticket ID into the credit note memo when remindedPartial1
4Credit note to ledgerCredit note ID in the memo line by conventionPartial1
5Timestamp orderApprovals dated first; a few urgent credits issued before the approval field was setPartial1
6Partial-credit invoicesAging report filtered on credited invoices since 2020Pass2
7Policy versionCredit policy in a shared document without historyFail0
8Outcome after creditRenewal status in the CRM, linked by accountPass2
AllTotalEight checks scoredSum11 of 16

The sentence a partner would carry into the introduction: "Help desk decisions since 2017 with a structured approval field from 2021; ticket and credit note linked by memo text only; partial credits tracked since 2020; no policy history." That sentence is the deliverable. The number only helps you remember it.

For the general method of asking about data quality without seeing data, the data quality due diligence resource covers the same discipline across other record types. The companion guides cover the two things a scorecard cannot: how each identifier is carried from ticket to credit memo and what a single-system export leaves out.

Owners, sponsor and what SourceX settles

The scorecard names the owners for you: support operations for checks 1, 2 and 5; billing for check 3; the assistant controller or receivables lead for checks 4 and 6; whoever writes credit policy for check 7; customer success or sales operations for check 8. None of them authorizes a licensing discussion. That is the CEO, who sits above support and finance (in an owner-run company, usually the owner).

Confirm the company baseline before introducing: 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 covers the same basics.

What stays unknown until SourceX reviews it: what customer contracts and vendor terms allow, how customer names and amounts would be removed, which years a buyer wants and what the company would be paid. Partners never ask for or handle tickets, credit notes or ledger rows. If the help desk is about to be replaced, exporting Zendesk tickets before canceling explains why checks 1 and 2 have a deadline. The Zendesk and NetSuite pages cover each system on its own.

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.

When the scorecard gives you one honest sentence about the company's credit trail and a named officer who can act on it, register as a partner, confirm who qualifies and read the program terms before you make the introduction.

  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

Does a low score mean the company should not be introduced?

No. The scorecard tells you how to describe the trail, not whether SourceX or a buyer will want it. A company scoring 6 of 16 with honest notes is a cleaner introduction than one scoring 14 on guesses.

Who should answer the eight questions?

Usually the support operations manager for the help desk rows, the billing lead for the credit note rows and the assistant controller for the ledger rows. None of them needs to open a ticket or an invoice to answer.

Can I share the filled scorecard with SourceX?

You can summarize it in your introduction with the sponsor's agreement. Keep it to marks, years, systems and counts. Ticket IDs, customer names and credit amounts stay inside the company.

Sources

  1. refer.sourcex.si/terms
  2. developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits
  3. docs.stripe.com/invoicing/dashboard/credit-notes
  4. docs.stripe.com/metadata
  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