# License true-up: check before you cancel | SourceX

Canonical: https://refer.sourcex.si/guides/moment-annual-license-true-up-saas-spend-consultants
Last updated: 2026-11-04

Sometimes, and the people building the true-up cancel list rarely ask. A cancellation deletes unique decision histories when the app is the only place where years of approvals, case resolutions, deal notes or design decisions were recorded, and when no export happens before the vendor's retention period ends. SaaS spend consultants can test each app on the cancel list with one question. If the company holds such records, looks eligible and wants to explore licensing, the consultant introduces its decision-maker to SourceX.

The [SaaS spend audit guide](/guides/saas-spend-audit) shows how to find every system a company pays for, and the [renewal management guide](/guides/saas-renewal-management-portfolio-companies) places a data check on a portfolio's renewal calendar. This page covers the narrower moment when a true-up turns a usage count into a cancel list.

## Will the proposed cancellation delete unique decision histories?

It will if two things are true: the app holds records of decisions that exist nowhere else, and the cancellation takes effect before anyone exports them. Most cancel lists are built from seat usage and cost, so neither question gets asked.

The annual true-up is the moment. Under a Microsoft Enterprise Agreement, for example, customers submit an annual true-up order that must reach Microsoft between 60 and 30 days before the agreement anniversary. Many other vendors run their own annual reconciliations or renewals. In the weeks before those orders, finance and IT agree which products to drop, downgrade or consolidate. A tool with few active users looks like an easy saving, yet low current usage often means the tool's working life is over and its value now sits in its history.

Records behind retired applications are easy to overlook because the people who created them have moved on. A service desk replaced two years ago may still hold eight years of resolved tickets. An old project tool may hold every change request and sign-off for a decade of client work. Once the subscription ends, vendor retention rules take over. Atlassian's documentation, for instance, says it keeps data for deactivated cloud apps for 60 days after the end of the subscription period for Free, Standard or Premium plans (15 days for trials), then deletes it permanently. Microsoft describes a Disabled stage for lapsed Microsoft 365 for business subscriptions, usually 90 days, during which only admins can reach and back up data. Other vendors differ, so the consultant's task is to ask for each vendor's rule, not to assume one.

### The opening question and four metadata follow-ups

For every app on the cancel list, ask exactly: **"Will the proposed cancellation delete unique decision histories?"** The system owner can usually answer it in a sentence.

Where the answer is "yes" or "not sure", ask four metadata questions:

1. **What:** which decisions does the app record (approvals, resolutions, design changes, quote revisions)?
2. **How much and how long:** approximate record counts and years covered.
3. **Which system:** the plain-text tool name and whether a newer system already holds a copy.
4. **Who owns it:** which executive owns the records, and do customer contracts limit their reuse?

Record only the answers. Consultants never request exports, sample records, admin access or screenshots.

## The cancellation triage test: an illustrative example

Illustrative only; the company and apps are fictional. A 300-person engineering services firm prepares its true-up and proposes canceling five tools.

| App on cancel list | Active users | Decision history held | Copy elsewhere? | Vendor rule after cancellation | Triage result |
|---|---|---|---|---|---|
| Legacy service desk | 4 | Nine years of resolved client tickets with root causes | No; new desk started fresh | Ask the vendor; check contract | Pause: owner decides on export or a licensing review |
| Old project tracker | 11 | Change requests and sign-offs, 2014 to 2022 | Partial; only open projects migrated | If it is an Atlassian cloud app, 60 days after period end | Pause: export closed projects first |
| Survey tool | 3 | Customer satisfaction responses | Yes; exported to the data warehouse yearly | Not relevant once copy verified | Cancel as planned |
| Screen recording tool | 7 | Short training clips | Yes; stored on the company's file share | Not relevant | Cancel as planned |
| Duplicate chat workspace | 20 | Two years of team messages | No | Ask the vendor | Owner and counsel decide; retention policy applies |

Two of five tools fail the test. Neither needs to be kept forever; each needs a decision by its owner before the order is placed. That decision is where a licensing conversation can start, if the owner wants one. The [network opportunity finder](/tools/network-opportunity-finder) helps spot similar patterns across other clients.

## How do you disclose the reward and get the owner's permission?

Tell the owner, before any introduction, that you are a SourceX referral partner and may receive a reward if a license completes, and that SourceX pays it separately so it never reduces the company's payout. Then ask whether they want to be introduced at all. Many owners will simply export and cancel, which is a good outcome for the true-up in its own right.

If the owner does want to explore a licensing review, introduce the executive who owns the records, not the IT admin who runs the export. Name the app, the kind of decision history at stake and the years covered, and say that no records have been shared. Keep vendor names and counts to what the owner has confirmed. ERP replacements raise the same question at a larger scale; the [NetSuite consultants guide](/guides/how-erp-consultants-spot-referral-opportunities-during-netsuite-projects) covers that version. If the true-up falls into an owner's yearly planning cycle, the [annual client review](/guides/an-annual-client-review) is a natural place to raise it.

## Which companies qualify, and what stays unknown until SourceX reviews?

The company needs 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.

| Known before introduction | Unknown until SourceX reviews |
|---|---|
| Which canceled apps hold unique decision histories | Whether those records fit a dataset need |
| Years covered and rough volumes | The rights review result |
| Each vendor's retention rule, from its documentation | Offer, exclusivity and agreed terms |
| Who owns the records and can authorize a discussion | Whether any reward becomes payable |

Partners sign the Channel Partner Agreement before submitting introductions. See [who qualifies](/who-qualifies) for the full criteria and the [rewards page](/rewards) for how a reward is calculated. Other role playbooks are on the [partner hub](/for).

## Go deeper on the annual license true-up

- [Annual license true-up archive context checklist](/resources/annual-license-true-up-archive-context-checklist): a dated, tick-box checklist to work through before the order date removes records.
- [Annual license true-up introduction email](/resources/annual-license-true-up-introduction-email): a ready-to-edit email template for introducing the record owner to SourceX.

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

When a true-up cancel list includes a tool whose history exists nowhere else and the owner wants to explore it, [register as a partner](/register), confirm the fit on [who qualifies](/who-qualifies), and check the [program terms](/terms) before the order date passes.

## Sources

- https://refer.sourcex.si/terms
- https://www.microsoft.com/licensing/guidance/Enterprise-Agreement
- https://support.atlassian.com/subscriptions-and-billing/docs/reactivate-a-subscription/
- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires?view=o365-worldwide
- https://refer.sourcex.si/rewards
