Organisations in Australia facing an SAP audit are tested most on indirect, or digital, access — the document-based charge that arises when third-party systems read SAP data — alongside named-user classification and the S/4HANA conversion. This page covers the SAP audit climate in Australia, the local legal context, and the firms that defend the pair, listed alphabetically with pros and cons, not ranked.
Last reviewed: 5 June 2026
SAP runs annual system measurement through USMM and LAW and pursues compliance via its Global License Audit & Compliance group, with around 30% of organisations reporting at least one SAP audit (2025 surveys; indicative). Australia has a concentrated SAP base in mining and resources, utilities, government and large retail, where SAP often sits at the centre of the estate and is surrounded by integrations — precisely the pattern that generates indirect-access exposure.
The signature Australian risk is third-party systems — Salesforce, e-commerce, bespoke integrations and bots — reading or writing SAP data and triggering document-based digital-access charges. With the 2027 ECC end-of-mainstream-maintenance deadline driving S/4HANA and RISE conversions, measurement is increasingly tied to migration, so the timing of any conversion shapes the licence position as much as the raw user count.
The named-user, engine and digital-access mechanics that decide the number, the same worldwide but enforced locally.
ECC and S/4HANA named-user types plus engine metrics; user misclassification inflates the count.
Third-party systems reading SAP data trigger document-based digital-access charges — the signature high-value finding.
Annual system measurement runs via USMM and LAW; what it reports shapes the claim.
The S/4HANA conversion and 2027 ECC deadline drive conversion-linked measurement.
Reclassifying over-provisioned named-user types is the most common reduction lever.
Audits run through SAP Global License Audit & Compliance (GLAC).
Australia is a common-law jurisdiction in which limitation periods are set by each state and territory; for a simple contract claim the period is commonly six years (for example under the Limitation Act 1969 in New South Wales), running from when the cause of action accrues. SAP agreements in Australia are usually contracted through the local SAP entity and frequently carry an Australian governing-law clause, so the audited period and back-charges turn on the specific agreement and its measurement provisions.
Data handover is constrained by the Privacy Act 1988 and the Australian Privacy Principles, which regulate how personal information is used and disclosed and place conditions on sending it offshore to an auditor. Government buyers procure through panel arrangements that add an approval layer to any settlement. Commercial disputes are often routed to arbitration. This page is information about the Australian environment and SAP’s practices, not legal advice.
This page is general information about the Australia legal and procurement environment and SAP’s audit practices, not legal advice for your situation. SAP’s program is described factually; figures are labelled indicative.
Listed alphabetically with balanced pros and cons — a directory, not a ranking.
ServiceNow-centric licensing and estate-reconciliation practice that also covers Salesforce, Oracle, Microsoft, SAP, IBM and Adobe. Reconciles entitlement against actual consumption ahead of renewals and reviews.
One of the largest SAM teams in Australia and New Zealand, offering multi-vendor software asset management, licensing consultancy and procurement. ANZ-native with on-the-ground presence across the region.
Big Four professional-services network offering multi-vendor SAM and license-compliance advisory. Deloitte member firms are also appointed by publishers, including IBM and SAP, to run license audits of their customers.
Independent enterprise-software advisory founded in 2014 by Doug Gibson. Explicitly does not resell, implement, or audit software, and runs a structured three-phase audit-defence methodology across the major publishers.
Independent, vendor-neutral software advisory formed by uniting IBM, Microsoft, Oracle, and SAP specialists under one alliance, with a defined Tier-2 practice for Adobe, Autodesk, Micro Focus, Quest, TIBCO, Veritas, and VMware.
Big Four professional-services firm with a multi-vendor software-advisory practice and global delivery in every major market.
Independent, buyer-side enterprise licensing advisory with the broadest multi-vendor coverage in this directory.
Independent IT sourcing and negotiation advisor working on large SAP, Microsoft, Oracle, Salesforce, ServiceNow, and Workday deals, renewals, and contract resets, with no vendor ties.
DEMO — listings are compiled from public information and labelled demo until the verified registry is live. Firms are listed alphabetically, never ranked. Independence is shown as a pro; reseller, Big Four or vendor-side audit ties are shown as a con — each a factual trade-off for you to weigh.
SAP claims in Australia typically resolve through negotiated settlement, and SAP frequently prefers to convert exposure into an S/4HANA or RISE migration commitment rather than collect a one-off back-charge. What moves the number is a clean USMM/LAW reconciliation, contesting or re-scoping the digital-access document count, reclassifying over-provisioned named users, and timing the conversation against SAP’s quarter and 31 December year-end.
Indicative outcomes vary widely by estate and are not scored here: independent firms report meaningful reductions where the digital-access scope is challenged or named-user types are corrected, but any figure a firm cites is self-reported and indicative until independently verified.
Up to the SAP hub and the Australia hub, across to sibling markets and services.
It is the charge that arises when third-party systems — a CRM, an e-commerce front end, a bot or a bespoke integration — read or write SAP data without a named-user licence. Under the 2018 digital-access model the exposure is measured by document counts, which is why mapping and scoping the integrations is central to the defence. This is information, not legal advice.
SAP counts the initial creation of certain document types generated through indirect access. The count is sensitive to how integrations are designed and to which document types are in scope, so an independent review of the document model frequently changes the number materially.
It can. Moving from ECC to S/4HANA or RISE re-bases the licence model and is often the point at which SAP ties measurement to the migration, so the timing and structure of a conversion shape the licence position and the settlement options.
SAP’s reach is set by your agreement, usually with the local SAP entity under an Australian governing-law clause; separately, state limitation periods — commonly six years for a simple contract claim — apply. Confirm the position for your specific contract and state with qualified counsel.
No. Every firm covering SAP in Australia is listed in neutral alphabetical order with balanced pros and cons. Independence is shown as a pro and Big Four or vendor-side audit ties as a con, never a ranking or a recommendation.
Tell us your situation and we route your brief to firms covering SAP in Australia. The directory and matching are free for buyers, no vendor ever sees your brief, and no firm is recommended over another.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.