BTP Year-End Credit Expiry: When You Must Review Your Burndown at the Latest

Unused BTP credits expire at the end of the contract period. That much is widely known. What is far less understood is exactly when you need to act to prevent expiry, and which review steps at which point in the year represent the critical governance moments. This article provides an operational timeline with clear decision points for Q3 and Q4.

---

Why Expiry Almost Always Gets Noticed Too Late

The credit expiry rule for CPEA and BTPEA is unambiguous: whatever has not been consumed by the end of the contract period expires. No automatic rollover, no balance transfer into the next year (source: SAP FAQ, Consumption-based Commercial Model CPEA).

In practice, the problem does not arise from ignorance of this rule. It arises from the rhythm in which BTP consumption is monitored. Most organizations have no consolidated burndown curve showing how credit consumption is tracking against planned annual usage. What they do have: monthly balance statements from SAP that document historical consumption but provide no forecast for the remaining period.

This structural gap, the absence of an ongoing burndown forecast, is the most common reason expiry only becomes visible in November or December, when the room to maneuver has already shrunk considerably.

---

The Operational Annual Timeline: Four Governance Moments

What follows is a concrete timeline with the four operational governance moments at which BTP burndown and credit planning must be reviewed, so year-end does not bring an unpleasant surprise.

Governance Moment 1: End of Q1 (March/April): Establish the Baseline

At the end of the first quarter, three months of actual consumption are on record. This is the earliest meaningful opportunity to establish a burndown baseline.

What to review:

• Cumulative Q1 credit consumption compared to the linear target (annual credit balance divided by four equals 25% annual consumption as the Q1 benchmark)
• Which services account for the largest share of credit consumption
• Whether planned BTP projects have launched as expected or experienced delays

What the result tells you: If actual Q1 consumption is below 15% of the annual balance, there is an early signal of over-commitment that should be addressed in Q2. If it is above 35%, there is a first overage risk that also warrants early attention.

This initial review creates the reference point for every subsequent comparison throughout the year.

Governance Moment 2: End of Q2 (June/July): Build the Q4 Forecast

The end of the second quarter is the most important governance moment of the year for credit planning. Six months of actual consumption allow for a reliable full-year projection.

What to review:

• Cumulative consumption after six months compared to 50% of the annual balance (linear target)
• Projection: if the current consumption trend continues, what is the expected year-end total?
• Which BTP projects are planned for the second half that will shift consumption?
• Are there deprecation-relevant services in the current catalog that must be migrated before year-end?

What to decide: Based on the Q2 forecast, there are three possible outcomes.

If the forecast falls well short of the annual commitment, for example only 60% of the contracted balance is likely to be consumed, there is significant expiry risk. You still have four to five months to initiate countermeasures, and this is the earliest sensible point for a conversation with SAP about a possible contract adjustment, or for identifying new use cases that would raise consumption.

If the forecast is close to the commitment (85 to 115%), no structural intervention is needed. Monthly monitoring is sufficient.

If the forecast substantially exceeds the commitment, a top-up conversation with SAP should be prepared starting in Q3 to avoid drifting into unplanned overages.

Key takeaway: The Q2 forecast is the foundation for all material H2 decisions. Missing this governance moment for burndown analysis means losing the largest mitigation window of the year.

Governance Moment 3: October: Top-Up Decision and Countermeasures

Early October marks the start of the critical window in which real options still exist.

If expiry risk is present (under-consumption):

If you are seeing significant under-consumption by October, you still have two to three months to increase credit consumption. The most practical options in this situation:

• Activating development and sandbox environments that have been kept at minimum capacity
• Scaling up test and dev instances (HANA Cloud, Kyma) for active projects
• Pulling forward the start of Q1 projects planned for the following year, where technically feasible
• Activating services for evaluation purposes that are already in scope for the coming year

These options are not a guarantee of full consumption, but they measurably reduce the amount that expires. Even a partial improvement is better than none.

If overage risk is present (over-consumption):

If by October you are tracking at 75 to 80% credit consumption and the trend continues, now is the time to initiate a top-up conversation with SAP. A top-up at original contract terms before the credit balance is exhausted is substantially cheaper than overage billing at list price without volume discounts (source: SAP BTP Licensing Models, Community Knowledge: Rizing).

That conversation should happen in October, not November. SAP has its own quarterly and annual cycles, and a top-up request in November arrives when your counterparts are already in year-end mode.

What applies to both scenarios: The governance moment for budget, reviewing the credit balance against the actual consumption path, must be completed in October. Not in December.

Governance Moment 4: Early December: Final Control Review

Early December is the last point at which operational adjustments are still possible before year-end is too close.

What to review:

• Remaining credits and realistic residual consumption through year-end
• Have all countermeasures planned in October been implemented and are they taking effect?
• Are there deviations from the October forecast that require correction?
• Are all active BTP services correctly configured and not generating unintended idle consumption?

What helps in practice: A subaccount-level check that identifies inactive or minimally used service plans can still help in December, either by stopping unnecessary consumption or redirecting it meaningfully. A service plan running for a completed project and consuming credits is not strategic consumption.

The goal of the December review is no longer to salvage large volumes, but to confirm that annual governance is closing as planned and that no obvious gaps remain.

---

What Effective Burndown Tracking Looks Like

Burndown tracking does not require a complex BI system. For most organizations, a structured monthly spreadsheet with five metrics is sufficient:

1. Total annual credit balance (from the contract)
2. Cumulative consumption to date (from the monthly SAP balance statements)
3. Linear target (annual balance multiplied by months elapsed, divided by twelve)
4. Variance: actual vs. target (positive number means under-consumption, negative means over-consumption)
5. Year-end projection (cumulative consumption divided by months elapsed, multiplied by twelve)

These five metrics can be derived monthly from the SAP balance statements and maintained in a simple table. They provide the governance foundation for all four review points throughout the year.

The BTP Cockpit also offers configuration options for usage alerts at the subaccount level. As a complementary governance moment, setting an alert at 70% credit consumption serves as a first signal, and a second alert at 90% marks the last proactive intervention point. Both alerts should be configured at the subaccount level, not only at the overall contract level, because consumption spikes typically originate in individual subaccounts rather than spreading evenly across the entire BTP landscape.

---

Three Signs Your Current BTP Burndown Governance Has Gaps

None of these reviews are technically complex. They require no additional software, but they do require clear ownership and regularity.

Sign 1: You cannot immediately state today how many BTP credits remain and when they are expected to run out. If that number is not available on demand, the governance foundation is missing.

Sign 2: The last time anyone looked at the BTP budget was more than 60 days ago. With a monthly billing cycle, a 60-day interval is too long to respond to deviations in time.

Sign 3: Responsibility for BTP burndown monitoring has not been explicitly assigned to a person or function. When everyone is responsible, in practice no one is. The governance moment around consumption requires a named owner, ideally within the Cloud Center of Excellence function with reporting accountability to Controlling.

---

Connection to the Annual Renewal

Year-end burndown management has a direct bearing on the next renewal conversation with SAP. The consumption record for the current year is a key argument in the commitment negotiation for the next contract period.

Demonstrating that the current commitment was fully or nearly fully consumed strengthens your position when negotiating a higher commitment at equal or better terms. Documenting significant under-consumption objectively weakens your starting position, because SAP can see that the current commitment was not fully utilized.

Burndown monitoring therefore serves not only expiry prevention but also preparation for the next renewal. Both goals share the same governance moment: systematic, regular tracking of credit consumption across the entire contract year.

A structured presentation of BTP consumption data for the renewal conversation is a separate topic covered in more depth in the hub article BTP FinOps: Governing Credits, Avoiding Overages, and Allocating Costs.

---

Next Steps

If you want to assess your current BTP burndown situation, FinOptory AI can answer initial questions about credit mechanics and your contract model directly.

For a structured analysis of your BTP contract structure, your credit commitment, and your ongoing governance situation, FinOptory offers a Contract Review as a defined starting point.

How the credit expiry logic fits into the broader context of all SAP contract types is covered in Why BTP Credits So Often Expire at Year-End and What You Can Do About It, from the Pillar 1 perspective.

---

Frequently Asked Questions

What is the latest point at which you can still prevent BTP credit expiry? The last viable intervention point is October. That leaves two to three months to increase consumption or discuss a contract adjustment with SAP. By November, options are already limited. By December, they are significantly constrained.

How often should BTP credit consumption be reviewed? Monthly, based on the SAP balance statements. In addition, there are four operational review points per year with specific decision tasks: end of Q1 (baseline), end of Q2 (Q4 forecast and decision), October (top-up review and countermeasures), early December (closing check).

What happens if BTP credits expire unplanned? Unused credits are written off at the end of the contract period with no compensation. The amount paid for those credits is non-refundable. No post-expiry contract adjustment is available. Only a contractually agreed rollover clause, if negotiated at contract signing or renewal, can carry a portion of unused credits into the next period.

Can a credit rollover be negotiated? A limited rollover is achievable in contract negotiations, but it is not an SAP default. Rollover arrangements of 10 to 20% of unused credits are documented in practice (Community Knowledge: Rizing, Redress Compliance). These are observed figures, not guaranteed outcomes. A rollover clause must be negotiated before contract signing or at renewal, not after expiry.

How do you set credit alerts in the BTP Cockpit? In the BTP Cockpit, usage notifications can be configured at the subaccount level. Two thresholds are recommended: a first alert at 70% consumption as an early warning, and a second at 90% as a signal for immediate action. Both alerts should be set at the subaccount level, not only at the overall contract level, because consumption spikes originate in specific subaccounts rather than distributing evenly.