Article map
The daily cash position is treasury's opening operating record. It connects what the banks report, what the business expects to pay or receive, and what treasury intends to fund, transfer or invest. When the process is weak, users spend the morning collecting spreadsheets, chasing missing balances and debating which total is correct. Decisions are delayed, excess cash remains idle and urgent funding is arranged with limited context.
A strong process is time-bound, risk-based and evidence-driven. It distinguishes confirmed flows from estimates, shows the freshness of each source, applies policy before execution and reconciles the outcome. This article describes the operating model required to make daily cash positioning both fast and controlled.
1. Define the position horizon and cut-off
Daily positioning should begin with a clear horizon. Some organisations manage only the current day; others maintain a rolling five- or ten-business-day view. The horizon should reflect payment cycles, market cut-offs, funding access and business volatility.
The process also needs a formal data cut-off. A position produced at 8:30 a.m. should state which bank balances, payment files and forecast updates were available at that time. Later events may create an updated version, but the original decision basis should remain recorded.
Without cut-off discipline, the position becomes a continuously changing spreadsheet. Reviewers cannot know which version supported a deal or whether later information has been incorporated.
2. Establish the opening bank position
Opening balances should be sourced from expected accounts, not assembled from whichever statements arrive first. The account inventory should identify reporting method, expected arrival time and materiality.
The process should test completeness, duplicates, stale data, currency and balance continuity. Missing material accounts should create an escalation before the position is approved. Where an estimate is necessary, it should be separately identified with rationale and sensitivity.
The opening position should retain bank-native balance type and value date. A ledger closing balance, available balance and value-dated balance can differ, particularly where uncleared items or overdraft arrangements exist.
3. Incorporate settled and pending movements
Transactions received after the prior close can materially change today's starting point. The position should identify overnight sweeps, bank charges, failed payments, unexpected collections, returned items and value-date adjustments.
Pending transactions should not be treated as settled merely because they appear in an ERP or payment system. Status matters: proposed, approved, transmitted, accepted by bank, scheduled, settled, rejected or cancelled.
A controlled status model prevents double counting. For example, an approved payment may be included as a current-day outflow, but once the bank transaction is visible it should not remain as a separate forecast item.
4. Build a hierarchy of current-day flows
Current-day inflows and outflows should be classified by certainty. A practical hierarchy may include:
- settled bank movements;
- bank-accepted payments and confirmed collections;
- approved obligations with known value date;
- high-confidence forecast flows; and
- judgemental or uncertain flows.
The hierarchy allows treasury to calculate a base position and an at-risk position. It also highlights which expected receipts should not be relied upon for critical payments.
Flow sources should remain visible. ERP payables, payroll files, tax schedules, debt records, investment maturities, payment workflows and business submissions each carry different control characteristics.
5. Separate legal-entity and currency positions
A positive group total can conceal an entity overdraft or a currency shortfall. Daily positioning must therefore preserve legal-entity ownership and settlement currency before consolidation.
Treasury should identify whether internal transfer, cash-pool sweep, foreign-exchange conversion or external borrowing can resolve each shortfall within cut-off. The position should include bank account, credit limit and permitted transaction route.
Consolidated reporting remains useful, but decisions occur through legal entities and accounts. The system should never imply that surplus cash in one entity has automatically funded another.
6. Add policy and minimum-liquidity requirements
The executable surplus is the projected closing balance after known flows, operating buffers, account limits and policy requirements. Minimum balances may reflect payment volatility, local restrictions, overdraft avoidance, collateral needs or business continuity.
The rules should be configurable by entity, currency and account. A blanket buffer may be inefficient; no buffer may be unsafe. Overrides should require reason and approval.
Policy can also specify permitted investments, maximum tenor, counterparty limits, borrowing sources and internal transfer preferences. Embedding these rules before dealing reduces rework and prevents action outside mandate.
7. Turn the position into a decision proposal
A useful cash position should recommend or support specific actions: draw a facility, repay debt, invest a surplus, execute an FX swap, transfer cash, change a sweep or retain a buffer.
The proposal should show amount, entity, currency, value date, counterparty or internal route, expected post-action position and policy checks. Alternatives can be compared where material. For example, an entity shortfall could be met through local borrowing, intercompany funding or a pool adjustment, each with different cost and timing.
Decision support should not remove professional judgement. It should make the inputs and consequences of judgement visible.
8. Apply maker-checker review proportionately
The preparer should review feed exceptions, classify flows and propose actions. An independent reviewer should challenge completeness, unusual movements, forecast reliance, buffer compliance and proposed transactions.
Review intensity can be risk-based. Routine positions within limits may use streamlined approval, while unusual deficits, manual overrides or large transfers require enhanced review. The platform should record the checks performed rather than relying on an email saying “approved.”
Delegated authority should distinguish approval of the position from authority to execute a deal or release a payment. One individual should not create the data, approve the action and execute it without compensating control.
9. Manage time and market cut-offs
Daily cash management is constrained by bank, payment, investment and foreign-exchange cut-offs. The workflow should therefore show deadlines and count down to required action.
A late balance feed may have a larger consequence at 11:45 a.m. than at 8:00 a.m. Escalation rules should reflect remaining options. If a sweep cut-off is missed, the fallback may be an external borrowing or overnight overdraft.
The operating calendar should also account for holidays by currency and country. A value date that appears to be tomorrow may not be a settlement day for the relevant market.
10. Execute through controlled channels
Approved actions should be transmitted through authorised dealing, payment or bank-connectivity channels. The position record should retain the deal or transfer reference, approval, bank acknowledgement and settlement status.
Manual execution creates additional risks: incorrect account, amount, value date or beneficiary. Where manual channels remain, independent confirmation and post-execution verification should be explicit.
The position should update as actions progress. A proposed transfer is not the same as a settled transfer, and a drawdown request is not available liquidity until conditions and bank confirmation are complete.
11. Reconcile planned and actual outcomes
At the end of the day or next morning, treasury should compare the approved position with actual bank activity. Differences can arise from timing, amount, rejection, duplication, unforecast activity, bank fee, value dating or classification.
Variance should be assigned to the relevant source and owner. A customer receipt arriving one day late is different from a payment file failing transmission. This analysis improves both the positioning process and the broader cash forecast.
The position should close with unresolved items carried into an exception queue. It should not be overwritten by actuals in a way that erases what was expected.
12. Define operating metrics and service levels
Important metrics include time to first position, time to approved position, material-account coverage, stale balance value, manual adjustment value, unclassified flows, decision completion before cut-off, overdraft incidents and planned-versus-actual variance.
Service levels should apply across the chain. Banks, interfaces, local entities and business units may each have expected delivery times. Treasury should distinguish a process delay from a source delay and address the root cause.
A faster process is valuable only if confidence remains high. Speed achieved by excluding difficult accounts or bypassing review is not improvement.
13. Design resilience and fallback procedures
Critical daily processes need fallback routes. Treasury should know how to obtain balances if an API fails, how to approve urgent actions if the workflow is unavailable, how to contact banks and how to restore the authoritative record afterward.
Fallback should not mean uncontrolled activity. Emergency procedures should define permitted users, limits, evidence, secondary communication and retrospective review. Periodic simulation helps ensure that contact details and access remain valid.
Resilience also requires key-person coverage. The position should be reproducible by trained alternates using documented procedures and system evidence.
Practical illustration: funding a morning shortfall
At 8:15 a.m., a manufacturing entity shows ₹18 crore available cash and ₹42 crore of confirmed supplier and tax payments. A ₹30 crore customer receipt is expected but has not been acknowledged. The entity has a ₹50 crore committed facility and access to an intercompany pool with a 10:30 a.m. cut-off.
Treasury treats the customer receipt as uncertain, proposes a ₹30 crore internal transfer and retains the facility as fallback. The reviewer confirms the source account has adequate usable cash and approves the transfer. When the customer receipt arrives at 10:05 a.m., treasury reduces the transfer before cut-off. The actual-versus-position review records the receipt timing and updates the customer's forecast profile.
The process avoids both an overdraft and unnecessary borrowing because certainty, cut-off and alternatives were visible together.
Implementation checklist
A controlled daily cash-positioning process should include:
- defined horizon, cut-off and versioning;
- expected-account completeness and freshness checks;
- opening balance, overnight movement and pending-item logic;
- flow certainty and status hierarchy;
- entity and currency positions before consolidation;
- minimum liquidity, account limits and policy rules;
- action proposals with post-action position;
- independent review based on risk and materiality;
- cut-off, holiday and fallback awareness;
- controlled execution and bank-status tracking;
- planned-versus-actual reconciliation; and
- metrics for timeliness, coverage, exceptions and outcomes.
Common operating failures
Common failures include relying on unconfirmed receipts, double counting approved and settled payments, hiding stale accounts, aggregating entities before addressing local deficits, approving after market cut-off, treating a requested drawdown as completed and overwriting the planned position with actual data.
Another failure is judging process quality only by preparation time. A position produced quickly but without coverage, review or reconciliation is not decision-ready.
Closing perspective
Daily cash positioning is where treasury data becomes treasury action. The process should establish a reliable opening position, incorporate flows by certainty, apply policy, support timely decisions and preserve an evidence trail through settlement and reconciliation.
When this operating record is controlled, treasury can move cash with greater confidence, reduce avoidable borrowing, invest genuine surplus and improve forecasting through daily feedback. The result is not merely a faster morning report; it is a more accountable liquidity process.
Frequently asked questions
What is daily cash positioning?
Daily cash positioning is the controlled process of establishing opening liquidity, incorporating known and expected current-day flows, deciding funding or investment actions and reconciling the resulting bank movements.
What is the difference between cash positioning and cash forecasting?
Cash positioning focuses on near-term executable liquidity, usually today and the next few days. Forecasting extends across longer horizons and includes assumptions with greater uncertainty.
Who should approve the daily cash position?
The approval model should reflect materiality and risk. A preparer should establish the position, an independent reviewer should challenge data and assumptions, and authorised dealers should execute actions within delegated limits.