Home / Services / Audit Defence

Audit defence,
from letter to
resolution.

A vendor audit is never just about compliance — it is the opening of a commercial negotiation, with a financial gun on the table. We manage the audit process, narrow the scope, defend the methodology, and convert exposure into commercial terms on your side of the table.

75%+
Avg. exposure reduction
6–12 mo
Typical audit duration
100+
Audits defended
6
Vendor audit programmes
Overview

The audit is the negotiation.

When Oracle LMS, SAP GLAS, Microsoft SAM, IBM IASP or VMware's compliance team open an audit, they are not seeking truth — they are constructing leverage. The exposure number on the first findings report is rarely the final settlement. It is the opening offer.

Our audit defence team takes over the process. We respond on your behalf, control what information leaves the company, challenge methodology that does not match the contract, and resolve the audit through commercial settlement rather than list-price true-up. The typical outcome is a 60 to 90 percent reduction against the first findings number.

Where this service applies

  • Oracle Database, Middleware, E-Business Suite and Java audits (Oracle LMS).
  • SAP licence and digital-access audits (SAP GLAS).
  • Microsoft SAM engagements and partner-led licence reviews.
  • IBM IASP audits across software and middleware.
  • VMware, Broadcom and Cisco compliance reviews.
  • Adobe, Autodesk and SaaS subscription compliance challenges.

What we don't do

We do not run a Software Asset Management tool deployment as the audit response. We do not negotiate "settlement plus expansion" deals the vendor offers as the easy way out. The first job is to get the exposure number to the right size; only then does it become a commercial conversation.

Engage us when

The audit letter has arrived

The earlier we are involved, the better — ideally before the formal scope and tools are agreed. But we routinely engage mid-audit when the findings number is unexpectedly large.

Typical duration

6 to 12 months end-to-end

Most audits run 6 to 9 months. Complex Oracle ULA exits or SAP digital-access disputes can run longer. We are with you from initial response to final settlement.

Engagement model

Fixed-fee or success-based

Audit defence is usually delivered on fixed-fee, with success-based options measured against the vendor's first findings number. See engagement models →

How we work

Audit defence, in six phases.

01

Letter response & protocol

We respond to the audit letter on a professional, contractual basis. We agree the scope, tools, methodology, timeline and confidentiality before any deployment data leaves the company.

02

Internal baseline

We run the equivalent measurement internally first, so we know the real position before the vendor does. Every metric the vendor will request, we have already calculated to our own standard.

03

Data control & submission

We control what data is submitted, in what form, and with what context. We do not let raw script output sit unexplained on the vendor's desk. Every submission is paired with the contractual interpretation.

04

Findings challenge

We challenge every line of the vendor's findings against the contract: editions, products in scope, partitioning, virtualisation, named users, indirect access, multiplexing. The first findings report usually halves before commercial discussion begins.

05

Commercial resolution

Once the technical findings are corrected, the audit becomes a commercial negotiation. We resolve it through forward licensing on negotiated discount — not through retroactive list-price true-up.

06

Posture for the next one

We document the methodology, fix the deployment patterns that created the exposure, and leave you with an audit posture file that protects the next vendor's audit too.

Where audit findings inflate

The methodology lines we routinely challenge.

Challenge 01
Virtualisation & partitioning
Oracle's view of soft partitioning, VMware vMotion, hyperconverged clusters and cloud guest VMs. The contract rarely says what the audit team initially asserts.
Challenge 02
Indirect & digital access
SAP digital-access methodology, integration users, RPA bots, downstream apps. The original contract often pre-dates the audit programme's interpretation.
Challenge 03
Named-user counting rules
Active-user definitions, service accounts, generic accounts, terminated users still in the directory. The script-default headcount is almost never contractually correct.
Challenge 04
Edition & feature use
Enterprise-edition features triggered by accident, monitoring packs auto-enabled, options invoked transiently. Each one is a separate contractual question.
Challenge 05
Multiplexing & aggregation
Multiplexed integrations and aggregation servers that the contract treats differently from how the audit team is treating them.
Challenge 06
Remediation pricing
Settlement at full list price rather than your contractual or negotiated discount. The remedy in the contract is almost never "pay list".

"The first findings letter said $9.4M. Their team challenged the methodology line by line. We resolved the audit for $1.1M of forward licensing — on negotiated discount."

Chief Information Officer
European Telecommunications Group
Outcomes

Recent audit defences.

All case studies

Audit letter on your desk?

Tell us the vendor, the date of the letter, and the scope as the auditor described it. We will tell you within one business day whether we can take it on and how.