Design clients paying late invoices: causes and fixes for Mac designers in 2026

Late payment is a cash problem before it is anything else. You finish a logo system or a website redesign, send the invoice, and then wait. Rent, software and tax keep their own schedule. Many freelancers cover that gap from savings or a credit card. A few late invoices can stall a whole month.

What late payment costs a design freelancer

The cost shows up in four places. It is cash you cannot spend yet. It is hours spent chasing. It is work you never get paid for. It is clients you stop taking on. Each one is easy to dismiss alone. Together they change how you price and how you plan your year.

Read these numbers with their sources in mind. Bonsai analysed three years of invoices from more than 100,000 freelancers. It found 29% of invoices were paid at least a day late. In that data, designers were paid late 28% of the time. Software developers were late 29% of the time, so designers are not an outlier.

The UK figures cover more freelancers. IPSE reports that 54% of freelancers have had a client delay a payment during their self-employed career. It also reports that 31% have completed work and never been paid for it. Freelancers who had been paid late were owed an average of £5,230.

How much time chasing invoices takes

The UK Small Business Commissioner found that businesses affected by late payment spend an average of 86 hours a year chasing it. That figure covers all businesses, not designers alone. For a studio of one, those hours are unbilled. They come out of design time and marketing time.

The same research says 15% of surveyed businesses have avoided doing business with specific customers because of their payment behaviour. That is the cost most designers feel last, and it lasts longest. A client who pays slowly today may not come back with a second project.

Why design clients pay late

Clients rarely decide to skip a designer. IPSE lists four common causes. The first is cash flow. The client delays spending because their own customers have not paid them. The other three are unclear terms, internal bureaucracy and simple forgetfulness.

• Cash flow: the client holds money until their own customers pay.
• Unclear terms: nobody agreed when payment is due, so nobody feels late.
• Internal bureaucracy: the invoice sits in a shared inbox or never reaches finance.
• Forgetfulness: the approver meant to forward it and did not.

Deliberate refusal is described as the least common cause. That changes how you respond. A lost invoice needs a clean resend, not a sharp email. A cash-flow delay needs a clear date you can both agree to. Refusal needs a paper trail and a formal notice.

Bonsai's data points to two patterns worth watching. Invoices over $20,000 were about three times as likely to be paid late as invoices under $100. Crypto payments were late almost three times as often as ACH or bank transfers. These are correlations in one dataset, not proof of cause. They still tell you where to tighten terms first.

Fix one: write payment terms nobody can misread

Put the payment terms in the proposal and again on the invoice. Say when payment is due in plain words. The date printed on the invoice works. So does a set number of days from the invoice date, written out in full. Avoid vague triggers such as 'on completion' unless you define completion.

If you share proposals as a Figma file or a Canva doc, put the same line on the first page. Finance teams often see only the first page. Put the payment line there, not buried on page six.

A common mistake is putting terms only in an email reply. That reply gets buried in a long thread. Put the terms in the signed contract, then repeat them in the invoice footer. Two places beat one.

Fix two: define when the work counts as done

IPSE recommends that you define when work counts as complete. Pick one trigger: submission, acknowledgement or acceptance. Many design jobs stall because nobody agreed what finished means. The client asks for one more round, then another, and the invoice waits with them.

Make the trigger concrete. For a Figma deliverable, the invoice goes out when you share the final file link. Acceptance can be a written approval in a comment, or a Slack message from the named contact. Save that message in the project. A phone call leaves no record.

Fix three: send the invoice to the person who pays

Slow approval is one of the most common causes. The invoice goes to a design lead who has no access to payments, and it sits there. Ask at kickoff who approves invoices and who processes payment. Then send the invoice to both, with the approver named in the first line.

• Ask for the accounts payable address, if the client has one.
• Ask whether they need a purchase order number, and add it to the invoice.
• Ask how often finance runs payments, so you can time the invoice.
• Keep the approver copied on every chaser.

Fix four: a chase schedule you follow every time

IPSE suggests a three-step process. Send a gentle reminder first. After a week, send a formal notice that refers to the invoice and the contract terms. After two weeks, send a final demand. Use the same steps for every client, so the process reads as routine, not personal.

Send each chaser from the same email thread. The history stays in one place, and finance can see the earlier messages. Keep each message short. A chaser should read like a receipt, not a complaint. Attach the invoice every time.

Set up automatic reminders in your invoicing tool

Automatic reminders take the awkwardness out of chasing. They fix forgetfulness, which IPSE lists as a common cause. Most invoicing tools have them. Each one has its own rules, so check the settings before you trust them.

• QuickBooks Online: Settings > Account and settings > Sales > Reminders > Edit. You can schedule reminders up to 90 days before or after the due date.
• QuickBooks Desktop: Edit > Preferences > Payments > Company Preferences for the switch, then Customers > Payment Reminders > Schedule Payment Reminders.
• Stripe: automatic invoice advancement is on by default for invoices created in the Dashboard. Turn it off for one invoice from its overflow menu.
• FreshBooks: an Invoice is Overdue notification tells you when a client is late and prompts you to enable late reminders.
• Xero: check Xero's help centre for its reminder settings and limits before you rely on them.

No study checked here shows that automatic reminders cut late payment for designers specifically. Use them as a backstop. Your own schedule, with the same steps every time, still does most of the work.

Statutory interest for UK business invoices

If your clients are UK businesses, the law gives you more than a polite reminder. The Late Payment of Commercial Debts (Interest) Act 1998 already allows statutory interest of 8% above Bank of England base rate on late business invoices. Adfin's worked example, with base rate at 3.75%, comes to 11.75% a year.

The clock does not always start on the invoice date. Section 4 of the Act defines the relevant 60-day period. It starts on the later of two days: the day you performed your obligation, and the day the client had notice of the debt. Check that wording before you quote a date.

Adfin also lists fixed compensation of £40, £70 or £100 per invoice. That detail comes from a secondary source, so check the Act before you quote it. Keep any figure to a formal notice, not a casual email.

Reform is still moving. Adfin says the proposed Commercial Payments Bill would cap payment terms at 60 days for large businesses paying smaller suppliers. It would also make statutory interest compulsory. As of Adfin's 22 October 2026 note, none of that is law.

Worked example: one invoice, three messages

Say you delivered a brand identity to a client whose finance team processes payments. The invoice went out on delivery, with the due date printed on it. On the day after the due date, you send a gentle reminder in the original thread. Nothing comes back.

A week later, you send the formal notice. It names the invoice, quotes the payment clause from the contract, and asks for a payment date. If that date passes, you send the final demand two weeks after the due date. It states the amount, the next step and the day you will take it.

Keep the promise you make in the final demand. If you said you would pause work, pause it, and tell the client the day you did. Lazur can help draft these three messages in plain language. You still read them, change them and send them yourself.

Mistakes that make late payment worse

• Chasing only in chat. A Slack message gets lost. Send chasers by email with the invoice attached.
• Apologising for asking. Say 'I am following up on invoice' and stop there.
• Starting the next phase before the last invoice is paid. Pause new work, or ask for a deposit.
• Waiting months before the first reminder. Send the reminder the day after the due date.
• Discounting to get paid. A discount teaches the client that late is fine.
• Leaving out the invoice number. Without it, finance cannot match the payment.

Edge cases: regulated clients and confidential work

Most design clients are businesses with no special data rules. Some are not. A healthcare provider, a law firm or a bank may restrict what you share with outside tools. Follow their rules on client and patient data before you paste a file, a screenshot or a case detail into any app. That includes AI assistants.

Confidentiality clauses matter too. An NDA can cover briefs, mockups and invoice details. Read the contract before you ask an AI tool to rewrite a chaser that names the project. If your client or employer has a data policy, their policy wins. Ask them what is allowed.

Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac. Hold ⌥⌘ to ask about anything on screen, and Lazur answers out loud. Ask where a control is, and Lazur draws a circle and label around it. Ask how to do something, and Lazur guides you one click at a time, waiting for each click.

For late payments, that means three real uses. Ask Lazur to walk you through the reminder settings in your invoicing tool. Ask it to draft a chaser, then read the draft aloud. Hold fn to dictate the final text at the cursor in Mail or any other app.

Lazur does not click buttons, send email or log into your invoicing tool for you. It does not operate other apps. The sending, the approval and the choice to chase stay with you. That keeps every message and every decision in your hands.

A chase routine that fits your Mac

A routine works best where you already work. Put each due date in Apple Reminders or Calendar. Set the chase dates on the same day you send the invoice. Send chasers from Mail, so the thread stays in one place. Store the invoice PDF in the same folder as the project files.

Dictation helps when you are tired of writing the same message. Hold fn to dictate clean, formatted text at the cursor in any app. Dictation is unlimited on both Lazur plans, so you can use it for every chaser you send.

What to do next

Start with the client who owes you money now. If the due date has passed, send the gentle reminder today. Then write payment terms into your next proposal and set the chase dates before you start the work. Check your invoicing tool's reminder settings once, and keep them on.

If you want help with the wording and the settings, see Lazur pricing for current plans. You can also read how designers use Lazur in Figma to see where a voice assistant fits in the rest of your day.