Interactive tool
SAP Treasury Module & Edition Selector
Tick what you need treasury to do; it lists the SAP components that address each need, linked to a full guide. Then weigh the edition trade-offs for your situation. It points you at the right components and questions — it doesn't decide your architecture, and it defers exact module scope to SAP's editions and official docs.
1 · What do you need treasury to do?
2 · Your SAP component shortlist
Tick the needs above and the SAP components to scope appear here — each with a link to what it actually does.
3 · Edition & deployment
- Greenfield — you can design straight to the S/4HANA target model, so weigh fit-to-standard against the customisation you genuinely need.
- The edition choice is a trade-off between standardisation and upgrade cadence (public cloud) versus customisation and control (private cloud / on-prem).
- Exact module availability and scope change by release and edition — confirm against SAP's official documentation and the edition-comparison guide before you commit.
Worked example
A group that already runs SAP ECC, wants group cash visibility and an FX hedging capability, and is leaning toward public cloud. This is an illustrative scoping pass to show what the tool returns — not a recommendation, and not a statement about what is available in any edition or release.
Needs ticked
- See cash positions and forecast liquidityticked
- Manage financial deals and instruments (FX, MM, securities, derivatives)ticked
- Aggregate FX and interest-rate exposuresticked
- Manage hedges and hedge accountingticked
- Connect to banks and process statementsticked
- Starting pointSAP ECC
- Cloud appetitePublic cloud
Shortlist
- SAP Cash Management (S/4HANA)Cash & liquidity
- Transaction Manager (TRM)Deals & risk
- One Exposure from OperationsDeals & risk
- Hedge ManagementDeals & risk
- Bank Communication Management + Electronic Bank StatementPayments & banking
Read it as: five needs, five components to scope — returned in catalogue order rather than the order you ticked them, so the list reads the same however you got there. The ECC starting point turns this into a migration project rather than an upgrade, and the public cloud lean adds a fit-to-standard trade-off to weigh against the customisation you genuinely need. What the shortlist deliberately does not say is whether each component is in scope for your edition and release — confirm that against SAP's official documentation.
How this works
Methodology
A scoping aid, not a configurator. Each need maps to the SAP component whose documented job is to address it, linked to a fact-checked guide; the edition section surfaces the trade-offs to weigh for your starting point and cloud appetite.
Assumptions
- The need→component mapping reflects each component's core function — read the linked guide for what it actually does in detail.
- A shortlist is a starting point for scoping with SAP or an implementation partner, not a licensing or configuration decision.
- The edition section describes general trade-offs (standardisation vs customisation), not per-module availability.
Limitations
- It does NOT tell you which module is available in which edition or release — that changes by release; confirm it in SAP's official documentation and the edition-comparison guide.
- It does not size licences, effort or cost, or account for your existing landscape and custom code.
- Module names and boundaries evolve across S/4HANA releases; treat the components as areas to investigate, not fixed product SKUs.
Frequently asked questions
Which SAP components can this selector shortlist?
Thirteen, grouped in four areas. Cash & liquidity: SAP Cash Management (S/4HANA), Bank Account Management and In-House Cash. Deals & risk: Transaction Manager, One Exposure from Operations, Hedge Management, and the Market Risk, Credit Risk and Portfolio Analyzers. Payments & banking: Bank Communication Management with Electronic Bank Statement, and Advanced Payment Management. Foundation: TRM accounting and posting, and market data. Each entry links to its own guide for what the component actually does — Hedge Management, for example, supports designating and monitoring hedges; hedge accounting is a separate, separately documented step.
Does anything I tick here leave my browser?
Not on its own. The selector runs entirely in the page: your ticked needs, starting point and cloud appetite are kept in this browser's local storage, and nothing is posted to a server. The one exception is deliberate — pressing Share link encodes those three values into the URL and copies it to your clipboard, so whoever you send that link to sees the same selection. Consent-gated analytics records that the tool was viewed, shortlisted, exported or shared; it never records which needs you ticked.
What do I get from Export markdown?
A sap-treasury-shortlist.md file containing a table of the needs you ticked, the SAP component each one maps to and a full link to that component's guide, followed by the edition considerations for your starting point and cloud appetite and the standing caveat to confirm scope with SAP. It is plain markdown, so it pastes straight into a scoping document, a ticket or a wiki.
Will my selection still be here when I come back?
Yes, in the same browser. The selection is saved locally as you make it and restored on your next visit, with a notice saying so and a Start fresh link that clears it. Nothing is synced to an account or to your other devices, a private window or cleared site data loses it, and if the browser refuses the save — storage full or blocked — the notice says that instead of pretending it saved. Opening a colleague's share link does not overwrite your own saved selection unless you press Keep it in this browser.
What does this tool deliberately not tell me?
Whether a given component is in scope for your edition and release. That changes release by release, so the selector maps needs to components and frames the edition choice as trade-offs to weigh, and never asserts availability — confirm the exact scope against SAP's official documentation and the edition-comparison guide. It also doesn't size licences, effort or cost, and it doesn't look at your existing landscape or custom code.
These answers are about the tool. The SAP questions behind it — what TRM is, which modules to select, how the editions differ — are answered in the implementation roadmap, the SAP TRM guide and the edition comparison.