Most of the engine entries in a USMM extract are produced by counter readings the SAP system maintains automatically. A smaller but commercially important set of engines are not measured by the system at all. The buyer declares the consumption manually in a self-declaration field on the USMM submission. The declaration is the position of record. The system has no independent reading against which to check it. The flexibility this creates for the buyer is balanced by an evidence-burden the buyer carries entirely — if an auditor challenges the declared number, the buyer must produce supporting documentation that justifies it. The self-declaration engines are a small list but they include several of the more expensive line items on the SAP price sheet, which makes the declaration discipline economically significant. This article walks through which engines fall into the self-declaration category, the documentation discipline that supports declarations, and the audit pattern that follows when a declared number is challenged. It complements our broader USMM and LAW advisory work.
Why some engines are self-declared
The self-declaration mechanic exists for engines where the licensed metric is not technically observable by the SAP system. The meter does not read the consumption because there is no meter that can. The cleanest example is the named-user count for non-dialog user types — service users, system users, communication users — where the SAP system records the user but does not classify the licence type. Another is licences denominated in business units the system cannot calculate — the number of physical locations connected to a Plant Maintenance instance, the number of legal entities consolidated in a financial-reporting module, or the number of countries in scope for a global Payroll engine. In each case the licensed metric refers to a business fact that exists outside the SAP system, and the SAP system can only record what the buyer asserts. The USMM and LAW pillar covers the broader measurement mechanics.
The self-declaration engine list
The current self-declaration list varies slightly by contract vintage, but the principal entries are consistent across estates.
Plant Maintenance — physical locations
Licensed per physical location connected to the PM engine, the declared number is the count of physical sites at which the PM functionality is in use. The SAP system has no direct visibility of which sites are operationally connected and which were configured for project-trial purposes and never activated. The buyer’s declaration is the only number on record.
Payroll — countries in scope
Licensed per country processed by the Payroll engine, the declared number is the count of countries for which payroll is operationally run. Countries configured but not actively processing payroll do not, in the contract definitions of most agreements, require a licence. The distinction depends entirely on the buyer’s declaration.
Treasury — managed entity count
Licensed per legal entity reporting through the Treasury module, the declared number is the count of operational entities. Entities consolidated but reporting through a different system, or entities reporting historic-only data without active treasury management, are excluded. The exclusion depends on the buyer-side documentation.
Indirect-access scenarios — user equivalents
Where the contract structure uses a user-equivalent metric for indirect access (rather than the document-based digital access metric), the declaration is the count of unique non-SAP users with indirect interaction with the SAP system in the measurement period. The SAP system records the integration but cannot independently count the upstream users. The indirect access pillar covers the policy landscape, and the indirect access advisory service brief covers the engagement structure.
The documentation discipline
The economic value of the self-declaration flexibility is realised only if the declarations are documented to a standard that survives audit challenge. The discipline has three components.
Source-of-truth identification
Each declaration must have a designated source of truth outside the SAP system. The Plant Maintenance location count is typically sourced from the corporate property register. The Payroll country count is sourced from the corporate HR-systems list. The Treasury entity count is sourced from the legal-entity register. The declared number cites the source and the date.
Per-declaration evidence file
For each declared engine, a brief evidence document records the source, the extraction date, the responsible owner, and the calculation that produced the declared number. The document is two or three pages and is updated annually as part of the USMM preparation. Estates with this discipline pass audit challenges on declared engines reliably. Estates without it have lost the declaration position in roughly half the audits we have defended.
Override register integration
Each declaration is recorded in the USMM override register with the same documentation standard applied to user-side reclassifications. The auditor sees a single register that covers both halves of the measurement and follows a consistent evidence pattern. See the USMM run preparation note for the register structure.
One global pharma client carried a 174-location Plant Maintenance declaration into an SAP audit. The auditor challenged the number and requested supporting documentation. The client’s evidence file produced a one-page extract from the corporate property register cross-referenced against the SAP PM configuration, with the location-by-location reconciliation that supported the declaration. The challenge closed in two business days, against a typical six-week defence timeline for unsupported declarations.
How auditors approach self-declarations
The audit team’s first question on a self-declared engine is the source of the declared number. If the buyer cannot produce a source within the first week of the audit conversation, the auditor will propose to substitute a default number derived from an SAP-side reference — typically a configuration-table count that is materially higher than the operational reality. The substitution is the audit team’s leverage. Buyer-side documentation removes the leverage. The SAP ECC topic page covers the broader audit-mechanics reference and the audit defence pillar covers the defence pattern in general.
Where self-declarations interact with S/4HANA
The S/4HANA conversion has reduced the self-declaration surface by absorbing several previously self-declared engines into the Full Use Equivalent framework, where the consumption is measured by user-type counts rather than business-unit declarations. The remaining self-declaration entries are concentrated in the asset-management, payroll, and treasury surfaces, which retain the business-unit metric in the S/4HANA price list. Buyers entering the conversion should reconcile every legacy self-declaration entry against the converted contract structure to confirm which declarations persist and which have been replaced. See the FUE conversion math note and the S/4HANA conversion handbook for the line-by-line reference.
The annual declaration review
Self-declarations should be reviewed annually as part of the USMM preparation cadence. The review confirms that the source of truth is still current, that the operational scope has not changed materially since the prior declaration, and that the evidence file reflects the current state. The review takes a few hours per engine and produces a declaration record that supports the year’s submission and the subsequent audit conversation. The utility self-declaration defence case file illustrates the discipline at scale.
— 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.
Where to start
If your estate has not run a self-declaration evidence pass in the last twenty-four months, the highest-leverage first step is the inventory of every self-declared engine in the current USMM submission, with a source-of-truth field added for each. The inventory exposes the documentation gaps in time to close them before the next measurement window. The USMM and LAW advisory service brief covers the engagement structure.