How to invoice a client so you actually get paid
An invoice gets paid faster when it reaches the person who approves payment, states a specific due date rather than a period, lists a single unambiguous total, and includes the reference the client's system needs. Format matters less than routing.
An invoice is not a bill. A bill records what is owed. An invoice is a request that has to travel through someone else’s organisation, land on the desk of a person who has never met you, and survive a process designed to slow money down. Most advice about invoicing concerns the document. Most of what determines when you get paid concerns the routing.
Send it to the person who approves payment
This is the single largest factor and it has nothing to do with the invoice itself.
In any organisation above roughly ten people, the person who hired you and the person who releases payment are different people. The first has no budget authority; the second has never heard of you. An invoice sent to your contact sits in their inbox until they remember to forward it, and they will remember somewhere between three days and never.
Ask for the accounts contact when you take the work, not when you chase the payment. Frame it as logistics rather than suspicion: who should I send the invoice to, and does it need a PO number? Nobody finds that question strange at the start of a project. Everybody finds it slightly pointed at week six.
Ask what their system needs
Many companies will silently reject an invoice that lacks something their process requires. Silently, because the rejection happens inside a system that does not email you.
Common requirements: a purchase order number, a specific email address rather than a person, submission through a supplier portal, a cost centre code, or a particular reference format. None of them are difficult. All of them are invisible until you ask.
One question at the start of the engagement saves a month of confusion later.
Invoice immediately
The correlation between how long you take to invoice and how long the client takes to pay is uncomfortably strong. An invoice that arrives the day the work finishes lands while the work is still fresh and while the person who approved it still remembers approving it. An invoice that arrives three weeks later lands as an interruption.
Same-day is best. Same-week is fine. Longer than that and you are actively working against yourself.
Give a date, not a period
“Net 30” requires the reader to work out a date and gives them an excuse not to. “Due 14 October 2026” does not.
Put the date on the invoice in a place that is hard to miss, and make it the only date that could be mistaken for a deadline. If your invoice shows an issue date, a service period, a delivery date and a due date all in the same size type, none of them is a deadline.
One total, unambiguous
The reader should be able to find the amount owed in under two seconds. Not the subtotal, not the tax, not the amount before discount — the number they need to pay.
Make it the largest number on the page. Everything else supports it.
Make paying easy
A surprising share of unpaid invoices are unpaid because the person who wants to pay could not quickly find how. Put the bank details on the invoice itself, not in the email body, not in an earlier attachment. Include everything the transfer needs: account name exactly as the bank holds it, account number, routing or IFSC or SWIFT as applicable, and bank address for international transfers.
If you take card or UPI, say so and include the details. The easiest payment method is the one that gets used.
Describe the work in the client’s language
“Consulting services, October” tells an accounts department nothing and gives them nothing to match against. “Brand identity: logo, two lockups and colour system, as per proposal dated 3 September” is checkable against something.
Where a purchase order exists, quote its number and use its wording. The person processing your invoice is matching it against a record. Make matching easy and they process it. Make it hard and they set it aside.
Terms worth stating
A late fee, if you intend to charge one. Whether it is enforceable depends on your jurisdiction and your contract, but stating it on the invoice changes behaviour regardless of whether you ever apply it.
A deposit, for new clients or large projects. Thirty to fifty per cent upfront filters out the clients who were never going to pay, which is more valuable than the cash flow.
Milestone billing, for anything longer than a month. Three payments of a third are three chances to notice a payment problem early, rather than one very large chance to notice it at the end.
The follow-up rhythm
Three messages, escalating.
A few days after the due date: a short, friendly note assuming it was missed, because it usually was. Two weeks: firmer, asking for a specific date or a specific reason. Four to six weeks: formal, stating the position and what happens next.
Half of overdue invoices clear on the first or second message. The third is for the rest. Escalate faster than this and you damage relationships that would have paid anyway. Escalate slower and you teach every client that your terms are decorative.
Our reminder writer drafts all three.
What to do when it does not work
At some point a client is not slow, they are not paying. The signals are consistent: repeated promises with specific dates that pass, a new person handling it each time, and requests to resend an invoice you have already resent.
At that point stop chasing informally and put something in writing that states the position. What that letter can say depends on where you are. In India, a registered micro or small enterprise has statutory interest under the MSMED Act that a buyer cannot decline. Elsewhere, late payment legislation may give you a similar footing. Either way, a message that states a position collects more than a message that makes a request.
And then stop working. Continuing to deliver to a client who is not paying is not diligence. It is an unsecured loan you did not agree to make.