Most freelance advice treats invoicing as paperwork — a chore at the end of the project that gets done when you have a spare hour on a Wednesday afternoon. That framing is what produces freelance practices where the work is finished but the bank account is empty. Invoicing is not paperwork; it is the operational stage where revenue becomes cash, and the difference between the two is often six weeks of life. This guide is the mechanical playbook for the payment half of the freelance lifecycle: invoice anatomy, deposit and milestone structures, payment terms that actually work, automated dunning, multi-currency billing and the international tax considerations that catch out cross-border freelancers in the first year.
TL;DR
- Invoice same day as delivery — every day you wait adds a day to your days-sales-outstanding.
- Net 7 or Net 14, deposit on signature, automated reminders on day 7/14/30. Manual chasing feels awkward and gets skipped; automated chasing feels professional and gets paid.
- Stripe is the default payment processor for cards and ACH/SEPA. Multi-currency billing requires a multi-currency processor — retail bank FX costs you 2 to 4 percent per invoice, often more than the processor fee itself.
The anatomy of a freelance invoice — what every line does
An invoice is a legal instrument, not a memo. Every field on it carries weight: it is the document a client uses to authorise payment, the record your accountant uses for the tax return, and the evidence a small-claims court uses if it ever comes to that. The structural shape is the same in every jurisdiction the freelancer is likely to operate in. The twelve fields below are the non-negotiable backbone.
Your legal trading name and address (sole-trader name or company name — match what is on your tax registration). The client's legal name and billing address (match what is on the contract). A unique sequential invoice number (never reset the counter, never reuse a number — most jurisdictions require sequence integrity). The issue date and the due date (not "Net 30" — an actual date the client can read). An itemised line for each deliverable or milestone (one line, one fee, one short description — no "consulting services" lump sums). The subtotal, the tax line if applicable (VAT, GST, sales tax with the rate and the registration number), and the total amount due. Your payment details (bank account or processor link). The late-payment terms (the interest rate and any fixed fee, quoted from the contract). A note line for anything project-specific.
The invoicing and payments module in COLO generates this anatomy automatically — branded with your logo, sequential numbering enforced, tax line surfaced based on the client's billing country, payment link embedded — so you never have to remember the structure on a tired Friday afternoon. For freelancers starting from a blank template, the free freelance invoice template carries the twelve fields with a jurisdiction-neutral late-payment clause at the bottom — a bracketed monthly interest placeholder you set yourself; fill it in for your jurisdiction once and reuse it from then on.
The single most expensive line freelancers leave off invoices is the late-payment clause. "Payment due upon receipt" states no date, so there is nothing for a court to measure lateness against; "Net 14 from invoice date, with statutory interest and debt-recovery costs on overdue balances" is enforceable. In the UK the Late Payment of Commercial Debts (Interest) Act 1998 sets statutory interest at 8% above the Bank of England base rate, plus a fixed sum that rises with the debt — £40 under £1,000, £70 from £1,000 to £9,999.99, and £100 at £10,000 or more (GOV.UK, checked August 2026). Outside the UK the mechanism differs, so state your own jurisdiction's rule rather than copying this one. Most clients pay on time, but the late-payment line is what turns a Wednesday-afternoon chasing call into a Monday-morning bank transfer.
Deposit and milestone structures — where the money actually moves
The shape of when the money moves matters more than the headline fee. A £12,000 project paid 100 percent in arrears Net 30 is a worse business arrangement than the same £12,000 paid 40 percent on signature, 30 percent at midpoint, 30 percent on delivery. Same gross revenue, completely different cash-flow risk and operational sanity.
The 2026 norm for freelance service work is 30 to 50 percent deposit on signature, with the remainder split across one to three milestones or paid at delivery. For projects under four weeks, a clean 50/50 (deposit and delivery) is fast and standard. For longer engagements, milestone billing keeps the cash flowing and prevents you from carrying the project on your own balance sheet for two months. The structural principle: you should always be carrying less unbilled work than the client has paid for. The moment that ratio inverts, you are extending unsecured credit.
The deposit must be collected at the same moment the contract is signed — not invoiced afterwards. The proposals and contracts workflows are designed for this: client accepts the proposal, signs the contract, deposit invoice generates and is paid in the same session. Split the events into "sign now, invoice tomorrow" and roughly half of deposits fall through to second thoughts and Monday-morning cold feet. The fix is operational, not legal.
For retainer engagements, billing happens in advance of the period, not in arrears. A monthly retainer invoiced on the first of the month, Net 7 due, with auto-renew and a card or ACH on file, runs itself for the life of the engagement. The client never has to remember to pay; you never have to remember to invoice. The invoicing and payments module handles the recurring schedule, the automatic delivery, and the receipt — set it up once and walk away. For freelancers currently running retainers manually through FreshBooks or QuickBooks, consolidating onto a workspace with the contract, the portal and the recurring invoice in one place removes most of the monthly admin overhead.
What do Net 7, Net 14 and Net 30 payment terms mean?
Net 7, Net 14 and Net 30 state how many days after the invoice date payment is due. Net 7 suits established retainer billing, Net 14 is the sensible default for project work, and Net 30 is an enterprise legacy term worth pricing into the fee.
Most clients pay roughly on the term you set, which means the term you set is the single biggest lever on when the cash arrives. Net 30 is a legacy enterprise default — it made sense when invoices were posted, processed by AP teams and paid by cheque. For modern freelance work paid digitally, Net 7 or Net 14 is the right default. You are not a bank; you are not extending 30 days of unsecured credit to a client whose balance sheet you have not seen.
Net 7 is the right tool for retainer invoicing where the relationship is established and the client expects the cadence. The invoice arrives on the first, payment is due by the eighth, and the client's AP cycle is built around it. Net 14 is the right tool for project work — long enough to give a normal AP cycle time to clear, short enough to keep your DSO under twenty days. Net 30 is what you reluctantly agree to for enterprise clients who insist on it as policy, and only after you have priced the 30 days of credit into the fee.
There is a structural asymmetry most freelancers do not notice. If the client pays Net 30 and you invoice on the 5th, the cash arrives around the 5th of the following month — about 30 days. If the client pays Net 30 and you invoice on the 28th, the cash arrives around the 28th of the following month — about 30 days. But if the client runs a calendar-month AP cycle (pays everything received that month at the end of the month), the difference is closer to 5 versus 35 days. Always invoice in the first week of the month for the cleanest cash flow.
The other piece of payment-terms hygiene is the due-date line on the invoice itself. "Net 14" is a developer's note; "Due 14 March 2026" is a client instruction. Always show the actual due date on the face of the invoice. The freelance invoice template does this automatically; the invoicing and payments module calculates it from the contract terms so you never have to do the arithmetic in your head.
Automated dunning — chasing without burning the relationship
The freelancer who manually chases invoices ends up sending the second reminder, hesitating on the third, and never sending the fourth. The freelancer with automated dunning sends a polite reminder on day 7 past due, a firmer one on day 14, a formal late-payment notice on day 30, and a demand letter on day 45 — without ever having to compose any of them. The difference between the two is six weeks of avoided cash-flow stress per slow-paying client.
A clean dunning cadence has three properties. It is automatic — you set it up once, it runs forever, you never have to remember. It is escalating — the day-7 email is polite, the day-14 email is firmer, the day-30 notice cites the late-payment clause. And it is documented — every email is logged, with timestamps, against the invoice record, so if the situation escalates to small-claims you have a complete audit trail.
The invoicing and payments module ships with this cadence built in: send-on-overdue reminders at configurable intervals, escalating language for each step, and an automatic switch from "reminder" to "formal notice" at the day-30 mark. The structural value is that you stop being the person nagging the client about money — the system is, on a schedule the client expects. The relationship survives; the cash arrives.
For the persistent non-payer who is sixty-plus days past due, the dunning workflow has done its job and the situation escalates to formal recovery. A formal demand letter (templates available from your jurisdiction's small-business advisory body), followed by small-claims filing if the amount is below the small-claims threshold (£10,000 in England and Wales, varies by US state, similar bands elsewhere). The IP-transfer-on-final-payment clause from your contract is the other lever — withholding finished work until payment lands is uncomfortable but is the leverage the contract gave you. For practices that work primarily with freelancers and small-business clients, knowing where the leverage actually is — and where the legal escalation path runs — is what keeps small unpaid invoices from becoming permanent write-offs.
Multi-currency billing and the FX trap
Cross-border freelance work is one of the most under-priced sources of margin loss in the industry. A freelancer based in the eurozone billing a US client in dollars loses 1 to 3 percent on the FX spread alone, plus 1 to 3 percent on the bank receiving fee, plus the processor fee, plus the FX timing risk if the dollar moves between invoice and payment. Roll those up and a freelancer who has not built FX into the rate is taking a 5 to 7 percent margin hit on every international invoice — often more than their entire monthly software cost.
The structural fix has three parts. First, quote in your home currency or in USD as a neutral, never in the client's local currency unless you have explicitly accepted the FX risk. Second, use a multi-currency payment processor — Stripe supports multi-currency natively, with settlement happening at near-interbank rates rather than retail bank rates. Wise is the other strong default for receiving in multiple currencies. Third, build a 3 to 5 percent buffer into the rate to cover the residual processor and bank fees. None of these are negotiation levers — they are structural protections that keep the headline rate intact when the cash actually lands.
The other piece of multi-currency hygiene is invoice tax handling. For cross-border B2B service invoices within the EU, the reverse-charge mechanism applies — you do not charge VAT, but you must state the client's VAT number and "VAT reverse-charged per EU Directive 2006/112/EC Article 196" on the invoice. For UK-EU cross-border, similar rules apply post-Brexit. For US-EU, US-UK and other cross-border invoices, sales tax / VAT treatment depends on the client's registration and the freelancer's place of supply rules. The invoicing and payments module handles the tax-line generation for common jurisdictions; for unusual cases, verify with a local accountant. Tax mistakes on the invoice are recoverable; not making them in the first place is faster.
For freelancers who currently run invoicing through FreshBooks and accounting through QuickBooks, the integration into a single workspace is what makes multi-currency tractable — the invoice carries the right currency, the payment lands in the right account, and the accounting sync happens automatically through the QuickBooks integration. Without the integration, the freelancer reconciles two systems every month, which is where the FX hidden costs accumulate.
Recurring and retainer invoicing — set it up once, run it forever
Retainer invoicing is the structural form of revenue that turns a freelance practice from project-by-project to predictable monthly cash. Done well, it runs itself: the invoice generates on the first of the month, the card on file is charged Net 7, the receipt arrives in the client's inbox, the freelancer's bank account reflects the deposit by the 8th. Done badly, it is a monthly admin chore that quietly drops every third month and a renewal conversation every quarter.
Set up the recurring invoice once: the invoicing and payments module handles the schedule, the contracts module carries the underlying retainer agreement, the Stripe integration carries the card or ACH on file. The structural rule: the client should be paying without ever clicking anything after the initial setup. Every monthly manual step is a step that will eventually be missed.
The two retainer failure modes both have operational fixes. Dormant retainers (the client pays but does not use the time, then quietly cancels) are fixed by a quarterly usage summary surfaced from the reports module — sent proactively, even when the client has not asked, with a short "here is what we did this quarter" note. The client who sees value continues; the client who does not gets the opportunity to cancel before they resent the cost. Unbounded retainers (the client treats the retainer like an all-you-can-eat) are fixed by a clear monthly hour cap and an overage rate, both written into the original contract.
For freelance practices building toward predictable monthly revenue — virtual assistants, fractional consultants, ongoing maintenance work — retainer billing is the structural change that smooths cash flow and lowers the new-business overhead. Two or three solid retainers at the base of a freelance practice is the difference between starting January at zero and starting January at break-even.
How COLO helps with this
Getting paid is not one workflow; it is six connected workflows — invoice generation, payment collection, recurring billing, dunning, multi-currency handling, accounting sync — that have to be one motion. COLO is built so the lifecycle from "work delivered" to "cash in account" is a single continuous workflow rather than five tools held together with copy-paste.
The invoicing and payments module handles invoice generation with the twelve required fields baked in, branded layout, sequential numbering, automatic tax-line calculation, embedded payment links and recurring schedules for retainers. The finance module surfaces days-sales-outstanding, total receivables and aged debt on a single dashboard, so you can see at a glance whether the practice is healthy or whether something has slipped. The reports module turns that into the monthly view you need for the rate-review conversation and the year-end accounting handoff.
The Stripe integration carries cards, ACH and SEPA in multiple currencies; the QuickBooks integration syncs paid invoices into the accounting ledger automatically so the year-end is calmer. For freelancers currently piecing invoicing together across FreshBooks and QuickBooks, or across FreshBooks and a separate payment processor, consolidating into one workspace removes the reconciliation overhead that quietly eats two or three hours a week.
For practices serving general freelancers and small-business clients, the Solo plan is free forever and carries the invoicing and payments module in full. The freelance invoice template is a free starting skeleton if you are still piecing invoices together by hand. The structural goal is the same: turn "getting paid" from a Wednesday-afternoon chore into a Tuesday-morning automated motion.
FAQ
Q: What information must every freelance invoice include?
Your legal name and address, the client's legal name and address, a unique invoice number, the issue date, the due date, an itemised line for each deliverable, the total amount due, your payment details, the tax breakdown (if applicable) and the late-payment terms. Twelve fields, no more, no less.
Q: How fast should I invoice after delivering work?
Same day as delivery, or next business day at the latest. Every day you wait to invoice is a day added to your days-sales-outstanding. The freelancer who invoices on delivery gets paid in two weeks; the freelancer who invoices on the first of the month gets paid in seven.
Q: What is a healthy deposit structure for freelance projects?
30 to 50 percent on signature, with the balance split across milestones or paid at delivery. Below 25 percent leaves you exposed; above 50 percent triggers cold feet. The deposit is collected at the same moment the contract is signed — never billed afterwards.
Q: Should I use Net-7, Net-15 or Net-30 payment terms?
Net 7 or Net 14 for freelance service work — most clients pay roughly on the term you set, so a shorter term means a shorter wait. Net 30 is a legacy enterprise default that has no reason to be in a freelance contract; you are not extending bank-level credit.
Q: How do I chase an overdue invoice without burning the relationship?
Automate the cadence — a polite reminder on day 7, a firmer reminder on day 14, a formal late-payment notice on day 30. Manual reminders feel awkward; automated ones feel like business. By day 30, escalation moves from email to a formal demand letter and small-claims if needed.
Q: Should I charge late fees on overdue invoices?
Yes — clearly stated in the contract and on the invoice. The UK Late Payment of Commercial Debts Act sets 8 percent plus base rate plus a fixed fee; US states vary by jurisdiction. Charging the fee matters less than the fact you stated you would; it changes the client's payment priority.
Q: Which payment processor is best for freelancers?
Stripe is the lowest-friction default for cards and ACH/SEPA. PayPal is acceptable as a secondary option for clients who insist on it. Wire transfer is fine for large international invoices but slower. For multi-currency, Wise or a multi-currency Stripe account avoids hidden FX spreads.
Q: How do I handle multi-currency billing without losing on FX?
Quote in your home currency or USD, never in the client's local currency unless you accept the FX risk. Use a multi-currency payment processor so settlement happens at interbank rates rather than retail bank rates, which usually cost 2 to 4 percent more.
Q: How do I structure recurring or retainer invoicing?
Auto-bill on a fixed date (usually the first of the month), Net 7 due date, automatic card or ACH on file, automatic email receipt on payment. The client never has to remember to pay; the freelancer never has to remember to invoice. Set it up once, run it for the life of the retainer.
Q: What international tax do I need to think about when billing foreign clients?
VAT (EU/UK) and GST (AU/CA/SG) treatment depends on where the client is registered and whether they are B2B or B2C. For most freelance-to-business cross-border invoices, the reverse-charge mechanism applies and you do not charge VAT — but you must state the rule on the invoice. Verify with a local accountant.
Related guides
Invoicing is the cash-flow half of the freelance lifecycle — the full lifecycle structure lives in the freelance business management guide. For setting the rates that flow into the invoice, see the freelance pricing guide. For the legal protection that makes the invoice enforceable, see the freelance contracts guide. For the tax side of the revenue you collect, see the freelance taxes and finance guide. For onboarding the engagement before the first invoice goes out, see the client onboarding guide. For invoicing at scale beyond solo work, see the solo to small agency scaling guide.