Skip to main content

Market-neutral small-business guide

How to Review Receivables Before a Cash Shortfall

Reconcile aggregate receivables, disputes and timing assumptions before running a privacy-safe cash-release scenario.

Complete the privacy-safe review in sequence

Printable receivables review

  • Lock the review date, currency, tax basis and privacy boundary. (not complete)
  • Reconcile the ledger and receivables control total to bank receipts; stop on an unexplained difference. (not complete)
  • In private records only, retain the invoice reference, amount, due date, expected date and evidence state. (not complete)
  • Separate paid/reconciled, committed, expected, uncertain and disputed receipts. (not complete)
  • Map each material aggregate receipt to its cash week and run a later-date downside. (not complete)
  • Assign a follow-up owner and date under the business’s lawful process; stop for disputed rights. (not complete)
  • Only after reconciliation, enter aggregate annual credit sales and collection-day assumptions in the planner—never customer-level data. (not complete)
  • Record the completion outcome, first affected week, action owner and escalation trigger. (not complete)

Prioritise review with evidence and dated cash checkpoints

Sequenced triage for private business records
CheckpointQuestion to answerAction or stop point
1. Verify due and dispute stateIs the balance reconciled, due under the private record and undisputed?Stop ordinary prioritisation for an unverified or disputed balance; use the approved local escalation path and obtain qualified advice where rights are unclear.
2. Check the promised dateIs there current evidence for a promised receipt date, and how reliable is it?Keep promised, expected and uncertain dates distinct; add a later downside date instead of predicting payment.
3. Compare amount with dated cash needWhich forecast week and user-defined cash boundary would the delay affect?Prioritise the decision consequence, not the largest invoice automatically; rerun the dated aggregate scenario.
4. Apply relationship and escalation constraintsWhat contract, service, relationship, approval or lawful-process constraint affects the next contact?Do not infer a collection tactic. Stop when the action needs legal, credit, accounting or insolvency judgement.
5. Record the next actionWho owns the action, when is it due and what evidence or cash trigger starts the next review?Record one approved action and review date in the private system; no automated customer ranking is produced.
This sequence organises a review. It does not predict payment, rank customers automatically or provide legal collection instructions.

Prepare baseline and downside totals from fictional rows

Fictional invoice-state review in generic currency units
Fictional local referenceAmountEvidence stateBaseline treatmentDownside treatment
Record A4,000Paid and reconciledActual bank receipt; not openActual bank receipt; not open
Record B6,000CommittedExpected Week 2Expected Week 2 unless evidence changes
Record C5,000ExpectedExpected Week 3Move to Week 5
Record D3,000UncertainShow separately in Week 4Exclude from available receipts until evidence improves
Record E2,000DisputedExclude and escalateExclude and escalate
Open total16,0006,000 committed; 5,000 expected; 3,000 uncertain; 2,000 disputed11,000 dated baseline plus 3,000 shown separately6,000 dated; 5,000 moved later; 5,000 excluded pending evidence/right
The 4,000 paid row reconciles to bank cash and is not part of the 16,000 open total. This scenario supplies no collection-period benchmark and assumes no disputed amount will be collected.

Record the completion outcome

Completion box

  • Review date, currency and tax basis recorded. (not complete)
  • Control total and bank receipts reconciled, or review stopped. (not complete)
  • Baseline and downside aggregate receipts mapped to weeks. (not complete)
  • Uncertain and disputed totals excluded or shown separately. (not complete)
  • First affected week and buffer effect recorded. (not complete)
  • Promised date, dated cash need and relationship or escalation constraint reviewed; invoice size was not used as the sole priority. (not complete)
  • Lawful action owner, action date and escalation trigger assigned. (not complete)
  • Only aggregate, non-identifying inputs prepared for the receivables planner. (not complete)

Prepare evidence before comparing waiting with financing

Post-reconciliation hand-off for one entered invoice-financing scenario
CheckpointEvidence to enterStop point
Expected collection timingA verified baseline date and a labelled downside date for the reconciled aggregate amountStop when the receivable is disputed, unreconciled or its enforceability is unclear.
Entered financing termsAdvance, fee, retained balance and collection assumptions copied from reviewed business recordsStop when provider terms are unidentified or cannot be compared on the same scope.
Wait-versus-finance costEntered waiting, funding and opportunity-cost assumptions on the same period and currency basisDo not claim financing is cheaper, suitable or available without the entered evidence and appropriate review.

Compare only the reconciled entered scenario

Receivables review questions

Should a disputed invoice enter the cash baseline?
Do not treat it as committed cash. Keep the amount and issue in private records, exclude or isolate it in the scenario and seek qualified advice where the right or process is unclear.
Which data belongs in the receivables planner?
Only reconciled aggregate annual credit sales, collection-day, funding and bad-debt assumptions on the stated basis. Customer names, invoice identifiers and contract details stay outside Margin101.
What is a normal collection period?
This checklist provides no universal benchmark. Compare a consistently defined internal baseline and scenario, then retain the customer, contract, cash and operating trade-offs.

Sources and methods

Change history

  1. Expanded the existing canonical owner with a bounded decision workflow, clearer interpretation boundaries and exact tool or methodology hand-offs without creating a competing article intent.
  2. Initial public release of the article after pre-launch factual, editorial, source and presentation review.