The annual SAP measurement cycle is not a single event; it is a twelve-month operating rhythm that opens with the previous year’s reconciliation memo and closes with the next year’s submission. Estates that treat the cycle as an event — preparing in the four weeks before submission and forgetting about classification the rest of the year — carry compounding licence drift into the conversion conversation and pay for it in true-up. Estates that operate the cycle as a calendar — with named owners, planned deliverables, and quarterly checkpoints — keep audit exposure approximately flat year over year and convert the savings into negotiation leverage. This article sets out the calendar in twelve monthly blocks, names the owner for each block, and identifies the deliverable that must exist on the last day of each month for the cycle to remain on schedule. The discipline underpins our USMM and LAW advisory retainers.
The fixed point
The cycle has exactly one fixed point: the day the USMM submission is due to SAP. Most contracts specify the submission window rather than a single date, but the buyer-side calendar should treat the latest acceptable day as the anchor. Every other deliverable in the calendar is plotted by counting backwards from the anchor or forwards from the previous year’s anchor. The anchor anchors the operating model. Reset it only when the contract is amended.
The natural anchor for most enterprise estates is the first or second week of a fixed quarter. Year-on-year consistency in the anchor week is more valuable than minor calendar optimisation, because the upstream deliverables become routine when they fall on the same week each year.
Month one — the reconciliation memo
The first month after submission is the reconciliation month. The deliverable is a one-page memo recording what the submission showed, where it differed from the previous year, what SAP’s initial reaction was, and what the open questions are. The memo is the canonical record of the measurement event and the input to next year’s planning. The owner is the licence manager. The memo is short and definitive. It is not the place for opinions about what should have gone differently; it is the place for what actually happened.
Why the memo matters
The submission file itself is dense and difficult to interpret out of context. The memo provides the context. When the same conversation re-opens nine months later in audit, the memo is the document that allows the buyer side to remember its own position. Estates without the memo re-derive their own position under audit pressure, which is the worst possible time to do it.
Months two through three — classification review
The first quarterly classification review falls in months two and three. The deliverable is a classification movement report showing every user whose role-collection assignment changed since the previous review, with the licence-impact flag for each change. The report runs against the live system and is the primary mechanism for catching the over-classification drift that otherwise accumulates between submissions. The owner is the SAP basis team, working with HR for the joiner-mover-leaver feed.
The classification review is the most under-resourced phase in most estates. The work feels routine and produces no visible business outcome. The economic value emerges only at the next submission, when the drift the review caught did not need to be undone. The named-user reclassification article covers the technical detail.
Months four through six — engine review and contract scan
The second quarter is the engine-metric review window. Engine metrics — ABAP-licence-units, document counts, named-employee counts under the HR module — have their own measurement disciplines that are independent of the user-licence review. The deliverable is an engine-metric movement report covering the previous twelve months, with a forward projection for the next twelve. The owner varies by engine; the licence manager coordinates.
The same quarter is the right window for the annual contract scan. The contract that authorises the measurement may itself be approaching a renewal point, and the leverage available in renewal conversations depends on data that takes months to assemble. The contract scan deliverable is a one-page summary of upcoming renewal dates, current pricing, embedded discount-protection clauses, and known points of contractual ambiguity. The summary feeds the negotiation strategy in contract negotiation engagements.
Months seven through eight — the LAW dress rehearsal
Month seven is the right month for a LAW dress rehearsal — a full consolidation run executed against the live system in a controlled window, with the output preserved as evidence and analysed in detail. The dress rehearsal exposes consolidation mismatches between systems while there is still time to correct them. Common findings include duplicate user-master records across systems that the production LAW will collapse, classification mismatches between equivalent users in different systems, and authorisation-object differences that the consolidation logic interprets as classification differences. The owner is the SAP basis team.
A dress rehearsal in month seven costs perhaps two days of basis time. The same finding discovered in week one of the submission window costs a calendar week of escalation and re-runs. The economics of the dress rehearsal are not subtle.
Months nine through eleven — the preparation window
The formal six-week preparation window opens in month nine and runs through to the submission. The preparation sequence is documented in the USMM run preparation article and need not be repeated here. The point for the calendar is that the preparation is a planned, six-week project, not an emergency. By the time it begins, the classification reviews, engine-metric reviews, and LAW dress rehearsal have already done most of the substantive work. The preparation becomes a structured validation rather than a first-pass analysis.
The owner of the preparation window is typically a dedicated programme lead with authority across basis, security, and procurement. The cross-functional authority matters: classification corrections often touch role-collection design (security), user-master cleanup (basis), and licence-type assignment (procurement). A single owner with the authority to direct work across all three avoids the coordination tax that otherwise consumes the window.
Month twelve — submission and immediate review
The final month is the submission month. The submission goes out on the anchor date. The immediate review follows in the same month. The deliverable is the reconciliation memo for the new cycle, closing the loop and opening the next year. The owner is the licence manager, who hands the memo to the executive sponsor and to any independent advisor supporting the engagement. The next cycle’s calendar is updated with the actuals from this cycle in the same review session, so the calendar evolves with the operating reality rather than as a static document.
The standing meetings
The cycle requires three standing meetings. A monthly licence-operations meeting that walks the calendar and confirms the current month’s deliverable. A quarterly licence-governance meeting that reviews the classification report and the engine-metric movement. And an annual licence-strategy meeting in the reconciliation month that resets the calendar for the new cycle. The standing-meeting cost is roughly two hours per month plus six hours per year. The estates that maintain the rhythm consistently outperform on submission readiness and on negotiation leverage; estates that let the rhythm lapse re-discover the calendar each year and pay the rediscovery cost in over-preparation effort and under-supported submissions.
Where it connects to the contract cycle
The measurement calendar runs in parallel to the contract-renewal calendar. The two should be plotted on the same wall. Measurement evidence is the principal input to renewal leverage; renewal terms are the principal constraint on the measurement methodology. Treat them as a single operating system. The contract-negotiation pillar covers the renewal calendar in detail, and the media-company case file shows the calendar in operation across a difficult cycle. The ECC topic page provides the underlying measurement context.
The artefacts that survive the year
By the end of a properly operated cycle, the estate has accumulated a stable set of evidence artefacts: the reconciliation memo, four classification movement reports, two engine-metric movement reports, the contract scan, the LAW dress-rehearsal output, the override register, the system-boundary document, and the final submission file. The artefacts together form the audit-defence position for the cycle. If an audit notification arrives during the cycle, the response is a curated subset of the artefacts already in hand, rather than an emergency document production. The USMM and LAW measurement checklist sets out the artefact list and the retention discipline by document type.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
If your estate does not currently operate a measurement calendar, build it backwards from the next submission anchor and forwards from the most recent reconciliation memo (or, in the absence of one, from the most recent submission file). The first cycle is heavier than the steady state; the second is roughly half the effort; by the third, the rhythm carries itself.