# Support-to-credit completeness scorecard | SourceX

Canonical: https://refer.sourcex.si/resources/support-to-credit-completeness-checklist
Last updated: 2026-11-04

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.

This resource belongs to the [support-to-credit records guide](/guides/chain-support-to-credit), 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

| # | Check | Question for the owner | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1 | Ticket coverage | Since what year can a credit request ticket still be opened? | Five or more years in one help desk or a documented migration | Years exist but an old help desk was not migrated | Under two years, or unknown |
| 2 | Decision marker | How does a ticket show that a credit was approved? | Required field or form since a known year | A tag some agents apply | Only the agent's reply text |
| 3 | Ticket to credit note | Does a credit note carry the ticket ID? | Stored in a structured field on every credit note | Typed into a memo some of the time | Only the invoice number is shared |
| 4 | Credit note to ledger | Does the ledger credit memo carry the credit note ID? | Synced or required reference field | Memo text by convention | Matched by amount and date only |
| 5 | Timestamp order | Is the approval time recorded before the credit note time? | Approval and issue both dated, approval first | Dated, but some credits issued before approval | Credits also issued from chat or email with no ticket |
| 6 | Partial-credit invoices | What happens to the rest of an invoice after a partial credit? | Open balance has a recorded reason and owner | Assistant controller knows, nothing recorded | Open balances look like ordinary unpaid invoices |
| 7 | Policy version | Can you show the credit policy as it read on an approval date? | Versioned policy with dated changes | A few archived copies | Current document only |
| 8 | Outcome after credit | Is it recorded whether the customer renewed, paid the rest or left? | Outcome linked to the account and the credit | Outcome in a CRM nobody links to tickets | Not 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.

| # | Check | Answer heard | Mark | Points |
|---|---|---|---|---|
| 1 | Ticket coverage | Help desk since 2017, earlier tickets lost in a migration | Pass | 2 |
| 2 | Decision marker | Required "credit approved" field since 2021, a tag before that | Pass | 2 |
| 3 | Ticket to credit note | Billing types the ticket ID into the credit note memo when reminded | Partial | 1 |
| 4 | Credit note to ledger | Credit note ID in the memo line by convention | Partial | 1 |
| 5 | Timestamp order | Approvals dated first; a few urgent credits issued before the approval field was set | Partial | 1 |
| 6 | Partial-credit invoices | Aging report filtered on credited invoices since 2020 | Pass | 2 |
| 7 | Policy version | Credit policy in a shared document without history | Fail | 0 |
| 8 | Outcome after credit | Renewal status in the CRM, linked by account | Pass | 2 |
| All | Total | Eight checks scored | Sum | 11 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](/resources/data-quality-due-diligence) 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](/guides/support-to-credit-record-linkage) and [what a single-system export leaves out](/guides/support-to-credit-missing-context).

## 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](/tools/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](/systems/export-zendesk-tickets-before-canceling) explains why checks 1 and 2 have a deadline. The [Zendesk](/systems/zendesk) and [NetSuite](/systems/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](/register), confirm [who qualifies](/who-qualifies) and read the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://docs.stripe.com/invoicing/dashboard/credit-notes
- https://docs.stripe.com/metadata
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1312521.html
