LPOs explained — the purchase order that unlocks the payment

A local purchase order is the client company's formal instruction to buy: it names the supplier (your firm), the scope or items, the agreed price, and carries the number their finance system tracks. "Local" distinguishes it from an import order; in UAE and Saudi business practice the LPO (or PO) is the document that turns your accepted quote into their payable commitment.

The sequence that gets you paid runs: quote → acceptance → LPO issued against it → work → invoice quoting the LPO number → payment. Skip the middle step and the last one stalls, because many finance departments literally cannot process an invoice their system has no order for.

Four things, in two minutes. The price matches your quote — not the earlier draft they still have on file. The scope matches what you priced, including exclusions. The entity name is the company you think you are contracting with — the name that must appear on your invoices. And the payment terms printed on it: companies' standard terms (30, 45, 60 days) apply by default unless your agreed terms were carried onto the order — which is why the terms battle is fought at quote stage, not at invoice stage.

If anything differs, query it before the work starts, in writing. An LPO corrected after delivery is a negotiation; before, it is an email.

It happens constantly, and sometimes commercially you accept it — eyes open. The protection is a written trail: the client's email or message confirming the go-ahead, the price and the awaited LPO, kept with the job. Work done on a verbal start with no trail is the classic unpaid small job: nobody acted in bad faith, but nobody can prove the instruction either — the same gap the WhatsApp paper trail guide exists to close.

Set your own line for how much work proceeds before the LPO lands — materials ordered is a reasonable hard stop for many firms — and apply it evenly. Clients respect a firm whose rules are boring and consistent.