Blog

Purchase Order Friction: Why Good Invoices Still Pay Late

A playbook for freelancers whose invoices stall in PO, vendor onboarding, and AP queues — and how to remove friction before the work starts.

Published 2026-07-28

Start 30-day trial

When a client says accounting is processing, the invoice often never entered the queue cleanly. PO friction is an upstream problem dressed as a late payment.

Late pay that is really intake failure

Enterprise and mid-market clients often cannot pay without a purchase order, vendor ID, or matching line description. An invoice that is financially correct but PO-incomplete sits in limbo while everyone believes payment is in motion.

Treat PO requirements as part of scope kickoff, not as a surprise after delivery. Ask who issues POs, what fields must appear, and which inbox actually pays.

  • Missing PO / vendor ID — Common stall reason (AP intake patterns on B2B freelance work)
  • AP owner + PO fields — Ask before kickoff (Pre-send invoice checklist practice)
  • Accounting is processing — Status phrase to decode (Often means queued — or never entered)

Build a PO-ready invoice every time

Include PO number, vendor name exactly as registered, project code, period of service, and line items an approver can match without calling your contact. Put the same fields in the email body so forwards survive.

Confirm the paying entity. Billing the wrong legal name is a classic silent reject. Currency, tax ID if required, and payment method constraints belong on the checklist before send.

Organized paperwork and checklist representing purchase-order ready invoicing
PO-ready invoices look boring on purpose — finance systems reward matchable fields over clever copy.

A friction playbook after the invoice is stuck

Day 0–2 after due: confirm receipt and ask whether the invoice is in the AP system with a matching PO. Day 3–7: escalate to your day-to-day contact plus AP owner with the exact missing field list.

If onboarding is incomplete — W-9/VAT forms, portal registration, bank verification — treat that as a separate checklist with owners and dates. Reminder ladders cannot fix a vendor record that does not exist.

The most useful reply is not thanks. It is a short acknowledgment plus a request for a concrete timeline.

DueChat: When a client says accounting is processing

Prevent the next stall in the contract

Write into proposals: work begins when PO is issued or deposit clears; invoices include listed required fields; payment terms print as calendar dates. That language makes friction a shared process, not a personal chase.

For repeat clients, save a one-page AP profile: portal URL, required attachments, typical cycle length, and who to ping. Reuse it so every new invoice skips rediscovery.

Further reading

FAQ

Can I invoice without a PO if the client promised one?

You can, but expect delays. Prefer a deposit or written PO-in-progress with a named owner before large unpaid work starts.

What fields matter most for AP match?

PO number, legal entity name, invoice number, amount, currency, service period, and a description that matches the PO line.

How do I follow up without annoying my champion?

Ask them for the AP owner once, then copy both on factual status asks. Protect the relationship by making finance the process owner.

Get paid faster with polite chase that runs itself.

30-day Pro trial, card required at checkout. Cancel before day 30 to pay nothing, then €19/month or €190/year.

  • Scheduled 7/14/30-day reminders in your name until you are paid.
  • Stripe pay links on your account; you keep control of funds.
  • Confirm-before-send for sensitive steps, with a clear audit trail.
Start 30-day trial