# The Freelancer's Guide to Getting Paid on Time

Airtym · March 12, 2026 · Updated August 24, 2026

> Late payment is a property of a client, not an event on an invoice. The pattern only shows up if payment history sits next to the work history.

## How do freelancers actually get paid on time? {#how-do-freelancers-actually-get-paid-on-time}

**Most advice targets the invoice: clearer terms, deposits upfront, automated reminders. Those work, and they work once per invoice. What decides whether it keeps happening is which clients pay late, and that is a property of the client rather than of any single invoice. The pattern only becomes visible when payment history sits beside the work history.**

The problem is close to universal. Remote's Contractor Management Report 2025 found that 85% of freelancers have their invoices paid late at least some of the time, and just over 21% are paid late or not at all more than half the time ([Remote](https://remote.com/blog/contractor-management/reversing-late-payment-culture)). Remote sells contractor payment services, which is worth knowing when reading their number, though the direction is consistent with anything else published on this.

The second figure is the interesting one. Occasional lateness is noise. Being paid late over half the time describes a relationship, not an accident.

**[Definition]** One late invoice is an event. The same client paying late five times is a fact about that client, and it is the only version worth acting on.

## Why does invoice-level advice stop working? {#why-does-invoice-level-advice-stop-working}

Because it treats every invoice as the first one. Tighter payment terms, a deposit, a reminder schedule: each is a good idea and each resets to zero with the next engagement.

The question that actually changes your income is different. It is whether to keep taking work from a particular client, price it differently, or ask for more up front, and answering it requires knowing how that client has behaved across every invoice you have sent them.

That is a question about history, and history is exactly what a per-invoice workflow does not accumulate.

## Does your payment tool not already track this? {#does-your-payment-tool-not-already-track-this}

Partly. Stripe groups payments under a customer, so you can see what somebody has paid and when. The gap sits between systems.

Stripe knows the money and knows nothing about the work. It has no record of the eight sessions you ran, what was agreed in them, or how much of your year that client represents. Your notes know the work and nothing about the money. Answering "is this relationship worth the payment friction" means holding both at once, and nothing does.

The cost of collection is at least visible: Stripe takes 2.9% plus $0.30 per card transaction ([Stripe pricing](https://stripe.com/pricing)). The cost of a client who reliably pays at day 55 is not on any statement.

## What changed legally, and why does it matter? {#what-changed-legally-and-why-does-it-matter}

Payment timing became enforceable in two large markets. On 28 August 2024 New York's Freelance Isn't Free Act added Article 44-A to the General Business Law, introducing contractual requirements for freelance work and a formal enforcement process ([New York State Department of Labor](https://dol.ny.gov/freelance-isnt-free-act)).

California followed. SB 988, the Freelance Worker Protection Act, applies to contracts entered into or renewed on or after 1 January 2025, covers professional services worth $250 or more, requires a written contract stating scope, rate and method of payment, and requires payment by the date in the contract or within 30 days of completion where no date is given. Enforcement sits with the freelance worker, the Labor Commissioner, or a public prosecutor ([California SB 988](https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240SB988)).

This turns a vague grievance into a measurable one. There is now a defined date, which means the useful thing to record is not that a client was slow but how many days past terms they were, every time.

**[Key takeaways]** With statutory deadlines in place, "days past terms" is a number you can hold per client. Without a record that keeps it, it stays a feeling about who is annoying to invoice.

[See how a per-client record works →](/signup)

## Why does this land on repeat clients? {#why-does-this-land-on-repeat-clients}

Because that is where most of the money is. David A. Fields puts healthy repeat business at 40 to 80 percent of a consulting firm's revenue, treating anything below 40 percent as a problem ([David A. Fields Consulting Group](https://davidafields.com/whats-the-right-amount-of-repeat-consulting-business/)).

So the clients most likely to develop a payment pattern are also the ones you are least willing to lose, which is precisely why the decision needs evidence rather than irritation. A client who pays at day 45 on a 30-day term but represents a fifth of your year is a pricing conversation. The same behaviour from a one-off is a different decision entirely.

Without a per-client record you cannot tell those two apart at the moment you need to.

## What to record, starting now {#what-to-record-starting-now}

Four fields, kept against the client rather than the invoice:

- Agreed terms, in writing, per the statute that now applies to you.
- Days past terms on every payment, rather than a paid or unpaid flag.
- Whether chasing was required, and how many times.
- Share of your annual revenue, so lateness can be weighed against value.

None of this requires new software if you keep it by hand. It does require the record to be organised around the person, because that is the unit the decision is about.

**[Key takeaway]** Boundary condition: with three or four clients you already hold this in your head and a spreadsheet adds nothing. The pattern becomes invisible somewhere past a dozen active relationships, or once enough time passes that memory stops being reliable.

## Frequently Asked Questions {#frequently-asked-questions}

### How common is late payment for freelancers? {#how-common-is-late-payment-for-freelancers}

Remote's Contractor Management Report 2025 found 85% of freelancers have invoices paid late at least sometimes, and just over 21% are paid late or not at all more than half the time ([Remote](https://remote.com/blog/contractor-management/reversing-late-payment-culture)). Remote sells contractor payment services, so read the figure with that in mind; the second number matters more than the first, because chronic lateness describes a relationship rather than an accident.

### Do freelancers now have a legal right to be paid on time? {#do-freelancers-now-have-a-legal-right-to-be-paid-on-time}

In some jurisdictions. New York's Freelance Isn't Free Act took effect on 28 August 2024 with contractual requirements and a formal enforcement process ([NY Department of Labor](https://dol.ny.gov/freelance-isnt-free-act)). California's SB 988 applies to contracts from 1 January 2025 for work worth $250 or more, requiring payment by the contracted date or within 30 days of completion ([California SB 988](https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=202320240SB988)). Check what applies where you and your client are located.

### Does Stripe show which clients pay late? {#does-stripe-show-which-clients-pay-late}

It shows what a customer has paid and when, so the raw material is there. What it cannot show is that history alongside the work: how many sessions you have run, what was agreed, and what share of your revenue the client represents. That combination is what the keep-or-reprice decision actually needs.

### Should I ask for a deposit instead? {#should-i-ask-for-a-deposit-instead}

Deposits are effective and they solve a different problem. They reduce exposure on any single engagement without telling you anything about which relationships are costing you time to collect. Both are worth doing; only one of them compounds into a decision.

[Airtym](/) keeps booking, the video room, payment and the session summary on one running record per client, so the next conversation opens with the last one already in front of you.

## Related Articles {#related-articles}

- [The Client You Lose Isn't the One Who No-Shows](/blog/client-you-lose-isnt-the-one-who-no-shows) — why the repeat client who stops booking costs more than the one who misses a session, and produces no signal at all.
- [Meeting Notes Apps for Client Calls: Two Questions Before You Pick One](/blog/meeting-notes-app-for-client-calls) — per-client grouping exists in every major notetaker; what decides it is who does the filing, and what none of them hold.
- [Transparent Pricing Built for Real Consultation Work](/blog/transparent-pricing-built-for-real-consultation-work) — per-seat, per-transaction and per-client pricing each tax a different thing.