Lesson 1 of 5
Why cash visibility matters
5 min
A company can be profitable and still run out of cash. Profit is an accounting result over a period; cash is what is in the bank today and what will arrive or leave in the coming days and weeks. Treasury's job is to make sure there is always enough cash in the right account, in the right currency, at the right time, without leaving too much idle. That job starts with cash visibility: a reliable daily view of cash across all banks and companies.
What treasury needs to know each morning
- How much cash is in each bank account at the start of the day, by currency.
- Which payments are going out today and in the next few days: the supplier payment run, payroll, taxes, loan repayments.
- Which receipts are expected: customer payments due, intercompany settlements.
- Where cash must be moved: to cover an account that will go negative, or to sweep surplus to an investment or concentration account.
- Whether any bank account is close to an overdraft limit or covenant threshold.
Before SAP S/4HANA, many companies answered these questions in spreadsheets fed by bank portals and AP and AR reports. It worked, but it was slow, error-prone and depended on one or two people. SAP S/4HANA Cash Management brings the same view into the system, built from bank statements, the bank G/L accounts and open items in AP and AR.
How cash visibility connects to AP, AR and banking
Every earlier course in this track feeds the cash view. The payment run decides when cash leaves, so its proposals are tomorrow's outflows. Incoming payments and dunning drive when cash arrives. Bank statement processing tells the system what actually happened. If any of those processes is late or wrong, the cash position is wrong too, and treasury makes decisions on bad data.
- AP invoices and payment runOpen payables by due date; payment proposals show tomorrow's outflows
- AR invoices and incoming paymentsOpen receivables by due date; cleared receipts reduce expected inflows
- Bank statementsActual balances and movements per account
- Bank G/L and clearing accountsPostings not yet on a statement
- Cash position and forecastOne view per bank account, company code and currency
Licensing and edition differences
This is an area where the edition and license matter, and you should confirm them for your own system. SAP S/4HANA includes a basic scope for all finance customers, often called basic cash management or bank account management "lite": bank account master data, a cash position, and memo records. The full scope (SAP S/4HANA Finance for cash management) adds features such as approval workflows for bank accounts, signatory management, liquidity items, and fuller liquidity forecasting and analysis, and it requires a separate license. SAP publishes a note comparing the bank account management scopes. In Public Edition, cash management capabilities are delivered as scope items and their availability also depends on what was licensed. Before a project designs anything here, the program should confirm with SAP which scope Contoso owns.
What would you do?
Contoso's treasurer asks why the daily cash position in SAP S/4HANA showed 2 million USD more than the bank portal yesterday. Investigation shows yesterday's statement for one account was not imported. What does this tell you about cash visibility?
- Profit is not cash; treasury needs a daily view of cash by bank, company and currency.
- Cash management has three layers: bank account management, cash operations and liquidity management.
- AP, AR and bank statement processing all feed the cash view; their quality decides its accuracy.
- Basic scope is included; full cash management needs a separate license. Confirm scope early.
Check your understanding · not graded
Lesson check
1. Which data feeds today's cash position most directly?
2. Which layer of cash management covers today's cash position and bank transfers?
3. What should a project confirm before designing cash management?
4. Why does a late payment run affect the cash view?