The Cloud Platform Enterprise Agreement is the prepaid credit construct that anchors a buyer's commitment to SAP Business Technology Platform. The credit pool is one number on the order document; the sizing decision behind it is the whole BTP roadmap.
The CPEA is a prepaid commitment to consume SAP BTP services from a single credit pool over a defined term (typically one to five years). The credit pool draws against the published BTP price list at a discount that scales with commitment level and tenor. The construct is the SAP equivalent of an AWS Enterprise Discount Programme or a Microsoft Azure MACC.
The credit pool is fungible across the BTP catalogue. A credit pool of one million euros, drawn down at the published list rate for the consumed services, will fund any combination of Integration Suite, Extension Suite, Build Apps, HANA Cloud, Data Intelligence and the AI services on the platform. The fungibility is the credit construct's commercial value; the constraint is the commitment level and the use-it-or-lose-it expiry rule that applies to most CPEA tiers.
The CPEA reads alongside three other SAP commercial constructs: the Pay-As-You-Go model (full list, no discount, no commitment), the Subscription model (defined-service commitment with defined pricing) and the Free Tier (limited consumption, named services). The buyer-side question is which construct, at what commitment level, against which roadmap. The methodology runs in nine sections below.
The credit pool is sized against the deployed BTP workload, the eighteen-month roadmap and the discount-versus-burn-risk trade-off. SAP's published CPEA discount schedule gives more discount at higher commitment levels; the buyer's risk is the unconsumed credit balance at term-end.
The Admodum methodology sizes the pool against three distinct demand forecasts: the named projects on the eighteen-month roadmap, the steady-state extension and integration spend that recurs across the BTP estate, and the AI and data services that may or may not consume meaningful credit. The pool is sized at the eightieth percentile of the consolidated demand, not at the publisher's recommended commitment level.
Where the demand profile is uncertain (a typical position for a first-time BTP buyer), the buyer takes a shorter tenor at a lower discount, validates the consumption pattern over twelve months and renews into a longer tenor at a higher discount once the forecast is real. The discount foregone at year one is recovered at year two against a defensible demand picture.
A RISE with SAP contract typically bundles a CPEA credit allocation inside the broader subscription. The bundled CPEA is sized by SAP, against SAP's view of the buyer's BTP demand, and is rarely the right number. The buyer-side methodology pulls the CPEA out of the bundle and prices it on its own merits.
Where the bundled CPEA is undersized, the buyer either tops it up at the published list rate (an expensive position) or amends the RISE schedule mid-term (a contentious negotiation). Where it is oversized, the unused balance is forfeit at term-end. Either error has a multi-year cost.
The full read on the RISE bundle structure sits in Anatomy of the RISE bundle and BTP, the platform tour.
Once the CPEA is signed, the burn rate is the next load-bearing read. The buyer monitors monthly credit consumption against the time-line burn-down curve, named project by named project, named service by named service. A burn rate above the forecast is a budget question; a burn rate below the forecast is a risk question (the unused balance trends to forfeit).
The monitoring discipline is procurement's responsibility, not the BTP architect's. The CPEA dashboard sits inside the BTP Cockpit; the operational read sits inside the SAP for Me portal. The Admodum methodology runs a quarterly CPEA review for the buyer's CIO and CFO across both surfaces.
Where the year-two read shows a structural over-commitment, the firm runs the in-year amendment negotiation with SAP. Where the read shows an under-commitment, the firm runs the supplementary order at the original discount level rather than at the published list rate.
A CPEA renewal sits inside the wider SAP renewal cycle and is rarely a standalone negotiation. The renewal posture depends on the buyer's burn position, the BTP roadmap for the next term and the wider commercial picture across RISE, on-premise S/4HANA and the named subscription seats (SuccessFactors, Ariba, Concur, Fieldglass).
Where the buyer's burn rate is healthy and the roadmap is real, the renewal commits at a longer tenor for a higher discount. Where the burn is weak, the buyer steps the commitment down to a defensible level and absorbs the smaller discount as the cost of optionality. The decision is the buyer's, not the publisher's.
The renewal methodology runs under one of three Admodum engagement frameworks: fixed fee, contingency / gainshare or annual retainer.
Six checks for the buyer running into a CPEA decision: size the pool against the eighteen-month demand, not the publisher's forecast. Pull the CPEA out of the RISE bundle and price it on its own. Monitor the monthly burn rate against the time-line curve. Take a shorter tenor at first commitment, longer at renewal. Run the quarterly CPEA review through procurement, not through the architect. Open the next negotiation on the buyer's burn position, not on the publisher's renewal proposal.
For the wider SAP reading, return to the SAP pillar, visit the SAP knowledge hub, or open a private conversation with a senior Admodum SAP advisor through /contact/.
The SAP Cloud Platform Enterprise Agreement (CPEA) is a prepaid commitment to consume SAP Business Technology Platform (BTP) services from a single credit pool over a defined term, typically one to five years. Credits draw against the published BTP price list at a discount that scales with commitment level and tenor. It is SAP's equivalent of an AWS EDP or an Azure MACC.
CPEA credits are consumed against the published BTP list rate for each service, and the commitment buys a discount that increases with the commitment level and the contract tenor. The credit pool is fungible across the BTP catalogue, so one balance funds Integration Suite, HANA Cloud, Build Apps, AI services and more.
Yes. Most CPEA tiers carry a use-it-or-lose-it rule: credit unconsumed at term end is forfeit. Oversizing the pool therefore destroys value, while undersizing forces top-ups at full list rate. This is why sizing is the load-bearing decision.
Admodum sizes the pool against the eighteen-month BTP roadmap at roughly the eightieth percentile of consolidated demand, not at SAP's recommended commitment level. Where demand is uncertain, take a shorter tenor at a lower discount, validate consumption over twelve months, then renew into a longer tenor at a higher discount.
Often, yes. A RISE with SAP contract typically bundles a CPEA credit allocation sized by SAP against its own view of demand, which is rarely the right number. The buyer-side discipline is to pull the CPEA out of the bundle and price it on its own merits.
A senior Admodum SAP advisor will run the methodology through with your CIO, CFO, procurement team or audit response team on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active SAP audits route directly to the Audit Defence programme.