CRM order-volume claim, reconciled.

The order-volume claim

The firm operates SAP CRM as the order-management spine for its global advisory and consulting practice. The CRM engine is licensed on annual order volume, with a tiered price per order above the licensed threshold. The 2024 self-declaration showed 2.4 million orders processed across the global instance. SAP's commercial team converted the figure into an $8.2M overage claim for a single year, with retroactive exposure on three prior years also flagged in correspondence.

The firm's internal SAM function had reviewed the figure and concluded that the count was technically correct — the CRM order table did contain 2.4 million records for the year. The procurement leadership was preparing a settlement around the $6.5M mark on the assumption that the count was defensible only on the price-per-order, not on the count itself. We were engaged to test whether the count was actually the correct measurement basis.

The opening question we asked was simple. What counts as an "order" under the contractual engine definition? The contract referenced sales orders for billable service delivery. The CRM order table contained sales orders for billable service delivery, plus internal transfer orders, plus a category of zero-value orders generated by the resource scheduling system. The internal team had not separated the categories before submitting the figure.

The opening position

SAP's opening position rested on the raw 2.4 million figure with no categorical breakdown applied. The supporting workpaper was a single screenshot of the CRM order-count table from the licence administration workbench. There was no exclusion analysis, no zero-value filter, no internal-versus-external attribution.

We obtained the CRM order table for the full measurement year and ran a deconstruction analysis. The breakdown produced four categories: 1.49 million billable sales orders to external clients, 580,000 internal transfer orders between practice areas, 250,000 zero-value resource-allocation orders, and 80,000 reversed or cancelled orders that remained in the count under the firm's order-retention policy.

Only the first category — 1.49 million billable sales orders — matched the contract definition of an order subject to the engine metric. The other three categories were either internal, zero-value, or reversed transactions that should not have been counted under any defensible reading of the contract. The defended count was 38 percent below the SAP figure before any further argumentation.

The defence

The defence strategy ran on three workstreams. The first documented the categorical breakdown with source-table evidence, transaction-type filters, and a per-category sample of forty orders with full transaction history. The samples were submitted to SAP with an invitation to test any category for accuracy.

The second workstream addressed the contract definition. We obtained the original 2017 CRM engine contract and the two subsequent amendments. The engine definition specified "billable sales orders processed through the CRM system on a transactional basis." The word "billable" was unambiguous in the context, and the supporting commercial correspondence from the 2017 negotiation reinforced the intent. Internal transfers, zero-value allocations, and reversals were all out of scope on a plain reading.

The third workstream addressed the historical retrospective. SAP had raised retroactive exposure for three prior years on the same methodology. We applied the same categorical breakdown to each year and demonstrated that the original self-declarations had used the same un-deduplicated count, meaning the historical exposure was a methodology error, not a usage growth. The retrospective was withdrawn before the formal settlement discussion began.

The counter-position offered to settle at the defended count of 1.49 million billable orders for the current year, with a goodwill payment of $2.4M to close the historical exposure and a renewed engine licence at 1.8 million annual orders to provide growth headroom. The contract amendment included a refined definition of "order" that explicitly excluded internal transfers, zero-value allocations, and reversals.

The settlement

Settlement closed at the proposed $2.4M figure with the proposed amendment language. The retrospective exposure was withdrawn in full. The forward engine licence was renewed at the 1.8 million annual order tier with the refined definition attached as a binding amendment. The reduction against opening was 71 percent.

The amendment was the durable outcome. The CRM order-count methodology was now governed by a contractual definition that the internal SAM team could apply consistently. The next self-declaration cycle would produce a defended figure on the first submission, removing the need for a re-examination after the fact.

Total elapsed time from engagement to executed settlement was sixteen weeks. The settlement was concluded ahead of the firm's fiscal year-end, which had been the original deadline for procurement leadership.

Five lessons for the next CRM engine claim

• The raw order count from the CRM workbench is not the engine measurement. The engine measurement is the count filtered by the contract definition of "order." The two figures diverge by 30 to 50 percent in most estates.
• Internal transfer orders are not external sales orders. The CRM transaction-type field distinguishes them. The exclusion is straightforward once the categorical breakdown is done.
• Zero-value resource-allocation orders are not billable orders. If your CRM hosts internal scheduling, you are almost certainly over-declaring.
• Historical retrospectives can be withdrawn if the methodology error is consistent across years. The argument is that the same methodology was applied and accepted in prior cycles, making the retrospective a methodology dispute, not an enforcement matter.
• The amendment language is the protection. A refined definition of "order" in the contract removes the need for the same dispute in the next cycle.

Further detail on the methodology behind the defence is set out in the Engine Metrics Reconciliation white paper. For the broader topic context, see the cluster pillar on Engine metrics, the cluster pillar and the deep dive on CRM engine metric explained. The topic landing at Engine Metrics provides the broader category context.