Where Your Invoice Actually Stalls in Approval

You sent a clean invoice on Net 30. It is now day 50. Nothing has bounced back, no one has complained, and the money has not arrived. That gap is almost never about a client who cannot pay. It is about an approval step that quietly stalled and stayed stalled because nobody told you.

Payment is the last event in a chain. Before a single dollar moves, your invoice has to be received, matched, coded, approved, and scheduled. Each of those is a place it can sit for a week. Map your delay to the step where it is stuck and the fix is usually small. Guess, and you send three polite follow-ups that all land on the wrong problem. If you want the full breakdown of causes, the answer on why an invoice takes so long to get paid covers each one.

The invoice never reached the person who approves it

The most common delay happens before approval even starts. You emailed your contact. Your contact is not the person who pays. In a company with an accounts payable function, invoices need to arrive at AP, often with a PO reference, sometimes through a specific inbox. Your contact meant to forward it, got busy, and it died in their inbox.

A PDF attachment makes this worse. It gets detached from the email, renamed, and lost. Sending the invoice as a link keeps it in one place that everyone can open, and it lets the recipient route it to accounts payable without you playing telephone. If you are still emailing attachments, read why you should send an invoice as a link instead.

The PO number is missing, so AP will not touch it

Many AP teams run three-way matching: they compare your invoice to a purchase order and a goods receipt before they pay. No PO number, no match, no payment. The invoice does not get rejected loudly. It gets set aside until someone tracks down the PO, which can take a fortnight on its own.

The awkward part is that the PO often does not exist when you invoice, or your contact forgot to give it to you. Chasing it by email means a new PDF, a new version, and a fresh round of back and forth. It is cleaner when the recipient can add the PO number after the invoice was sent as a tracked amendment, without you reissuing anything. For the deeper mechanics, see what happens with a missing PO number and how it quietly kills an invoice.

The billing details are wrong, so it fails validation

Your invoice says "Acme Inc" and their system pays as "Acme Holdings LLC". Or the billing address is the office your contact sits in, not the registered entity AP pays from. Either mismatch fails validation and the invoice bounces back to you, sometimes weeks later, with a note to correct and resend.

The recipient always knows their own billing entity and address better than you do. Letting them edit their own invoice fixes the entity, address, and AP contact at the source, and you get notified so you can revert anything odd. That single change removes an entire resend cycle. More detail on the pattern here: fixing wrong billing details on a sent invoice.

Someone wants a change and is negotiating by email

A line item is disputed. The discount was supposed to be 10 percent, not 5. The currency is wrong. Traditionally this becomes an email thread, then a corrected PDF, then a question about which version is current. During all of it, the clock keeps running and nothing gets approved.

Handle changes as structured requests instead. The recipient asks to change a line item, price, or due date; you approve or decline; the tool creates a clean new version and marks the old one superseded. Everyone knows which invoice is live. See how to run an invoice change request without the thread spiraling.

The terms were long to begin with

Some delay is real, just baked into the terms you agreed to. Net 30 does not mean 30 days from when you sent it. It usually means 30 days from when AP accepts it as valid, and that acceptance can be a week after you hit send. Net 60 stretches this further. If your cash flow depends on faster turnaround, the terms themselves are the lever. Start with what Net 30 payment terms actually mean, then look at how to shorten payment terms without losing the client.

You cannot see where it is stuck

The reason a stalled invoice stays stalled is that you are blind to it. You do not know if it was opened, forwarded, or is waiting on a PO. You just know it is quiet. Invoice tracking shows you the status: Sent, Viewed, Change Requested, or Approved. If it says Viewed but never moved, you chase the right person about the right blocker. If it was never opened, chase delivery, not payment.

Map the delay, fix the one step that is stuck, and most invoices clear fast. When you are ready to send one that lets the recipient add a PO, fix their billing entity, and approve it without an account, create an invoice and share the link. It is free, and you can watch exactly where it lands.