# Entitlement records across systems: a map | SourceX

Canonical: https://refer.sourcex.si/guides/entitlement-exception-handling-records-across-systems
Last updated: 2026-11-04

Reconstructing an entitlement exception takes three joins across four systems: the CRM account to the billing plan, the plan change to the identity event that changed permissions, and the identity event to the helpdesk ticket that asked for it and confirmed it. The keys are usually an account or customer ID, a user or group ID with a timestamp, and a ticket number typed into a change note. Each join can break, most often after an acquisition.

This system map is part of [exception handling records for AI agents](/guides/exception-handling-ai-agents-data). It answers one question for customer platform consultants: where does each record sit, and what ties them into one case?

## The four systems behind one entitlement case

An entitlement exception touches more systems than most people expect. Each holds one part of the story, and none holds all of it.

| System | Record it holds | Linking key out | Usual owner |
|---|---|---|---|
| CRM | Account, contract and the order form that sold each feature | Account ID, customer ID in billing | Sales operations or revenue operations |
| Billing or subscription system | Plan history with effective dates, add-ons, discounts, renewals | Customer ID, subscription ID, plan code | Finance or billing operations |
| Identity platform | Group and app memberships, who changed them and when | User ID, group ID, timestamp, change note | IT or identity administrator |
| Helpdesk | The complaint, the approval comment, the resolution | Ticket number, requester, organization | Customer support director |
| Legacy billing (after an acquisition) | The acquired product's plans and contracts | Old account ID | Often nobody, once retired |

The last row is the one that causes trouble. An acquired product arrives with its own customer IDs, plan codes and contract history, and the join from those IDs to the buyer's systems is a mapping table somebody built during integration.

## Join by join: the keys that hold a case together

**Join 1: account to plan.** The CRM account carries a customer ID that billing recognizes. When accounts merge, the surviving account keeps one ID, and the other becomes an alias or disappears. A reviewer needs the mapping, or the legacy plan history cannot be attached to the customer.

**Join 2: plan change to permission.** In Stripe Billing, a plan change, a discount or a renewal triggers a `customer.subscription.updated` event. Okta's System Log records a user added to or removed from a group, or assigned to or removed from an app. When provisioning is automated, the two events share a user and a timestamp a few seconds apart. When an administrator grants an exception by hand, there is no billing event at all, and the identity event stands alone.

**Join 3: permission to ticket.** The strongest link is a ticket number in the identity change note. The weaker link is time: the same users, the same day, the same organization. Zendesk ticket audits keep a read-only history of every update to a ticket, with previous and new values, so the moment of approval can be placed against the identity event.

## One fully joined case (Illustrative)

Invented for this page. A fictional 400-person software company has merged an acquired customer's two accounts, and 14 users lost a reporting module the legacy contract had included. Here is the same case seen through each key.

| Step | System | Record | Key that links it to the next step |
|---|---|---|---|
| Legacy contract sold reporting | CRM | Order form on the old account | Old account ID mapped to new customer ID |
| Accounts merged on March 3 | Billing | Subscription update; legacy plan closed | Customer ID, subscription ID |
| Users lose reporting | Identity platform | 14 group removals the same day | User IDs, timestamp within minutes of the merge |
| Customer complains on March 5 | Helpdesk | Ticket from the customer's operations lead | Organization matches the customer ID |
| Exception approved on March 7 | Helpdesk | Approval comment naming the approver and end date | Ticket number |
| Reporting restored on March 7 | Identity platform | 14 group adds, change note citing the ticket | Ticket number in the note |
| Priced at renewal on September 1 | Billing and identity | Subscription update; 14 group removals | Subscription ID, group ID |

Every row joins to the next one with a key a reviewer can check. Remove the ticket number from the change note and the restore looks like an unexplained grant. Remove the old-to-new account mapping and the complaint looks unfounded. The [worked exception case](/guides/entitlement-exception-handling-exception-examples) tells the same story as a sequence of decisions.

## Where the joins break after an acquisition

Four gaps come up again and again.

- **Old IDs with no mapping.** Integration teams map active customers. Churned or merged accounts may never get a row in the mapping table.
- **Manual grants with no billing event.** Exceptions are granted by hand by definition, so join 2 is often missing exactly where it matters.
- **Change notes left blank.** If the administrator did not cite the ticket, join 3 depends on timing.
- **Retention windows.** Okta's System Log query returns 90 days of events. Older identity history exists only if the company streamed or exported it. Zendesk's list-all-audits endpoint excludes archived tickets, which are read ticket by ticket instead.

One system alone rarely makes a licensable record set; [is one system's data enough for licensing](/questions/one-system-company-data-enough-for-licensing) explains why. The [post-merger integration data migration guide](/guides/post-merger-integration-data-migration) covers how mapping tables usually get built.

## Questions for the customer support director

Stay at metadata level. Ask about systems and keys, not about records.

- Which systems hold plans, permission changes and tickets, and since when?
- Does the company keep a mapping from acquired account IDs to current ones?
- Do identity administrators cite ticket numbers when they grant exceptions?
- Are identity events kept beyond the platform's own window?
- Who owns customer data and contracts, and could authorize a licensing discussion? The CEO authorizes; the COO or CFO often owns the records and prepares the case.

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Customer contracts may limit how account data is used, and identity logs carry personal data, so [why data rights matter](/proof/why-data-rights-matter) applies here. What is licensable stays unknown until SourceX's rights review. Partners never ask for or handle raw client records. For the support side in general, see [customer support workflows](/data-types/customer-support-workflows), and when the map is clear, the [entitlement referral brief template](/resources/entitlement-exception-handling-referral-brief-template) turns it into one page.

## 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 a client's billing, identity and helpdesk records still join into whole cases, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce its decision-maker.

## Sources

- https://developer.okta.com/docs/reference/system-log-query/
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://docs.stripe.com/billing/subscriptions/webhooks
- https://refer.sourcex.si/terms
