The most common procurement mistake in an SAP audit dispute is to negotiate inside SAP’s framing of the finding. The audit letter lands, the procurement team studies the line items, and the response is a series of objections to specific numbers — the user count is wrong, the engine metric is overstated, the maintenance back-charge calculation is excessive. This is the conversation SAP wants to have. It accepts that the audit framework is valid and disputes only the arithmetic.
A counter-offer letter does something different. It establishes a parallel framing of the licensing position, supported by the customer’s own evidence, and presents a written settlement proposal at a substantially lower number. The audit becomes a negotiation between two positions rather than a defence against one. In our experience across 500+ engagements, customers who lead with a structured counter-offer letter close findings forty to seventy per cent below the auditor’s opening number, even when the underlying technical position is largely conceded.
When to send the counter-offer
Timing is the single most important variable. The counter-offer is most effective when sent between fourteen and twenty-eight days after receipt of the formal audit finding letter — long enough that the customer can demonstrate they have analysed the finding in detail, short enough that SAP’s account team has not yet anchored an internal expectation around the opening number.
Sending too early signals reactivity and weakens the implicit threat of a longer dispute. Sending too late lets SAP’s internal commercial process lock the finding into a quarter-end revenue plan, after which discount latitude evaporates. The two- to four-week window is where the account team has the discretion to settle and the pressure to do so.
The structural anatomy of an effective counter-offer
The letter has seven sections, each playing a specific role. Skipping any of them measurably weakens the impact, because each section either establishes credibility, narrows the scope, or builds the leverage that supports the proposed number.
1. The framing paragraph
The opening paragraph acknowledges receipt of the finding, expresses the customer’s commitment to compliance, and signals that the response is a settlement proposal rather than an objection. Tone matters: confrontational openings invite escalation; constructive openings invite settlement. The framing also establishes the document as a "without prejudice" communication for negotiation purposes only.
2. The scope-of-finding clarification
The second section identifies which specific elements of the finding the customer accepts in principle, which it disputes on technical grounds, and which it considers outside the scope of the audit clause in the licence agreement. Even where the customer intends to settle the entire finding, this section is essential — it establishes a written record that the audit scope has been examined and challenged on contractual grounds.
3. The evidence summary
A two- to three-paragraph summary of the customer’s own measurement evidence, with cross-references to attached exhibits. This is where USMM reconciliations, role-content analyses, engine-metric recalculations, and any third-party verification reports are introduced. The evidence does not need to definitively rebut the finding; it needs to demonstrate that the customer has a defensible alternative measurement that SAP would have to litigate to dismiss.
4. The pricing-convention challenge
The most consistently undervalued section. Even where the customer accepts the underlying volume finding, the price applied is negotiable. The auditor’s opening number typically uses current list price multiplied by maintenance back-charges across the prior contract years. None of those numbers are fixed in the licence agreement. The customer’s counter-offer challenges the unit price (proposing the existing weighted-average discount), the back-charge window (proposing current contract year only), and the maintenance multiplier (proposing prospective basis). These three challenges alone typically move the finding by thirty to fifty per cent without any change to the underlying compliance position.
5. The proposed settlement number
A single, specific dollar figure that the customer is willing to settle for, supported by the prior sections. The number should be approximately thirty to forty per cent of the auditor’s opening position — low enough to anchor the negotiation downward, high enough to remain credible. Round numbers are more credible than precise ones; "$3,400,000" reads as a negotiation position, "$3,427,816.42" reads as an arithmetic submission.
6. The non-monetary terms
The settlement proposal should include non-monetary terms that improve the customer’s position going forward: a written closure of the finding without prejudice to future audits, a defined measurement protocol for the next USMM cycle, an extension of the audit-rights cooling-off period, and a commitment from SAP not to back-apply the same finding methodology in subsequent audits. These terms cost SAP nothing in the current quarter and are routinely conceded when the monetary settlement is reached.
7. The escalation path and signature
The closing section identifies the customer-side decision-makers, the expected SAP-side counterparts, and the proposed sequence of meetings to close the finding. It is signed by the procurement executive with contract authority, not the SAP administrator who manages day-to-day licensing. The seniority of the signature signals that the counter-offer carries executive sponsorship and that delay or rejection will result in escalation rather than capitulation.
The eight clauses that always appear
Across the counter-offer letters we have drafted in active matters, eight specific clauses appear in every successful settlement. They are mechanical, defensible, and rarely contested by SAP’s commercial team once the broader settlement is in motion.
- Without-prejudice language establishing the letter as a settlement communication.
- Reservation of rights regarding any matters not specifically addressed in the proposed settlement.
- Existing-discount anchor for all proposed unit pricing.
- Prospective-maintenance application excluding back-charges beyond the current contract year.
- Defined measurement methodology for the next audit cycle, eliminating ambiguity that produced the dispute.
- Written closure of the finding upon settlement payment, with no carry-forward to future audits.
- Confidentiality provision preventing disclosure of the settlement terms.
- Severability clause ensuring that disagreement on any single element does not collapse the entire settlement.
What happens after the counter-offer is sent
SAP’s typical response to a structured counter-offer is a counter-counter — a revised finding letter that accepts some of the customer’s evidence challenges, rejects others, and proposes a number between the customer’s opening and SAP’s. This is the negotiation working as designed. The conversation that follows is bounded by the framing of both letters rather than by SAP’s original finding letter alone.
The most important discipline at this stage is to resist the temptation to "split the difference". The customer’s counter-offer is a credible settlement proposal in its own right. SAP’s counter-counter is a negotiating position. The next move from the customer should be a refined counter-offer at approximately ten to fifteen per cent above the original, supported by additional evidence where the customer has it. The settlement typically lands within one to three further exchanges.
For more on managing the broader response sequence, see our first 72 hours playbook and audit letter escalation handling articles, along with the audit defence playbook white paper.
The independent-advisor question
Counter-offers drafted by internal procurement teams without independent context typically anchor too high — conceding the audit framing while disputing the arithmetic. Independent advisory adds calibration: what range of settlement is achievable on similar findings across other customers, what specific evidence SAP’s commercial team weighs most heavily, and what non-monetary terms the customer can realistically extract. For a real example of how this played out in a $14M-to-$2.3M reduction, see our global manufacturer audit defence case file. For the broader contract-negotiation context that surrounds the counter-offer, see our SAP Contract Negotiation service.