Ask any asset accountant what the worst part of their job is, and somewhere in the answer you will hear two complaints, back to back. The first is explaining depreciation to someone who doesn’t run Asset Accounting for a living. Why did net book value drop $40,000 this period, why does this depreciation key front-load the expense and that one doesn’t. The second is usually a reporting one. Everyone is opinionated when it comes to reporting which usually leads to questions. Where did the Asset Balance report get this value? Why does the Asset History Sheet show a different breakdown from what they see at the Asset Explorer?
SAP just handed both jobs to AI. Three features now live in SAP S/4HANA Cloud Public Edition; two of them ask SAP Business AI to explain, in plain language, what is driving the depreciation calculation as well as explain the figures in a report, and the third asks Joule to just create the asset for you. Two are new as of the 2508 release; the third has been quietly reworking how it grants access. Together they cover a surprising amount of the day-to-day friction in Asset Accounting.
.
AI-Generated Explanation of Depreciation Keys
This one targets the depreciation key itself. Instead of decoding a base method, a declining-balance percentage, period control methods, and the potentially complex multi-level method by hand, you can now ask the system for a natural-language explanation of how a specific depreciation key affects the value of the asset over its useful life – which is, frankly, a fair description of a question every new asset accountant has asked and every experienced one has answered a hundred times.
Getting to that button takes more than a support pack, though. This is a generative AI feature, which means SAP treats it as its own entitlement: you register for it in SAP For Me, and your account executive is the one who confirms what additional entitlement and authorization apply. Once registered, business users still need to be explicitly granted access – the business catalog Asset Accounting – Explain Depreciation Key (AI) (SAP_FIN_BC_AA_AI_EXDEPRKEY_PC) and the IAM app Explain Depreciation Key (AI) (F8942_TRAN). On the technical side, the feature lives under scope item J62, app ID F3425, in the Asset Accounting (FI-AA) component, with no localization requirement, and it’s valid as of SAP S/4HANA Cloud Public Edition 2508.
Here’s how it looks in the system [Note: these screenshots are actually from a Private Cloud S/4HANA system, not Public Cloud. There is a difference between the two that I’ll mention below]. If you launch the Manage Fixed Asset (MFA) app, pull up an asset, and then navigate to the Valuation section, you’ll see the familiar list of ledgers and depreciation areas. Included in this is the familiar combination of depreciation key, useful life, and depreciation start date. If you click on the depreciation key, you get the pop-up window shown below. The first highlighted option Explain Depreciation Key (complete with a magic twinkling stars icon!)…
.
… will then show you the window below. This serves as an explanation of how the key is structured (two phases in this case) and the basic components that drive the calculation.
.
If you go back and click on the 2nd link ‘Depreciation Key: Display Details’, the following window will appear. This shows the technical details of the key and its underlying methods. This isn’t geared at accountants, it’s more useful for SAP Consultants such as myself to quickly view the definition of a key, particularly in a productive system where I won’t have access to the configuration transactions that define these parameters. Anyways, if you are in a Private Cloud system (not Public Cloud) at the top of the screen is a similar button…
.
… which launches a similar pop-up window. Though, for some reason, it uses a different font which looks inconsistent with everything else I see in Fiori. More importantly, I’ve highlighted the disclaimer text SAP puts at the bottom of each window. ‘Verify results before use’. To be clear, this button only appears in the S/4HANA Private Cloud, not Public. Public Cloud has this depreciation key details as a separate app but the Depreciation Key Explanation button doesn’t appear on it.
.
A word of caution seems fair here, though, because it’s easy to oversell a feature like this. Treat the depreciation key explanation as a strong first draft, not a verdict. Depreciation keys are deceptively simple right up until they aren’t – multi-level methods layered with period controls, changeover conditions that trigger mid-life, base value methods that offload the whole calculation to a BADI. [Quick question: Do you know how many configuration parameters are on a depreciation key and it’s underlying components? A: 55. It’s a complex object!] The AI will nail the straightforward 80 or 90 percent of cases without hesitation: a standard straight-line key doing exactly what the label says. But when a value goes sideways because of some obscure interaction between a changeover method and a period control parameter that you can’t maintain (not every configuration parameter is actually visible and maintainable!), that’s still a job for someone who has actually configured all of the depreciation components and knows where the bodies are buried. This feature was clearly built to handle the easy requirements – the routine questions that eat an accountant’s time without needing their judgment – and to free up actual expertise for the cases that genuinely require it, not to replace that expertise outright.
.
AI-Generated Explanation of Key Figures
This one goes a level deeper, targeting the actual calculated numbers. The Value Display section of the Manage Fixed Assets (MFA) app already shows a fixed asset’s key figures — acquisition and production costs, depreciation, and net book value— for the depreciation area, fiscal year, and currency you select, laid out in a table. What it has never done is tell you how those numbers got there. The new Explain Key Figures function fixes that: click it, and the AI generates a natural-language explanation of the origin of the displayed values, right down to illustrating how a depreciation value works out after a mid-year acquisition under a specific depreciation key.
.
Unlike the depreciation key feature, this one is flagged in SAP’s own release documentation as a genuine innovation — brand new as of SAP S/4HANA Cloud Public Edition 2508, not an update to something that already existed. The access model mirrors its sibling feature almost exactly: register in SAP For Me, confirm entitlement with your account executive, then assign business users the business catalog Asset Accounting – Explain Key Figures (AI) (SAP_FIN_BC_AA_AI_EXKEYFIGS_PC) and the IAM app Explain Key Figures (AI) (F8941_TRAN). It lives under the same scope item (J62) and the same host app (F3425, Manage Fixed Assets) as the depreciation key feature, in the Asset Accounting (FI-AA) component, with no localization requirement.
Both functions live inside Manage Fixed Assets, both are genuinely just “explain this” buttons, and both are aimed at the same underlying problem: valuation calculation logic that is perfectly correct and almost entirely illegible to anyone outside Asset Accounting.
.
Creating Fixed Asset Master Data with Joule
The third feature flips the direction entirely – instead of explaining an asset that already exists, Joule will create one for you, through a plain conversation. You tell Joule you need a fixed asset, it asks for a company code, an asset class, and a cost center (asset description is optional but helpful), and it walks you through the rest like a reasonably patient colleague:
You: Please create a fixed asset.
Joule: Sure, let me guide you through creating a main asset. To create a main asset, provide the following information: Company Code, Asset Class, Cost Center, Asset Description (Optional)
You: 1010, 3200, 10101041, Laptop ABC
Joule: Here is the main asset based on your input. Either confirm the creation, or provide more details, or enter something you want to edit.
If what you give Joule is ambiguous – “I bought a computer” instead of a specific asset class – it doesn’t guess. It offers a proposal list of matching asset classes and lets you pick. Once all four pieces of data are in hand, Joule summarizes them on a card, and you confirm, adjust, or discard before anything actually gets created. Confirm it, and Joule creates the asset master record, issues a success message, and drops a navigation link straight into the Manage Fixed Assets app (F3425) so you can pick up where the conversation left off.
It is worth being precise about what this does and doesn’t do. Joule creates the core record – company code, asset class, cost center, description. Anything more granular, like an inventory number, isn’t part of the dialog; you add that afterward in the MFA app. SAP says as much directly, and goes further: it recommends checking every Joule-created asset master record in the app and adding whatever additional detail it’s missing. That is a sensible instinct to build into your own process regardless of what SAP recommends – a chat-created record is a starting point, not a finished one.
.
The benefits, according to SAP (and to anyone who has done this job)
For the two explanation features, SAP doesn’t publish a benefits list quite this tidy in the release notes themselves, but reading between the technical details: faster, more consistent onboarding for anyone new to Asset Accounting, fewer ad hoc explanations pulled out of a senior accountant’s head during close, and an audit trail written in plain English instead of reconstructed after the fact from configuration tables.
The Joule feature’s benefit is more straightforward: it takes the least interesting part of asset creation – remembering the right transaction, filling in the same four fields correctly, every time – and turns it into a conversation short enough to have while you’re already on the phone about something else. For a cost center owner who touches Asset Accounting twice a year, that is the difference between opening a ticket and just asking.
Translated further out of release-note language, the real audience for all three features isn’t the senior asset accountant who already knows the answer or the T-code. It’s the new hire three weeks into the role, the controller asking why NBV moved the way it did, the auditor who wants the calculation logic in writing, and the occasional user who just needs one laptop capitalized without a training session first. None of that requires a different depreciation calculation or a different chart of accounts. It just requires someone – or, now, something – willing to handle the routine part.
.
Why this matters
Depreciation calculation has always been one of the least self-explanatory corners of SAP. Like I said above, it’s a very complex object (and justified in my opinion). Base methods, multi-level methods, period controls, declining-balance methods, and changeover keys stacked on top of each other, fully deterministic and almost entirely opaque to anyone who didn’t configure it. Asset creation, meanwhile, has always been simple in principle and tedious in practice. It’s just a handful of fields, repeated endlessly, gatekept by whoever remembers the transaction code. These three features attack both ends of that problem without touching the actual logic underneath. The depreciation math doesn’t change. The fields on an asset master record don’t change. What changes is who can get an answer, and who can get a record created, without needing to already be the expert. For a module that has spent decades being correct but inaccessible, that is worth something on its own.
.
What do I think?
Honestly, all three of these are useful, but two of the three are just documentation with better manners. Explaining a depreciation key or a key figure is genuinely helpful but it’s still SAP telling you about a decision the system already made. It doesn’t move any faster, doesn’t touch any process upstream, and doesn’t change what an asset accountant actually does all day beyond answering fewer repeat questions. I’ll never use these two but if they trim my inbox by a few emails a month, then I welcome them to the table.
Joule creating the asset master record is the one I’d watch. That’s not documentation, that’s the system doing part of the actual job, and it’s a small, deliberately narrow slice of it – one main asset, four fields, nothing fancy. Given how aggressively SAP has been pushing Joule across the rest of S/4HANA, I don’t read this as the finish line for AI in capital asset management. I read it as the opening move. If SAP is comfortable letting Joule create a main asset today, I’d expect the next releases to push further into the capital space — asset transfers, retirements, maybe even parts of the acquisition-to-capitalization chain — rather than stopping at explanations. Can I tell it to mass retire all assets on cost center 10101001? Transfer all assets currently on the screen using transfer variant Z1 as of the end of this period to corresponding new records in company 9001? Reverse the unplanned depreciation adjustments made on <date>? Yeah, why not? SAP is constantly mentioning in their roadmaps about “All-in on AI”, the “Autonomous Enterprise” and “Autonomous Finance” so it’s clear that more is coming. When? Well, probably not this year (2026) but given how this has been handled thus far, perhaps 2027 will be when SAP releases more of these features. Either way, this is something I’m keeping my eye on to see where Joule shows up next in Asset Accounting, because this feature reads like a pilot, not a destination.
.
Sources
- AI-Generated Explanation of Depreciation Keys (SAP Help Portal)
- AI-Generated Explanation of Key Figures (SAP Help Portal)
- Creating Fixed Asset Master Data (SAP Help Portal, Joule Capabilities Guide)
- SAP Note: 3695833 – AI-assisted settlement rule proposal for asset capitalization | Component: IM-FA | Released: April 1, 2026
- SAP Note: 3693996 – AI-assisted depreciation key explanation in S4HANA | Component: FI-AA | Released: December 17, 2025
- SAP Note: 3694048 – AI-assisted fixed asset key figures explanation in S4HANA | Component: FI-AA | Released: March 17, 2026
- SAP Note: 3641239 – refinement of AI-assisted explanation feature in FI-AA | Component: FI-AA | Released: December 17, 2025
