The starting point
85.9 days sales outstanding at the beginning of the period.
Flowwiz / Customer outcomesThe work changes.
[Reported result]
The work changes.
The result follows.
One reported result from a professional services customer, and the workflow changes behind it.
The workflow change
Invoice follow-ups, payment promises, and dispute routing connected into one process.
The result
50.1 days after three months, 35.8 fewer days to collect.
What changed
The collection story behind the number.
The result came from changing the process, not from sending more reminders. Three things were connected that had been separate.
- 01Follow-ups
Recurring invoice follow-up ran as workflow rather than from individual inboxes.
- 02Promises
Payment commitments were captured, dated, and tracked against the invoice.
- 03Disputes
Disputes were identified and routed to the people who could resolve them.
- 04Result
Measured on the same basis as the baseline, over three months.
Days sales outstandingReported outcome
| Period | DSO | Change |
|---|---|---|
| Baseline | 85.9 days | n/a |
| Month 1 | 72.4 days | −13.5 |
| Month 2 | 59.8 days | −12.6 |
| Month 3 | 50.1 days | −9.7 |
FAQ
Before you go further.
Is this result guaranteed?
No. It is one reported customer outcome. Your result depends on your baseline, customer behaviour, workflow design, and adoption.
How should we measure our own?
Record a baseline and a defined evaluation period before you start, then compare completed work, unresolved exceptions, and the finance outcome together.
What counts as a fair comparison?
The same DSO definition and the same customer population at both ends. The customer above was measured on a consistent basis across the three months.
What else should we look at besides DSO?
Unapplied cash, disputed invoice volume, promise-to-pay reliability, and the age of open exceptions. A DSO number moving on its own does not tell you whether the process improved.
Can we talk to the customer?
Ask the Flowwiz team during a demo. Reference conversations are arranged directly rather than published here.
Start
See it with your team’s context.
Bring your workflow, your systems, and who approves what.