You finished the work three weeks ago. The invoice went out the same day. And now the money you already earned is sitting in someone else's bank account while your own bills come due. If you freelance in the UK, this is not bad luck — it is the normal state of affairs. Nearly half of all invoices issued by UK small businesses arrive late, and the average late payer keeps your money for almost a month past the agreed terms. The most awkward part of freelancing was never the work. It is the chasing.
That chase is exactly what Sage handed to an AI agent in February 2026, when it launched the Payments Agent inside Sage Sole Trader, its free bookkeeping app for non-VAT-registered sole traders. You still approve every action, but the agent drafts the invoice from a voice note, watches its status, sends the reminders, and matches the payment when it lands. Whether you use Sage or not, the launch marks a shift worth understanding: payment chasing is moving from a task you dread to a system that runs itself. This guide explains what the agent does, the numbers behind the UK's late-payment problem, and how to build a chase system — automated or manual — that gets you paid faster.
The Scale of the Problem You Are Chasing Against
Start with the numbers, because they explain why an AI agent for payment chasing exists at all.
Sage's SME Performance Pulse for June 2026, drawn from anonymised accounting data across almost 150,000 businesses, found that 49% of invoices issued by UK small businesses were overdue, with firms waiting an average of 27 days beyond their agreed payment terms. Separate Sage research puts the average amount small businesses are owed in overdue invoices at £42,000 — a figure that has risen for three consecutive years. Research from Bibby Financial Services, published in spring 2026, puts the average SME's unpaid-invoice pile at £66,770, up 10% year on year, and estimates late payment costs the UK economy £11 billion a year. A Hiscox survey of 1,000 sole traders and small-business owners in February 2026 found the typical respondent chasing 14 late payments a year, adding up to 331 cumulative days of waiting.
For the solo end of the market the figures are smaller but sting harder: IPSE, the body representing the self-employed, found the average self-employed worker is owed about £5,230 in overdue invoices at any one time. When there is no payroll department and no credit controller, that £5,230 is chased by the same person who did the work — you, in the evening, rewriting the same polite email for the fourth time.
That is the job the Payments Agent takes on.
What the Payments Agent Actually Does
Sage Copilot is the AI assistant embedded across Sage's products; the Payments Agent is its invoice-to-cash workflow inside the Sage Sole Trader mobile app. The journey it automates covers the full life of an invoice:
- Create the invoice in seconds, from a typed note or a voice message, instead of opening a template and filling in fields.
- Track its status — sent, viewed, paid, overdue — without digging through email threads.
- Send reminders that nudge the client toward faster payment.
- Collect the money through a built-in Pay Now button, so the client can settle the invoice the moment the reminder lands.
- Match the payment to the right invoice automatically when it arrives, closing the loop in your records.
Two design choices matter more than the feature list. First, every action requires your approval — the agent prepares, you decide. The reminder goes out because you said so, which keeps you in control of the client relationship. Second, the launch added automatic transaction categorisation and smart reminders to the app, so the records behind the chase stay accurate with less manual upkeep. Accurate records matter beyond tidiness: with Making Tax Digital for Income Tax phasing in from April 2026, sole traders above the income threshold face quarterly digital updates to HMRC, and a well-kept invoice ledger is the raw material those updates are built from.
Sage says early Copilot adopters report saving more than five hours a week on manual tasks. Treat vendor numbers with the usual scepticism — but the direction is not in doubt. Across the industry in 2026, accounts-receivable work has become one of the most automated corners of small-business finance: venture investors committed well over $100 million to startups selling AI chasing, payment matching and credit scoring, and every serious product in the space keeps a human approving the send. The pattern is consistent: the agent does the watching and drafting, the person keeps the relationship and the money.
Late Payment Is a Systems Problem, Not a Wording Problem
Here is the uncomfortable truth the agent's design quietly admits: most late payments are not caused by a badly worded reminder. They are caused by vague terms, late invoicing, no fixed follow-up routine, and friction between the reminder and the payment. An agent fixes these because it is a system. If you chase manually, you need the same system. Here is what it looks like.
Set the expectation before work starts
Agree payment terms in writing before the first hour is billed: the price, when you will invoice, and when payment is due. Short terms get money in faster — "due on receipt" or seven days beats 30 days every time. A real due date on every invoice matters twice over: it tells the client when to pay, and it gives your reminder sequence — human or automated — something concrete to count from.
Invoice immediately
Delayed invoicing creates payment delays almost day for day. Invoice on completion, or on the contractually agreed date, without letting finished work sit unbilled while you move on to the next client. This is the single cheapest change on this list.
Run a fixed chase sequence
Decide your reminder routine once, so you never have to wonder whether it is "too soon":
- 3 to 7 days before the due date: a friendly heads-up with the invoice attached again. This is the reminder most likely to get acted on, because it arrives before payment becomes a problem.
- On the due date: a brief note that payment is due today. Assume positive intent.
- 3 days after the due date: a polite, direct reminder asking when payment will be sent. Reattach the invoice and the payment link.
- Two weeks overdue: a firmer note, and a phone call if you have the number. Voice resolves what email threads cannot.
- Around 60 days overdue: a final formal reminder referencing your next step — whether that is a collections process, statutory interest, or pausing further work.
Every reminder repeats the same core details: invoice number, amount, due date, and exactly how to pay. The Pay Now button in Sage's app is this principle in product form — each reminder carries the payment with it, so the client never has to go looking for your bank details.
Remove every reason to pause
Offer more than one way to pay: bank transfer plus at least one instant option. Each additional step between "I should pay this" and "paid" costs you days. When a client does raise a query — a disputed line item, a missing purchase order number — resolve it the same day. A disputed invoice is not a late invoice yet, but every day it sits in dispute is a day added to your wait.
The Bookkeeping Behind Every Chased Invoice
Whether an agent or your own calendar runs the chase, the books underneath it work the same way. Issuing an invoice creates a receivable — money earned but not yet in hand. Receiving payment clears it. The chase exists in the gap between those two entries, and clean books are what let you — or software — see exactly which invoices are sitting in that gap and for how long.
In a plain-text ledger, the life of one invoice looks like this:
2026-02-10 * "Invoice #104 - Brand design" "Client: Acme Ltd"
Assets:Receivables:Acme-Ltd 1200.00 GBP
Income:Freelance:Design -1200.00 GBP
2026-02-24 * "Payment received - Invoice #104"
Assets:Checking 1200.00 GBP
Assets:Receivables:Acme-Ltd -1200.00 GBPThe first entry books the income and the receivable on the day you invoice — your profit for February includes this work even though no cash has moved. The second entry, two weeks later when the client pays, moves the value from receivables to your checking account without touching income again. That separation is the whole point: income is recorded once, at invoice time, and the payment is just cash changing buckets.
This structure is also what makes automatic matching possible. When the agent reports that £1,200 arrived and clears invoice #104, it is proposing exactly that second entry. And when you want to see who owes you what, an aged-receivables view — every open receivable grouped by how many days past its due date it sits — falls straight out of these postings. The Beancount documentation covers balance assertions and scheduled transactions if you want to harden this further, and a Fava dashboard renders the receivables position visually so the invoice drifting past 30 days is impossible to miss.
One discipline makes all of this work: book the invoice the day you send it, not the day you get paid. Books updated at payment time cannot produce an overdue list, cannot age your receivables, and cannot tell an agent — or you — that invoice #104 needs chasing today.
Where the Agent Stops and You Start
An agent that drafts and tracks is genuinely useful. It is not a replacement for judgement in three situations.
Disputes need a person. When a client replies "this isn't what we agreed" or "the PO number is wrong," the correct next step is a conversation, not another reminder. Route anything that smells like a dispute out of the automated sequence immediately and handle it directly. Chasing a disputed invoice on autopilot poisons the relationship and rarely produces payment.
Large or strategic balances deserve a call. The fixed sequence above already says this at the two-week mark, but it bears repeating: for your biggest client, a two-minute call beats any sequence of emails. Agents handle the routine so you have time for the calls that matter.
Know your statutory backstop. In the UK, the Late Payment of Commercial Debts (Interest) Act 1998 gives you the right to charge business clients statutory interest at 8% above the Bank of England base rate, plus fixed compensation of £40, £70 or £100 depending on the size of the debt. You do not need to have mentioned it in your contract — the right exists by law. Most freelancers never invoke it, and waving it at a good client over a week's delay would be absurd. But for the client who treats your invoices as an interest-free credit line, mentioning in your 60-day reminder that statutory interest now applies changes the conversation. It is the escalation the whole sequence quietly points toward.
Mistakes That Keep Freelancers Waiting
- Invoicing late. Every day between finishing the work and sending the invoice is a day added to the wait, and clients mentally start their payment clock when the invoice arrives, not when the work was done.
- Terms agreed verbally or not at all. "I'll sort you out next month" is not a due date. Without written terms and a date on the invoice, your first reminder reads as a favour requested rather than an obligation restated.
- Chasing from memory. If the follow-up schedule lives in your head, busy weeks mean skipped reminders, and skipped reminders teach slow payers that your deadlines are soft. A calendar routine or an agent's queue beats memory every time.
- Re-attaching nothing. A reminder without the invoice and payment link attached forces the client to search their inbox — and gives the disorganised ones, who are most of the late payers, a reason to stall.
- Letting it slide past 60 days. The older a debt gets, the less likely it is to be paid in full. A firm final reminder with a stated next step, sent on schedule, recovers money that silence writes off.
Pick one of these to fix this week. If your invoicing currently lives in your head and your inbox, the highest-value move is the fixed chase sequence: write down the five touchpoints, put them in your calendar or your app of choice, and let the next overdue invoice test the system instead of your nerve.
