DEV Community

Karactif Tech
Karactif Tech

Posted on Edited on

The Invoice Was Approved. So Why Hasn't It Been Paid?

The Invoice Was Approved. So Why Hasn't It Been Paid?

You finished the work three weeks ago and sent the invoice the same day. Yesterday the client's project manager told you, cheerfully, that it was "approved last week." It still isn't in your account, and nobody seems to think anything is wrong.

Nothing is wrong, exactly. You have simply discovered that in most companies, "approved" is not a decision. It is a queue.

Approval is a process, not a decision

For a solo business, approval is one person saying yes. For a company with more than a handful of staff, it is a chain: the person who received the work confirms it, a budget holder confirms the spend, finance confirms the vendor exists and the bank details match, and then the payment waits for the next scheduled run.

Four steps, four people, four chances for your invoice to sit untouched in an inbox for a week. Your document cannot skip that chain, but it can be built to move through it.

Design the invoice for the person who has to approve it

Approvers are not reading your invoice for pleasure. They are trying to answer three questions:

  1. Did we agree to this?
  2. Is the amount right?
  3. Which budget does it come from?

Every field that answers one of those questions removes a round trip. That means:

  • The purchase order number, quoted exactly, in the reference field and in the line description.
  • The project name or cost centre, spelled the way the client spells it.
  • The name of whoever signed off on the work, if the approver is someone else.
  • Line items that map to the quote, in the same order, at the same quantities.
  • Payment terms restated clearly, not buried in small print.

The most common cause of a slow invoice is not a dispute. It is a mismatch. Your invoice says "Consulting — Phase 2"; their PO says "Q3 advisory retainer." Now someone has to email someone to find out whether those are the same thing, and that email takes three days, and the person who sent it is on leave on Thursday.

Map the chain before you send, not after

Ask four questions at kickoff, or when the first invoice goes out:

  • Who receives invoices, and at what address? An accounts payable inbox is not the same as your day-to-day contact. If they have a supplier portal, use it from the start.
  • Who approves, and is there a threshold above which a second person has to sign?
  • When does the payment run happen — weekly, twice a month, on the 1st and 15th?
  • What reference do they need to route the invoice to the right cost centre?

It is an awkward email to send at kickoff, and it is worth more than any invoicing feature you will buy this year.

Status you can actually see

Most invoicing tools can tell you an invoice was sent. Almost none can tell you it was approved, because approval happens inside the client's systems, out of your view. Do not confuse "sent" or "viewed" with "in the payment queue."

So track the states you can verify yourself:

  1. Sent — you have a copy and a timestamp.
  2. Received — a human confirmed it, or the portal shows it in their system.
  3. Approved — someone told you, ideally in writing.
  4. Scheduled — it has a payment date.
  5. Paid — the money is in the account.

The gap between 2 and 3 is where invoices go to die. That is the only gap worth a follow-up.

The follow-up that isn't nagging

"Just checking in" gets ignored because it asks the approver to do work without telling them what work. A better message does the work for them:

Subject: Invoice 1042 — anything needed to get this approved?

Hi Sam — invoice 1042 for the March retrofit ($4,800, PO 88-441) was delivered on the 3rd. Is anything missing on your side to move it to approval? Happy to reissue with a different reference if that helps.

It names the document, the amount, the PO, the delivery date, and one specific question. If the answer is "we need a revised PO reference," you find out on day three instead of day thirteen.

Cadence: once three to five days after delivery, once around the payment-run boundary, then a firm note. Not daily. Daily is how you become the supplier people route to voicemail.

When the chain jams

Three jams explain a lot of late payments:

Missing or wrong PO. The invoice is unapprovable by rule, no matter how correct the work was. Ask for the correct PO in writing and reissue. Depending on their rules, that may mean a corrected reference or a credit note plus a new invoice. Do not invent a PO to get past a form.

A new AP system. Companies migrate to portals with no announcement. If your invoice went to an address that no longer accepts mail, you may not get a bounce, because the mailbox still exists and still swallows everything. Ask your contact to confirm the current submission route rather than resending into the void.

Approver on leave. There is nothing to do but know about it — which is why you ask about the chain at kickoff, before you need the backup.

The pre-send checklist

Before you send any invoice over a few hundred dollars:

  • PO number present and matching the client's record.
  • Legal entity name and address exactly as their vendor file has them.
  • Line items in quote order, same quantities, same descriptions.
  • Currency code written, not just a symbol.
  • The right inbox, not your contact's personal address.
  • Payment terms and a specific due date.

Two minutes, fewer delays.

Doing it inside the app

If you want the invoice to carry the right references without retyping them every month, Invoice Maker is a free iOS and Android app from Caractiv Tech built around repeatable billing. You can describe a job in text or by voice and get an editable invoice or quote draft to review and correct before anything is final. Saved clients keep the entity name and address consistent; reusable line items mean a repeat invoice maps to the original quote instead of drifting from it. It exports PDFs, tracks paid, unpaid and partially paid invoices, supports 34 currencies and 40+ Premium templates, and creates documents manually while offline — AI drafting needs a connection. Free to download, with a subscription for Premium.

One honest limit: it tracks what you have been paid, not what the client has approved. No invoicing app can see that. That part stays your job.

What actually changes

You cannot accelerate someone else's approval process. You can stop adding friction to it. The invoice that gets paid on time is rarely the prettiest one. It is the one that answers the approver's three questions without them having to ask, and arrives at the address where approvals actually happen.


Get Invoice Maker

Disclosure: I work on the invoicing app linked above, which is why I write about this. The workflow advice is general and applies to any billing tool. This article is general information, not legal, accounting or financial advice.


Appendix: distribution assets (not part of the article body)

Social summaries

X: "Approved" is not a decision. In most companies it's a queue: receiver confirms, budget holder confirms, finance confirms, then it waits for the payment run. Your invoice can't skip the chain, but it can be built to pass through it — PO number, cost centre, line items in quote order.

LinkedIn: Late payment is usually an approval-chain problem, not a billing problem. Four steps, four people, four chances for your invoice to sit for a week. The fix is unglamorous: ask at kickoff who receives invoices, who approves, what the threshold is, and when the payment run happens. Then build the document for the approver's three questions — did we agree to this, is the amount right, which budget. The gap between "received" and "approved" is where invoices die, and it's the only gap worth chasing.

Reddit (r/freelance — answer-first, no link): The thing nobody tells you: "approved" often just means one person signed off, not that finance has it. Ask three questions before your first invoice — who receives them, who approves above what threshold, and when the payment run is. Then put the PO number and cost centre on the document. Many "late payments" are invoices that were never routable in the first place.

Image suggestion

Concept: A clean overhead shot of a desk with a printed invoice, a sticky note reading "PO 88-441?", a coffee cup, and a laptop showing an email thread with the subject line "Invoice 1042 — anything needed to get this approved?" The invoice has one field circled in red: the reference number.

Alt text: An invoice on a desk with the purchase order reference circled, next to an email asking whether anything is missing for approval.

Notes: 1200×800 for a blog header; 1080×1080 crop for LinkedIn. Use a fictional client name and blur any account numbers. Keep the palette neutral — this is a process story, not a product shot.

Top comments (1)

Collapse
 
jose_lpez_9b1680b7a88dd5 profile image
Jose López •

interesting