The question whether to run an SAP audit response in-house or bring in an independent advisor sits on the desk of every CPO and General Counsel inside the first two weeks of a notification. The instinctive answer — that the in-house SAM team is closest to the data and should therefore lead — misses the structural point. The question is not who knows the SAP estate best. It is who is structurally positioned to negotiate against SAP’s license-compliance organisation. The answer for most enterprises turns out to be a hybrid model, and the design of the hybrid is what determines the settlement value.
What the in-house team is structurally positioned to do
The internal SAM, basis, and architecture functions own the SAP estate. They know which systems are productive, which are sandbox, which integrations are live, which RFC users are in use, where the historical loads sit, and which named users have been left active long after the user left the company. That knowledge is irreplaceable. No external advisor will know the estate at that level of detail in the first six weeks of an engagement. The in-house team is the right home for the operational workstream of the audit response: the USMM extraction, the LAW consolidation, the integration topology questionnaire, the named-user clean-up, the role-mapping correction. The pattern is covered in the related article on the USMM and LAW defensive prep.
What the in-house team is not structurally positioned to do
The in-house team sits in two structural positions that work against it in the negotiation. First, the SAP account team and the in-house technical team have a multi-year relationship that depends on cooperation. The same SAP account director who is escalating the audit is also closing the next renewal, the next module purchase, and the next professional-services engagement. The technical lead who is talking to the account team during the audit is the same person who relies on that account team for support escalations and roadmap visibility. The relationship pressure on the in-house team to be cooperative is real and persistent.
Second, the in-house team is in an operational reporting line. The CIO, the SAM lead, the basis manager, and the procurement category manager all have multiple competing priorities and budgets to defend. An audit settlement that lands at thirty per cent of the opening claim looks like a win against the opening claim but does not look like the same win if the team is later measured against the budget hit. The internal accountability for the cost is real and personal.
An external advisor sits outside both pressures. The advisor has no roadmap relationship to protect and no internal budget line to defend. The advisor can take the procedural and negotiating positions that the in-house team cannot take without consequence.
The hybrid model in practice
The model that consistently produces the strongest settlements has three components. The in-house team owns the operational workstream — measurement, data preparation, named-user remediation, integration mapping. The external advisor owns the channel to SAP — the scope letter, the data-exchange protocol, the position papers, the substantive negotiation, the settlement structure. The General Counsel or CPO owns the matter end-to-end under an engagement letter that protects communications under privilege. The mechanics are covered in the responding to the audit letter article.
Under this model the in-house team does the work it is best positioned to do, the advisor does the negotiation work it is best positioned to do, and the matter is routed through a single accountable owner with privilege protection. The settlements that arrive on this footing are typically two to three times better than settlements run end-to-end by either party alone.
When a fully in-house response is the right call
A fully in-house response is the right call in three specific scenarios. The first is a routine, low-exposure audit on a stable named-user estate with no integration complexity, no recent S/4HANA migration, and no indirect-access history. The second is a buyer with an unusually experienced internal SAP procurement function that has run multiple SAP audits in living memory and has the documented playbooks to repeat the work. The third is a buyer whose SAP spend is small enough that the cost of an external advisor would exceed the realistic settlement saving. Across our engagements, perhaps one in fifteen audits falls into one of these categories.
For everything else — particularly any audit that touches indirect access, digital access, named-user reclassification, or a RISE or S/4HANA conversion — the in-house-only model under-performs the hybrid by enough margin that the advisor cost is several times paid back.
The cost question
An independent advisor on a typical mid-market SAP audit defence engagement carries a fee that lands between one and four per cent of the opening claim. On a five-million-euro opening claim, that is fifty to two hundred thousand euros of advisor fee. The median settlement saving from the hybrid model, against the in-house-only outcome, is between thirty and fifty per cent of the opening claim. On the same five-million-euro claim, that is one-and-a-half to two-and-a-half million euros of saving. The ratio is consistent enough across our practice that the cost question rarely survives a serious analysis of the expected outcome distribution.
The exception is contingent or success-based fee structures, which align the advisor and the buyer on the settlement number. These structures are common in audit defence and are described in the audit defence service page.
How to choose the advisor
The choice of advisor matters as much as the choice to bring one in. Three filters help. First, the advisor must be independent of SAP — not a partner, not a reseller, not in any commercial relationship that creates a conflict on settlement value. Second, the advisor must have specific SAP audit defence experience — general license management or general IT procurement experience does not transfer cleanly to the SAP audit context. Third, the advisor must work under engagement letter with privilege protection, not on a transactional consulting basis. The pattern is described in the SAP RISE topic page and in the global manufacturer case file, which records how the hybrid model was designed in a complex audit defence engagement.
The decision window
The decision to bring in an advisor is best made inside the first two weeks of the notification, before the scope letter goes back to SAP and before the first data-exchange call. Decisions made later are still recoverable — the reset sequence is described in the responding-to-the-audit-letter article — but the cost of a late reset is typically four to eight weeks of additional elapsed time and a settlement that lands at a higher percentage of the opening claim. Audits that bring the advisor in at week one routinely close inside twelve to sixteen weeks at thirty to forty per cent of the opening claim. Audits that bring the advisor in at week ten close more slowly and settle higher. The pattern is consistent enough across the practice that we treat the decision window as the single most important commercial variable in the engagement.
The engagement letter as the routing artefact
The engagement letter that brings the external advisor in does more than appoint the advisor. It establishes the privilege channel that protects communications between counsel, the buyer team, and the advisor. The letter should be drafted by counsel, signed by the General Counsel or CPO, and routed to all internal stakeholders within the first week of the engagement. The letter defines the scope of the engagement, the deliverables, the fee structure (including any contingent element), and the privilege protection that applies to all communications under it. The letter is the routing artefact that determines what is on the record and what is not. The pattern is covered in the audit letter response article.
The handover at the end of the engagement
A well-designed engagement also has a defined handover at close. The advisor leaves the buyer with the artefacts the matter produced: the integration inventory, the licence-position document, the negotiation file, the settlement structure, the contract red-lines, the renewed entitlement schedule. Those artefacts become the buyer’s permanent record of the matter and the input into the next audit cycle. The handover discipline matters more than it sounds — an engagement that closes without it leaves the buyer dependent on the advisor for the next matter as well. The strongest engagements transfer the methodology along with the outcome, so that the in-house team is in a better structural position for the next cycle than for this one.
The strongest in-house teams we work with do not insource the audit response. They run the operational workstream and place the negotiation in an arm’s-length channel.
For any SAP audit that touches indirect access, digital access, named-user reclassification, or a RISE or S/4HANA conversion, the hybrid model with an independent advisor is the structural position that consistently produces the strongest settlement. The SAP Audit Defence Playbook documents the model in more detail.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.