Cash Positioning That Holds Up Under Scrutiny
A bank balance can look healthy at 9:00 a.m. and be operationally unavailable by noon. Payroll files may be approved but not yet debited. Card settlements may be pending. A customer payment may be recorded as received in the ledger while still subject to processor timing. Cash positioning is the discipline of separating the number in the account from the cash the business can actually deploy.
For an owner or CFO, this is not a reporting exercise. It determines whether to release a vendor payment, accelerate collections, move funds between accounts, approve a hire, or preserve runway. The answer has to be based on evidence that can be traced to transactions, reconciled to the bank, and projected according to actual payment timing.
Cash Positioning Is More Than a Cash Balance
A cash balance answers one narrow question: how much money was in an account at a point in time? A cash position answers the operating question: where is cash held, what is restricted or committed, which inflows are likely to arrive on specific dates, and which outflows will clear before then?
That distinction matters most in businesses with multiple accounts, recurring payroll, processor settlements, invoices, debt service, and vendor payment terms. A company might show $420,000 across its bank accounts while only $95,000 is available after payroll, tax reserves, approved bills, and near-term loan payments. Treating the gross balance as deployable cash creates a false sense of capacity.
A useful position therefore combines three layers: cleared cash, known near-term movements, and forecasted movements. Each layer should remain visible. Blending them into one unexplained number may make a dashboard look simpler, but it removes the evidence needed to act with confidence.
Build Cash Positioning From Reconciled Evidence
The starting point is not an income statement or a top-down forecast. It is the bank and payment activity that determines when money moves. Every position should begin with balances that reconcile to $0.00 against the underlying accounts, then layer in transactions with known timing.
Start with account-level cleared cash
Capture the cleared balance for every operating account, savings account, payroll account, merchant processor reserve, and debt-related account. Then identify cash that is not freely available. Restricted customer funds, minimum balance requirements, tax reserves, and lender-controlled accounts should not be treated as general operating liquidity.
Account-level visibility also prevents a common error: assuming that consolidated cash can move instantly. A balance held in a processor reserve may not be accessible this week. A payroll account may be funded for a specific payroll run. The position should preserve those constraints rather than flatten them.
Model timing, not just categories
Transaction category is useful, but timing drives cash decisions. A $60,000 sales invoice is not equivalent to $60,000 of cash expected tomorrow. The forecast needs its due date, collection history, customer-specific behavior, and any known dispute or approval dependency.
The same applies to outflows. Rent may be contractually fixed. Payroll is usually highly certain once approved. Contractor payments may move within a range. A purchase order is not the same as an approved vendor bill, and an approved bill is not always the same as a scheduled bank debit.
A practical position distinguishes the status of each movement:
| Cash movement | What the position should show | | --- | --- | | Cleared bank transaction | Actual cash movement and posting date | | Scheduled payment | Expected debit date and confidence level | | Customer invoice | Expected collection date, not only invoice due date | | Processor settlement | Gross sales, fees, reserves, and settlement timing | | Recurring obligation | Rule-based amount and next expected occurrence |
This is why direct-method cash forecasting is more useful for daily management than a cash estimate derived backward from net income. Net income can explain performance. It cannot, by itself, explain whether payroll clears on Friday.
Reconcile before projecting
Forecasting on top of unreconciled data compounds uncertainty. If an uncategorized bank debit, duplicate card feed, missing settlement, or stale balance exists in the historical record, the projected position inherits the error.
The control is straightforward: each position should trace back through a reconciled ledger to transaction-level rows. When a number changes, the team should be able to identify whether it changed because cash cleared, a forecast rule changed, an invoice date moved, or an assumption was updated. Without that provenance, a cash forecast becomes difficult to trust and impossible to audit.
Run the Position as an Operating Workflow
Cash positioning becomes valuable when it is reviewed on a reliable cadence. For many businesses, that means a short daily review and a more detailed weekly planning session. The purpose is not to rebuild a spreadsheet. It is to resolve exceptions and make decisions before timing gaps become emergencies.
In the daily review, compare actual cleared cash with the prior projected position. Investigate material variance. If a settlement was delayed, determine whether the cause is processor timing, a reserve, a bank holiday, or an incorrect rule. If an expected customer receipt did not arrive, update the collection date and assess the impact on obligations due before the revised date.
In the weekly review, look further ahead. Confirm payroll, tax payments, debt service, major vendor commitments, expected collections, and planned transfers. The time horizon depends on the business. A company with tight working capital may need day-level visibility for the next 13 weeks. A well-capitalized business may focus on weekly liquidity while preserving daily controls around payroll and settlements.
The discipline is to treat variances as information, not noise. Repeated late collections from one customer should change that customer's expected cash timing. A processor that consistently settles two business days after sales should be modeled that way. Deterministic rules should improve with observed behavior, while retaining a replayable record of why the forecast changed.
Forecast the Cash Position Without False Precision
Forecasts should express what is known and what remains conditional. Presenting one exact ending balance three months from now can imply certainty that does not exist. A better approach is to show a base case grounded in committed and historically supported movements, alongside bounded scenarios for material uncertainty.
For example, a business may model a base case in which 85% of invoices collect on their expected date, a downside case with a seven-day delay for its largest customer, and an upside case where a pending contract closes on schedule. The scenarios should alter explicit drivers, not silently change a result.
That makes the model useful for decisions. A hiring scenario should show the incremental payroll amount, pay dates, taxes, benefits, and the date the change begins. A pricing scenario should show the expected impact on billing and collections, not merely a revised revenue line. A vendor extension should shift the actual expected debit date while preserving the underlying obligation.
The question is not whether a forecast is perfectly accurate. No operating forecast is. The question is whether assumptions are visible, the result can be replayed, and the team can see the cash consequence of being wrong.
Common Cash Positioning Failures
The most damaging failures are usually control failures rather than mathematical ones. One is using book cash without checking bank reconciliation status. Another is counting invoices as cash without reflecting collection behavior. A third is ignoring settlement timing, fees, reserves, and chargebacks in payment processor activity.
Teams also get into trouble when they maintain separate versions of the truth. Accounting has one close process, operations has a payment tracker, and leadership has a cash spreadsheet. Each may be reasonable in isolation, yet none is continuously connected to the others. The result is manual rework and meetings spent debating whose number is current.
Opaque forecasting creates a related risk. If a system cannot explain which transactions, rules, dates, and assumptions produced a projected balance, finance cannot validate it. AI may help identify anomalies or propose a classification, but it should not be allowed to override the reconciled calculation path. Cash requires controls that can be inspected.
Make the Position Decision-Ready
A decision-ready cash position should let a finance leader move from balance to evidence in seconds. It should show current cash by account, near-term inflows and outflows by date, restricted or committed amounts, forecast confidence ranges, and the transactions behind every material figure.
That is the operating model Shekl is designed to support: a continuously reconciled ledger paired with direct-method cash intelligence and scenario controls. The goal is not a prettier cash dashboard. It is one reconciled truth that remains usable when the business needs to decide what can be paid, funded, delayed, or approved.
The next time an account balance appears comfortable, ask a harder question: after the cash already spoken for clears, what remains available on each day that matters? The quality of that answer is the quality of your cash position.