A multinational services group disputed a Concur true-up by reclassifying subscriber categories, retiring dormant accounts, and rewriting the active-user definition in the contract.
Every result on this site is anonymised at the client's request. Specific figures are real and verifiable through a confidentiality-protected reference call arranged on request.
The group is a global services multinational with approximately sixty-two thousand subscriber records on SAP Concur covering Travel, Expense, and a small Invoice deployment in Europe. Concur had been the corporate travel and expense system of record since 2018, with a contracted active-subscriber count of forty-two thousand five hundred.
The annual measurement cycle produced an active-subscriber count of sixty-two thousand against the contracted ceiling of forty-two thousand five hundred. SAP Concur issued a true-up demand of three point two million dollars covering the cumulative excess and the prospective adjustment.
The group's Travel & Expense leadership had been tracking the subscriber count internally and had not anticipated the demand at this scale. The discrepancy traced to the definition of an active subscriber under the contract versus the platform's default counting methodology.
Concur had counted every active subscriber record on the platform during the measurement window, regardless of expense-report activity. Of the sixty-two thousand records, approximately fourteen thousand had no expense-report or travel-booking activity in the prior twelve months. A further six thousand were terminated employees whose records had not been deactivated on the platform.
The contracted definition of an active subscriber required at least one expense-report submission or travel booking in the measurement window. The platform's default counting methodology counted any active account regardless of submission activity.
Concur's account team initially presented the platform count as the binding measurement. The framing was that the platform definition controlled the contract definition rather than the reverse.
We worked four tactics in parallel against the true-up demand. Each one rebuilt the active-subscriber count against the contract definition and produced documentary evidence at the activity level.
We extracted the expense-report submission logs and the travel-booking logs for the prior twelve months. The defendable active-subscriber count under the contract definition was forty-one thousand eight hundred against the platform count of sixty-two thousand. The rebuild was documented at the subscriber level with activity timestamps.
We extracted the HR termination dates and identified five thousand nine hundred subscriber records associated with terminated employees. The records were either deactivated or scoped out of the count with documented termination evidence. Concur's reconciliation team accepted the exclusion.
A small population of subscribers had been provisioned in multiple regional instances during a platform migration. We identified seven hundred duplicate subscriber records and consolidated them with a single-source attestation from the global Travel & Expense lead.
The settlement included a rewrite of the active-subscriber definition into the contract, removing the ambiguity between the platform count and the contract definition. The new definition is activity-based and is supported by a documented measurement protocol.
The true-up closed at nine hundred thousand dollars against an opening demand of three point two million, a seventy-two per cent reduction. The settlement covered a true-up of approximately twelve hundred active subscribers and a small adjustment to the prospective baseline. No additional licences were purchased outside the reclassification.
Contractually, the active-subscriber definition is now written into a measurement addendum with activity-based criteria. The termination purge is recognised as a recurring reconciliation right. The multi-region consolidation protocol is documented for future platform changes.
Total elapsed time from the true-up notification to signed settlement was ten weeks. The matter closed inside the same financial year, allowing the group to remove the contingent liability from its year-end disclosure.
First, Concur measurements anchor on the platform's active-subscriber count, which is a provisioning artefact rather than an activity record. The contract definition rests on activity and should be applied as the binding count.
Second, terminated employees are excluded under the contract but are routinely retained on the platform when the HR-to-Concur deactivation workflow lags. The exclusion requires HR-termination evidence at the subscriber level.
Third, multi-region instances produce duplicate subscriber records that must be consolidated before any measurement closes. Fourth, the active-subscriber definition is contract language, not platform language. It should be rewritten into the contract if it is not already documented. Fifth, Concur true-up disputes resolve fastest when the activity data is presented at the subscriber level rather than at the aggregate count.
The platform count was sixty-two thousand. The contract count was forty-two. Once that distinction was put on paper, three quarters of the demand came off.
Reconciliation of Concur subscriber categories against the contract definition. Run before the annual true-up cycle, not after the demand letter arrives.
Read the brief →Reset the active-subscriber definition into the contract. Termination-purge protocols documented. Multi-region consolidation rules written into the measurement addendum.
Read the brief →The topic page sets out the licensing structure, the audit triggers, and the negotiation levers across this SAP product line.
A 3,500-word analyst paper covering the methodology behind the defence, with five numbered recommendations and the field evidence.
The pillar article in this cluster covers the licensing structure, the audit triggers, and the defence sequence applicable to estates like this one.
A global logistics firm reclaimed 4,100 dormant subscriber records and reduced its annual licence demand by 19%.
A global services firm restructured an HXM renewal by reclassifying subscriber categories and removing unused modules.
One hundred-plus anonymised case files across audit defence, license compliance, contract negotiation, and S/4HANA conversion.
Every engagement opens with a confidential, no-obligation conversation. We listen, test the position, and tell you whether there is a defendable case before any commercial discussion begins.
Contact Us →Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.