The freelancer's guide to getting paid on time

Late payment is rarely one delay. It is six, stacked end to end, and only the last one is the client deciding when to release money. The other five sit inside your own process, and each adds days you can count.

The number worth managing is time-to-cash: the days between the work being done and the money being available to spend. Payment terms are one input to that number. They are not the number, and a freelancer on Net 14 with a slow internal process routinely gets paid later than one on Net 30 who has the chain tight.

Time-to-cash is six links, and you control five of them

Here is the arithmetic on an illustrative project, not on observed data. A €9,000 build is delivered on 3 September. You batch the invoice to 30 September. The project contact forwards it internally on 6 October, accounts payable approves it on 14 October, it goes into the 31 October run, and it clears on 3 November. Terms were Net 30 and the client never broke them. Time-to-cash was 61 days, and 27 of those days elapsed before the client's clock even started.

That is the shape of most late-payment complaints. The client is slow, but you funded the slowness.

The clock starts when the invoice arrives, not when the work does

This is jurisdictional, so know which rule you are under.

In the EU, where nothing else is agreed, the default B2B payment period is 30 calendar days running from the debtor's receipt of the invoice — or from receipt of the goods or services where the date of the invoice is uncertain (Directive 2011/7/EU, Article 3(3)(b)). If the contract provides for an acceptance or verification procedure, that procedure cannot exceed 30 calendar days from receipt of the goods or services unless expressly agreed otherwise and not grossly unfair to you (Article 3(4)). Payment periods themselves are capped at 60 calendar days on the same "expressly agreed and not grossly unfair" test (Article 3(5)).

In the UK, where no terms are agreed, payment is late 30 days after the customer receives the invoice or receives the goods and services, whichever is later, and a period longer than 60 days has to be fair to both businesses.

In the US there is no general federal default for private B2B contracts. The Prompt Payment Act binds federal agencies only, and its rules are a useful model precisely because they are written down: payment is due 30 days after the start of the payment period where the contract says nothing else, and acceptance of delivered work is deemed to occur on the seventh day after actual delivery unless the agency accepts sooner (5 CFR 1315.4). Private clients rarely publish their equivalent. They still have one.

Three lines in the contract close most of the ambiguity:

Payment. Invoices are payable 14 days from the date of issue.
Invoices are issued by email to the address the Client nominates
for accounts payable and are deemed received on the day of
transmission.
Where the Client operates an invoice approval or verification
procedure, that procedure shall not extend the payment period.

The first line sets the period. The second removes the argument about when receipt happened, which is the argument that costs you a week. The third stops an internal approval queue being treated as a suspension of your terms, which is the most common way a Net 14 becomes a Net 45 without anyone announcing it.

A deposit is a funding decision, not a trust test

People frame the deposit as a signal about whether the client is serious. That framing is why deposits get dropped for clients who seem respectable. Treat it as a funding question instead: whose working capital pays for the first phase of this project?

If you take nothing up front on a two-month engagement, you are lending the client the cost of two months of your time, unsecured, at zero interest, with no facility agreement. Take a deposit on every engagement above a threshold you set once and do not renegotiate per client. Invoice it the same day the contract is signed, with the payment link on it, and do not schedule a start date until it clears — not until it is "approved," until it clears.

For longer work, a deposit plus milestone billing keeps the exposure roughly flat instead of letting it grow all the way to delivery. The exposure you care about is not the contract value. It is the largest amount you will ever have delivered and not been paid for, which is one of the operational defects worth measuring once a year.

Milestones must fire on events, not on dates

A milestone billed "end of month two" invites a conversation about whether month two really ended. A milestone billed on an event does not: the event either happened or it did not.

Good triggers are things with a timestamp attached — designs delivered to the shared folder, staging environment handed over, the client's written approval of phase one. Bad triggers are things like "on completion of the design phase," where completion is a judgment call the client makes and you invoice after.

Where a trigger depends on the client acting, put a fallback in the contract. Approval not given within five working days of delivery counts as given for billing purposes. Without that fallback, an unresponsive client can hold your billing indefinitely while remaining fully within the terms.

The invoice goes out the day the trigger fires

Batching invoices to month end is the single most expensive habit in this list, and it is invisible because it feels organized. Work finished on the 2nd waits 28 days for the invoice run, then starts its Net 30. You have converted a 30-day term into a 58-day one and the client did nothing wrong.

Pick a standing invoice day if you cannot face invoicing continuously, but make it weekly. The gap between "work done" and "invoice sent" is the only part of the chain where you get the days back for free — no negotiation, no relationship risk, no clause to add.

The mechanical failure underneath this is usually data entry. If the timer lives in one app and the invoice in another, someone has to move hours across, and that someone is you on a Friday when you are tired. That is the comparison the Toggl alternative page draws out: tracked hours only shorten time-to-cash if they land on an invoice without a re-entry step, and a time tracker that stops at the timer leaves the expensive half of the job undone. The same logic runs through time-to-cash: where freelancers actually lose money.

An unpayable invoice is not late, it has been rejected

Accounts payable departments do not usually refuse to pay. They fail to match. An invoice that cannot be matched to a purchase order, a legal entity or a bank account goes into an exceptions queue, and in many organizations nobody tells the vendor.

Federal agencies publish exactly what they need before the clock starts, which makes their list the best free specification available. A proper invoice under 5 CFR 1315.9(b) has to carry the vendor's name, the invoice date, the contract or other authorization for delivery, the invoice number and any account number agreed in the contract, the description, price and quantity of what was supplied, shipping and payment terms, the taxpayer identifying number, banking information, and a contact name and telephone number. Miss any of it and the invoice is improper — the agency returns it, and the payment clock restarts on the corrected version.

If you are VAT-registered in the UK, VAT Notice 700, section 16.3 sets the separate legal minimum: your name, address and VAT registration number, an invoice number and date, the customer's name and address, a description of what was supplied, the quantity or rate, the unit price and total excluding VAT, the VAT rate, the VAT amount, and the tax point. The same guidance requires the invoice to be issued within 30 days of the basic tax point, which is a deadline most freelancers have never checked themselves against.

Build the header block once and stop re-deciding it:

Your legal name and trading name, address, tax/VAT number
Client's registered legal entity and billing address <- not the brand name
Invoice number (sequential, no gaps)
Invoice date, and the payment due date written as a date, not "Net 14"
Their PO / project / cost centre reference <- ask for this at kickoff
Line items: description, quantity, unit price, total
Tax rate and tax amount shown separately
Total due, in the currency of the contract
Bank details, or a payment link that works on a phone

Two lines there earn their keep more than the rest. Writing the due date as an actual date removes the "we thought Net 14 ran from month end" conversation entirely. Getting the client's purchase order or cost centre reference at kickoff, rather than at invoicing, means you are never waiting on a reply from someone on holiday to send a document you have already earned.

You can produce a compliant itemized invoice PDF in the browser with the free invoice generator if you want a reference layout; it runs locally, with no signup and no watermark. Or run the whole cycle inside Worklyn's invoicing, where an invoice inherits its numbering, entity details and payment options from the proposal it came from.

Send it to accounts payable, and to a named person

The project contact briefed you, approves your work and has no ability to pay you. Sending them the invoice adds an internal forwarding step of unpredictable length, and if they are away it adds a week.

Ask two questions at kickoff and write the answers in the project file: which email address should invoices go to, and is there a purchase order or reference number that has to appear on them. Then send to accounts payable and copy the project contact, so the person who can pay has the document and the person who wants the work continued knows it is outstanding. The other six defects that produce the same result are laid out in seven reasons clients pay late.

Reminders belong on a schedule, decided in advance

The last link in the chain is the one you cannot control, so control your response to it instead. Decide the cadence once, before anything is overdue, and let it run: a note before the due date, one on it, then fixed steps after. Deciding each chase individually is what makes chasing feel like confrontation, because you are re-litigating the decision every time.

The full cadence, with what changes at each step and two templates, is in a reminder schedule that works without souring the relationship. Once a chase stops working, the next instrument is a formal written notice stating your statutory entitlements, covered in how to write an overdue payment letter that gets paid, and after that the escalation options by jurisdiction are in the escalation ladder when a client stops paying.

Three changes worth making this week

Move invoicing off month end and onto the day the trigger fires, or at worst onto a weekly slot. That is the largest single reduction in time-to-cash available to most freelancers and it costs nothing.

Add the accounts payable address and the purchase order reference to your kickoff checklist, so both are captured before there is anything to invoice.

Rewrite your payment clause to fix the point of receipt and to stop an internal approval process extending the period. If you work with EU clients, check it against the 60-day ceiling in Article 3(5) before you sign anything longer.

Measure the result the same way each time: date the work was delivered, date the invoice went out, date the money cleared. Three dates per project, and the middle one is yours.

Worklyn's CFO Mode tracks that gap across every open project, so the days between work done and cash landed stop being something you reconstruct after the fact.