# Support-to-credit records: metadata packet | SourceX

Canonical: https://refer.sourcex.si/guides/chain-support-to-credit
Last updated: 2026-11-04

A referral partner can describe a company's support-to-credit history entirely from metadata: which systems hold the ticket decision, the approved credit and the ledger entry, the date range of each, how many records exist, which identifier links them, and who owns each step. You never open a ticket or an invoice. The one case to test before introducing is a partial credit that reduces an invoice without closing it, because that is where the chain most often stops explaining itself.

## The business task: one support decision, three records

A customer complains about an outage. A support agent agrees to a service credit, billing issues it, and finance records it against the customer's balance. Three teams, three tools, one decision. The business question is whether the company can show, for any credit, why it was granted, who approved it, and what it did to the invoice.

The graphic follows one credit (Illustrative). An invoice of $1,200 has $500 paid, leaving $700 due. On day 1 a Zendesk ticket approves a $300 credit. On day 2 Stripe issues a $300 credit note. On day 9 NetSuite applies a $300 credit memo. The balance falls from $700 to $400 and the invoice stays open. That is expected behavior: Stripe's documentation says a credit note on an open invoice reduces the amount due and marks the invoice paid only if the balance reaches zero. The open $400 is not an error. It is simply the point where someone reading only one system can no longer tell what happened.

## What metadata can a referral partner collect about support-to-credit without reading private content?

Collect facts about the records, not the records. A billing advisor can fill in the packet below during a normal conversation with a controller or support lead, from admin screens and memory, without exporting anything.

### The metadata packet (Illustrative)

The values describe a fictional 240-person B2B software company that bills by invoice. Replace them with what your client tells you.

| Field | Zendesk (ticket decision) | Stripe (approved credit) | NetSuite (ledger entry) |
|---|---|---|---|
| Object types | Tickets, ticket audits, macros, a "billing dispute" form | Invoices, credit notes, refunds | Invoices, credit memos, customer refunds |
| Date range | 2017 to today | 2019 to today | 2016 to today |
| Approximate volume | 410,000 tickets; about 9,000 tagged as credit requests | About 6,500 credit notes | About 7,200 credit memos |
| Decision marker | Tag plus a required "credit approved" field since 2021 | Credit note reason code | Memo line and item used for service credits |
| Link to next step | Ticket ID typed into the credit note? Unknown | Credit note ID in a NetSuite memo field? Unknown | Not applicable |
| Step owner | Support operations manager | Billing lead | Assistant controller |
| Retention or deletion rule | No ticket deletion policy known | None known | Seven-year finance policy |
| Planned change | Help desk migration discussed for next year | None | None |

Three things make this packet useful without being sensitive. It has counts and ranges, not samples. It names an owner per step, which tells SourceX who would have to sign off. And the "Unknown" cells are honest: an introducer who marks a join as unknown is more credible than one who assumes it exists.

Two documented features explain why the link cells matter. Zendesk ticket audits are a read-only history of every ticket update, so the decision itself is usually well kept. Stripe lets a company store custom metadata on objects and suggests putting an external object's ID there, so a ticket ID on a credit note is possible but only if someone set it up. NetSuite applies a credit memo to the oldest open invoice or to one chosen by hand, which is worth a single question: which does the team use?

## The partial-credit question

Ask the assistant controller how the team handles an invoice that a credit reduced but did not close. Note three answers: whether such invoices are reported separately, who chases the remaining balance, and whether the ticket is updated when the balance is finally settled or written off. "We have an aging report filtered on credited invoices since 2020" and "we would not know without looking" are both usable answers. Neither requires an amount or a customer name.

If you want a single-system starting point, the [Zendesk inventory template](/resources/a-metadata-only-zendesk-inventory-template-for-company-introductions) and [NetSuite inventory template](/resources/a-metadata-only-netsuite-inventory-template-for-company-introductions) cover the per-system fields. If the help desk is about to be replaced, [exporting Zendesk tickets before canceling](/systems/export-zendesk-tickets-before-canceling) describes the deadline that creates.

## Sponsor, fit and open questions

The sponsor has to sit above both support and billing, which in most companies means the CFO, COO or owner. A support operations manager can describe the help desk; licensing finance records is not their call.

Fit, in four checks:

| Check | What to confirm |
|---|---|
| Size | 50+ full-time employees at peak, contractors excluded |
| History | A documented operating history behind the records |
| Rights | The company owns the records and has not signed them away to a help desk or billing vendor |
| Contact | A named decision-maker willing to take a first call |

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.

Open until SourceX reviews it: de-identification to a buyer's standard, the date ranges a buyer would want, limits in customer contracts, and the company's payment. None of those are yours to answer, and you never handle or forward raw records. The company's side is covered in [what support data licensing involves](/resources/license-customer-support-data-for-ai); the [Zendesk](/systems/zendesk) and [NetSuite](/systems/netsuite) pages and the [systems hub](/systems) cover other record locations.

## Go deeper on support-to-credit records

- [How to link tickets, credit notes and credit memos across systems](/guides/support-to-credit-record-linkage): a guide to the IDs that join Zendesk, Stripe and NetSuite records.
- [Support-to-credit completeness checklist](/resources/support-to-credit-completeness-checklist): a checklist of the breaks that leave a credit trail incomplete.
- [What a single-system ticket or billing export leaves out](/guides/support-to-credit-missing-context): a guide to the context lost when only one system is exported.

## 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.

If your client can fill in the packet above and name the person who owns both support and billing, [register as a partner](/register), check [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
