Add your invoice history
Choose a file of paid invoices and a file of open invoices. PaidWhen checks the columns, dates, amounts, and duplicate IDs.
PaidWhen turns your payment history into a ranked collections list, showing which open invoices need attention first and how much cash is at risk.
When every overdue invoice looks equally urgent, teams chase the loudest account or the oldest balance. PaidWhen adds a forward-looking view, so your weekly review starts with the invoices that combine meaningful value with a higher chance of delay.
It does not replace your accounting system. It gives your team a clearer order of work.
Start with the sample data, then use exports from your own accounting system when you are ready.
Choose a file of paid invoices and a file of open invoices. PaidWhen checks the columns, dates, amounts, and duplicate IDs.
PaidWhen learns from older invoices and checks its estimates against newer ones. If the result is weak, it tells you.
Review invoices ranked by estimated cash at risk, inspect the reason, and choose the right follow-up for the customer.
Everyone sees the same priorities and the reason behind them.
PaidWhen reads and scores the two CSV files inside your browser tab. You do not need to include customer names, email addresses, phone numbers, bank information, or free-text notes.
Read the privacy detailsRun the sample or use your own CSV files. There is no account, subscription, or hidden usage limit.
Open the workspaceWe review your export, test whether the payment pattern is useful, produce the first ranked queue, and hand over a repeatable weekly process.
PaidWhen is for B2B finance, accounts-receivable, and bookkeeping teams that have enough invoice history to make a weekly collections review more focused.
You need one CSV of closed invoices and one CSV of open invoices. The required fields are invoice ID, account key, invoice date, due date, and amount. Closed invoices also need a payment date.
Sixty or more clean closed invoices is a practical starting point, with both late and on-time payments represented. More history usually produces a more useful test. PaidWhen warns you when the data is too thin.
It is the open invoice amount multiplied by the estimated chance of late payment. It helps a team balance probability with financial impact when deciding what to review first.
No. File reading, validation, scoring, and exports happen in your browser tab. If you request an optional action brief, only a small summary of dates, amounts, and risk values is sent—never your CSV or account and invoice IDs.
No. PaidWhen suggests a next step, but a person reviews the customer context and decides whether any message should be sent.
The sample is ready. No account or setup required.