The SAP audit engagement letter — how to draft it

The engagement letter for an SAP audit defence is the document that turns an in-house response into a privileged, externally advised, properly scoped procedure. It looks routine on the surface — a one or two page instrument that names parties, fees, and scope — but every clause in it has a specific defensive function. Get the engagement letter wrong and the rest of the audit defence is run on uncertain footing. Get it right and the matter runs predictably through procurement and counsel for the next twelve to sixteen weeks.

Why the engagement letter is filed first

Across every matter we see, the engagement letter is executed before the substantive measurement work begins and before the first written exchange with SAP. The sequence is deliberate. Once the letter is signed, communications between the buyer team, the advisor, and counsel are protected as work product. Once measurement begins without the letter in place, those communications are not protected, and the SAP audit team can request them under the data-exchange protocol. The cost of that difference, in matters we have seen, runs into the millions.

The engagement letter is also the document that defines the chain of command. It names the General Counsel or Chief Procurement Officer as the engagement principal, names the advisor as the technical lead, and explicitly subordinates the SAM team, the basis team, and the SAP account-team relationship to the engagement principal. Without that, the SAP account team will continue to call the basis lead directly, and informal commitments will leak.

The eight clauses that always appear

An engagement letter built for an SAP audit defence contains eight standard clauses. Each has a specific defensive purpose, and missing any of them creates exposure later in the matter.

• Parties and engagement principal — names the buyer entity, the advisor, and the single accountable principal inside the buyer.
• Scope — defines the audited period, the in-scope entities, the in-scope products, and the defensive work product to be produced.
• Privilege footing — confirms that the engagement is under counsel direction and that all advisor work product is privileged.
• Communications protocol — defines who can speak to SAP, in what form, with what cadence.
• Data exchange — defines what data leaves the buyer environment, in what form, with what commentary.
• Fee structure — fixed-fee or hourly with cap; success-fee components if any.
• Retention and conflict — confirms the advisor is not an SAP partner and has no SAP commercial relationship.
• Termination and transition — defines how the engagement can end and how work product transfers.

The scope clause in detail

The scope clause does more than describe what the advisor will do. It defines the universe of audit-relevant work product that will be produced. The clause should reference the audit-rights clause in the SAP master agreement by section number and date, name the audited period, list the in-scope SAP product lines, and list the substantive deliverables: independent measurement, position paper, scope letter, negotiation strategy, and settlement memorandum. If indirect access or digital access are in scope, the clause should call them out explicitly, because the measurement methodology for those workstreams is different and the work product they generate is more sensitive.

A scope clause that is too narrow leaves work product unprotected. A scope clause that is too broad creates a fee dispute later. The right scope is the audit cycle as defined in the SAP notification letter, with explicit allowance for follow-on negotiation if the audit closes into a renewal or RISE conversation. The pattern is documented in the SAP Audit Defence Playbook white paper.

The privilege footing

For the privilege footing to hold, the engagement letter must do three things. It must name counsel as the engagement principal or as a co-engaging party. It must confirm that the advisor is engaged to assist counsel in providing legal advice on the audit matter. And it must define all advisor work product — measurement files, position paper, scope letter drafts, negotiation memoranda — as work product produced at counsel direction.

The framing matters. Privilege in commercial-audit matters is often tested when the audit closes into a contested settlement or, in rare cases, a dispute. The advisor's measurement files are the most contested category of work product because they contain the buyer's reading of the data. A clean privilege footing in the engagement letter protects those files. A weak footing exposes them.

What the privilege clause should not say

The clause should not promise absolute confidentiality. It should not claim privilege over data extracts that originate from the SAP systems themselves — those extracts are not privileged and pretending otherwise causes problems later. The privilege protection extends to advisor analysis, advisor commentary, advisor recommendations, and counsel directions. The raw data is what it is. The reading of the data is privileged.

The communications protocol clause

One of the most important clauses, and the one that buyers most commonly leave out, is the communications protocol. It names the single channel through which all written and verbal communication with SAP will flow. It names the engagement principal as the gatekeeper. And it instructs all internal teams — SAM, basis, application owners, regional leads — to route any SAP contact through the principal without informal exception.

The clause is the operational counterpart to the privilege footing. Privilege protects what the buyer team says to counsel and to the advisor. The communications protocol controls what the buyer team says to SAP. Without the protocol, the SAP account team will continue to call basis leads directly, and informal commitments will leak into the audit file. With the protocol, every call is routed through procurement and every email goes through counsel review before transmission. See also the article on responding to the notification letter for the operational sequence in the first ten days.

The fee structure question

SAP audit defence engagements typically use one of three fee structures. A fixed fee for the full audit cycle, sized to the complexity of the landscape. An hourly fee with a defined cap. Or a hybrid structure with a fixed base fee plus a success component tied to the reduction in the opening claim. Each has tradeoffs. Fixed fees give the buyer cost certainty but require the scope to be tightly defined. Hourly with cap is most flexible but requires monthly reconciliation. Success components align incentives but require careful definition of the baseline — usually the opening claim figure in the first SAP position paper.

Across the matters we work, the most common pattern is a fixed base with a modest success component. The fixed base covers the procedural work — engagement letter, scope letter, data-exchange protocol, measurement, position paper. The success component is tied to the gap between the opening claim and the final settlement. Specific benchmarks are documented in the SAP price benchmark article.

The conflict-of-interest clause

The conflict-of-interest clause confirms that the advisor is not an SAP partner, does not hold an SAP reseller agreement, and does not receive any commission, referral fee, or commercial benefit from SAP or from any SAP-affiliated entity. The clause is short — typically a single paragraph — but it is the structural foundation of independent advice. Without it, the advisor is, at best, a vendor with a divided loyalty. With it, the advisor is buyer-side only, with no commercial reason to advise toward a particular SAP product or commercial outcome. The principle is described on the SAP audit defence service page and is one of the standard questions covered in the RISE topic page when conversion comes up.

The termination and transition clause

Engagements end. Sometimes the audit settles cleanly and the engagement closes on schedule. Sometimes the buyer reorganises, the audit pauses, or the matter converts into a renewal negotiation that needs different scope. The termination clause defines how the engagement can be wound down without leaving work product unprotected. It typically gives both parties a thirty-day notice right, defines fees up to the termination date, and confirms that all work product produced under the engagement remains privileged after the engagement closes. The clause should also confirm that the advisor will not subsequently act for SAP on the same matter — a standard provision in advisory engagements.

If you are about to engage an independent advisor for an SAP audit, the engagement letter should be on the table in the first conversation, not negotiated after the work has started. Our standard form runs to two pages and is reviewed by buyer-side counsel in every matter. The global manufacturer case file includes a redacted version of the engagement letter used in that matter, and the contract clause article covers the parallel clauses inside the SAP master agreement that the engagement letter cross-references.