Skip to content 
Ask a treasury team what they open first in the morning and the honest answer is rarely a report — it is two questions. How much cash do we have, where is it, and is it enough? And what does the next four weeks look like? In SAP S/4HANA, Cash Management answers those with two views built from the same machinery: the cash position for actuals and the near term, and liquidity planning for the forecast. This post explains how both are assembled — because once you see the assembly, the reasons the numbers sometimes lie become obvious.
The cash position: actuals, organised
The cash position starts from bank account balances, fed by imported bank statements and by the postings hitting your cash and clearing accounts. But a balance alone is not a position. SAP organises every amount by planning level and planning group: the planning level says how certain and how detailed a figure is (an actual bank balance sits at a different level from a posted-but-not-yet-cleared payment), and the planning group says which account or counterparty view it belongs to.
That classification is the configuration that matters. Get the planning level derivation wrong on a house bank account and the position still totals correctly — while every drill-down by bank or account is quietly wrong, which is worse, because the total earns trust the detail has not.
Liquidity planning: the forecast is a classification exercise
The liquidity forecast extends the same logic forward. Planned flows arrive from FI payables and receivables, from purchasing and sales documents in MM and SD, from TRM transactions, and from payroll and tax calendars. Each flow is classified by a liquidity item — operating receipts, supplier payments, debt service, capex, taxes — and the liquidity item is what turns a pile of due dates into a forecast a treasurer can reason about: inflows and outflows by category, by week, by entity.
Two practical consequences follow. First, forecast quality is mostly master data and derivation quality: if liquidity items are derived from the wrong characteristics, the forecast is precisely wrong instead of roughly right. Second, flows with no source document — a known tax payment, a one-off transfer — enter through memo records, and memo records never retire themselves. When the real posting arrives, someone has to clear the placeholder, or the forecast counts the payment twice. It is a small discipline that separates forecasts people trust from forecasts people argue about.
The daily cash desk routine
Tools aside, cash management is a routine. A typical morning in a well-run S/4HANA cash desk:
- Confirm yesterday landed. Check that bank statements imported for all house banks; chase the missing statement before trusting any balance.
- Read the cash position. Balances by bank and currency, today’s expected settlements against them, any account drifting toward a limit or an overdraft.
- Act on the position. Concentration sweeps, funding a short account, placing a surplus — the decisions the position exists to support.
- Refresh the forecast. Review the coming days’ liquidity items, add or clear memo records for known one-offs, and flag variances between yesterday’s forecast and yesterday’s actuals.
- Close the loop. Note what the forecast got wrong and why; forecast accuracy improves through this feedback, not through more data.
None of these steps is technically difficult. The implementations that fail are the ones where step 1 or step 4 has no owner, so the position is read off stale statements and the forecast quietly fills with dead memo records.
Where it usually hurts
- Bank statements that fail to import and are noticed days later, so the “position” is archaeology
- Planning levels derived inconsistently across house banks, breaking every by-bank view
- Liquidity items too coarse to act on (“other outflows” as the largest line) or too fine to maintain
- Memo records created without an owner or an expected clearing date
Going further
Aumtech Solutions’ course SAP Cash & Liquidity Management Training covers this end to end — cash position setup, planning levels and groups, liquidity planning and liquidity items, and the daily routine that keeps both honest — in recorded lessons for $99: https://www.aumtechsolutions.com/courses/sap-cash-liquidity-management/
Not sure where your own cash setup stands? The free SAP Treasury Health Check scores your processes across treasury, payments, and bank statements in about 20 minutes: https://www.aumtechsolutions.com/treasury-health-check/
