What Makes an Invoice Payable
An invoice is payable when a machine can match it and a person can approve it. Nine things decide that, and all nine are yours.
Yourswho controls this stretch
An invoice becomes payable when a system can match it and a person can approve it. Nine things decide whether both happen, and every one of them is within your control.
The invoice problem in “What Makes an Invoice Payable” is easier to resolve when the work behind it has an approved record. A service team assessing visit the platform website here for attendance sheet template can connect time and projects with the billing file, while the invoice and accounting system remains authoritative for amounts, tax and settlement.
This is the only stretch of the whole process that is entirely yours, which is what makes it worth doing perfectly.
As a separate reference point for “What Makes an Invoice Payable”, see Fiverr Workspace business resources. Confirm current legal, tax and accounting requirements with a qualified adviser where necessary.
The right legal entity
The exact name of the company that engaged you, as it appears on the order. Not the trading name, not the group.
The nine, checked once before sending:
- The right legal entity.
- The order number, in the format they use.
- Your own registered details.
- An invoice date and a unique number.
- Lines that match the order.
- The tax treatment they expect.
- The payment terms, stated.
- How to pay you.
- A description a stranger can recognise.
An invoice to the wrong entity cannot be paid by the right one.
The order number
Exactly as issued, in the field their system reads. The single most common cause of rejection, covered at length in its own note here.
Your own details
Legal name, address, registration numbers, and bank details matching the supplier record they hold.
A mismatch between the invoice and the record stalls the payment at the last gate rather than the first.
A date and a number
The invoice date, which usually starts the clock, and a unique sequential number that both sides can quote.
Reused or skipped numbers cause queries that are entirely avoidable.
Lines that match the order
Same descriptions, same quantities, same unit prices, same total. Many systems match line by line.
Invoicing "as agreed, £4,800" against an order with four priced lines fails without a human ever seeing it.
The tax treatment
Correct, shown separately, with the rate and any registration number. What is required differs by place and by what you supply, and getting it wrong produces a rejection and a correction.
That is a question for somebody qualified where you are.
The payment terms, stated
The due date, calculated, on the document. Not "30 days" but the actual date.
It removes an argument later about what the terms were and when they started.
How to pay you
Bank details in full, with a reference they can use. Plus any alternative route the buyer prefers.
What it is for, in words a stranger can follow
One line per item, naming the thing delivered. The approver was not involved in the work and has to recognise it.
"Professional services" tells them nothing and invites a query.
The nine, checked once
Two minutes per invoice, against a list.
Suppliers who do this report first-time acceptance rates close to total; suppliers who do not spend those two minutes many times over on the telephone.
What happens to the ones that are not
An invoice failing any of these does not come back with the reason. It is parked, queried internally, or left unmatched, and the first signal you receive is the absence of payment on the date you expected it.
By the time you ask, two things have usually happened: the delay is already a month old, and the person who could have fixed it in a minute on day one now has to reconstruct what went wrong.
This asymmetry is the entire argument for checking the nine items before sending. Each check costs seconds; each failure costs weeks and is invisible for most of them.
The checks a template can do for you
Most of these items are stable for a given customer, which means the checking can be built once rather than performed each time.
The legal entity, the invoice address or portal, the terms as stated, the reference format and the tax treatment do not change between jobs. Recorded against the customer rather than looked up each time, they stop being a source of error.
What remains variable per invoice is small: the order number, the lines, the dates, the description and the total. Five things to check against the job record, which is a different task from reconstructing how this customer wants to be invoiced.
Suppliers who work this way make almost all their invoicing errors on first jobs and very few afterwards. Suppliers who rebuild each invoice from a general template keep making the same errors indefinitely, because nothing in the process remembers what was learned the previous time. The habit worth forming is that a customer's invoicing requirements get written down once, at the point they are discovered, in the place the next invoice will be built from.
The one that is not on anybody's list
Legibility. An invoice that satisfies every formal requirement and describes the work as "professional services per agreement" still stops, because the approver cannot tell what they are approving.
A line a stranger can read and recognise is not a legal requirement anywhere, and it is the difference between an approval taking a day and taking a fortnight of internal questions.
What it still cannot do
Make the approval fast, or make the payment run earlier.
A perfect invoice fails at none of the gates you control, which is the most that is available to you here.