A regional utility defended a $6.1M IS-U engine-measurement claim with a documented self-declaration, mapped meter-event volumes to the contractual measurement definition, and closed the dispute at $0.9M.
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 utility ran SAP IS-U as the core billing and customer information system across approximately three point two million meter points. The audit cycle opened with a claim of $6.1M against an IS-U engine overage, citing approximately twenty-four million annual meter events against a contracted entitlement of twelve million.
The internal SAM team had no visibility into the IS-U engine measurement methodology because the engine had been licensed under a self-declaration model in the original 2018 contract. The internal measurement cadence had not been established and the prior audit cycles had simply accepted the SAP-provided figures.
The CFO engaged us to test the SAP measurement against the contractual definition of a meter event and to establish whether the claim was substantively defensible. The engagement opened with a contract-language review and a parallel measurement rebuild.
The 2018 contract addendum defined an IS-U meter event as a billing-relevant meter reading processed through the billing engine. The definition explicitly excluded non-billing-relevant events such as estimated readings, validation events, dispute events, and re-bills. The exclusions were material because the utility's IS-U environment processed approximately eighteen million events annually that fell within the excluded categories.
SAP's measurement had counted all events, including the contractually excluded categories. The arithmetic of the over-count matched the gap between the claim and the contractual measurement — approximately twelve million events.
The contract definition was favourable. The work was to rebuild the measurement against the definition and to establish a continuing self-declaration framework that would carry the defence forward.
Four tactics carried the defence from the opening $6.1M claim to the settled $0.9M position.
We extracted twelve months of IS-U event data and mapped each event to the contractual category: billing-relevant, estimated, validation, dispute, or re-bill. The mapping produced a billing-relevant count of approximately 12.4M events against the SAP-claimed 24M. The mapping was documented per event category with the source-table evidence.
We prepared a formal self-declaration package with the event-category mapping, the contractual definition reference, and a methodology statement. The package was submitted under the contractual self-declaration right and accepted by SAP after one round of clarification correspondence.
We established a quarterly event-category measurement framework with the internal IS-U team, with continuous evidence maintained in a dedicated reporting view. The framework carries forward as the standard measurement methodology and removes the recurring audit-cycle pressure.
We secured a contract amendment that formalises the event-category methodology in the addendum and confirms the customer's self-declaration right. The amendment carries the methodology forward as the agreed contractual definition for future cycles.
The claim closed at $0.9M against the opening $6.1M, an eighty-five per cent reduction. The 12.4M billing-relevant event count was modestly above the 12M contracted entitlement, with the $0.9M settlement covering the small overage at the contracted unit pricing.
The self-declaration framework was formalised in a contract amendment that documents the event-category methodology and the supporting evidence cadence. The amendment carries forward as the standard for future audit cycles.
The internal SAM function adopted the quarterly measurement cadence and maintains continuous evidence in the IS-U reporting layer. The audit-readiness package now includes the event-category methodology, the per-category counts, and the year-on-year trend.
The contract definition was clear and favourable. We had simply never measured against it. The work was to start measuring on the right definition and to keep measuring.
End-to-end self-declaration defence, event-category mapping, and amendment negotiation across the IS-U engine portfolio.
Read the brief →Self-declaration framework establishment and quarterly event-category measurement.
Read the brief →Engine measurement, self-declaration frameworks, and the contractual definitions that govern the count.
Engine measurement mechanics, including the IS-U event-category model and the self-declaration framework.
How an industrial manufacturer defeated a $9.2M engine claim through document-flow rebuilding.
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 USMM and LAW measurement pillar and the manufacturer engine-claim 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.