Revenue belongs in a forecast when the contract terms support recognition. Cash belongs in a bank account only after the customer pays, and treating those as the same thing leaves finance teams exposed.
The forecast can look healthy while the account runs thin
A forecast often starts with an enterprise invoice: a signed agreement, a go-live date, a renewal, or a contracted minimum. The revenue team sees a deal that closed. Finance sees an amount that meets the company’s recognition policy. Leadership sees a quarter that may land.
Then Friday arrives and the payment status still reads “failed.”
The failure could be mundane. An accounts-payable contact has changed. The purchase order number is missing. A customer’s payment portal rejected the invoice format. A card expired. The invoice landed in an unmonitored inbox. None of those explanations changes the immediate problem: payroll, cloud bills, contractors, and tax obligations run on cash timing.
The operational gap grows when the forecast treats an invoice as a completed event. It is an open process with several handoffs: correct billing data, clear terms, a valid purchase order, delivery evidence when required, approval routing, dispute handling, and persistent follow-up. A signed contract does not perform those steps on its own.
This distinction matters most for companies with a small number of large customers. One delayed enterprise payment can erase the cushion created by several smaller accounts paying on time.
Revenue recognition answers a different question
Revenue recognition asks when the company has earned revenue under its accounting policy. Collections asks whether, when, and how the customer will pay. Both matter, but they answer different questions.
A company can correctly recognize revenue and still face a collection problem. It can also receive cash before it has earned all of the related revenue, such as an annual subscription paid upfront. The accounting treatment may be sound in both cases while the operating picture remains incomplete.
That is why a finance dashboard needs more than booked revenue and recognized revenue. It needs a current view of:
- Cash collected against the period’s invoices.
- Accounts receivable by customer, invoice age, and dispute status.
- The next payment action and the person responsible for it.
- Expected payment dates based on confirmed customer information, not the original due date alone.
- Concentration risk, especially where one customer represents a large share of expected collections.
The original due date is useful, but it can become a false comfort. A 30-day term does not mean cash will arrive on day 30. It means the invoice entered a process whose weak points should be visible early.
Collection failures usually begin before the invoice goes out
Finance operators often inherit collection risk at the moment an invoice is issued, but the cause may sit earlier in the sales and implementation process.
A seller may close a deal without confirming who approves invoices. An implementation team may finish work without documenting the acceptance step the customer requires before payment. A contract may promise net-30 terms while the customer’s procurement system pays on a fixed monthly run. The invoice can be technically correct and still be difficult for the customer to process.
The practical response is to make collection readiness part of the commercial workflow. Before a large invoice is issued, confirm the legal entity, billing address, tax treatment, purchase-order requirement, invoice-submission method, payment contact, and internal approval path. Record the answer somewhere finance can use, rather than leaving it in a sales thread or an account manager’s memory.
For recurring revenue, the same discipline applies at renewal. A customer who paid last year may have changed systems, budget owners, or payment terms. Treating renewals as automatic collections invites avoidable surprises.
This is a familiar operating lesson in other parts of a company. A lead that looks qualified can still disappear if a system buries the follow-up, as explored in The Lead the Dashboard Nearly Buried. Revenue collection has the same dependency on visible ownership and timely action.
Build a cash forecast that can survive a failed invoice
A useful cash forecast separates committed revenue from expected collections. It should show the confidence level behind each incoming payment and change when new evidence appears.
For example, an invoice with a confirmed payment date from the customer’s accounts-payable team deserves more confidence than one that is merely within terms. An invoice in dispute deserves less. A large invoice with no purchase order should not quietly carry the same weight as a customer who has confirmed receipt and scheduled payment.
Give every overdue or at-risk invoice an owner and a next action. “Follow up” is too vague. “Confirm missing PO with customer procurement by Tuesday” creates accountability and a deadline. Escalation rules help too: an invoice that crosses a defined age, exceeds a defined amount, or belongs to a strategically important customer should move from routine reminders to an account-level conversation.
The goal is not to pressure customers indiscriminately. It is to find the real blocker while there is still time to act. A missing document is easier to fix before the month closes. A disputed scope issue is easier to surface before it becomes a 90-day receivable.
On Friday afternoon, the most useful forecast is the one that admits the invoice failed, lowers expected cash accordingly, and names the next move. That version may be less pleasant to present. It gives the company a chance to decide with the numbers it actually has.
Comments
No comments yet.