# Entitlement exception: a worked hard case | SourceX

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

The records that explain an entitlement exception are the plan history for each account, the approval that allowed a non-standard grant, the permission change that carried it out, the ticket that confirmed it worked and the billing amendment that settled it at renewal. In the Illustrative case below, an acquired customer lost a feature after an account merge. Seven decisions by seven roles, from the merge to the renewal, each left a dated record in one of four systems.

This worked case is part of [exception handling records for AI agents](/guides/exception-handling-ai-agents-data). That page explains why exception histories matter. This one walks through a single hard case from the first complaint to the renewal, then shows how a customer platform consultant can spot similar cases at a client.

## What went wrong at the merged account (Illustrative)

Invented for this page. A fictional 400-person B2B software company buys a smaller competitor. The buyer runs billing in Stripe, permissions through Okta groups and support in Zendesk. The acquired product had its own billing system, which the company plans to retire.

One customer used both products. On the buyer's side it holds an enterprise plan for 120 seats. On the acquired side it holds a legacy plan that includes an advanced reporting module, a feature the enterprise plan sells only as a paid add-on. On March 3, the integration team merges the two accounts into one enterprise account. The legacy plan ends, the reporting group falls away and 14 users lose the module overnight.

On March 5, the customer's operations lead opens a ticket: reports they run every Monday are gone. Nothing is broken in any one system. Billing shows a valid enterprise plan, identity shows correct enterprise groups, and the ticket is a reasonable complaint. The problem sits between them: the customer had paid for the module under a contract the merge did not honor.

## Decision by decision: who chose what

Each row is one decision, the role that made it and the record it left.

| Date | Decision | Decided by | System | Record left |
|---|---|---|---|---|
| Mar 3 | Merge the two accounts under the enterprise plan | Integration lead | Billing | Plan change with effective date; legacy plan closed |
| Mar 5 | Escalate the ticket as a contract question, not a bug | Support agent | Helpdesk | Ticket priority and group change |
| Mar 6 | Confirm the legacy contract included reporting through its term | Account manager | CRM and contract store | Note on the account citing the legacy order form |
| Mar 7 | Skip the standard add-on quote; grant reporting free until renewal | Head of customer success, as approver | Helpdesk | Approval comment naming the approver and the end date |
| Mar 7 | Add the 14 users to the reporting group | Identity administrator | Identity platform | Group membership events, change note citing the ticket |
| Mar 10 | Confirm Monday reports ran | Customer, then agent | Helpdesk | Customer reply; ticket solved |
| Sep 1 | Add reporting to the renewal at a negotiated price; remove the exception group | Renewal manager | Billing and identity | Subscription update; group removal events |

The fork is on March 7. The standard rule said: a customer who wants reporting buys the add-on. The head of customer success chose another path because the legacy contract had already sold the feature. That choice is the heart of the case, and it is only visible because someone wrote down who approved it and until when.

## The record each decision left

A reviewer needs five kinds of record to follow the case, and each lives somewhere different.

- **What the customer was entitled to:** plan histories for both accounts, with effective dates. In Stripe Billing, a plan change, a discount and a renewal each trigger a `customer.subscription.updated` event, so the merge and the September amendment both have a billing footprint. The acquired system's history is the one at risk, because it is being retired.
- **Who approved the exception:** the approval comment in the ticket. Zendesk describes ticket audits as a read-only history of all updates to a ticket, with change events that record the previous and new value of each property. That is how a reviewer can see when the priority changed and when the approval was written.
- **What was actually changed:** the identity events. Okta's System Log has event types for a user being added to or removed from a group, and for app assignments. Fourteen adds on March 7 and fourteen removals on September 1 bracket the exception exactly, provided the events were exported: Okta's System Log does not return data older than 90 days.
- **Whether it worked:** the customer's reply and the solved status, with no reopen.
- **How it ended:** the renewal amendment, which turned a free exception into a priced line.

If one link is missing, the case stops making sense. Without the approval, the group grant looks like an administrator error. Without the plan history, the complaint looks like user confusion. The [system map for entitlement records](/guides/entitlement-exception-handling-records-across-systems) shows the keys that join these records.

## Why this sequence is useful evidence

A clean entitlement change teaches one rule: the plan decides the permissions. This case shows people handling a situation the rule did not cover. There is a contract fact that overrides the price list, an approver with a reason and an end date, a technical change that cites the ticket, a checked outcome and a commercial close six months later. Each judgment can be tested against a dated record made by the person responsible.

That is the kind of operational history AI developers describe needing when they need examples of real work rather than idealized procedures; [why operations data is valuable](/proof/why-operations-data-is-valuable) explains the demand in general terms. It does not mean any buyer wants a given company's records. That is decided only after SourceX reviews them.

## How to spot similar cases at a SaaS client

Customer platform consultants see the signs during ordinary integration work. Without opening a record, ask the customer support director:

- **Have acquisitions or plan consolidations merged customer accounts in the last few years?** Each merge creates conflicts like this one.
- **When an agent grants something outside the plan, where is the approver written down?** In the ticket, in a change note, in chat or nowhere.
- **Do identity changes cite a ticket number?** If they do, the join between permission and complaint survives.
- **Does the acquired product's billing history still exist, and until when?**
- **Roughly how many entitlement exceptions a year?** A range is enough.

[Useful resolution context in support tickets](/guides/how-to-identify-support-tickets-with-useful-resolution-context) covers the ticket side in more depth, and the [acquisition integration introduction plan](/guides/a-practical-introduction-plan-for-advisors-supporting-an-acquisition-integration) covers timing.

Then ask who can authorize a licensing discussion, which is the CEO, often with the COO or CFO preparing the case; the [who-can-license decision tree](/questions/who-can-license-entitlement-exception-handling-records) maps that path. 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 what remains licensable is unknown until SourceX's rights review. Partners never ask for or handle raw client records. More sector context is on the [software and SaaS industry page](/industries/software-and-saas).

## 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 software company you work with can follow a case like this from the merge to the renewal, [register as a partner](/register), check it against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing 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
