Check the files
PaidWhen checks required columns, dates, positive amounts, duplicate invoice IDs, and whether there are enough usable closed invoices.
How it works
A useful estimate should prove itself on later invoices.
PaidWhen checks whether your own payment history contains a repeatable pattern before asking your team to trust the ranked list.
The calculation
Six steps, shown in plain language.
The payment date is used to check what happened. It is never used to predict an open invoice.
Define late payment
A closed invoice is marked late when its payment date comes after its due date.
Learn only from the past
For each historical invoice, PaidWhen uses only account behavior that was already known at that time.
Test on newer invoices
Older invoices are used to learn the pattern. The newest quarter is kept aside to see how that pattern performs on later business.
Compare with a simple rule
The result must be more useful than assigning every invoice your company’s usual late-payment rate.
Rank the open balance
Each open amount is multiplied by its estimated chance of delay. The resulting cash-at-risk value sets the order of the list.
Reading the results
What the numbers mean.
The workspace includes plain explanations beside the technical measurements.
Late risk
The estimated chance that an invoice will be paid after its due date.
Cash at risk
Invoice amount × late risk. It combines likelihood with financial impact.
Ranking quality
How well the check put later-paid invoices above on-time invoices.
Probability error
How close the estimated percentages were to what actually happened. Lower is better.
When to be cautious
PaidWhen will not dress up weak data as certainty.
A run is marked limited or unavailable when there are too few invoices, too few examples of both outcomes, too little recent history to test, or no improvement over the simple comparison.
- History is tested in date order
- Future payment information is excluded
- A simple comparison appears beside the result
- Weak runs carry a visible warning
- Every customer action remains human-approved
Inspect a completed check.
The sample workspace shows the list and its reliability measures.