12 Common Invoice Mistakes That Delay Your Payment
Missing PO numbers, vague descriptions, wrong tax rates: the errors that push invoices to the bottom of the pile, and how to avoid them.
Why small errors cost weeks
Accounts payable is a gatekeeping function. When an invoice fails a checklist (missing PO, wrong entity, maths mismatch), it is rejected or parked. You rarely get a detailed coaching email; you get silence until you chase. Preventing mistakes is faster than curing them.
Use the list below as a pre-send audit. A structured tool such as the free invoice generator removes several of these automatically by keeping required fields visible and totals calculated.
The twelve mistakes
- No unique invoice number. Impossible to reference in bank transfers or reminder emails. Always use a sequential scheme and never reuse numbers.
- Missing purchase order number. Enterprise systems often reject invoices without a PO match. Ask at kickoff; print it on the PDF.
- Vague line descriptions. "Consulting" invites questions; questions cost weeks. Name deliverables, periods, and phases.
- No due date. "Soon" or "ASAP" is not a term. Give a calendar date and match it to contracted Net terms.
- Wrong legal entity. Bill the company on the contract, not a trading name, nickname, or personal Gmail for a limited company.
- Maths that does not add up. Hand-edited totals that disagree with line sums are an instant red flag. Let the tool calculate.
- Incorrect tax rate or missing tax number. Blocks the client's reclaim and can make the invoice non-compliant. See the tax invoice guide.
- No payment instructions. Do not make clients ask for bank details. Put them on the invoice in a scannable block.
- Editable file formats. Send PDF, not spreadsheets or docs that reflow or get altered.
- Sending to the wrong inbox. Find accounts payable early; CC the project contact for internal push.
- Invoicing late. You slip a whole payment cycle. Invoice on delivery or on the agreed milestone day.
- No follow-up system. Unchased invoices are paid last. Diary reminders on day 1, 7, and 14 after due.
Mistakes 1–4: identity and timing
Number, PO, descriptions, and due date are how buyers route and schedule payment. If any are wrong, the invoice may never enter the payment run. Freelancers underestimate PO culture; corporates underestimate how often trading names differ from legal entities.
Fix: maintain a client profile with legal name, AP email, PO rules, and default terms. Refresh it when the client rebrands.
Mistakes 5–8: compliance and clarity
Wrong entity, bad maths, tax errors, and missing payment details create either rejection or manual exception handling. Exception handling is where invoices go to wait.
Fix: dual-check large invoices; use templates with tax fields; keep IBAN/account name identical every time so clients can save a payee record. For VAT/GST specifics, read the VAT and GST guides.
Mistakes 9–12: delivery and discipline
Format, recipient, timing, and follow-up are operational habits. Teams that batch send on Fridays with a shared tracker outperform heroic individuals who invoice from memory.
Fix: adopt the send checklist in how to send an invoice and the process tips in the small business invoicing guide.
Quick pre-send checklist
- Filename includes invoice number and client
- Buyer legal name and address verified
- PO / reference present if required
- Lines, discounts, tax, and total agree
- Due date visible beside amount due
- Payment methods complete
- PDF attached (not a link that expires)
- Subject line includes number and due date
What to do if an invoice is already rejected
- Ask for the rejection reason in writing.
- Do not silently edit and resend under the same number if the document was formally issued. Use a credit note plus a new invoice when required.
- Fix the root data (entity, PO, tax) in your template so the error does not recur.
- Resend with a short note listing what changed.
Mistakes that look like client problems
Sometimes the invoice is fine and the buyer's process is slow. Still, rule out your own errors first: confirm delivery to AP, confirm PO match, confirm entity. Only then escalate. Approaching a late payer with "please check whether anything is missing" lands better than accusations, and occasionally surfaces a fixable defect you caused.
Document every chase with dates. If you eventually need a collections letter or legal help, that timeline matters. Memory is not a ledger.
Template drift across the team
One founder uses a solid template; a contractor later pastes totals into a slide deck. Standardise on a single generator workflow and forbid ad-hoc invoices for anything above a trivial amount. Drift is how mistakes nine through twelve return after you thought you fixed them.
Review a sample of recent PDFs quarterly. Look for missing POs, pale payment text, and inconsistent seller addresses after an office move.
Preventing repeat rejects
When a client rejects an invoice, add the reason to their profile checklist. The second invoice to that client should not fail the same way. Institutional memory turns one painful reject into a permanent intake improvement.
Currency and rounding traps
Display currency explicitly on every total. Rounding tax to the nearest unit incorrectly (or rounding each line differently from the system that filed the return) creates one-cent disputes that still block payment in rigid ERPs. Let your generator calculate, and match the rounding mode your accountant expects.
Do not convert currencies by hand in a spreadsheet cell you forget to update. State one currency and stick to it for that invoice.
The fix going forward
A structured template eliminates many of the twelve automatically. Our free invoice generator keeps totals consistent and required fields in view. Pair it with a layout that matches your buyer (Corporate for strict AP teams, Modern for everyone else) and run the checklist above until it is muscle memory.
Frequently asked questions
Is an invoice still valid if it contains a mistake?
Usually it still works as a request for payment, but the client may refuse to pay until the error is fixed. Mistakes on tax invoices are more serious, because a missing or wrong tax field can stop your customer from reclaiming tax. Correct the problem with a credit note and a new invoice, or a reissue, according to your local rules.
What should I do if I sent an invoice to the wrong client?
Contact the recipient immediately, explain the error, and ask them to delete it and not pay it. Void the invoice in your records or issue a credit note against it, then send a correct invoice to the right client with a new number. If the invoice contained another client's personal data, check whether your privacy rules require you to report it.
What if I undercharged a client on an invoice?
Tell the client promptly and explain the error. If the invoice is unpaid and not yet recorded, you may be able to cancel it and issue a corrected one. Otherwise, send a supplementary invoice or debit note for the difference, referencing the original number. Whether the client must pay depends on your agreement, so be polite and specific.
What should I do if a client overpaid or paid an invoice twice?
Confirm the duplicate payment against your bank statement, then tell the client. Offer either a refund or a credit toward their next invoice, and do what they choose in writing. Record the overpayment in your books so it is not mistaken for income. Paying it back quickly protects trust and avoids reconciliation problems for both sides.
Can I still send an invoice months after I did the work?
Usually yes, but late invoices are more likely to be questioned, fall outside the client's budget year or get pushed down the queue. Legal time limits for recovering unpaid debts exist and vary by country and state, often several years. Tax rules may also set deadlines for issuing invoices, so send late invoices as soon as you notice them.
Should the invoice date be the day I did the work or the day I send it?
Usually the invoice date is the day you issue it, and payment terms count from that date. If the work happened on a different date, show the supply date or service period separately. In VAT and GST systems, the supply date can affect when tax is due, so make sure both dates are correct rather than backdating the invoice.
Does an invoice need a signature to be valid?
In most countries a signature is not required on an ordinary invoice, and a missing one rarely delays payment. Some tax regimes or clients do ask for a signature or digital signature, for example on certain GST invoices. If a client's policy requires one, add it. Otherwise, an empty signature line can make the document look unfinished.
What happens if I use the same invoice number twice?
Duplicate numbers confuse both your records and your client's. Their accounts system may reject the second invoice as a duplicate, or someone may pay the wrong one. In tax audits, repeated numbers can raise questions about missing sales. If it happens, keep the first invoice, cancel the duplicate with a note, and reissue it under the next unused number.
What if my client paid into the wrong bank account because of a typo?
Contact your bank and the client's bank as soon as possible, because a quick recall request has the best chance of recovering funds. Then send a corrected invoice with the right details. To prevent this, copy bank details from a saved profile instead of retyping them, and use payee name-checking services where your country's banks offer them.
Is rounding hours on an invoice a mistake?
Rounding is fine if it is consistent, fair and agreed. State your policy, such as rounding to the nearest quarter hour, in the contract and the invoice notes. Problems arise when rounding always goes up, is applied differently each time, or makes line totals disagree with the timesheet. Let your invoice tool calculate totals from the rounded hours.
Invoice Creator Editorial Team
Guides on invoicing, cash flow and small-business finance from Invoice Creator, operated by Next Software Development Company. Content is reviewed for accuracy against the fields our own invoice generator produces.
Try the invoice generator