The renewal you found out about from the customer
A customer emails on a Tuesday morning: their design software stopped opening overnight and their team cannot work. You check the vendor portal and there it is, a term licence that expired at midnight. The renewal was never quoted because nobody at your end knew the date. The account manager who sold it three years ago left last spring, and the date lived in his calendar.
Meanwhile, a different customer has three subscriptions from the same vendor bought at different times, each with its own anniversary, and your CRM shows one renewal date for all of them. Someone typed it in once and it has been wrong ever since the second purchase.
Most resellers recognise both situations. The information exists, somewhere. It just is not anywhere a person can look at on a Monday and see what is due in the next ninety days.
Why the dates never end up in one place
A value added reseller usually sells for several vendors, and each vendor keeps its own record of what each end customer owns. Some show it in a partner portal, some send a monthly renewal report as a spreadsheet, some only show it in the distributor's system. The formats differ, customer names differ between them, and the same customer can appear as the parent company in one portal and a subsidiary in another.
Your own CRM was filled in at the point of sale, by hand, often with the close date of the deal rather than the start date of the licence. Add-ons bought mid-term get their own dates unless someone co-termed them. Multi-year deals renew on a different cycle to annual ones.
| Source | What it knows | What it gets wrong |
|---|---|---|
| Vendor partner portal | Current term end per contract | Customer names, only that vendor |
| Distributor order history | What you bought, when, at what cost | Licence start and end dates |
| Your invoices | What you billed the customer | Nothing about the vendor term |
| CRM opportunity | Who sold it and the deal value | Dates typed once and never updated |
No single source is complete, so the answer is not to pick a better one. The answer is to combine them and reconcile the differences.
What the missing dates are costing
Lapsed licences mean an angry customer, and in some vendor programmes a reinstatement or late renewal cost that someone then has to argue about. Renewals caught late are quoted in a rush, without time to review seat counts or offer an upgrade, so the conversation is about getting the order in rather than about what the customer needs next year.
There is also the quiet cost. Renewals your team never sees are renewals a competitor or the vendor's own direct team can pick up. And your account managers spend part of every week logging into portals to check dates they should already have.
The renewal register we build
- Collection: vendor renewal reports and portal exports are collected on a schedule, by API where the vendor offers one, or by reading the report files your team already downloads.
- Distributor history: order lines from your distributor account, including contract or agreement numbers where they appear, are pulled in alongside.
- Customer matching: each record is matched to your customer list by domain, agreement number and address, with a review queue for anything the rules cannot match confidently, such as a subsidiary trading under a different name.
- Contract level dates: renewals are held per contract and per product line, not per customer, so three subscriptions with three anniversaries show as three rows.
- Conflict flags: where the vendor date and your CRM date disagree, the register shows both and asks the account manager to confirm which is right.
- Pipeline push: confirmed renewals create or update renewal opportunities in your CRM, such as HubSpot or Salesforce, at the lead time you choose for each vendor.
We do not decide which vendor terms apply to a renewal. The register shows dates and what was bought; your team and your vendor agreements decide the rest.
A normal Monday with the register running
The renewals lead opens one view: everything due in the next quarter, grouped by account manager, with the vendor, product, seat count and last price paid. Rows marked amber have a date conflict to settle. Rows marked red have no confirmed date at all, usually a legacy customer bought before the current systems.
Account managers work their renewals from the CRM as normal. Nobody logs into five portals to build the list, and when a new vendor report arrives, changes show up as updates rather than as a new spreadsheet to compare by eye.
Does this sound like your renewal book?
- Customers have told you their licence expired before you knew it was due.
- Renewal dates in your CRM are the original deal close dates.
- Account managers keep their own renewal spreadsheets.
- The same customer appears under different names in different vendor portals.
- Add-on purchases have renewal dates nobody has recorded.