Accounts Receivable for Freelancers: A Weekly 20-Minute Process

Accounts receivable is the money clients owe you for work you have already invoiced. It is not your bank balance, it is not this month's income, and — depending on where you file and how you account — it may not be taxable revenue yet either. It is a list of promises with dates on them, and the only thing that turns those promises into cash is somebody looking at the list on a schedule.

This is that schedule: a weekly pass that takes about twenty minutes at a modest invoice volume, and that is deliberately boring. It is the routine that stops invoices becoming crises. If one already has — if a client has gone quiet on a balance that is sixty days old — that is a different problem with a different playbook, and it is covered in the escalation ladder for a client who will not pay. Come back here afterwards, because almost everything on that ladder is preventable by the process below.

You can run all of it in a spreadsheet. There is an ungated CSV at the end.

Why weekly beats chasing when you remember

Sporadic collection has a structural flaw that has nothing to do with discipline: the interval between reviews is the maximum lateness you cannot see. Look monthly and an invoice can sit thirty days past due before it enters your attention, by which point the person who approved the work has moved on and the accounts-payable run you missed is a month away. Look weekly and nothing gets more than seven days past due before somebody reads it.

The second reason is emotional, and it matters more than the arithmetic. Most freelancers do not dislike collections — they dislike deciding to do collections. A fixed slot removes the decision. You are not confronting a client about money; it is Friday, and this is the Friday list.

The UK government's 2026 response to its late-payment consultation puts the cost of the alternative in hours: businesses affected by late payment spend an average of 86 hours a year chasing invoices, and are collectively owed around £26 billion at any given time — roughly £17,000 per affected business. Those figures are UK-specific and cover businesses of every size, so read them as scale rather than as your forecast. The direction is the point: unstructured chasing is expensive in the currency freelancers have least of.

Four words that are not synonyms

Most receivables confusion is vocabulary. Keep these four apart and the rest of the process gets easier.

Whether an invoice counts as income yet depends on your accounting method and your jurisdiction, and the difference is not academic. The IRS notes that most individuals and many sole proprietors with no inventory use the cash method, under which income is reported when you receive it — so an unpaid invoice is not yet income at all. In Canada the default runs the other way: the CRA says you generally have to report business income using the accrual method, reporting it in the period you earn it regardless of when it lands. Same invoice, two different answers to "is this revenue".

This is why "I invoiced £40,000 this quarter" is a sentence that needs a second half. Ask your accountant which method applies to you before you build any tax or drawings decision on top of a receivables number.

The minimum receivables list

Twelve fields. Fewer than this and the weekly pass turns into archaeology; more and you have started building accounting software.

Two rules about the sheet itself. If you bill in more than one currency, keep one sheet per currency: a total that adds dollars to euros is not a number you can act on, and a mixed sheet quietly invites one. And this list is an operating aid, not an accounting ledger — it exists to drive next actions, not to close a year. Your accounting software or your accountant owns the books.

The weekly 20-minute process

Print this. The timings are a shape, not a stopwatch — at ten open invoices most weeks finish early, and the weeks that overrun are the weeks worth the time.

Minutes 0–3: reconcile what actually arrived

1. Open your bank feed and your payment processor for the last seven days.
2. Match each deposit to an invoice number, not to a client name — a client with two open invoices will pay the wrong one about as often as the right one.
3. Record part payments as part payments, with the amount outstanding updated. A part payment is the most common collections stall there is: it buys goodwill and a month of silence.
4. Mark nothing paid on the strength of a promise, a screenshot, or a "payment's gone out today". Paid means the money is in the account.
5. Note anything you cannot match and move on. Unidentified deposits are a question for the client, not a puzzle to solve at minute two.

Minutes 3–6: read the aging list

Sort by days overdue, descending, and read it in buckets rather than as one number. Total outstanding tells you almost nothing: £12,000 of which none is due for three weeks is a healthy book, and £12,000 of which £9,000 is ninety days late is a different business.

Formal aging reports conventionally use flat 30-day intervals — current, 1–30, 31–60, 61–90, over 90 — and that is what accounting software and Stria's own receivables ledger report. The finer buckets above are for deciding what to do this Friday; the 30-day ones are for reading the shape of the book over a quarter. Use both and do not try to reconcile them.

Minutes 6–10: prioritise by risk, not by age alone

Take the overdue rows and rank them. Age is one input among several, and the biggest number is not automatically the first call.

• Amount outstanding. Concentration of risk, not size of grievance.
• Age. How long the silence has run.
• Client response. Answering and paying late is a very different situation from not answering.
• Active work. Are you still delivering against this balance?
• Contract terms. What do your own terms actually entitle you to do next?
• Dispute status. A disputed invoice is not a late invoice. Route it separately.
• Delivery to the right person. Did the invoice reach accounts payable, or the creative lead's inbox?
• Missing documentation. No PO, no vendor onboarding, no approved timesheet.
• The relationship. A client you want in two years earns a phone call, not a template.

Resist turning this into a score. A weighted number implies a confidence nobody has about whether a particular client will pay, and the one time it is badly wrong is the time you trusted it instead of your judgement about a specific relationship. Rank the list, take the top three, move on.

Minutes 10–15: send the right message

One message per row, matched to the bucket. Templates are in the next section. The discipline is that each message names the invoice number, the amount outstanding, the due date, and one requested action — and that you never send the same message twice.

Minutes 15–18: write down the next action

Every row you touched gets a next action with a date on it, an owner, and — if the client committed to anything — a promised payment date. Three reminders and no next-action date is not follow-up, it is a paper trail of you being ignored.

Minutes 18–20: fix one upstream cause

Spend the last two minutes on prevention rather than collection. Pick the single thing that would have stopped the worst row on today's list, and change it: the deposit policy, the milestone structure, the due date, the billing contact, the PO requirement, the approval that has to land before you can invoice, or the reminder schedule. One a week compounds. Deposits do more work here than anything else, which is why how much deposit to ask for is a receivables decision and not just a pricing one.

The follow-up ladder

Five rungs. The ladder's job is to make each step obviously different from the last, so the client can tell that something has changed.

Three days before due. A short courtesy note, only for material amounts. This is the highest-value message on the ladder and the one almost nobody sends: it catches the wrong-recipient and missing-PO failures while there is still time to fix them without anything being late.

Day one overdue. Warm, factual, assumes an administrative slip. Restate the invoice number, the amount and the due date, and re-attach the invoice. No consequence language.

One week overdue. Neutral and procedural. Reference the agreed terms without editorialising, and ask a closed question: has this been scheduled for payment, and on what date?

Two or more weeks overdue. Stop asking for payment and start asking for a date. "Can you confirm the date this will be paid" is answerable; "please pay as soon as possible" is not. Change channel if email has produced nothing — two unanswered emails means email is not working.

Serious escalation. Beyond about sixty days, or on any deliberate non-response, this process is no longer the right tool. Hand off to the non-payment escalation guide, which covers formal demands, work stoppage, small claims and the records that decide those arguments.

Message templates

Copy, cut, keep them short. Every one of these is written to be forwardable to a stranger in an accounts department without needing context, and none of them threatens anything.

Courtesy note, three days before due.

Subject: Invoice [number] — due [date]

Hi [name],

Quick note that invoice [number] for [amount] is due on [date].

If it helps, I can re-send it to your accounts team directly — just let
me know the right address. And if anything is needed from me first (a PO
number, a reference, a signed timesheet), tell me and I'll get it over.

Thanks,
[you]

First overdue reminder, day one.

Subject: Invoice [number] — [amount] now due

Hi [name],

Invoice [number] for [amount] was due on [date], so I'm flagging it in
case it got stuck somewhere. I've attached it again for convenience.

If it's already scheduled, no action needed — just let me know the date
so I can stop watching for it.

Thanks,
[you]

Request for a specific payment date, around two weeks.

Subject: Invoice [number] — confirming a payment date

Hi [name],

Invoice [number] for [amount] is now [n] days past its due date of
[date], and I don't have a payment date for it yet.

Could you confirm the date it will be paid? If there's a problem with
the invoice itself, tell me what it is and I'll deal with that instead.

Thanks,
[you]

Missing purchase order or billing information.

Subject: Invoice [number] — what do you need from me?

Hi [name],

Invoice [number] for [amount] is outstanding, and I want to rule out the
likeliest cause before chasing it further: is there anything your process
needs that I haven't supplied?

Specifically — do you need a PO number on the invoice, a different
billing address, a vendor form completed, or the invoice submitted
through a portal rather than by email?

Happy to re-issue it correctly. Just tell me the format.

Thanks,
[you]

Invoice dispute acknowledgement.

Subject: Invoice [number] — noted, let's sort the detail

Hi [name],

Thanks for telling me. I've paused the payment reminders on invoice
[number] while we work through it.

So I can look at the right thing: which line is in question, and what's
the objection — the scope, the quantity, the rate, or the delivery?

I've got the signed scope and the delivery record to hand, so I'd rather
compare notes than go back and forth. Can we agree a date to close this
out — would [date] work?

Thanks,
[you]

Work-pause notice. Use this rung with real care. It is only available if your agreement provides for it, and sending it when it does not can put you in breach rather than the client. Confirm first that the invoice was received, is not disputed, and is genuinely overdue under the terms you both signed — and take legal advice before pausing anything material.

Subject: Invoice [number] — pausing work from [date]

Hi [name],

Invoice [number] for [amount] has been outstanding since [date], and I
haven't been able to get a payment date.

Under [clause reference] of our agreement, I'll be pausing work on
[project] from [date] until the balance is settled. Everything completed
to date is safe and I'll pick straight back up once payment clears.

I'd much rather not do this — if there's a blocker on your side, tell me
what it is and I'll work with it.

Thanks,
[you]

Two things to keep out of every one of these. Do not state a legal consequence you are not prepared to pursue, and do not imply that a debt has been reported to a credit bureau or referred to collections unless it actually has — in several jurisdictions a false statement of that kind is itself unlawful. Keep copies of everything you send; the record is what makes the later rungs work.

Eight failure modes, and what actually fixes them

• The invoice went to the wrong person. Ask for the accounts-payable address at kickoff, not at day thirty. This is the single most common cause of an invoice that is "ignored".
• A missing PO or unfinished vendor onboarding. Larger clients cannot pay an invoice their system will not accept. Find out the requirement before the first invoice, not after.
• A vague due date. "Net 30" without a date on the document, or "on receipt", produces an invoice nobody can tell is late. Put a calendar date on it.
• No deposit. An unpaid deposit is a cheap signal you get before you have spent the time. An unpaid final invoice is an expensive one you get afterwards.
• Work continued through a material overdue balance. You do not have to stop, but you should have decided consciously rather than by default — and the decision is easier when the contract already covers it. Fixed-price and hourly work fail differently here, because an hourly engagement compounds the exposure every week you keep going.
• Reminders with no next-action date. Four reminders and no promised date is not persistence, it is a loop. Escalate the type of ask, not the volume.
• A disputed invoice treated as ordinary lateness. Different problem, different queue. Reminders into a dispute burn the relationship and move nothing.
• Memory used as a financial record. "I think I chased them a couple of weeks ago" is not a last-contact date, and it is the field that decides what today's message should say.

Metrics worth tracking, and one to be careful with

Six numbers, reviewed monthly rather than weekly. Weekly is for actions; monthly is for whether the process is working.

• Total accounts receivable. Per currency, never summed across them.
• Overdue receivables. The subset past due. The gap between this and the total is your real health signal.
• Percentage of receivables overdue. The one number to trend. A rising share while the total is flat means collection is slipping, not that you are selling more.
• Average days overdue. How late "late" typically is, which tells you whether you have a terms problem or a client problem.
• Collection rate. Collected against invoiced over the same window. Consistently under about 95% is worth investigating.
• Concentration. The share of receivables owed by your largest client. This is a risk measure, not a revenue one, and it is the number most freelancers have never calculated.

A promise-to-pay kept rate — the share of committed dates that were actually met — is worth adding once you have enough promised dates to divide by. Below about ten it tells you nothing but noise.

On DSO. Days Sales Outstanding is the standard corporate receivables metric, and it is usually the wrong tool at freelance volume. It divides receivables by revenue over a period and multiplies by the number of days, which means it moves sharply when one large invoice lands or clears — so at eight open invoices it swings for reasons that have nothing to do with how well you are collecting. "Average days to payment", measured on invoices that were actually paid, answers the question you care about with far less arithmetic and no false precision. If you want the corporate metric, calculate it quarterly and never react to a single month of it. Your effective hourly rate is a more useful monthly number than DSO ever is for a business this size.

Download the weekly worksheet

Weekly receivables worksheet (CSV) — the twelve fields above, as a plain CSV with one worked example row. No email required, no macros, no tracking. Opens in Excel, Numbers, Google Sheets or LibreOffice.

It is an operating aid, not an accounting ledger: it drives your Friday twenty minutes and nothing else. Delete the two seed rows, add one row per issued invoice, and re-sort by days overdue each week.

How Stria fits the process

Every step above works in a spreadsheet, and the honest reason to move it into software is that steps one, two and five are the ones that decay. Reconciliation is manual, the aging list has to be re-derived, and the next-action date lives wherever you last wrote it.

Here is what Stria does with this loop, limited to what it actually does today.

• The receivables ledger is one cross-client list. Every issued invoice with its outstanding amount, days overdue, and payment state — drafts and voids excluded, because a draft was never issued. It also flags invoices that were issued but never actually sent to anybody, which is a different problem from being ignored.
• Aging is grouped for you, per currency. Current, 1–30, 31–60, 61–90 and over 90 days, and money is never summed across currencies. Part payments have their own filter, because a part-paid invoice looks identical to any other outstanding one until you separate it.
• Due dates come from your payment terms. Presets from due-on-receipt through net 45, with a per-invoice override. An invoice with no due date can never become overdue, so nothing will ever chase it — where an invoice gets its due date covers that trap.
• Reminders escalate on a schedule. Up to three per invoice, at least five days apart, and the three are genuinely different messages — friendly, then firm, then a final notice — rather than one body sent three times. They go out under your brand. You can also send one by hand from any row. See chasing what is late.
• Late fees are yours to state and yours to apply. A percentage, a flat amount and a grace period you set. Automatic application is off by default, and where it is switched on a fee is withheld until a final notice has gone out, so it never arrives unannounced. It is charged on what is still outstanding rather than the original total, so a part payment reduces it.
• Payments recorded honestly. Card payments run on your own Stripe account and the paid status is written from Stripe's webhook, not from a browser reaching a success page. Offline payments are recorded by hand as the total received to date, which is what makes part payments come out right.
• Deposits can hold the work. A kickoff deposit can gate file release, so the files stay withheld until it clears — holding files until the deposit clears explains how.
• Uncollectible is a state, not a deletion. Writing off an invoice records a reason, stops the reminders, and is reversible if the client pays two months later.
• The numbers are computed, not assembled. Overdue share, the 60-plus-days share, average days to payment, collection rate, largest-client share and revenue per client. Invoices and line items export as CSV for your bookkeeper.

What it will not do: guarantee that anybody pays, tell you whether a late fee is enforceable where you live, or decide for you that it is time to stop work. Those are your calls, and two of them need a professional who knows your jurisdiction.

If you want the list, the aging and the reminder ladder in one place instead of three, start a 14-day trial — the free tier carries three clients, which is enough for a cross-client receivables list to actually have something in it.

Frequently asked questions

When should a freelancer follow up on an invoice?

Three days before the due date with a short courtesy note, on the first day overdue, again around a week overdue, and at two weeks with a request for a specific payment date rather than another reminder. Following up before the due date is not chasing — it is confirming the invoice reached the person who pays it, which is where most late payment actually starts.

How often should accounts receivable be reviewed?

Once a week, on a fixed day, for about twenty minutes at a modest invoice volume. Weekly beats sporadic because it caps how late anything can get before you look at it, and because a routine removes the decision about whether today is the day to talk about money. Daily is noise at freelance volumes; monthly lets an invoice reach thirty days overdue before it is read.

Should I pause work over an overdue invoice?

Only where your agreement provides for it, and only after you have confirmed the invoice was received and is not disputed. An invoice inside its payment terms is not late and is not a reason to stop. Pausing without a contractual basis can itself be a breach, so check the agreement and take advice on anything material before you send that notice.

Can I charge a late fee on an unpaid invoice?

It depends entirely on your jurisdiction and your contract. In the UK, statutory interest for business-to-business debt is 8% above the Bank of England base rate, but you cannot claim it if your contract sets a different rate. Elsewhere, enforceability turns on local interest and consumer-protection rules. State the fee in the agreement and on the invoice, and take local advice before relying on it.

What if the client disputes the invoice?

Stop the reminder sequence and change the question. A dispute is a factual disagreement about scope, amount or delivery, and sending a fourth overdue reminder into one damages the relationship without moving the money. Acknowledge it in writing the same day, ask for the specific line and the specific objection, and agree a date to resolve it.

Is an unpaid invoice the same as a bad debt?

No. An unpaid invoice is a receivable you still expect to collect; a bad debt is one you have concluded is worthless. The tax treatment differs by jurisdiction and accounting method — the IRS says a cash-method taxpayer generally cannot deduct unpaid fees as a bad debt, because that amount was never included in income. Ask your accountant before writing anything off.

Not advice

This article is educational. It is not legal, tax or accounting advice, and nothing in it is specific to your situation. Late-fee enforceability, interest rates, collections conduct, credit reporting and the right to withhold work or files all vary by jurisdiction and by contract, and accounting and tax treatment of receivables varies by jurisdiction and by accounting method. Take advice from a qualified professional in your own jurisdiction before acting on anything here that has money or a contract attached to it.

Related reading

• Client won't pay? Freelance escalation
• How much deposit should freelancers require?
• Effective hourly rate for freelancers
• Fixed price vs hourly for freelancers

Start your 14-day trial · Try a free scope check · All articles