# License true-up archive context checklist | SourceX

Canonical: https://refer.sourcex.si/resources/annual-license-true-up-archive-context-checklist
Last updated: 2026-11-04

It will when a tool holds decisions recorded nowhere else and the switch-off lands before anyone exports them. This checklist puts that test on a timeline: what to confirm before the drop list is shared, before the true-up order is placed, and before the old subscription is switched off. Each item names an owner and the cost of skipping it. Dates come from the company's own agreement and each vendor's documentation, never from assumption.

This checklist is part of the [true-up playbook](/guides/moment-annual-license-true-up-saas-spend-consultants). Work through it next to the licensing calendar. When the owner wants an introduction, the [annual license true-up introduction email](/resources/annual-license-true-up-introduction-email) is the next document.

## How to read the timeline

Each milestone hangs off a date the company already holds: the order deadline in its licensing agreement, the end date in each vendor contract, and the deletion point in each vendor's own retention documentation. The worksheet borrows those dates; it never sets them. Real examples of each are collected near the end of this page.

Write the real dates for each tool at the top of the worksheet before starting:

| Milestone | Where the date comes from | Who confirms it |
| --- | --- | --- |
| Drop list drafted | The true-up project plan | Person running the true-up |
| True-up or renewal order placed | The licensing agreement or renewal notice | Procurement or licensing lead |
| Subscription ends | The vendor contract | Procurement or licensing lead |
| Data deleted by the vendor | The vendor's own retention documentation | System owner or IT lead |

If a date cannot be found, write "unknown" and treat it as an item to resolve, not a gap to guess.

## Before the drop list is shared

At this point nobody has been told their tool is going, so the questions are cheap. The aim is to find the tools whose worth now sits in their history.

| Confirm | Owner | If skipped |
| --- | --- | --- |
| Will the proposed cancellation delete unique decision histories? Ask it for every tool on the draft list | System owner for each tool | Little-used tools are cut on seat count alone and their history is never discussed |
| Which decisions each flagged tool records: approvals, resolutions, sign-offs, quote revisions | System owner | The owner cannot judge what is at stake |
| Years covered and rough record counts | System owner or IT lead | Depth of record is unknown, so nobody can weigh a pause against a saving |
| Whether a newer system already holds a copy | IT lead | A pause is requested for records that already exist elsewhere |
| Which executive owns the records | Person running the true-up | The question lands with an admin who cannot decide |

Record only the answers. Never request exports, sample records, admin access or screenshots. The [SaaS spend audit guide](/guides/saas-spend-audit) helps make sure the draft list covers every paid tool.

## Before the true-up order is placed

This is the decision point. Once the order goes in, the switch-off is committed and the vendor's clock takes over.

| Confirm | Owner | If skipped |
| --- | --- | --- |
| A decision for each flagged tool: export, keep, or explore a licensing review | Executive who owns the records | The default, deletion, happens without anyone choosing it |
| The vendor's retention rule after the end date, from its documentation | System owner | The team assumes a grace period that may not exist |
| Whether customer or supplier contracts limit reuse of the records | Counsel or contract owner | Records are exported or discussed without knowing their limits |
| Who runs any export, and in what format | IT lead | Nobody owns the work and the window closes |
| Whether the owner wants an introduction, after your referral interest is disclosed | Executive who owns the records | An introduction goes ahead without informed consent, or a willing owner is never asked |

The disclosure is simple: you are a SourceX referral partner and may receive a reward if a qualifying license completes; SourceX funds it separately and it never reduces the company's payout. Many owners will simply export and cancel, which is a good result for the true-up.

## Before the old subscription is switched off

The order is placed and the end date is fixed. What remains is making sure the decision is carried out before the vendor deletes anything.

| Confirm | Owner | If skipped |
| --- | --- | --- |
| The export, if chosen, has run and been checked by the company | IT lead | The vendor deletes the only copy at the end of its retention period |
| The exported records have a named owner and a storage location | Executive who owns the records | The export becomes an orphaned file nobody can find |
| The decision and its date are noted in the true-up file | Person running the true-up | Next year's team repeats the work or assumes it was done |
| The introduction, if agreed, went to the person who can authorize a licensing discussion | Consultant | SourceX hears from someone who cannot approve anything |

A worked example helps. Illustrative only: a 300-person engineering services firm flags an old project tracker holding change requests and sign-offs from 2014 to 2022. Before the cancel list, the owner confirms no other system holds closed projects. Before the order, the chief operating officer chooses an export and agrees to an introduction. Before switch-off, IT confirms the export ran and names its owner. Every box is ticked before the vendor's retention period ends.

## Reference dates, qualification and what stays unknown

The reference dates differ by vendor, which is why the worksheet asks for each one. Under a Microsoft Enterprise Agreement, the annual true-up order must reach Microsoft between 60 and 30 days before the agreement anniversary. Atlassian keeps data for deactivated cloud apps for 60 days after the end of the subscription period on 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. Treat these as examples of where to look, not as defaults for other vendors.

The company needs 50+ full-time employees at peak (contractors excluded), 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.

What stays unknown until SourceX reviews it: whether the records fit a dataset need, what the rights review allows, preparation needs and any offer. Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. For why old records can still matter, see [does old data have value for AI](/questions/does-old-data-have-value-for-ai); to fold this check into a yearly review, use the [annual client review handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-annual-client-review), and the [IT budget template](/resources/it-budget-template) helps place export costs next to license savings.

## 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 an owner ticks "explore a licensing review" before the true-up order is placed, [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- 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/terms
