How to Invoice Correctly So the Payment Is Never Stuck
How to invoice correctly: ask how the customer pays, raise the invoice the moment the trigger happens, and remove every reason a payment might sit unprocessed.
To invoice correctly, ask the customer at the start exactly how they pay, then raise the invoice immediately on a trigger event with every required detail, sent to the inbox that actually processes it. The leading cause of late payment is a defective invoice, not an unwilling customer.
Most of collections is not chasing. It is removing every reason a payment might not happen. This post is about the first half of that sentence: getting the invoice itself right.
How to invoice correctly: the defective invoice problem
Think about what usually goes wrong. A wrong reference. A missing purchase order number. An invoice sent to a person instead of the accounts inbox. The wrong entity name, the wrong amount, or a missing detail the customer's system needs.
What makes these mistakes expensive is their silence. In most cases the invoice is not rejected loudly. It simply sits, unprocessed, until you ask. You assume it is moving through approval, while in fact nobody is looking at it. Getting the details right the first time removes more delay than any amount of chasing afterwards, as how to chase an overdue invoice explains from the other direction.
Ask how this customer pays, at the start
The way to get the details right is not to guess. It is to ask, at the beginning of the relationship, exactly how this customer pays. It takes five minutes, and it removes the most common causes of delay.
| Ask this | Because it decides |
|---|---|
| Which entity is invoiced? | Whether the invoice names the right company |
| What address? | Whether it reaches the right place |
| What reference or purchase order is required? | Whether their system will accept it at all |
| Which inbox receives it? | Whether it lands where payment is processed |
| Who approves it? | Who must act before money moves |
| On what cycle do they run payments? | When it will realistically be paid |
Larger organisations in particular have specific requirements that are entirely knowable and entirely fatal to ignore. An invoice missing a purchase order number at a company that requires one is not late. It is invisible. Asking after the first invoice has stalled is too late, so ask before you raise it.
Check the entity that signed
One of the details on the list deserves special attention: the entity being invoiced should be the entity that signed. It is easy to assume, and easy to get wrong when a customer has several related companies.
The same point matters before the work begins, when you decide whether to extend credit at all. Whether the signing entity is the one that will pay is part of the check described in how to decide who gets credit.
Define the trigger event, then make it automatic
A surprising amount of late payment is actually late invoicing. The work finished, everyone moved on, and the invoice went out eleven days later. That is eleven days of runway given away for nothing, before the customer has done anything wrong.
The fix has two steps. First, decide what event causes an invoice to be raised. It might be delivery, a milestone, the start of a subscription period or the signing of a contract. Second, make the invoice happen immediately on that event, rather than in a monthly batch that suits your admin rhythm and nobody's cash position.
- Name the event that triggers each kind of invoice.
- Check that the event is something you can see, not something you must remember.
- Make the invoice follow the event without waiting for a quiet afternoon.
- Confirm that the right customer details are already stored where the invoice is raised.
When this works, the invoice is a by-product of the work, not a separate task competing with it.
Send it right
With the trigger fixed and the details known, the invoice itself needs to be unambiguous. Each line below is a way an invoice stalls, and each has a simple preventive.
- Every required reference is present. Include the purchase order or reference number the customer asked for.
- The amount, description and dates are clear. Nobody should have to work out what the total covers or when it is due.
- It goes to the accounts inbox. Sending only to your contact risks the invoice sitting with a person who does not process payments.
- The reference to quote is stated. When money arrives, it should be obvious which invoice it settles.
The person who bought from you is frequently not the person who pays you, and may not know there is a problem. Copying the accounts inbox helps close that gap. Naming a person at each end closes it further, as how to send invoice reminders describes.
Make paying as easy as possible
Every point of friction is a delay. A payment method the customer does not use, a currency that complicates their process, no clear reference or an ambiguous total will each slow the money down.
| Friction | Remedy |
|---|---|
| A payment method they do not use | Match the methods to what this customer actually uses |
| A currency that complicates their process | Choose with their process in mind |
| No clear reference | State the reference to quote |
| An ambiguous total or due date | Make both unmistakable |
This is one of the few places where a small amount of setup work returns cash indefinitely. You do it once for each customer, and it keeps paying back.
Where a deposit changes the picture
The best invoice problem is the one you have less of. If part of the money arrives before or during the work, the final invoice is smaller and matters less. That is covered in how to ask for a deposit, and the two practices work well together.
A short check before you press send
You can run the whole post as a quick routine. Before any invoice goes out, tick each of these.
- I asked how this customer pays at the start of the relationship, not after the first stall.
- The invoice is raised on the triggering event, not in a batch.
- Every required reference and detail is on it.
- The amount, description and dates are unambiguous.
- It goes to the accounts inbox as well as to my contact.
- The payment method suits this customer.
- A question about it will reach a named person quickly.
If a box cannot be ticked, that is your next task, and it is worth doing before the invoice leaves. A correct invoice costs a few minutes. A defective one costs a stalled payment and a conversation you did not need to have.
Why a correct invoice is invisible when it works
The reward for getting this right is that nothing happens. The invoice arrives, it is processed, and the money turns up on the due date. Nobody thanks you, and there is no drama to remember. That is exactly why the discipline is so easy to neglect and so valuable to keep.
The cost of getting it wrong is equally quiet. The invoice sits, you assume it is being handled, and the weeks pass. By the time you notice, the delay has already happened, and you are chasing a problem you created. Treat the care taken now as the cheapest insurance in your collections.
Where the detail lives
Everything above depends on knowing the customer's requirements at the moment you raise the invoice. If the answers live in your head, or in an old email, they will be missing when you need them. Store the customer's payment details where the invoice is made, so the right entity, address, inbox and reference are there every time.
| Detail to store | Used for |
|---|---|
| Invoiced entity | The name on the invoice |
| Address and inbox | Where it is sent |
| Reference or purchase order | Whether their system accepts it |
| Approver and payment cycle | Who acts, and roughly when money moves |
This is the practical meaning of the guide's advice to keep it all in one place. It also means that when a new person raises an invoice, they are not relying on memory.
Fixing a defective invoice
If you discover that an invoice was wrong, deal with it plainly. Correct it, send the corrected version to the right place and say what has changed. Do not wait for the customer to ask, and do not treat it as an embarrassment. A quick, accurate fix reads as organised.
Then ask why it happened. If the cause was a missing detail, add it to what you store. If it was the timing, go back to the trigger event. Each defect that you trace to its source is one you are less likely to repeat.
Frequently asked questions
Why does a correct invoice matter more than chasing?
Because the leading cause of late payment is a defective invoice. Getting details right the first time removes more delay than any later chasing, and chasing cannot fix an invoice that is invisible to the customer's system.
When should I ask how the customer pays?
At the start of the relationship. It takes five minutes and removes the most common causes of delay. Asking only after the first invoice stalls means the first payment has already suffered.
Why not invoice in a monthly batch?
A batch suits your admin rhythm, not your cash position. Every day between finishing the work and sending the invoice is runway you give away, so tie the invoice to the trigger event instead.
Is sending to my contact enough?
Not on its own. The person who bought from you is often not the person who pays, so make sure the invoice reaches the accounts inbox.
The full method, with the checklists, is in The Getting Paid Playbook, a free 34-page playbook.