The audit statement of position: a template

Most SAP-audit defence writing focuses on what happens after the final report. The statement of position is the document that goes in before it. A statement of position filed eight to ten weeks into the audit — after measurement is substantially complete but before SAP’s audit team has drafted the formal report — changes the geometry of the finding. SAP’s draft is then written against a buyer-side statement that is already on file, rather than into an empty space. The statement of position is the cheapest single intervention in the entire audit defence cycle. It is also the one most buyers omit.

Why the timing of the SoP matters

SAP’s audit team writes the draft report on a defined internal timeline. The drafting work begins once measurement is substantially complete. The team reads the measurement, the integration topology, the engine extracts, and the questionnaire responses, and constructs a draft narrative of the findings. The draft narrative is internally reviewed, sharpened, and converted into the formal draft report shared with the buyer.

The buyer’s statement of position has to be on file before the draft narrative is constructed. Once the narrative exists, the SAP team is invested in the narrative. The buyer’s rebuttal then has to overcome the team’s own writing, which is heavier work than writing into an empty draft. The eight-to-ten-week window is the practical timing in most matters. The companion final-report rebuttal method article covers the post-report sequence; the SoP is the pre-report variant.

The four sections of the statement

A defensible statement of position has four sections. Each section addresses a distinct dimension of the finding the SAP team is about to draft.

Section one: the methodology

The methodology section states the buyer’s methodology for measurement and classification. It references the contract clauses, the relevant SAP notes, and the audit-protocol exhibits. It explicitly names the buyer’s methodology choices on the contested points — named-user category boundaries, engine-metric counting, integration classification — and explains the rationale for each. The methodology section is the foundation; everything else in the SoP refers back to it.

Section two: the measurement

The measurement section presents the buyer’s own measurement against the methodology in section one. The measurement is sourced from the buyer’s independent run — not from the USMM extract sent to SAP. The measurement is presented as numbers, in the form of the SAP findings the buyer expects to see, so that the eventual draft report can be read directly against the SoP. The USMM and LAW measurement checklist covers the independent measurement protocol.

Section three: the position

The position section states the buyer’s position on each anticipated finding category. Where the buyer agrees with the anticipated finding, the position says so explicitly. Where the buyer disagrees, the position states the alternative and the basis. The position section does not negotiate against findings the buyer expects SAP to make; it states the buyer’s view of each anticipated category and waits for the formal draft to land.

Section four: the procedure

The procedure section addresses the audit procedure itself — the data-exchange protocol, the meeting cadence, the escalation contacts on both sides, and the resolution timeline. The procedure section confirms what has been agreed at the engagement letter stage and serves as a procedural anchor for the post-report negotiation.

What the SoP changes in the draft report

SAP’s audit team writes the draft report after reading the buyer’s SoP. The draft is written either in alignment with the SoP or in explicit divergence from it. The cases that divergence is most likely are in section two (measurement) and section three (position) on contested classifications. The cases of alignment are most common in section one (methodology) and section four (procedure).

The buyer’s SoP closes the methodology argument before the draft is written. If the methodology in the SoP is consistent with the contract and the SAP notes, the draft report typically accepts the methodology and disputes only the application. That is the geometry the SoP is built to produce. The substantive disputes then are about classification of specific cases, not about the rules themselves. The global-manufacturer case file documents a deal where the SoP closed the methodology argument on day fifty-two of the audit window.

The tone and length of the SoP

The SoP is short and formal. A typical SoP runs twelve to twenty pages, with the methodology section the longest. The tone is procedural and analytical, not adversarial. The SoP is not a litigation brief; it is a structured position paper that the SAP audit team can read into the draft.

The tone matters because the SAP team will read the SoP through several reviewers. A tone that reads as procedural and reasonable is read carefully. A tone that reads as adversarial is filtered through the legal-review channel and absorbed into a different process — one that takes longer and produces a more defensive draft.

What the SoP does not include

Three categories of content should not appear in the SoP. Settlement-structure proposals, including any indication of what the buyer would settle at or what credits the buyer would seek — the SoP is not a settlement document and including settlement terms anchors the negotiation prematurely. Commercial roadmap content, including statements about future contract structure or product direction — the SoP is bounded to the audit matter, and broader commercial content invites broader commercial reading. Statements about the buyer’s internal organisation, including process failures, organisational gaps, or remediation in progress — the SoP is the buyer’s formal position, not its self-assessment.

The distribution of the SoP

The SoP is filed with the named SAP audit contact, cc'd to the buyer’s named contact at counsel, and circulated internally to the small steering group running the matter. It is not distributed widely inside the buyer organisation. The internal distribution should mirror the privilege protocol from the engagement letter. The SAP audit defence service page describes the engagement-letter and privilege structure.

The SoP is dated. The date is referenced in subsequent correspondence. If the draft report misrepresents a position taken in the SoP, the dated SoP is the artefact the buyer references in the rebuttal. The dating is procedurally important and small enough to overlook; we have seen matters where the SoP was effectively retracted because the date was vague enough that the SAP team was able to date the engagement differently.

When the SoP is not appropriate

Two scenarios where the SoP should not be filed. The first is when measurement is not yet substantially complete and the buyer’s position on contested findings is still in flux. An SoP filed prematurely commits the buyer to a position that has to be amended later, and amendments are read as weakness. The second is when the matter is in an active settlement negotiation that has reached a structural agreement — in that scenario the SoP is folded into the settlement discussion and need not be filed separately. The SAP RISE topic page covers the variant where the audit and a RISE conversion are running concurrently.

If you are inside an audit and measurement is substantially complete, the most efficient next step is a scoping conversation about whether the timing supports an SoP and what the structure would look like. We work alongside in-house teams under engagement letter. The first conversation is at no cost.