Promised cash, invoiced amounts and collected cash represent different events. Define each, reconcile timing and allocations, and show uncertain or unmatched items separately. A signed order or payment promise can inform planning, but it is not evidence that money has reached the account.
Name the event represented by each number
A signed agreement may authorise future work, an invoice requests payment and a bank receipt records an incoming movement. Delivery, acceptance and payment allocation add further milestones. State which event each view uses and the reporting cut-off. The same transaction can legitimately appear in several views at different dates, so differences do not automatically indicate missing money or a broken system.
Separate promises by evidence and timing. A buyer's proposed payment date, an agreed instalment schedule and a seller's assumption are different inputs. Record the latest confirmation and responsible owner. Do not replace an overdue promise with a new date without retaining history. A cash planning figure should identify what is committed, assumed or uncertain so operational decisions do not mistake a confident-looking total for a verified receipt.
Reconcile receipts to the obligations they settle
Use a stable reference to connect incoming receipts with invoices or other obligations where possible. Partial payments, combined remittances, fees, currency conversion and refunds can complicate matching. Keep unmatched money in a visible category with an owner rather than allocating it by guesswork. A bank movement may be real even when its commercial purpose is not yet established.
Apply one cut-off consistently across the bridge. A receipt initiated by a customer but not yet visible in the relevant account may belong in a pending category under the stated process. A payment received after month end should not silently rewrite the earlier snapshot. If bank settlement, accounting posting and operational allocation occur on different dates, record the distinction and choose the clock appropriate to the question.
Use the reconciliation to guide a realistic review
Build a bridge from invoiced open balance to allocated collections, credits and remaining open items. Keep future expected receipts outside the collected-cash total. Review large unmatched movements, missed promises and invoices awaiting acceptance before making collection assumptions. Each exception needs a next action, owner and evidence requirement. Avoid treating every difference as a customer failure when internal allocation or document errors remain possible.
Maintain the planning view alongside the observed view, with updates clearly dated. Compare previous promises with actual receipts to understand planning reliability without assuming past patterns will continue. A reconciliation supports understanding of recorded movements; it does not establish future liquidity or replace professional financial judgement. Material decisions should use the appropriate controlled records and make unresolved timing, currency and allocation issues visible.
A fictional cash-review bridge
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional studio begins a week with 12,000 currency units of open invoices. During the week, the bank shows receipts totalling 7,000. Of these, 6,000 are matched to those invoices and 1,000 is an unidentified customer transfer. An approved 500 credit also reduces the opening invoice population. The remaining open balance for that population is 12,000 minus 6,000 minus 500, or 5,500.
Customers separately promise another 4,000 next week. The studio reports 7,000 observed bank receipts, 6,000 allocated collections against the opening invoices, 1,000 awaiting allocation and 5,500 remaining open after the credit. It does not subtract the future promise or the unidentified transfer from that invoice balance. The unidentified amount receives a matching task, and the promise remains in a dated planning view. These fictional categories explain why several valid totals can differ without claiming that a promise is cash already collected. The reviewer also checks whether all seven thousand receipt units use the same currency basis and whether any bank fee was recorded separately. A conversion difference or fee should have its own bridge line, rather than being disguised as a short payment by the customer.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Define commitment, invoice, receipt and allocation events.
- Use one explicit cut-off for each snapshot.
- Keep unmatched receipts and future promises visible.
- Assign owners to timing and allocation exceptions.
Common questions.
Is a payment confirmation equivalent to a bank receipt?
It may be evidence of initiation, but confirm the relevant receipt or settlement event before calling the amount collected.
Why can receipts exceed allocated collections?
Some receipts may be unmatched, relate to other periods or settle obligations outside the selected invoice population.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse Accuralytix.
Found an error or a missing qualification? Send an editorial correction.
Check my data readiness.
Use a practical tool to turn this idea into a clearer starting point.
Check my data readiness