Analyse the account
Payment history, prior replies, and open invoices per customer, before deciding what to send.
Flowwiz / Collect CashCollect cash without
[Receivables]
Collect cash without
manual chasing.
Most tools send more reminders. Collecting faster means knowing why an invoice is unpaid and taking the step that fits that customer.
Guide the approach
A predicted payment date and risk score choose between a light touch and active follow-up.
Act or escalate
Send, log the promise, pause the reminder, or raise a dispute task with the context attached.
Collections workflow
Analyse. Guide. Act.
Three steps, not one reminder sequence sent to everyone. A reliable payer gets a light touch; an account showing risk signals gets earlier attention.
- 01Analyse
Reads payment history, communication, and behaviour to predict when a customer will actually pay and how much risk they carry.
- 02Guide
Selects the workflow that fits that customer rather than applying the same dunning sequence to all of them.
- 03Act
Sends the reminder, logs the promise to pay, routes the dispute, or pauses the sequence.
Collections · needs a decision3 waiting
Northstar Studio$4,800Promise logged
Atlas Services$8,400Dispute to route
Meridian Labs$12,250High risk
Why an invoice is unpaid
A reminder cannot fix the actual reason.
Customers delay for reasons a generic chase does not touch. The workflow reads the invoices, emails, tasks, promises, remittance details, and payment history to find which one applies, then takes that step instead.
Reasons a reminder misses
- Timesheet missing
- Rate incorrect
- Purchase order issue
- Project milestone disputed
- Supporting documents missing
- Invoice sent to the wrong contact
- Question still unanswered
- Payment already initiated
What the workflow does instead
- Chase the missing timesheet internally
- Flag the rate for correction
- Route the PO query to the account owner
- Hold the reminder while the milestone is disputed
- Attach the documents the customer asked for
- Reissue to the right contact
- Answer or escalate the open question
- Stop chasing, and reconcile the payment already on its way
Prediction
Know who is going to pay late, before it happens.
Scoring moves the team from reactive chasing to managing the accounts that actually need attention this week.
- 01Historic behaviour
Average days late, broken promises, dispute frequency, communication pattern.
- 02Current exposure
Outstanding balance, recent payment activity, and customer-specific trend.
- 03Predicted date
An expected payment date per invoice, not a flat term assumption.
- 04Priority
Accounts ranked so attention goes where the risk is, not where the age is.
Predicted this week3 at risk
| Customer | Invoice | Predicted | Outstanding |
|---|---|---|---|
| Northstar Studio | INV-1048 | Fri 14 Mar | $4,800 |
| Meridian Labs | INV-1052 | 26 Mar | $12,250 |
| Atlas Services | INV-1039 | Held: dispute | $8,400 |
Coverage
Everything that goes into collecting faster.
The full set of collections capabilities available on the platform.
- 01Invoice follow-up
- 02Payment reminders
- 03Promise-to-pay detection
- 04Payment date prediction
- 05Customer risk scoring
- 06Negotiation workflows
- 07Dispute detection and routing
- 08Cash application support
- 09Root-cause classification
- 10Customer-specific sequences
- 11Escalation and task creation
- 12DSO reporting and outcomes
Proof Reported result
85.9 → 50.1 days DSO
Days sales outstanding for a professional services customer within three months, using Flowwiz collection workflows. An individual customer outcome, not a guaranteed result.
FAQ
Before you go further.
How are promises to pay handled?
A configured workflow records the commitment, updates the timeline, pauses the reminder, and notifies the account owner. If the date passes without payment, the sequence resumes automatically.
Can we get a DSO result like this?
That is the goal we work toward together. We start by measuring your current DSO, agree a target for the first three months, and design the workflow around the customers and invoices that slow you down. Then we review progress with you every month and adjust the workflow until the number moves. The 85.9 to 50.1 day result came from this same process with a professional services customer.
Can we keep our own collection process?
Yes. Sequences, escalation points, and tone are configured around the responsibilities your team already has.
What happens to a dispute?
The workflow assembles the invoice, the communication, and the open items, then routes it to the person who can resolve it, and holds the reminder until it is closed.
Does it send email from our domain?
Yes. Communication sends from your own domain, so customers see the address they already know.
How does it decide between a light touch and escalation?
By the payment prediction and risk score for that customer, plus any rules you set on amount, age, or segment.
Start
See it with your team’s context.
Bring your workflow, your systems, and who approves what.