SAP Cash Management in S/4HANA

SAP Cash Management in S/4HANA is the redesigned solution for cash and liquidity — three areas: Bank Account Management, Cash Operations (the daily position), and Liquidity Management (the forecast) — built on One Exposure from Operations as its single source of cash-relevant data. The word that matters here is redesigned. If you're coming from classic Cash Management in ECC, do not assume your muscle memory transfers: the concepts survive, but the data model, the tools and most of the configuration are new. I've watched more than one project treat the S/4HANA move as a technical upgrade and then discover, in testing, that it's a re-implementation wearing an upgrade's clothes.

The three areas

S/4HANA Cash Management organizes into three parts, each answering a different question:

• Bank Account Management (BAM) — which accounts do we have, and who can act on them? Bank accounts and signatories as governed master data.
• Cash Operations — how much cash do we have today? The daily cash position, short-term cash management, and bank statement monitoring.
• Liquidity Management — how much will we have, and when? The liquidity forecast over the medium and longer term.

Three questions, three parts. Keep them straight in your head and the module stops feeling like a maze.

Built on One Exposure from Operations

The foundation under all three is the One Exposure from Operations hub — the single store of cash-relevant flows (table FQM_FLOW) that S/4HANA Cash Management reads from. This is the biggest architectural change from classic, and it earns its own article next, because until it clicks, the rest of S/4HANA Cash Management feels arbitrary. Once it clicks, the design suddenly makes sense: one place where every cash-relevant flow lands, and the position, forecast and reporting all read from it.

What changed from classic

For those of us who cut our teeth on classic Cash Management, the honest map of what's different:

• The data model. Classic maintained its own summary records, updated as documents posted. S/4HANA reads from One Exposure instead — a genuinely different foundation, not a reskin.
• The tools. Much of the classic transaction-driven work moves to Fiori apps.
• The organization. Reorganized into the three areas above.

The concepts a treasurer cares about — position, forecast, account control — all carry over. What changes is everything underneath, which is exactly why "we're just upgrading Cash Management" is the sentence that sinks the plan.

Bank Account Management

BAM manages bank accounts as master data — every account, its attributes, and its signatories — with review and, in the fuller version, workflow-driven opening, closing and change processes. It's the SAP home for the account-inventory and governance discipline every treasury needs: one controlled record of every account and who can act on it. Done well, it's also what makes account rationalization and eBAM something you can actually run inside SAP rather than in a spreadsheet on the side. (There's a basic tier and a fuller one with more governance and workflow — worth checking which your scope and licensing cover before you design around the richer features.)

Where this guide goes next

This is the map; the next articles walk the territory — starting with One Exposure from Operations and FQM_FLOW, because until that clicks, everything else in S/4HANA Cash Management feels arbitrary. Then Flow Builder, liquidity items and derivation, planning levels, and the bank-statement and BCM side.

Part of the SAP Treasury & Cash Management guide. See also what is SAP Treasury and Risk Management and building a daily cash position. The newsletter sends one finance-systems pattern every two weeks.