An unpaid invoice does not chase itself. Someone has to open the accounting software, find the overdue invoices, write an email firm enough without being rude, then remember to do it again if nothing moves.
We have no Quebec statistic to quote here, and we will not invent one. But you know the mechanics: follow-up demands consistency and earns no credit. When the week gets busy, it is the first thing pushed back. Meanwhile the money stays with your customer.
Run the math on your own numbers: the total of your overdue invoices today, and the time your team spends each month chasing them. If you are paying interest on a line of credit while that money sits elsewhere, add it in. That is the cost of the task.
Five sub-tasks, with different weight and different risk. We put them in place one at a time.
A few days before the due date, a courteous email restates the amount, the date and how to pay. It is the most profitable reminder of all: it prevents the delay instead of repairing it.
Past the due date, follow-ups move through the stages you set: tone, delay between sends, maximum number of messages. The first one reminds, the last one states what comes next. Nothing goes out on a template you have not approved.
The customer who writes “send me what I owe” gets a complete, up-to-date account statement, without anyone assembling it by hand.
When a file runs past the planned stages, it leaves the automation and lands on your desk with the full history: what was sent, when, and what the customer replied. The hard call stays human.
Every message is recorded: recipient, date, content, reply. When a customer says they never received anything, the question is settled by opening the log.
The five numbers below belong to a plausible SMB, not to yours. Replace them with your own figures: the picture is redrawn with every keystroke.
One calculation convention, stated plainly: a month counts 4.3 weeks. Every other number is one you entered above — nothing is assumed elsewhere.
Based on your numbers, here is the order of magnitude
Amount tied up in overdue invoices
$30,000
25 overdue invoices × $1,200 per invoice = $30,000
Hours per month spent chasing
6.5 hours
15 follow-ups per week × 4.3 weeks × 6 minutes ÷ 60 = 6.5 hours per month
What that time costs
$208 per month
6.5 hours × $32 per hour = $208
The $30,000 overdue is not a cost: it is your money, somewhere else. Every day of delay won back on that amount is money landing in your account sooner. We add no interest rate and no cost of capital here: that figure depends on your own banking terms, and we will not invent it for you.
These amounts are an estimate computed on the numbers you just entered. It is not a guaranteed result: the calculation describes the current situation as you described it, and it predicts nothing.
The calculation stays in your browser: nothing is sent, nothing is stored, nothing is measured.
Calling is the shortest path. By form or by email, we reply within 1 business day. The audit takes 30 minutes and commits you to nothing.
Here is how a day runs once the system is in place. Every step is labelled: done by the AI, or kept by your team.
Invoices coming due soon trigger a courteous reminder. Invoices already overdue move to the next stage.
Whoever handles the books opens a short list: customer replies, promises to pay, files not to chase this week.
A customer asks for their account statement. They get it, up to date, with no one involved.
Payments received pull their invoices out of the follow-up queue. Nobody chases a customer who has already paid.
The owner sees the escalated files, with the full history and the decision to make.
Quebec SMBs often keep their books in Acomba, QuickBooks or Sage.
A connection is generally possible as soon as your software offers a connection interface; we verify this during the audit. We promise no integration before that check. If there is no interface, we look at exports, dropped files and assisted entry, and we tell you plainly what that changes for the project.
Data is hosted in Canada. When we hand over the system, you receive its Law 25 file: privacy impact assessment, processing register, list of subcontractors and the hosting region of every supplier.
Price range
CA$4,000 to CA$25,000
Timeline
First process in production in 2 to 6 weeks
A project runs between CA$4,000 and CA$25,000. Simple billing reminders wired to a single source: low end of the range. Several stages, several entities, an account statement assembled from two systems: higher up.
The first process is in production in 2 to 6 weeks. We start with the pre-due reminder, because it is simple and it measures quickly.
Not if it is done right. Messages carry your name, your tone and your payment terms; they are templates you approve before launch. What changes for the customer is consistency: the reminder arrives at the right moment, every time.
You exclude them, or you give them their own rules: longer delay, different tone, no automatic follow-up at all. Exceptions are part of the setup, not cases to catch after the fact.
A connection is generally possible as soon as your software offers a connection interface; we verify this during the audit. We promise no integration before that check. If there is no interface, we look at exports and dropped files, and we tell you plainly what that changes for the project.
You do. The automation handles written reminders, keeps the log and prepares the file; the hard call and the negotiation stay with a person. That is deliberate: it is where your judgment is worth something.
The first process is in production in 2 to 6 weeks. The effect is measured on your numbers: the overdue total before, the overdue total after, and the time your team no longer spends chasing.
The pages on this site that go with this one:
The free AI audit takes 30 minutes. We look at how your invoices go out, how you chase them today and where it stalls, then we tell you what to automate first and what it costs. No commitment.
Calling is the shortest path. By form or by email, we reply within 1 business day. The audit takes 30 minutes and commits you to nothing.