Skip to main content

Methodology

Receivables Collection Impact Planner methodology

Test how collection days and bad-debt assumptions affect receivables cash, funding cost and annual benefit.
Duc Nguyen X.By Duc Nguyen X.· Founder, Margin101Last reviewed: View update historyMethodology

Educational only: Business decision support, not accounting, tax or legal advice.

Privacy: Calculations run locally; Margin101 does not receive your commercial inputs.

Update policy: Reviewed when formulas or official dependencies change.

Scope: Market-neutral small-business planning using your own assumptions.

1. Formulas and units

Current receivables
currentReceivables = annualCreditSales ÷ periodDays × currentCollectionDays

Where

annualCreditSales
Annual credit sales (currency units/entered annual basis on the selected sales and tax basis)Source: Business record
currentCollectionDays
Current collection days (calendar days/current customer collection cycle)Source: Business record
periodDays
Days in annual basis (whole calendar days/entered annual calculation basis)Source: Business record
currentReceivables
Current receivables (currency units on one consistent tax basis)Source: Calculated output
Proposed receivables
proposedReceivables = annualCreditSales ÷ periodDays × proposedCollectionDays

Where

annualCreditSales
Annual credit sales (currency units/entered annual basis on the selected sales and tax basis)Source: Business record
proposedCollectionDays
Proposed collection days (calendar days/proposed customer collection cycle)Source: User decision
periodDays
Days in annual basis (whole calendar days/entered annual calculation basis)Source: Business record
proposedReceivables
Proposed receivables (currency units on one consistent tax basis)Source: Calculated output
Cash released
cashReleased = currentReceivables − proposedReceivables

Where

currentReceivables
Current receivables (currency units on one consistent tax basis)Source: Calculated output
proposedReceivables
Proposed receivables (currency units on one consistent tax basis)Source: Calculated output
cashReleased
Cash released (currency units on one consistent tax basis)Source: Calculated output
Annual funding saving
annualFundingSaving = cashReleased × annualFundingRate

Where

annualFundingRate
Annual funding rate (decimal annual funding-cost rate applied to released receivables (1 = 100%))Source: Business record
cashReleased
Cash released (currency units on one consistent tax basis)Source: Calculated output
annualFundingSaving
Annual funding saving (currency units on one consistent tax basis)Source: Calculated output
Annual bad-debt saving
annualBadDebtSaving = annualCreditSales × (currentBadDebtRate − proposedBadDebtRate)

Where

annualCreditSales
Annual credit sales (currency units/entered annual basis on the selected sales and tax basis)Source: Business record
currentBadDebtRate
Current bad-debt rate (decimal bad-debt fraction of annual credit sales in the current case (1 = 100%))Source: Business record
proposedBadDebtRate
Proposed bad-debt rate (decimal bad-debt fraction of annual credit sales in the proposed case (1 = 100%))Source: User decision
annualBadDebtSaving
Annual bad-debt saving (currency units on one consistent tax basis)Source: Calculated output
Total annual benefit
totalAnnualBenefit = annualFundingSaving + annualBadDebtSaving

Where

annualFundingSaving
Annual funding saving (currency units on one consistent tax basis)Source: Calculated output
annualBadDebtSaving
Annual bad-debt saving (currency units on one consistent tax basis)Source: Calculated output
totalAnnualBenefit
Total annual benefit (currency units on one consistent tax basis)Source: Calculated output

Money inputs and outputs use the currency selected in the scenario without changing the canonical methodology. Rates, margins, utilisation and buffers are entered as percentages and converted to decimal values for calculation.

2. Worked example

Input assumptions

The worked rows below come from the exact engine and the visible default assumptions.

Calculation and outputs

Example

The worked rows below come from the exact engine and the visible default assumptions.

Current receivables
60,000.00 currency units
Proposed receivables
30,000.00 currency units
Cash released
30,000.00 currency units
Annual funding saving
3,000.00 currency units
Annual bad-debt saving
3,650.00 currency units
Total annual benefit
6,650.00 currency units

The exact engine-derived outputs are shown in the labelled rows below.

Interpretation

The annual benefit combines entered funding and bad-debt effects; it is not a causal forecast.

Scenario study: collection days and estimated cash release

Treat collection-days value as an average-balance estimate

Use one annual credit-sales amount and day-count convention for both cases. The result estimates a balance difference; it does not promise a customer receipt date.

Input basis

  • Annual credit sales: 730,000 CU; day-count basis: 365.
  • Current collection days: 45; proposed scenario: 35.
  • Same currency and indirect-tax basis in both cases.
RowIntermediate calculationResult
Current estimated receivables730,000 ÷ 365 × 4590,000 CU
Proposed estimated receivables730,000 ÷ 365 × 3570,000 CU
Estimated cash release90,000 − 70,00020,000 CU

Interpretation

The 20,000 CU result is an average-balance estimate under the stated sales/day assumptions. Carry the collection change into a dated forecast before making a cash-timing decision.

Boundaries and next step

  • No customer payment promise, dated receipt or demand forecast is created.
  • Funding-rate and bad-debt benefits are separate user assumptions, not automatic consequences.

Continue with Receivables Collection Impact Planner or Thirteen-week Cash Flow Forecast.

3. Validation and boundary checks

  • The day basis must be positive and all three entered rates remain between 0% and 100%.
  • A worsening proposed scenario may produce negative savings.
  • Receivables are normalized using the same annual credit-sales and day basis.

4. Assumptions and source classification

  • All inputs use one consistent reporting period, balance date, currency and indirect-tax basis.
  • Targets and proposed values are user scenarios, not forecasts or benchmarks.

This planner has no current policy-data dependency. Its commercial assumptions are user supplied. Registered family-level regression suites exercise the shared business-logic engine and worked-result reconciliation.

5. Limitations

  • No market rate, statutory late-payment fee, bad-debt forecast or accounting classification is inferred.
  • This is educational decision support, not accounting, tax, legal or financial advice.

This is educational decision support, not tax, accounting, legal or financial advice. Check the treatment of your actual transactions under the rules that apply to your business and seek qualified advice where appropriate.

6. Update and evidence policy

Registered family-level suites test formula invariants and example reconciliation; the release ledger records that coverage without claiming a separate oracle for every line of public copy. There is no official threshold or benchmark to refresh for this planner. Commercial inputs remain user-supplied because they vary by business and contract.

Change history

  1. : Initial public release of the Receivables Collection Impact planner and methodology.

Related reading

Guides to interpret the decision and its assumptions.

Return to the planner