An industrial manufacturer defeated a SAP engine-metric claim built on duplicate line-item counting, rebuilt the measurement on document-flow rules, and reduced the claim by eighty-three per cent.
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 manufacturer ran an ECC environment with active FI Engine, SD Engine, and MM Engine licensing. The audit cycle delivered an opening claim of $9.2M against engine-metric overages, with the largest component being a $5.4M overage on the FI Engine line-item count. SAP's measurement cited approximately 720 million annual line items against a contracted entitlement of 480 million.
The internal SAM team had run the measurement transaction at the standard cadence and had not flagged any overage. The SAP-submitted measurement diverged from the internal measurement by approximately fifty per cent across all three engines. The divergence triggered an immediate validation request.
The CFO engaged us to test the SAP measurement against the internal measurement and identify the source of the divergence. The engagement opened with a parallel rebuild of all three engine measurements on the same source data.
The parallel rebuild surfaced the source of the divergence within the first week. SAP's measurement had counted line items at multiple stages of the document flow rather than at the contractually defined measurement point. A single sales-order-to-invoice chain was counted at the order, the delivery, the invoice, and the accounting document — four counts against a contractual one count per chain.
The pattern repeated across all three engines. FI counted accounting documents and journal lines separately. SD counted orders and deliveries and invoices. MM counted purchase orders and goods receipts and invoices. The cumulative double-counting accounted for the full $7.6M gap between SAP's $9.2M claim and the internal measurement.
The contractual definitions were unambiguous. Each engine has a defined measurement point per the contract addendum, and the addendum specifies single-count-per-chain measurement. SAP's claim was an artefact of an incorrect measurement methodology rather than a licensing exposure.
Four tactics carried the defence from the opening $9.2M claim to the settled $1.6M position.
We rebuilt each engine measurement on the contractual single-count-per-chain methodology. The corrected counts were FI 410M, SD 220M, MM 180M against the SAP-claimed FI 720M, SD 380M, MM 290M. Each rebuild was documented with the document-flow logic and presented as a defensible measurement.
We mapped the contractual measurement-point definitions against SAP's measurement output and documented the divergence. The mapping was signed off by external counsel and presented as a formal position. SAP retracted the multi-stage counting after two rounds of correspondence.
We negotiated a self-declaration framework for the three engines, with the customer providing measurement evidence on the contractual methodology and SAP accepting the evidence subject to a documented audit right. The framework removes the multi-stage counting risk from future cycles.
Within the corrected measurement, FI ran at 410M against 480M contracted (under entitlement), MM ran at 180M against 240M contracted (under entitlement), and SD ran at 220M against 200M contracted (a small overage). The settled position purchased the SD overage at $1.6M and accepted the contracted entitlements for FI and MM as is.
The claim closed at $1.6M against the opening $9.2M, an eighty-three per cent reduction. The settlement included the self-declaration framework for all three engines and a contractual confirmation of the single-count-per-chain measurement methodology.
The internal SAM function now runs the engine measurements quarterly on the contractual methodology and maintains continuous evidence of compliance. The framework documentation is part of the standard audit-readiness package.
The manufacturer's contracted engine entitlements for FI and MM remain unchanged. The SD entitlement was lifted modestly to provide headroom for projected growth. The annual run-rate uplift was $0.3M, against the $9.2M opening claim that triggered the engagement.
The vendor measurement counted a single transaction four times. The arithmetic was wrong by design. We rebuilt it on the contract definition and the claim collapsed.
End-to-end engine-measurement defence, document-flow rebuilds, and self-declaration framework negotiation.
Read the brief →Quarterly engine measurement on contractual methodology and continuous audit-readiness packaging.
Read the brief →FI, SD, MM and the document-flow measurement points across the ECC engine portfolio.
How the engine measurement works, where the double-counting traps sit, and how to defend against them.
How a CPG manufacturer rebuilt the engine measurement and reduced the audit position by $6.4M.
It is the opening position of a negotiation. Speak with a specialist before responding. The first conversation is at no cost and under privilege.
Further reading from the firm: the SAP engine metrics pillar and the utility self-declaration defence.
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.