Internal cost allocation

Most enterprises buy SAP licences centrally, hold the licence cost in central IT, and absorb the consumption growth as the cost of doing business. The arrangement is administratively simple. It is also why most enterprises over-licence: the consuming business units have no economic signal to optimise, the central IT team has no leverage to constrain consumption, and the optimisation conversation becomes a top-down mandate that produces resentment rather than results. A working internal cost-allocation model converts the dynamic. The business units that consume the licences pay the cost; the optimisation becomes a business decision; the next contract negotiation becomes a multi-stakeholder exercise rather than a central-IT exercise. This article walks through the allocation model, the implementation sequence, and the consequence for the optimisation programme. It is one of the working patterns underneath our licence optimisation service.

What the central model misses

The central-IT model misses three signals. First, the business unit does not see the licence cost of its decisions. Provisioning a new user, requesting a higher classification, requesting a new module — each has a licence-cost consequence that the business unit does not bear. Second, the central IT team cannot force discipline. Without a budget consequence, the optimisation request is an administrative inconvenience, not a financial one. Third, the contract negotiation cannot draw on the business-unit position. The business units have no skin in the negotiation, no view on what they need versus what they have, and no voice in the renewal decision.

The central model is comfortable for the business units (no licence-cost visibility) and frustrating for central IT (no leverage). It is also expensive for the enterprise: the over-licensing it accumulates compounds across renewals. The named-user topic page covers the consumption-driver detail.

The allocation model

The allocation model has four components. Each component drives a different behaviour and each can be implemented independently.

Named-user allocation

The named-user allocation charges each business unit for the licences consumed by its named users. The charge is calculated from the SAP unit price by classification, multiplied by the count of users in that classification belonging to the business unit. The allocation is recurring (annual or monthly) and is reflected in the business-unit budget.

Engine-consumption allocation

The engine-consumption allocation charges each business unit for its share of engine consumption: HANA memory, BPC users, payroll regions, output documents. The allocation requires a consumption-attribution method (consumption logs by user, by company code, or by allocation ratio). The method matters: too granular and it becomes administratively burdensome; too coarse and it loses the optimisation signal.

Module-licence allocation

The module-licence allocation charges each business unit for the modules it uses. Where a module is licensed enterprise-wide but used by a single business unit, the allocation should reflect the actual use. Where a module is shared, the allocation should split by a defined ratio.

Indirect-access allocation

The indirect-access allocation charges each business unit for its share of digital-access documents. The attribution is by the originating non-SAP system; the cost is the document-tier cost from the contract. The allocation signals which business units are driving the indirect-access exposure. The engine-consumption review article covers the attribution methodology.

The implementation sequence

Implement the allocation model in stages. Each stage delivers visibility before the next, and the visibility itself drives behaviour change.

Stage one — visibility without charge

The first stage produces the cost report by business unit without applying the charge to the budget. The report is published quarterly. The visibility alone changes behaviour: business units that see their licence cost for the first time begin asking for optimisation support.

Stage two — charge with reconciliation

The second stage applies the charge to the business-unit budget and provides the reconciliation mechanism for disputed items. Business units that disagree with their attribution can raise a dispute and have it adjudicated against the underlying data. The reconciliation builds the data discipline that the long-run allocation requires.

Stage three — allocation as governance

The third stage integrates the allocation into the procurement workflow. New-user provisioning, classification changes, and module-access requests are accompanied by the licence-cost impact, which the business unit accepts or rejects at the request stage. The allocation becomes the governance mechanism.

The negotiation consequence

Internal cost allocation transforms the next contract negotiation. The business units that bear the cost have a direct stake in the contract terms. The user-count forecast is built bottom-up from the business-unit projections, not top-down from the SAP-recommended figure. The classification distribution reflects the business-unit positions on entitlement, not the inherited classification from the prior contract. The renewal economics are debated by the business units alongside central IT.

The outcome is a negotiation position that is substantively buyer-side, defended internally before it is taken to SAP. SAP's customary negotiation approach — offer a bundled price, escalate to the buyer's central IT, accept the small concessions on the periphery — is less effective against an enterprise that has done its internal alignment first. The manufacturer 68% case file documents the pattern.

The audit-defence consequence

The allocation also improves audit defence. The business units that bear the licence cost have a direct interest in defending the licensed estate during an audit. The audit-response coordination becomes easier: the business unit understands the stakes, provides timely data, and supports the central position. Estates that allocate cost typically resolve audits faster than estates that do not. The licence optimisation framework white paper covers the audit-defence interaction.

Where to start

Start with stage one: the visibility report. The report can be produced from existing data in two to four weeks. Publish it. The conversations the report initiates are the first deliverable of the allocation programme.