SAP License Audits Contact Us
Home · Case Studies · Case File 049 · Engine Metrics

Order-to-cash claim, defended.

A global manufacturer rebuilt its SAP order-to-cash engine measurement, separated invoiced sales orders from quote-and-credit activity, and reduced a $7.4M claim to $1.9M with a refined contractual definition.

Manufacturer order-to-cash operations centre
Industry
Manufacturing
Geography
Global · 22 countries
SAP Estate
ECC SD + S/4HANA Sales
OTC Documents
9.8M counted
— Case File 049 · Engine Metrics

The headline numbers, on the record.

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.

Opening claim
$7.4M
SAP's initial position
Settled value
$1.9M
final close, goodwill basis
Reduction
74%
vs. opening claim
Duration
17wk
engagement to executed settlement
Section I · The Brief

The order-to-cash claim

The manufacturer ran SAP SD as the global order-to-cash spine, with regional instances consolidated under a single tiered engine licence. The 2024 self-declaration produced a figure of 9.8 million OTC documents, against a contracted tier of 6 million. SAP's commercial team calculated a $7.4M overage on the 3.8-million-document excess.

The supporting workpaper was a standard measurement-utility output applied to the SD document table. The internal sales-operations team had reviewed the figure and concluded that the count was technically accurate — the SD document table did contain 9.8 million rows for the year — without questioning whether all of those rows were OTC transactions subject to the engine metric.

The sales revenue figure reported in the firm's annual statements implied approximately 4.2 million distinct invoiced orders for the year. The gap between the reported invoiced-order figure and the engine declaration was over 5 million documents, which suggested that more than half of the engine-counted documents were not invoiced sales orders.

Section II · The Opening Claim

The opening position

SAP's opening position rested on the 9.8 million raw figure. The workpaper applied the tier-overage rate to the 3.8 million excess, producing the $7.4M claim. There was no document-type analysis.

We obtained the SD document table for the measurement year and applied a deconstruction. The breakdown produced seven categories: 4.2 million invoiced sales orders, 2.1 million open quotations that never converted to orders, 1.4 million credit-memo-and-return processing documents, 0.9 million sample-and-no-charge documents, 0.7 million internal stock-transfer documents booked through SD, 0.4 million blocked orders that never released, and 0.1 million other.

Only the first category — 4.2 million invoiced sales orders — matched a strict contractual reading of the OTC engine definition. The remaining 5.6 million documents were either unconverted activity, return processing, internal transfers, or technical artefacts. Each category required a separate evidentiary basis for exclusion.

Section III · The Defence

The defence

The defence ran on four workstreams. The first documented the categorical breakdown with source-table evidence, document-type filters, and per-category samples drawn from each regional instance proportionally.

The second workstream addressed the unconverted quotations — the 2.1 million category. Quotations that never converted to orders are pre-order activity, not OTC transactions. The contractual engine definition referenced "order documents subject to invoicing," and the open quotations were demonstrably not subject to invoicing. The exclusion was supported by the quotation-status field and a sample audit trail.

The third workstream addressed the credit-memo-and-return category — the 1.4 million documents. The contractual question was whether returns and credit processing constituted separate OTC transactions or reversal activity. The position we took was that returns reverse the original order rather than creating new OTC volume, with the supporting argument that double-counting both the original sale and its reversal would be commercially incoherent.

The fourth workstream addressed the sample-and-no-charge category, the internal stock-transfer category, and the blocked-order category. Each was demonstrably outside the contractual definition of an invoiced sales order, with documented evidence available from the SD document-type table. The exclusions removed approximately two million further documents from the count. The counter-position offered a settled current-year measurement of 4.2 million invoiced sales orders, with a $1.9M goodwill payment to close the historical period and a renewed engine tier of 5 million annual invoiced orders.

Section IV · The Settlement

The settlement

Settlement closed at the proposed $1.9M figure with the proposed amendment. The current measurement was accepted at the defended 4.2 million count. The forward engine tier was renewed at 5 million annual invoiced orders with a 12 percent forward-growth allowance. The reduction against opening was 74 percent.

The amendment language placed the OTC engine measurement on a clean contractual footing. The sales-operations team adopted the categorical filtering as a standard practice in the quarterly licence-position reviews. The next self-declaration cycle ran on the refined methodology and produced a clean defended figure on the first submission.

Total elapsed time from engagement to executed settlement was seventeen weeks. The reduction against opening was 74 percent. The audit window was closed with no further measurement obligation.

Section V · Lessons Applicable

Five lessons for the next OTC engine claim

Further detail on the methodology behind the defence is set out in the Engine Metric Audit Playbook white paper. For the broader topic context, see the cluster pillar on Engine metrics, the cluster pillar and the deep dive on The order-to-cash engine explained. The topic landing at Engine Metrics provides the broader category context.

Continue with the firm

The two services this matter drew on.

I.

SAP Audit Defence

End-to-end audit response. From the opening letter to the executed settlement, with the contract reviewed, the measurement deconstructed, and the negotiation handled by a buyer-side specialist.

Read the brief →
III.

Contract Negotiation

When SAP escalates a measurement claim, the right counter-position is contractual, not technical alone. We negotiate the settlement, the contract language, and the forward measurement protocol.

Read the brief →
Related reading

From the research desk.

— Engine Metrics

Engine metrics, the cluster pillar

The cluster pillar covering measurement methodology, contractual definitions, and the standard defence patterns for the engine in question.

May 2026 · Pillar
— Case Studies

Consumer goods engine reconciliation

A multinational CPG group rebuilt its FI and SD engine measurements and removed $7.2M from a self-declaration claim.

Case File · Adjacent
— Case Studies

Manufacturing engine claim defended

Engine measurement claim contested on contract definitions and decommissioned-system rules.

Case File · Adjacent

An audit notification is not an invoice.

It is the opening position of a negotiation. Speak with a specialist before responding. The first conversation is at no cost and under privilege.

Contact Us →
— Subscribe

SAP Audit Alerts · The weekly briefing

Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.