The promo did not end everywhere

SAP has extended the free period for the SAP Build side of Joule for Developers to December 31, 2026, and kept September 30 as the end date for ABAP AI. We reported earlier this week that SAP ends free Joule for Developers on September 30, and that stands for ABAP AI. Nothing in our earlier report is being withdrawn. The fuller text of SAP's post shows the change splits by tool, so read this as the addendum that completes that story.

The SAP Community post is dated September 23, 2026 at 17:25 Central European Summer Time, and because the page returns an access error to ordinary retrieval we pulled the body through SAP Community's public Khoros search API, with two passes coming back byte-identical. It carries a community login we could not verify and no executive quote, so everything below is attributed to SAP rather than a person.

SAP is direct about both halves. The promotional period that brought generative AI into SAP Build and ABAP at no additional cost "is ending on September 30th, 2026", and SAP adds, "We are extending the promo offer for SAP Build features to December 31st, 2026". A separate line states that "SAP Joule for Developers, ABAP AI capabilities will be commercially available starting October 1, 2026, outside the promotion". A platform owner whose developers use both sides now has two deadlines instead of one.

Work out exposure tool by tool

The line that decides who is actually affected sits in SAP's FAQ, and it is narrow. "ABAP Development Tools remain free; only the AI capabilities require licensing." An ABAP developer who opens ADT every day and never calls the AI features has nothing new to buy on October 1. The charge attaches to the AI capabilities, not to the development environment around them.

So the count that matters is per tool rather than per team. One squad can hold people who use ABAP AI daily, people who tried it in July and forgot, and people who only touch the Build side, and those groups sit on different dates. Sorting by the tool someone opens gives you a number you can act on this week.

For the fastest version of that count, ask in the developer channel rather than raising a licensing ticket. Joule usage is still free to talk about, and people answer usage questions plainly while no money is attached. From October 1 that question has a cost attached, and the answers get shorter.

SAP describes the price two different ways

Here the post stops being useful, and the problem deserves stating plainly. In one place SAP frames the commercial phase as consumption-based pricing measured in AI Units, and the next steps point at an AI Units contract under a stated SKU. In the FAQ, the same change is described as a subscription: ABAP AI capabilities "moves to the Per User Per Month" commercial license from October 1, 2026. SAP's abbreviation for that licence sits outside our quotation marks; the quoted words are unchanged.

Those are two different billing models and they produce two different budgets. A per user per month licence scales with the developers you name, and finance can forecast it from a seat list. A consumption contract measured in AI Units scales with usage, a number nobody in your organisation has been shown, because the usage has been free. We cannot tell you which applies, because SAP's own document says both.

None of that is evidence of bad faith. Transition posts get written while commercial terms are still moving, and an FAQ drafted by a different team than the pricing section is ordinary in enterprise software. It remains a real obstacle. Nobody can forecast a cost while the vendor describes the meter two ways in one document, and the honest move is to get the answer in writing from your account team before October 1 rather than inferring it. Anyone who has worked through a licensing change with a checklist in hand will recognise the shape of it.

December 31 is the second date to write down

The December date covers a different set of features and ends differently. SAP Build Process Automation and Joule Studio classic edition generative AI authoring features run to December 31, 2026, and then continue without the generative AI. The tools stay. The generated part of the authoring experience goes, and anyone reading that date as a shutdown will plan for the wrong outcome.

SAP Build Code AI Chat is handled separately again. The post says it continues beyond December 31 under fair use limits, with a model provider the customer chooses. A new Joule Studio is given general availability in the second half of 2026, and the Joule for Developers brand narrows to ABAP AI in 2027.

The December items belong in the year-end change freeze conversation rather than this week's. Put them in the same calendar entry as October 1 so nobody discovers the second date during a quarter close. Anyone who has watched a BTP pilot turn into a running cost knows the awkward month is the one after the meter starts.

The call to make before September 30

Two things fit in the time left. Pull the list of who has ABAP AI capabilities turned on, by name, and mark which of those people would notice if access changed on October 1. That list is your October scope, and your evidence if the first invoice looks wrong.

Then send one written question to your SAP account team today. Ask whether ABAP AI is charged per user per month or drawn down from an AI Units balance, which contract vehicle applies to your agreement, and ask for the reply in an email. A forecast built on somebody's recollection of a phone call gets challenged in November.

If only one of those gets done, make it the written question. The user count can be rebuilt later from tenant telemetry. The answer about which meter applies decides whether the figure you hand finance is a seat count or a usage estimate, and SAP has already moved its own AI spend into regular finance planning. Send that email before the thirtieth.