What Changed in Treasury on S/4HANA

The functionality of SAP Treasury did not shrink on S/4HANA. The assumptions underneath it changed: the data model moved, ownership moved, and the posting rules became considerably stricter. Most treasury migration pain is not a missing feature — it is a configuration chain that used to tolerate gaps and no longer does.

Bank Account Management: configuration becomes master data

In ECC, house banks were maintained as configuration and moved by transport, which meant IT owned the data Treasury depended on. In S/4HANA, bank accounts are master data, maintained in production and owned by Treasury, with workflow approval, an audit trail and a change log built in. This is an organizational change wearing a technical costume: Treasury inherits governance work it did not previously do, and projects that treat it as a data-migration task discover the problem in user acceptance testing. Somebody has to design the approval workflow before go-live.

Classic cash management is gone

The reports Treasury ran every morning no longer exist in that form. The classic cash position (FF7A), the classic liquidity forecast (FF7B) and the classic Liquidity Planner are replaced by SAP Cash Management, with interactive, drillable Fiori apps updated in real time and Bank Account Management as a core component. Some classic settings survive underneath — planning levels and planning groups are still configured — but the reporting layer users actually touched has changed, which makes this a training problem as much as a technical one.

Two tables to understand

Both follow the same idea: collapse scattered data into one source. ACDOCA, the Universal Journal, holds general-ledger and subledger line items in one table, with Treasury sitting in the subledger broken down by treasury position. One Exposure from Operations (FQM_FLOW) is the central repository for cash-flow and exposure data, fed from Transaction Manager, financial accounting, materials management and electronic bank statements, so the cash position reads from one place rather than assembling itself from several. A custom report that reads the old cash-management tables directly is why it stops working.

The chain that has to be complete

A treasury position is held per valuation area. If that valuation area posts to financial accounting, an accounting principle must be specified; the accounting principle determines which ledger receives the posting; and the assignment must exist for the specific company code being posted. S/4HANA enforces this chain far more strictly than classic G/L ever did. In ECC a gap often went unnoticed. Here the posting simply fails — and the error points at accounting, not Treasury, so the investigation frequently starts in the wrong module. The fix is to check the mapping for every company code and every valuation area before go-live, not just the ones that were tested.

Hedging and exposures, joined up

Exposure Management 2.0 integrates natively with hedge accounting, so exposures can be assigned directly to a hedge plan and are visible from inside hedge accounting — removing the spreadsheet that used to sit between the two. Both internal and external position management assume parallel valuation is configured correctly, which means a hedge-accounting failure often traces back to the valuation-area chain rather than to hedging setup itself.

Before go-live

The items that surface late and cost the most: the valuation-area-to-ledger chain verified for every company code; the bank-account approval workflow designed and tested; custom reports reading old cash tables rebuilt; business partners established for counterparties; and user training focused on the replaced morning reports, because that is the moment users decide whether the migration went well.

Sources & further reading

• SAP Help — Cash and Liquidity Management (FIN_FSCM_CLM)The business function covering workflow-driven bank account processes and Bank Account Management. Verified live.
• SAP Community — Treasury & Risk ManagementPractitioner coverage of the ACDOCA and One Exposure changes. Verified live.

Module scope and transaction availability vary by release. Verify against SAP Help and the simplification item list for your target release. SAP guidance, transaction availability and dates change between releases and editions. Verify anything here against SAP Help for your own situation before you commit to it. This article is independent commentary and is not affiliated with SAP or any implementation partner.