# Zendesk export missing context: before and after | SourceX

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

A single-system support-to-credit export keeps one side of the decision. A help desk export keeps the conversation and loses the money: it shows the complaint, the agent's reply and an approval field, but not whether a credit was issued, against which invoice, or what the customer still owed. A billing export keeps the money and loses the reason. Read alone, each one supports a confident conclusion that the other would contradict. The joined history explains both, and the gap table below shows where each missing piece lives.

This comparison is part of the [support-to-credit guide](/guides/chain-support-to-credit). Here one Illustrative credit is read three times: as a ticket row, as a billing row and as one history.

## Before: the ticket on its own

A fictional 270-person HR software company invoices a customer $3,600 for a quarter. The customer has paid $1,600 when a payroll export fails three days running. The customer opens a ticket asking for a credit.

What the Zendesk export says about ticket T-40977:

| Field | Value in the export |
|---|---|
| Subject | Payroll export failures, three days |
| Tags | outage, credit-request |
| Credit approved field | Yes, set on day 2 by a support manager |
| Agent's last comment | "We've approved a $600 credit, which billing will apply to your open invoice." |
| Status | Solved |

A reader of this row concludes that the customer was compensated and the matter closed. Zendesk keeps ticket audits as a read-only history of updates, so the approval moment and the person who set it are reliable. What the ticket cannot say is whether billing acted, when, or what the credit did. "Solved" describes the conversation, not the invoice.

## Before, the other way: the billing record on its own

Now the billing view of the same quarter, from Stripe.

| Field | Value in the export |
|---|---|
| Invoice | $3,600, issued at the start of the quarter |
| Payments | $1,600 received |
| Credit note | $600, issued on day 6, reason "service credit" |
| Amount due | $1,400 |
| Status | Open |

A reader of this row concludes that a customer received an unexplained $600 credit and still owes $1,400. Nothing links the credit note to a complaint. A reviewer cannot tell whether the credit was a goodwill gesture, a pricing error or an outage remedy, or which policy allowed it. Stripe's documentation explains the open status: a credit note on an open invoice reduces the amount due and marks the invoice paid only if the balance reaches zero. The open invoice is correct, and still unexplained.

## After: the same credit with its full context

Joined through the ticket number typed into the credit note and the credit note ID in the ledger memo, the case reads as one history (Illustrative).

| Day | Source | What it adds |
|---|---|---|
| 0 | Zendesk | Customer reports payroll export failures; ticket T-40977 opened |
| 2 | Zendesk | Support manager sets the approval field for a $600 credit under the service credit policy |
| 6 | Stripe | Billing issues a $600 credit note citing T-40977; amount due falls from $2,000 to $1,400 |
| 13 | NetSuite | Finance records a $600 credit memo and applies it to the same invoice |
| 40 | NetSuite and Zendesk | Customer pays the remaining $1,400; nobody updates the ticket |

Now the credit has a cause, an approver, a policy and a result, and the remaining $1,400 is visibly ordinary rather than suspicious. One gap remains even in the joined version: the ticket was never updated when the balance was settled, so a reader of the help desk still cannot see the end of the story.

## The gap table: what is lost and where it lives

| Question a reviewer would ask | Zendesk export alone | Billing export alone | Where the context lives |
|---|---|---|---|
| Why was a credit given? | Yes: complaint and reply | No | Ticket conversation and tags |
| Who approved it, and when? | Yes, from the ticket audit | No | Ticket audit events |
| Was the credit actually issued? | No: only a promise | Yes: credit note date and amount | Billing credit notes |
| How much, against which invoice? | Sometimes, if typed in a comment | Yes | Billing credit note and invoice |
| Did the customer still owe money afterward? | No | Yes: $1,400 | Billing amount due; ledger balance |
| Did finance record it the same way? | No | No | Ledger credit memo and its apply link |
| Which policy allowed it? | Rarely | No | A versioned credit policy, if one exists |
| When was the matter finally closed? | No | Partly: payment date | Ledger payments; ticket only if updated |

The "finance" row matters because NetSuite lets a credit memo be applied automatically to the oldest open invoice or to one chosen by hand. If the memo lands on a different invoice, billing and the ledger disagree, and only a joined history shows why. The "policy" row is where connected histories often still fall short, and it is fine to say so in an introduction. The [record chain](/guides/support-to-credit-record-linkage) shows the IDs that carry each piece, and the [completeness checklist](/resources/support-to-credit-completeness-checklist) scores whether a company's history has them.

## Sizing the gap with the company's owners

Ask each owner which columns of the gap table their system fills, and from which year: the support operations manager for approval fields and tags, the billing lead for whether ticket numbers are typed on credit notes, and the assistant controller for how memos are applied. Answers such as "approval field required since 2021; ticket numbers on credit notes since 2022; memos applied by hand" are enough.

Timing can matter. If the client is planning a help desk migration or cancellation, the export decision for ticket history will be made soon, and [exporting Zendesk tickets before canceling](/systems/export-zendesk-tickets-before-canceling) explains what is commonly kept. An [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) covers the ledger side, and [what a data asset is](/questions/what-is-a-data-asset) explains why a joined history is worth more than its parts.

The company baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact: the CEO (in an owner-run company, usually the owner), with the CFO or COO involved, since the history spans support and finance. 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. Unknown until SourceX reviews it: whether customer contracts allow licensing, how ticket text and names would be de-identified, and what a buyer would want. Partners never open tickets or invoices; the [Zendesk system page](/systems/zendesk) and [Zendesk inventory template](/resources/a-metadata-only-zendesk-inventory-template-for-company-introductions) list the metadata to ask about instead.

## 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's owners can say which columns of the gap table their systems fill, and since when, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms) before you make the introduction.

## Sources

- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- 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
