# Support-to-credit record chain: IDs by step | SourceX

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

A company connects support-to-credit records by finding the one ID that survives each handoff and checking whether someone actually wrote it down: the ticket ID on the billing credit note, and the credit note ID on the ledger memo, applied to the same invoice the customer complained about. Many companies connect these steps through people, not keys. The realistic answer is often "partly, from a given year onward," and the year is the useful fact.

This record chain is part of the [support-to-credit guide](/guides/chain-support-to-credit), which covers what a partner collects from a first conversation. This page has a narrower job: follow one service credit from complaint to ledger and name the ID at each hop.

## The IDs available at each hop

Each team creates its own identifier, and only some of them travel forward.

| ID | Created when | Lives in | Carried forward by default? |
|---|---|---|---|
| Ticket ID | The customer writes in | Help desk | No; billing must type it |
| Audit event | Any ticket field or comment changes | Help desk ticket history | No; it records the approval moment only |
| Invoice number | The bill is issued | Billing, then ledger | Yes, through the billing-to-ledger sync |
| Credit note ID | Billing issues the credit | Billing | Only if the ledger memo field is filled |
| Credit memo number | Finance records the credit | Ledger | No |
| Apply link | The memo is applied to an invoice | Ledger | It is the link, if the right invoice is chosen |

The invoice number is often the only key carried automatically. It ties billing to the ledger, but not to the reason for the credit. The ticket ID is the anchor that explains why, and it travels only by habit.

## One $450 credit, hop by hop (Illustrative)

A fictional 330-person logistics software company bills a customer $2,400 on invoice INV-7702. The customer has paid $900, leaving $1,500 due, when it reports two days of failed route syncs and asks for a credit.

| Day | Record | ID that points to the next step | System |
|---|---|---|---|
| 0 | Ticket T-58213 opened; customer describes the failed syncs | Ticket ID; the audit trail logs each field change and comment | Zendesk |
| 1 | Support manager approves a $450 credit; agent sets "credit approved" | Approval field and approver name in the ticket audit | Zendesk |
| 3 | Billing issues a $450 credit note against INV-7702 | T-58213 in the credit note's metadata, typed by billing | Stripe |
| 3 | Amount due on INV-7702 falls from $1,500 to $1,050; invoice stays open | Invoice number | Stripe |
| 11 | Finance records a $450 credit memo with the credit note ID in the memo | Credit note ID; applied automatically to the oldest open invoice, INV-7460 | NetSuite |
| 35 | Collections chases $1,050 on INV-7702 in the ledger, which shows $1,500 | Invoice number only | NetSuite |

Steps 0 to 3 hold together because billing typed the ticket number. Step 11 is the weak link: the memo names the credit note, but it was applied to a different invoice. Billing says $1,050 is due on INV-7702; the ledger says $1,500. Collections, reading only the ledger, asks the customer for money already credited.

## What the vendors' own features make possible

Each join in the chain rests on a documented feature, which is why it is reasonable to ask about them.

- **The approval moment.** Zendesk describes ticket audits as a read-only history of ticket updates, each made of events such as field changes and comments. If the agent sets an approval field, the date and the person are kept.
- **The ticket ID on the credit.** Stripe lets a company attach custom key-value metadata to its objects and suggests storing an external system's ID there. A ticket ID on a credit note is possible; whether it is there depends on the billing team.
- **The open balance.** Stripe's credit note documentation says a credit note on an open invoice reduces the amount due and marks the invoice paid only if the balance reaches zero. A $450 credit against $1,500 due leaves the invoice open by design.
- **The apply choice.** NetSuite lets a credit memo be applied automatically to the oldest open invoice or to one chosen on the Apply subtab. Automatic application is convenient and is exactly what broke step 11.

None of this means a given company used these features. The question for the client is simple: "Since when has billing written the ticket number on credits, and does finance choose the invoice when it applies a memo?"

## Four places the ticket number drops out

Four breaks recur in support-to-credit chains, each with a signature a partner can recognize from a conversation.

**No ticket ID on the credit.** Signature: billing staff who say they "look up the customer" to find out why a credit was given.

**The memo applied to the oldest invoice.** Signature: open invoices whose ledger balance and billing balance disagree by the amount of a recent credit.

**The partial credit nobody closes.** Signature: invoices that stay open for months after a credit, with no note on the ticket when the balance is finally paid or written off.

**Refunds outside the credit note.** Stripe's documentation notes that on a paid invoice a credit note does not change the amount due; money goes back by refund, customer balance credit or outside Stripe. Signature: credits recorded as refunds or manual adjustments that never touch the original invoice.

The dated summary is the deliverable: "ticket ID on credit notes since 2021; memos applied by hand since a 2022 process change; open-balance follow-up not logged on tickets." The [completeness checklist](/resources/support-to-credit-completeness-checklist) scores each hop, and the [missing-context comparison](/guides/support-to-credit-missing-context) shows what a single export loses when a hop has no key.

## Who answers for each hop, and what SourceX decides later

The support operations manager owns days 0 and 1, the billing lead owns day 3, and the assistant controller owns days 11 and 35. Each can describe their hop from admin screens. Authorizing a licensing discussion across support and finance takes the CEO, or the owner in an owner-run company, often with the CFO or COO preparing the case.

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.

Partners stay at metadata level: which IDs are carried, from which year, rough volumes and owners. They never open tickets or invoices. Unknown until SourceX reviews it: whether customer contracts allow licensing, how ticket text and names would be de-identified, whether a buyer wants this chain and what the company would be paid. Help desk detail sits on the [Zendesk system page](/systems/zendesk) and the [Zendesk inventory template](/resources/a-metadata-only-zendesk-inventory-template-for-company-introductions); [how CX consultants spot opportunities](/guides/how-cx-consultants-spot-referral-opportunities-during-zendesk-projects) covers the advisor's view, and the [NetSuite partner page](/for/netsuite-partner-referral-program) covers the ledger side.

## 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 say since when its credits carry the ticket ID and who chooses the invoice a memo is applied to, [register as a partner](/register), confirm [who qualifies](/who-qualifies) and read the [terms](/terms) before you introduce them.

## Sources

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