Article · Payments

How to review a payment plan when an expected receipt changes

Trace which outgoing payments rely on a delayed or short customer receipt, then review the affected decisions using actual account-level funds.

View Markdown

First separate actual available funds from the expected receipt. Identify which outgoing payments depend on that expectation, check their dates and constraints, and present the affected decisions for review. A revised plan is useful only if its authorized actions can still be executed with the funds and timing available.

Keep the earlier assumption visible

When a receipt moves, preserve the previous expectation and record the new information with its source and time. A customer moving Friday’s payment to Monday changes a planning assumption. It does not by itself establish that the money will be available on Monday or that every outgoing payment can wait.

The useful first question is “Which decisions relied on this receipt?” Trace the affected payments, funding accounts and deadlines. Leave unrelated work intact. This produces a focused review instead of asking the controller to reconsider the entire plan from memory.

Check funds where they can actually be used

Use the applicable available balance for each funding account and distinguish it from forecasts, pending items and balances held elsewhere. Do not quietly assume an account transfer, overdraft or financing arrangement. Those are separate actions with their own availability and authority.

In a synthetic example, an account has $65,000 available, payroll requires $50,000 and a supplier payment requires $20,000. The two outflows total $70,000. A missing expected receipt leaves a $5,000 gap for that set of assumptions. The arithmetic identifies a question; it does not authorize a delay, borrowing or transfer.

Present options with their conditions

For each potential sequence, show the dates, required funds, relevant cutoffs and obligations it supports. Bring the real contractual requirements and business priorities to the authorized decision-maker. If a supplier payment is proposed for a later date, establish whether that date is actually permitted rather than calling it safe because the spreadsheet balances.

A changed plan may need a changed authorization. Record the version approved and the facts it depends on. If the later receipt arrives short, revisit the affected assumption before releasing a payment. An approval should not conceal a funding condition that is no longer true.

Follow the result and retain unresolved work

Confirm actual receipt and payment outcomes as they occur. Keep an uncollected remainder visible in AR; keep an uncertain outgoing instruction open until its outcome is established. A plan that looks feasible is different from a completed sequence with supporting evidence.

Alto’s Payments AI Wow is a future concept exploring this continuing coordination. Use it as a demonstration brief: change a receipt date, then change the amount and ask which decisions reopen. Confirm what Proper’s available product can currently do, which records it can access and where a person must intervene. If there is no feasible authorized path, the answer should show the gap clearly.

Questions & answers

Should expected receipts be included in the plan?

They can be included as clearly identified expectations with dates and evidence. Keep them distinct from actual available funds and show which decisions depend on them.

Does a revised cash plan authorize payment changes?

No. A plan explains a proposed sequence and its consequences. The business’s authorization process determines who can approve changed timing, funding or instructions.

Start with your workflow.

Bring your records, exceptions and the decisions that matter to your team.

Let’s talk Proper