Section I · The Brief
The FI document-line claim
The pharma group's SAP FI estate spanned four ECC instances and one S/4HANA Finance instance, all consolidated under a single tiered engine licence on annual FI document lines. The 2024 self-declaration produced a figure of 412 million document lines, against a contracted tier ceiling of 280 million. SAP's commercial team calculated a $14.3M overage, with a parallel three-year retrospective threatening a further $32M in cumulative exposure.
The opening claim arrived eleven weeks before the next renewal, with language tying acceptance to the renewal terms. The internal finance leadership had reviewed the 412 million figure and treated it as essentially uncontestable on the basis that the figure was generated by SAP's own measurement utility. We were engaged to test that assumption.
The first observation was that 412 million is a very large number for an estate of that size. The peer benchmark for a global pharmaceutical group of comparable revenue and structure is approximately 180 to 240 million FI document lines per year. The 412 million figure was nearly double the benchmark, which suggested either a measurement error or an inclusion of categories that peers excluded.
Section II · The Opening Claim
The opening position
SAP's opening position rested on the raw 412 million figure from the standard measurement run. The workpaper applied the tier overage rate to the 132 million lines above the contracted ceiling, producing the $14.3M claim. The retrospective exposure applied the same methodology to the prior three years' self-declarations, all of which had used the same measurement utility.
We obtained the full FI document table extracts for the measurement year across all five instances. The categorical deconstruction took eight engagement-weeks and produced a breakdown across nine categories: 168M external business postings, 92M intercompany reconciliation lines, 48M system-generated automatic clearing entries, 38M tax-determination posting lines, 24M reversed-and-restored document lines, 18M cost-allocation distributions, 14M closing-process entries, 8M technical adjustment postings, and 2M other.
Only the first category — 168 million external business postings — matched the contract definition of an FI document line subject to the engine metric. The remaining 244 million lines fell into categories that were either system-generated, internal reconciliations, technical adjustments, or reversal-restorations. Each category had a documented exclusion basis under SAP's own measurement notes or under the executed contract language.
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. The samples were drawn from each of the five instances proportionally and submitted as testable evidence.
The second workstream addressed the system-generated automatic clearing lines — the 48M category. SAP's own measurement note from 2019 explicitly excluded automatic clearing entries from the FI engine metric on the basis that they were system-generated reconciliation activity, not productive postings. The clearing-entry document types were programmatically identifiable, and the exclusion was uncontroversial once the document types were named.
The third workstream addressed the intercompany reconciliation lines — the 92M category. The pharma group's intercompany volume was elevated due to the cross-border manufacturing-and-distribution structure: each external sale generated approximately three intercompany posting lines as the inventory moved through the corporate structure. The contractual engine definition referenced "external business postings," with intercompany activity historically excluded by precedent. The precedent was documented in two prior settlements between SAP and pharma-sector clients, which we cited with permission.
The fourth workstream was the reversal-restoration category — the 24M lines. Under SAP's standard accounting model, a reversed document generates both a reversal line and a restoration line, doubling the line count for what was a single business event. The contractual measurement should count the net postings, not the gross. The exclusion was procedural rather than evidentiary, but it removed 12 million lines from the total. The counter-position offered a settled figure of 168 million external business postings for the current year, with a $4.2M payment to close the historical period and a renewed tier of 220 million annual lines.
Section IV · The Settlement
The settlement
Settlement closed at the proposed $4.2M figure with the proposed amendment. The retrospective was withdrawn in full on the basis that the same measurement methodology had been used in prior declarations and accepted by SAP at the time, making the retrospective a methodology dispute rather than a compliance enforcement. The forward tier was renewed at 220 million annual lines.
The amendment was the durable outcome. The seven exclusion categories were now explicit in the contract, removing the need for category-by-category re-argumentation in the next cycle. The finance shared-service team adopted the categorical reporting in their quarterly licence-position reviews, surfacing any drift before the next self-declaration.
Total elapsed time from engagement to executed settlement was twenty weeks. The reduction against opening was 71 percent. The renewal closed on the original schedule.
Section V · Lessons Applicable
Five lessons for the next FI engine claim
- The raw FI document-line count is not the engine measurement. The engine measurement is the count filtered by the contract definition. The two figures diverge by 40 to 70 percent in pharmaceutical and other intercompany-heavy estates.
- Intercompany reconciliation lines are not external postings. The cross-border manufacturing-and-distribution model generates multiples of the external posting volume. The exclusion is precedented.
- Automatic clearing entries are system-generated reconciliation, not productive postings. SAP's own 2019 measurement note documents the exclusion. Cite it explicitly.
- Reversal-restoration pairs should be netted, not summed. The procedural fix removes a measurable percentage of the total at no contractual risk.
- Refine the engine definition in the renewal amendment. The seven exclusion categories are now contractually protected. Future cycles run cleanly on the first submission.
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 FI engine document-line volumes. The topic landing at Engine Metrics provides the broader category context.
