Almost every accounting system can handle step one: send a reminder when an invoice goes overdue. It's step two that decides whether the money actually comes in. The customer who promises to pay on Friday and doesn't. The invoice copy that never gets sent because the request lands in a shared inbox nobody reads. That part of accounts receivable still happens by hand at most finance teams, no matter how modern the accounting system is.
Fortnox, Visma and most accounting systems can send a reminder. None of them handle what happens when the customer replies, or doesn't reply at all. A pattern that keeps showing up in customer conversations: 80-90% of customers pay on time with no follow-up at all, and the rest account for almost all of the manual work. The problem isn't reminder volume, it's the missing process for what happens after.
Why the reminder isn't enough
Fortnox, Visma and most other accounting systems are built to send outbound information, not to hold a conversation. A reminder goes out, and the system's job ends there. If the customer replies with a question, a dispute, or a promise to pay next week, that reply lands in a shared inbox where nobody owns the follow-up.
A concrete example that comes up in almost every customer conversation: the reminder goes to a generic billing address, something like invoices@company.com, instead of a specific person. Nobody on the receiving end feels ownership of that inbox, so even a perfectly worded, on-time reminder risks never being read by anyone who can actually act on it.
That's why two companies with an identical reminder feature can end up with completely different results. The difference is rarely in how the reminder is worded. It's in what happens during the days after, while the invoice is neither paid nor actively being tracked by anyone.
| Share | |
|---|---|
| Pay on time, with zero follow-up | 85% |
| Account for nearly all the manual work | 15% |
An approximate pattern from customer conversations, not an exact measurement per customer.
The numbers above are a pattern, not a precise measurement, but they show up in nearly every customer conversation we've had: most customers pay without anyone having to do anything at all. It's the small remaining group that eats up a finance team's time, because they need an answer to a question, a new payment promise tracked, or a reminder sent to someone who actually reads their email.
The invoice copy goes to a shared inbox. Nobody on the other end knows whose job it is to open it, so it just sits there.
What actually happens after a reminder
In practice, follow-up looks something like this at a typical finance team: someone exports a list of overdue invoices to Excel, goes through it manually, emails the customers who look most urgent, and types the replies back into the same spreadsheet by hand. Next week, the same thing happens again from scratch, because the list has no memory of what happened last time.
Take a typical example: a $4,000 invoice goes 14 days overdue. The automatic reminder goes out as it should. The customer replies the next day with a simple question: can you resend the invoice, we can't find it. That email lands in a shared inbox at 3:40pm on a Friday. By Monday morning it's already buried under twenty other emails, and the invoice sits unanswered until someone happens to go through the list again, often a week later. Nothing about this scenario is unusual, and none of it requires a better-worded reminder. It requires someone, or something, to actually handle the reply the same day it arrives.
| Stage | Share collected |
|---|---|
| Before due date | 8% |
| Day 3 | 22% |
| Day 7 | 41% |
| Day 14 (reminder sent) | 58% |
| After active follow-up | 89% |
Illustrative pattern, not a live measurement. The big move doesn't happen at the reminder itself, it happens after, once someone actually follows up.
Five signs your follow-up is leaking time
- The Excel list gets updated by hand — every week someone manually goes through overdue invoices instead of the system keeping track for you.
- Invoice copies get sent one at a time — the same question comes up every month, and the same person answers it every time, by hand.
- Payment promises get forgotten — someone promises to pay Friday, nobody tracks whether it actually happened, and the invoice quietly slips through the cracks.
- Every customer gets the same treatment — a $500 invoice and a $500,000 invoice go through the exact same flow, in the exact same order.
- Collections becomes the default path — when nobody follows up in time, external debt collection becomes the fix for what was really a follow-up problem.
Not every overdue invoice is equally urgent. One that's three days late and one at risk of write-off need different things. The point isn't more reminders, it's seeing which ones are actually burning and acting on those first.
Do the math on what follow-up costs you
This is the calculation almost nobody runs, because the work is spread across several people and never gets booked as its own line item. The base formula is simple: hours per week on manual follow-up, times an internal hourly cost, times 52 weeks.
If a finance manager spends 5 hours a week chasing overdue invoices, at an internal hourly cost of roughly $40, that comes out to around $10,400 a year, in labor alone. That's before counting the money that arrives later than it should, or the time spent answering the same question over and over.
The number above is a worked example, not a guarantee, but it's worth running with your own hours for real. For most finance teams, the answer is higher than they expected before they did the math.
Three ways to control how much the agent does on its own
Superclaim doesn't take over the entire process on day one, it's a dial you set yourselves, per customer or per stage of the flow.
| Mode | Description |
|---|---|
| Review mode | The agent proposes every action, a human approves before anything sends. Most teams start here. |
| Autopilot before due date | The agent sends proactive reminders before the invoice is even overdue, fully on its own. Low risk. |
| Full autopilot | The agent runs the entire sequence within rules you set, and only hands off what genuinely needs a judgment call. |
How an agent actually solves this
Superclaim sits as a layer on top of your existing accounting system and inbox, not as a new system to feed. The agent reads the same data a finance manager would: invoice history, prior replies, how a specific customer tends to pay, and acts on it instead of running the same template on everyone.
| Moment | Traditional system | Superclaim |
|---|---|---|
| Reminder at due date | Yes, automatic | Yes, automatic |
| Follow-up after an unanswered reminder | Manual, if someone gets to it | Automatic, daily |
| Invoice copy on request | Sent by hand | Sent directly by the agent |
| Prioritizing between customers | Same flow for everyone | By amount, age, and risk |
| Escalation on silence | Rare, or too late | Proposed by the agent, approved by you |
What happens if the customer still doesn't pay
Most cases resolve within this flow, but not all of them. When a customer still hasn't replied or paid after the full sequence has run, the agent escalates the case to you, not straight to collections. You decide whether to write it off, pause it, or send it onward.
On an actual decision to escalate, the case moves on to PS Finance, our collections partner, with one click instead of a manual handoff full of new forms and duplicate work. The idea is that collections should be the last resort after follow-up has actually had a chance to work, not the default path because nobody got to it in time.
Getting started
- Connect your accounting system and inbox — Fortnox or Visma, and the mailbox follow-up already happens from today. No new platform to learn.
- Set the rules — which customers get which tone, which amounts get priority, and which autonomy mode you start in.
- Review the first cases — the agent proposes, you approve, and you see exactly what it would have done before handing over more responsibility.
- Move to autopilot at your own pace — most teams start with pre-due reminders and expand from there.
Live within 24 hours is the promise, not because everything is finished the same day, but because the connection to Fortnox or Visma and your inbox can genuinely be up and running that fast.
Conclusion
More reminders don't fix a follow-up problem. If the goal is actually getting paid, not just getting an email sent, the question isn't "are we sending reminders?" it's "what happens when the customer doesn't reply to one?". For most finance teams, the honest answer today is: too little, too late, and by hand.
