Writing the SAP audit position paper

The position paper is the single most leveraged document a buyer produces during an SAP audit. It is not a rebuttal letter, not a settlement memo, and not a technical commentary. It is a self-contained analyst document that records what the buyer measures, what the buyer disputes, and what the buyer concludes about the audited estate. SAP’s licence compliance team works in position papers because procurement counterparts who are serious about an audit work in position papers. The matters that resolve at the lowest percentage of the opening claim across our $180M+ in client savings are the matters where the buyer produced one in the first sixty days. The matters that settle high are the ones where the buyer never wrote anything down at all.

Why the position paper is the highest-leverage artefact

SAP’s opening claim is built on an extract from the buyer’s own systems. The USMM run, the LAW consolidation, the engine measurement, the integration topology questionnaire — these are buyer-supplied inputs that SAP’s team interprets and packages into a finding. If the buyer never produces a counter-narrative in the same format, SAP’s reading becomes the only structured document on the table, and every subsequent conversation argues from that document. A position paper inverts the polarity. It puts the buyer’s reading on the table in the same format as SAP’s reading, and forces the next conversation to argue between two documents rather than between a document and a complaint.

This is not theatre. We have measured it. Across our 500+ engagements, matters where the buyer produced a position paper inside the first sixty days settled at 30-40 per cent of the opening claim. Matters where the buyer never produced one settled at 60-75 per cent. The artefact matters because it changes what SAP’s team can defend internally when escalating settlement authority.

The four sections of a serviceable position paper

A serviceable position paper has four sections. They are produced in this order and read in this order. The first is the executive summary. The second is the methodology and evidence. The third is the dispute schedule, line by line. The fourth is the buyer’s reading of the resolution.

Section one: executive summary

Two pages, maximum. It states the opening claim figure, the buyer’s measured position, the gap between them, the principal causes of the gap, and the buyer’s proposed resolution structure. It is the only part of the document SAP’s commercial leadership will read in full. Every sentence should be defensible from the dispute schedule that follows. No rhetoric, no positioning language, no expressions of disappointment with the audit process. It is an analyst document.

Section two: methodology and evidence

The methodology section establishes how the buyer measured the estate. Which systems were in scope. Which were excluded and why. Which extracts were taken from USMM, LAW, and the engine measurement schedules described in the SAP ECC topic page. Which classifications were applied to user buckets. Which integration patterns were assessed against the indirect-access definition. Every methodological choice is footnoted to the underlying data extract, archived in a controlled evidence pack. SAP cannot dispute a number that is footnoted to a clean extract.

Section three: the dispute schedule

The dispute schedule is the line-by-line accounting. Each line in the SAP opening claim is reproduced with the buyer’s measured equivalent next to it, the variance, and the documented basis for the variance. If SAP has counted 4,800 Professional users and the buyer measures 2,100, the dispute schedule records both numbers, the methodology gap, and the underlying data references. The format is non-negotiable. SAP’s commercial team needs to be able to read down the schedule and see where the gap is recoverable and where it is not.

Section four: proposed resolution

The proposed resolution section sets out the buyer’s view of what closing the matter looks like. It is rarely a single figure. It is more often a structured proposal: a settlement value range, a set of contract clauses to be amended, a commitment on go-forward measurement cadence, and a release. Reasonable resolution proposals get heard. A single figure with no structure attached does not.

The evidence pack behind the document

A position paper without an evidence pack is rhetoric. The evidence pack is the controlled archive of every data extract, every classification logic, every integration assessment, every screenshot, and every commentary that supports the methodology. It is held under engagement letter, indexed, and version-controlled. Every footnote in the position paper points into the evidence pack. When SAP’s team challenges a number, the response is a pack reference, not an argument.

The discipline matters because audits run on elapsed time. The buyer that can produce a referenced exhibit within forty-eight hours of a challenge controls the cadence of the negotiation. The buyer that has to rebuild a calculation each time is at SAP’s tempo. The case file global manufacturer cuts SAP claim 68 per cent describes a pack discipline that resolved the matter in fourteen weeks. The SAP Audit Defence Playbook white paper sets out the pack’s standard contents.

Sequencing: when does the paper go to SAP?

The position paper does not leave the buyer environment on day one. It is built in parallel to the procedural footing described in the first ten days of an SAP audit article, and it is delivered to SAP after the procedural exchange has set the data-exchange protocol. The typical sequence is: notification letter (day 0), procedural footing established (days 1-14), buyer-side measurement workstream (weeks 2-6), position paper draft (weeks 6-8), position paper delivery (week 8-10), settlement negotiation (weeks 10-16).

Delivering the paper before the measurement workstream is complete is a common error. The paper that goes early either lacks the dispute schedule or carries placeholders that SAP can challenge to discredit the rest of the document. Wait until the schedule is complete, the evidence pack is indexed, and the executive summary has been pressure-tested against the underlying numbers.

Tone, format, and who signs the paper

The position paper is signed by procurement or counsel, not by the SAM lead. The signature changes how SAP reads the document. A paper signed by the SAM lead is read as a technical commentary; a paper signed by procurement is read as a commercial position. The distinction matters because SAP’s licence compliance team escalates settlement authority on commercial positions, not on technical commentaries.

Tone matters. The paper is firm but not hostile, factual but not passive. It does not characterise SAP’s audit team negatively. It does not reach for emotive language about the burden of the audit, the disruption to the business, or the quality of SAP’s account coverage. None of those statements are useful, and all of them weaken the analyst posture that makes the document credible. The paper reads like a research note, not a complaint.

The dispute schedule: format that holds up

The dispute schedule is where most position papers fail. The format that holds up is a table with eight columns: claim line item, SAP-claimed quantity, SAP-claimed unit price, SAP-claimed value, buyer-measured quantity, methodology reference, evidence reference, and variance. Every disputed line in the SAP claim has a row. Every row that the buyer accepts also has a row, marked as accepted with no variance. The completeness signals that the buyer has reviewed the entire claim, not just the lines that hurt.

The methodology and evidence references point into the evidence pack. The methodology reference cites the rule by which the buyer measured the line. The evidence reference cites the extract that supports the measurement. When SAP’s team challenges the line, the response is to pull the references and walk through them. The challenge ends or the variance narrows. There is no middle ground.

What a well-built position paper unlocks

A well-built position paper changes the conversation in three measurable ways. First, the settlement value drops because SAP’s commercial team can no longer defend the opening claim internally against a documented buyer position. Second, the elapsed time falls because the negotiation argues between two documents rather than across an open-ended dispute. Third, the contract amendments that come out of the matter are richer, because the methodology section of the paper has surfaced the contract gaps that allowed the dispute in the first place.

The methodology section is also where future audit defence is built. A well-documented methodology becomes the buyer’s standing reading of the estate, and the next audit cycle starts from a defended baseline. The license position statement preparation article describes how the methodology becomes a running artefact, refreshed quarterly, that anchors the buyer’s posture across audit cycles.

If you are in an active audit and have not yet produced a position paper, the priority is to lock in the methodology, build the evidence pack, and produce the executive summary inside three weeks. We work alongside in-house teams under engagement letter. Our SAP audit defence service describes how we structure the work.