For a project-based business, cash coverage is the ability to see whether available and credibly expected cash can cover the obligations that need to be funded next. The calculation becomes more useful when it is tied to the jobs, invoices, and payouts creating the exposure.
A bank balance alone cannot answer that question. Neither can an A/R total or an accounts-payable report in isolation.
Quick answer
A practical cash-control view connects:
- Receivables — what customers owe and how reliable the timing appears
- Payout obligations — what has been approved, is active, or has failed
- Job economics — which projects are creating the exposure
- Funding gaps — where credible inflows do not safely cover obligations
- Operator actions — what needs review, collection, funding, or resolution first
The goal is not to predict cash perfectly. It is to identify the situations where an operator should not assume the money will be there.
Why project businesses have a timing problem
Many project-based companies pay contractors, crew, venues, vendors, or other direct costs on a timeline that does not perfectly match customer collections.
A job can be profitable on paper and still create a short-term funding problem if:
- The customer invoice is not due yet.
- A milestone payment is late.
- An expected receivable has not settled.
- Crew obligations became larger than planned.
- A payout failed and needs resolution.
- Several jobs require cash at the same time.
That is a working-capital problem, but operators experience it as a queue of concrete decisions. The working capital guide for project businesses explains how the timing of collections and obligations creates that gap.
Do not treat every receivable as cash
One of the easiest ways to overstate coverage is to count an invoice as if it were already money in the bank.
A conservative cash view separates evidence from hope. An unpaid invoice can be economically important without being immediately available to fund an obligation.
| Item | Cash-control treatment |
|---|---|
| Settled cash | Available subject to normal controls |
| Credible near-term receivable | Expected, but not equivalent to settled cash |
| Overdue receivable | Requires collection attention; timing is less reliable |
| Approved payout obligation | A real funding requirement |
| Failed payout | Requires operator resolution and should remain visible |
The point is not to assign universal accounting rules to every business. It is to prevent an operational dashboard from hiding timing risk.
Connect cash pressure back to the job
Portfolio totals are helpful, but job-level context makes them actionable.
Suppose a production has an overdue $18,000 customer invoice and $11,000 of approved or near-term crew obligations. Another job has a $6,000 receivable due next week and only $1,500 of remaining obligations.
A single company-level A/R total might show $24,000 outstanding. The job-level view reveals that the first production deserves more attention because the collection and payout timing are directly connected.
This is also where profitability matters. A job with a funding gap and deteriorating forecast margin may deserve different action than a healthy-margin job with a short administrative delay.
Build an operator action queue
A useful cash dashboard should not stop at red and green indicators. It should convert financial exceptions into a ranked worklist.
Examples include:
- Failed payout that requires investigation
- Conservative funding gap before an upcoming obligation
- Approved payout that has not yet been funded
- Overdue receivable affecting near-term coverage
- Job with a material Margin exception
- Currency or evidence limitation that prevents a safe assumption
The queue should also preserve the evidence behind each action. If one invoice or payout clearly supports the alert, the operator should be able to open that record directly rather than re-researching the issue.
A practical cash-control cadence
Daily or before payout activity
Review failed payouts, approved-unfunded obligations, and material funding gaps.
Several times per week
Review overdue receivables that materially affect near-term coverage and coordinate collections work.
At job review
Look at Margin exceptions alongside receivable and payout exposure. Profitability and liquidity are different questions, but they can reinforce each other.
At finance review
Export or summarize the active queue and visible totals so the team can document which issues were resolved and which remain open.
Where Kelvaro Cash fits
Kelvaro Cash connects Collect receivables, active payout obligations, and Margin context into a cash-control workspace. It surfaces job-level exposure and a ranked action queue for evidence-backed issues such as failed payouts, funding gaps, approved-unfunded payouts, overdue receivables, and Margin exceptions.
The design is intentionally conservative: uncertain inflows should not silently become assumed funding.
Explore Kelvaro Collect for the receivables workflow, Kelvaro Margin for job economics, or the full Kelvaro Financial Operations stack.
FAQ
What is cash coverage?
Cash coverage is a view of whether available and credibly expected cash can cover obligations that need to be funded. For a project business, a useful view links that exposure to the jobs, receivables, and payouts creating it.
Is an unpaid invoice the same as available cash?
No. An invoice is a receivable, not settled cash. It can be included as expected inflow in planning, but a conservative operating view should distinguish it from funds that have actually arrived.
What is a funding gap?
A funding gap occurs when the resources considered safely available do not cover the obligations that need to be funded within the relevant time horizon. The exact calculation depends on the business and the evidence used.
Why connect cash control to job margin?
Cash pressure and profitability are different, but seeing them together helps operators understand whether a liquidity issue is merely timing-related or is occurring alongside deteriorating job economics.