Nine document types that bill you for your own orders

Under SAP's Digital Access model, the billable event is not a person logging in — it is a document being created. When your B2B ordering portal, a rep app, or an EDI feed writes a sales order or an invoice into SAP ERP, that document is metered and licensed even though nobody logged in. Nine document types trip the meter, and the 2017 SAP v Diageo ruling made the principle enforceable: indirect access is still access.

What actually triggers a Digital Access charge?

Classic SAP licensing counts Named Users: a human with a login pays a seat fee. Digital Access, introduced in 2018, counts documents instead. It tallies records created in SAP ERP through indirect paths — anything that is not a person typing into the SAP GUI — and bills against the creation of the record, not the human behind it. As documented in SAP's Digital Access model, there are nine document types (as of March 2026), counted once when created rather than on every read or update, with sales, invoice, and purchase documents carrying the heaviest weighting.

The mechanic is worth sitting with. A single online order that becomes a sales order, then an invoice, then a goods movement has already touched three of the nine types before a human sees it. The bill is no longer a function of how many people you employ; it is a function of how many documents your systems create.

Why did Diageo pay £54.5m for orders its own customers placed?

The precedent that made this real is SAP UK v Diageo. Diageo ran mySAP ERP for manufacturing, stock and supply chain, financial control, and HR, and built customer- and rep-facing applications on Salesforce technology — including a sales-rep app known as Gen2 — that reached into mySAP ERP without their users ever being Named Users. SAP brought its claim in October 2015. In February 2017 the High Court sided with SAP, awarding £54,503,578 in licence fees plus a further £3,955,954 in interest, on the basis that roughly 5,800 customer-facing and sales users were reaching the ERP indirectly. Mrs Justice O'Farrell's reasoning was narrow and, for anyone running digital order capture on SAP, uncomfortable:

Only named users are authorised to use or access the mySAP ERP software directly or indirectly.

Read the phrase or indirectly carefully. A customer clicking Submit on a web form, or a rep tapping a tablet, is using the ERP for licensing purposes even though they never see it. The 2018 Digital Access model is SAP's tidier answer to the messiness of that ruling: rather than argue about who counts as an indirect user, count the documents. Cleaner to administer, and it puts the meter on exactly the events your route-to-market platform exists to generate.

Why does this land on architecture, not procurement?

Because the billable unit is a boundary crossing, and boundaries are drawn by engineers, not buyers. Viewed through the Digital Access lens, every item on the route-to-market roadmap is a document generator. A self-service portal that replaces telesales converts phone calls into sales documents. An EDI feed from a wholesaler posts orders directly. A returnables ledger writes material documents for every keg movement. A loyalty or settlement engine that posts accruals into finance raises financial documents. None of these have logins; all of them feed the meter.

The incentive runs backwards. Under a Named-User licence, moving an order from a human telesales agent to an automated portal removes a seat and reads as a saving. Under Digital Access the same automation is neutral at best and costly at worst, because the document still gets created — you have removed the human you used to pay for and kept the artefact you now pay for. The model quietly taxes the exact transformation the digital channel was bought to deliver.

It is also invisible until it is not. You cannot see a document count in your P&L; you see it when an auditor measures it. That is the same shape as the metered surprises picked apart in per-conversation AI pricing and other budget surprises: the unit of the bill is a runtime event nobody priced at budgeting time. And it maps straight onto the plumbing — every IDoc that posts a sales order is one of these chargeable documents. The ones you notice are the ones that fail, stuck in the IDoc queue where orders go to wait; the ones being counted are the thousands that succeeded silently.

Where does the exposure actually accumulate?

It compounds at the edges of the estate, where no one owns the whole picture. Each operating company that stands up its own ordering portal multiplies the document count against the same central ERP. Every third-party integration you commission is another uncontrolled source — and if you buy, say, an API-only loyalty product where you still build the integration that posts back to ERP, its documents are yours to account for. Because these are commissioned by different teams at different times, no single owner tracks the aggregate — and the aggregate is what gets priced.

The measurement is not optional, either. Estimating the volume of documents created through indirect access is, per ASUG,

likely part of the standard SAP annual audit.

So the figure that drives a seven-figure true-up is discovered during an audit window, from data your own systems generated, rather than modelled in advance by the people who designed the integrations. That is the core failure mode: a licence liability that behaves like a runtime metric but is governed like a contract term, and reconciled once a year by someone who was not in the room when the interfaces were drawn.

The way out is not a sharper negotiation; it is a boundary. When every external write into SAP ERP passes through one controlled, instrumented posting interface on a single event bus rather than a dozen point integrations, the document count becomes a design decision you can see, batch, and model before an audit forces the question.

As order capture goes digital across more operating companies and more channels, the Digital Access meter turns each new integration into a recurring licence line rather than a one-off build cost. The brewers who walk out of the next audit cycle unsurprised will be the ones already treating the ERP boundary as a metered interface — counted, owned, and designed on purpose — rather than a quiet assumption that only people cost money.