Self-billing, evaluated receipt settlement (ERS), and supplier-self-invoicing flows are operationally efficient and licensing-expensive. The flows reduce supplier-side invoicing effort, shrink the AP team, and tighten the order-to-cash and procure-to-pay cycles. They also produce some of the most expensive findings in SAP engine-metric audits, because the meter counts the underlying documents at the same rate as it counts traditional invoices, even where the customer's commercial intent was that these flows would not be license-bearing.
This article walks the mechanics of how self-billing volumes are counted by SAP's standard engine meters, the audit findings the counting produces, and the contractual language that prevents the finding at renewal.
What self-billing is, in SAP terms
Self-billing is the procurement pattern where the buyer generates the supplier's invoice on the supplier's behalf, typically based on a goods receipt or service confirmation. The supplier never raises a traditional invoice; the buyer's system creates a self-billing document that is treated, for VAT and accounting purposes, as the supplier's invoice. The flow is common in high-volume procurement (automotive, retail, FMCG), in scheduling agreements, and in consignment stock.
Evaluated receipt settlement (ERS) is a specific SAP implementation of self-billing, configured at the vendor-master level, in which the system automatically generates invoices on goods receipt without manual intervention. Supplier-self-invoicing is a related pattern where the supplier produces an invoice via an integrated portal but the document flow is managed by the buyer.
How the meter counts these flows
The SAP engine metric for the procurement engine (commonly the materials management or MM engine) counts invoice-equivalent documents. The meter does not distinguish, in its default configuration, between traditional invoices, self-billing documents, and ERS-generated documents. All three are counted at the same rate against the customer's licensed volume tier.
The implication is that a customer who has moved twenty per cent of supplier invoicing to ERS — an operational efficiency win — has not reduced the engine-metric volume. They have simply shifted who pressed the button. The volume is the same and the licence cost is the same.
The audit finding pattern
The double-count finding
In a meaningful minority of audits, the finding goes further than simple counting. SAP's auditors interpret self-billing documents as creating two countable events: the goods receipt that triggered the document, and the self-billing document itself. The interpretation produces a roughly two-fold inflation of the engine-metric volume for the affected procurement channels.
The customer-side defence on the double-count is contractual: the original licence agreement typically references "invoices" rather than "invoice-equivalent events," and self-billing documents are arguably the invoice rather than the goods receipt being the secondary count. The defence is usually accepted but only after structured methodology dispute.
The volume-tier-transition finding
The more common finding is simpler: the customer's actual procurement volume, including self-billing, exceeds the volume tier the customer is licensed for. The finding is straightforward to substantiate from the system data, and the customer-side dispute focuses on the back-charge calculation rather than on the underlying volume.
The contractual clauses that prevent the finding
1. The single-count clause
The cleanest preventive clause is one that explicitly defines the countable event as the invoice document itself, regardless of how it was generated, and prohibits the auditor from counting upstream events (goods receipts, service confirmations) as separate countable events. The clause prevents the double-count finding pattern.
2. The self-billing inclusion clause
The complementary clause includes self-billing and ERS volumes in the licensed-volume tier at no incremental cost up to a defined threshold. The clause aligns the customer's incentive to operate efficient self-billing flows with the licence cost; without it, the customer's efficiency improvements directly drive the licence bill.
3. The volume-flexibility band
A broader clause that gives the customer a flexibility band (typically plus or minus fifteen per cent) around the licensed volume before a tier transition is triggered. The band protects the customer against ordinary year-on-year variation and prevents minor self-billing growth from producing a tier finding.
The operational disciplines that limit the finding surface
Three operational disciplines materially limit the engine-metric finding surface around self-billing. First, a monthly reconciliation between the procurement system's document-volume report and the licensing-management team's declared volume. Second, an annual review of ERS-vendor configurations to identify vendors who have been moved to ERS without licensing review. Third, an explicit categorisation of countable events in the customer's internal documentation, so that any audit dispute starts from a customer-defined definition rather than an auditor-defined one.
These disciplines are operationally inexpensive but materially valuable. The full process is set out in our analysis of engine metric double-counting traps and the broader framework in the self-declaration process.
How the finding interacts with S/4HANA conversion
The S/4HANA conversion of engine metrics is a particular pressure point for self-billing volumes. The conversion logic in some target metric configurations counts self-billing documents differently than the source ECC configuration did, sometimes producing a step-change in declared volume even where the operational reality has not changed. Customers in S/4HANA conversion projects should specifically review self-billing volume treatment as part of the conversion analysis. See our analysis of S/4HANA conversion of engines for the full mechanics.
The supplier-side dimension
Self-billing flows occasionally have a supplier-side licensing implication too, particularly where the customer is using SAP Ariba Network for the self-billing document transmission. The Network fee is calculated on the supplier's side, but the buyer's commercial relationship with the supplier can absorb part of that fee through pricing. Customers who run high-volume self-billing through Ariba should review the supplier-side fee dynamics. See our Ariba Network fees explained analysis for the supplier-side detail.
When to bring in an independent advisor
Self-billing engine-metric findings are technical enough that most procurement teams benefit from external support at the methodology-dispute stage. The advisor's value is in three areas: documenting the contractual position on the single-count interpretation, providing comparable methodology data from prior matters, and managing the auditor-side dialogue without ceding the methodology argument. See the audit defence service for the engagement model and the broader SAP ECC topic page for the engine-metric context.
What good looks like
A well-managed self-billing engine-metric position includes explicit single-count language in the licence agreement, a defined flexibility band on volume tiers, a monthly internal reconciliation of declared and actual volumes, and a defensible documented methodology for countable events. Customers who hit this standard typically settle engine-metric findings related to self-billing at twenty to thirty per cent of the auditor's opening position; customers who do not, typically settle at sixty to seventy-five per cent. The SAP Engine Metric Defence Guide includes the full operational and contractual framework.