An industrial manufacturer challenged the Ariba document-count methodology, removed three categories that were never contracted as billable, and settled the overrun claim at sixty-seven per cent below the opening figure.
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 client is a mid-cap industrial manufacturer of specialty packaging and converting equipment with revenue near one point six billion dollars and operations across the United States, Canada, and the United Kingdom. The Ariba Network had been in production since 2019, connecting roughly nine thousand four hundred active suppliers across direct materials and indirect spend.
Eleven months into the contract year, SAP issued a document overrun claim of two point eight million dollars. The notification cited a measurement period covering the prior twenty-four months and asserted that document volume across multiple categories had exceeded the contracted tier by a margin large enough to require a retrospective true-up and forward re-tiering.
The procurement team had no working baseline of which documents counted, in which categories, or against which contractual limits. The first action was to put the audit on a written footing and obtain the raw measurement output from SAP.
SAP's claim assembled document counts across six categories: purchase orders, order confirmations, ship notices, invoices, payment remittances, and 'service entry sheets'. The aggregate document count exceeded the contracted band by approximately one point seven million documents over the measurement period. The asserted true-up combined per-document overage pricing with a tier re-set going forward.
The contract language defining 'billable documents' had been carried forward through two prior renewals and had not been re-stated in plain language since the original signing. The account team's interpretation was that all six categories counted; the contract text was less clear.
Linkage was also signalled to a forthcoming renewal conversation, with credits available to offset the true-up against a new multi-year commitment.
We obtained the raw measurement and reconstructed the document classification line by line. Two of the six categories — payment remittances and service entry sheets — were demonstrably outside the original contract definition of 'billable documents'. Removing those two categories reduced the asserted count by approximately seven hundred and twenty thousand documents.
Within the remaining categories, approximately three hundred and ten thousand documents were system-to-system traffic between client subsidiaries and not third-party supplier transactions. The contract definition of billable documents excluded intra-group traffic explicitly. The line item was removed in full.
Once the corrected document count was established, we re-walked the tier band methodology against the contract schedule. The actual overrun was approximately two hundred and twenty thousand documents, not one point seven million. The unit price for the excess was negotiated against the bulk-tier rate, not the per-document overage rate.
We refused to settle without a written release confirming no further claim could be raised on the measurement period. We also added a forward measurement-cap clause limiting any future true-up to documented bulk-tier pricing.
Settlement closed at nine hundred and twenty thousand dollars against the opening claim of two point eight million. The reduction was approximately sixty-seven per cent. The forward tier was re-set to the corrected document band, without the inflated multi-year commitment that the account team had signalled.
Three contract changes were written into the settlement: the billable-document definition was re-stated to exclude intra-group traffic and the two challenged categories; a measurement-cap clause was added for future true-ups; and a settlement-as-release clause closed the measurement period.
Total elapsed time from notification to signed release was fourteen weeks, allowing the matter to close before the year-end audit cycle.
Two of the six categories should never have been in the count. By the time we re-walked the methodology, the claim halved.
From the moment the document-overrun notice arrives, we take control of the matter. Measurement validation, evidence assembly, and a written release at the end.
Read the brief →Every audit closes with a contract. We draft the release language, the measurement-cap clause, and the renegotiated billable-document definition.
Read the brief →The dedicated topic page covering licensing structure, audit exposure, and the negotiation playbook for SAP Ariba.
The full Ariba audit response sequence with the document-classification checklist we use in every matter.
The three Ariba editions, what each one actually meters, and where the document-overrun risk lives.
A Fortune 500 industrial group reduced an Ariba renewal uplift from $4.6M to $1.8M.
A regulated utility rolled back an Ariba re-tier after demonstrating the methodology was non-contractual.
Browse the complete library of anonymised SAP audit, renewal, and indirect-access defence engagements.
An audit notification, a renewal proposal, or a contract clause that does not read clearly — the first conversation is at no cost and under privilege. Forty years of buyer-side SAP experience, $180M+ in client savings, 500+ engagements.
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.