A software subscription receipt proves an entitlement that ends when payment stops. This guide explains subscription versus perpetual licences, what happens to files and access at lapse, and enterprise true-up audits.
A software subscription receipt proves an entitlement that ends when payment stops. This guide explains subscription versus perpetual licences, what happens to files and access at lapse, and enterprise true-up audits.

The defining fact of subscription software is what happens when you stop paying: the software stops working. Not gradually — access ends, apps deactivate, and in the strictest models even opening your existing files requires an active plan.
That is the difference between a subscription and the perpetual licence it replaced. A perpetual licence bought version X forever (with updates sold separately); a subscription buys continuous access, always-current versions, and cloud services — for exactly as long as the payments continue. Neither is wrong, but they are different assets, and the receipt is the record of which one you hold. On a subscription, the receipt run is effectively your proof of entitlement: the evidence that, this month, you are licensed.
Before letting any software subscription lapse, three questions, answered from the vendor's terms rather than optimism:
What happens to the files? Proprietary formats can become read-only or unreadable without the subscription. Export to open formats before the lapse, not after.
What happens to cloud storage? Grace periods before deletion vary from generous to brutal; the receipt's coverage end-date is the clock.
What happens to the price if you return? Winback offers exist, but so do repriced plans — the rate on your old receipts is not a promise.
At business scale, software subscription paperwork becomes a compliance matter. Volume agreements license a stated number of users or devices, and vendors audit: an true-up is the periodic reconciliation where actual deployment is counted against licensed entitlement, and the gap is billed — sometimes with back-charges.
The defence is the same boring discipline as every audit: records. The agreement, the entitlement counts, the invoices, and the deployment inventory, kept current. A business that can show its licence position from its own records negotiates a true-up; one that cannot, receives one.
The product and edition — feature tiers matter at renewal and at audit.
The licence type: subscription term or perpetual.
Seats or devices covered, and the coverage period.
The account or licence ID the payment attaches to — entitlement is looked up by this, not by your name.
Amount, tax, and the payment method.
Two more fields earn their place. The billing entity — subscription receipts routinely arrive from a parent company, a reseller, or an app-store biller whose name matches nothing on the product — and reconciling the charge to the ledger means knowing which name to expect. And the renewal date with its cancellation window: the receipt that states when the next charge lands, and by when you must cancel to avoid it, is the one that prevents the accidental year.
Keep the receipt with the licence ID and, where one exists, the licence key — the receipt proves you paid, the ID proves what for, and support conversations require both. For a business, keep the full run for the life of the product plus your audit retention period.
Vendors' account portals hold billing history and can reissue documents, which is the first recovery route. If a record is missing while the payment genuinely happened, your card statement establishes date, amount, and vendor, and a clear reconstructed record documents that real payment for your files, matching the statement exactly — it cannot recreate a licence entitlement, which lives in the vendor's systems against your account ID.
Add one habit at the end of a subscription's life: keep the final invoice and the cancellation confirmation together. Proration and refund questions arrive after the account is closed — when you can no longer log in to check anything — and that pair of documents is the whole answer.
Everything you need to know about the product and billing.