LPO, PO or LPR? Purchasing documents explained

Why do purchasing documents cause so much confusion?

Purchasing documents cause confusion because they look alike and their abbreviations vary from company to company. A requisition, an RFQ and an LPO can all list the same items, quantities and delivery date. Only one of them commits your company to pay.

The confusion costs money. A supplier delivers against an RFQ because it “looked like an order”. A storekeeper accepts goods with no LPO behind them. Accounts receive an invoice and can’t tell which order it belongs to.

The fix starts with the vocabulary. Below, each document is defined, compared and traced through one purchase.

LPO meaning: what is a local purchase order?

An LPO is a purchase order, under the name used across the Gulf. It is a formal document from a buyer to a supplier that says: we will buy these items, in these quantities, at these prices, delivered here, by this date, on these payment terms.

The word “local” is historical. It separated orders placed with suppliers in the same country from import orders, which usually carried different paperwork such as letters of credit and shipping documents. Many companies now call every purchase order an LPO, whether the supplier is in Dubai, Dammam or overseas.

A complete LPO usually carries:

• your legal name, address, VAT tax registration number (TRN) and commercial registration or trade licence;
• a unique LPO number and the order date;
• the supplier’s legal name, address and VAT number;
• the delivery address or warehouse and the expected delivery date;
• each line’s item code, description, quantity and unit;
• the unit price, any discount, the VAT rate and VAT amount per line;
• the subtotal, VAT, total and currency;
• payment terms, such as 60 credit days from the invoice date;
• a reference to the supplier’s quotation;
• your standard terms and an authorised signature, often with the company stamp.

One more point trips people up. For the seller, your LPO is the customer purchase order that confirms their quotation. When a customer says “send the quotation and we’ll issue the LPO”, they mean this same document, seen from the other side.

Is an LPO the same as a purchase order?

Yes. An LPO and a purchase order (PO) are the same document. You will hear both names across the UAE and Saudi Arabia, sometimes inside one company. What matters is what the document does: it is the approved, numbered order the supplier delivers and invoices against.

If your team uses both terms, pick one for printed documents and treat the other as a synonym. Suppliers and auditors care that delivery notes and invoices quote an approved order number, not which name is printed at the top.

What is an LPR, and how is it different from an LPO?

An LPR is an internal request to buy, not an order. It usually stands for local purchase request; some companies say “local purchase requisition”. Either way, it is the fast lane for small, urgent or routine local purchases, such as consumables for a site or a part needed tomorrow.

The difference from an LPO is commitment:

• An LPR stays inside your company. It says “we need this”. It may name a preferred supplier and may be sent to suppliers as a request for prices, but it never obliges anyone to pay.
• An LPO goes to one supplier. It says “we are buying this”. Once the supplier accepts it, it is the basis for delivery, invoicing and payment.

An LPR is usually lighter than a full purchase requisition, often skipping formal approval and quote comparison. That speed is the point, so set a clear limit on what may go through it.

Requisition, RFQ and supplier quotation: what comes before the LPO?

Three documents usually come before an LPO on a sourced purchase. Each answers a different question.

1. Purchase requisition (PR): “May we buy this?” Someone inside the company asks for goods, with a purpose, quantities and a needed-by date. A manager approves it before anyone talks to suppliers.
2. Request for quotation (RFQ): “What would you charge?” The buyer sends the approved needs to several suppliers. A good RFQ says in plain words that it is not a purchase order and leaves the price columns blank.
3. Supplier quotation: “Here is our offer.” Each supplier replies with prices, validity, lead time and payment terms. The buyer lines the offers up in a quote comparison, picks a winner per line and records why.

Only then does the buyer raise the LPO, one per winning supplier.

How do the purchasing documents compare?

Print this table for new buyers and storekeepers. The key column is the fourth: only two documents commit you to pay.

What does the purchasing document flow look like?

The flow runs from an internal request to a supplier invoice that matches what was ordered and received. There are usually two routes into the LPO and one common path after it.

Route A, sourced purchase: requisition → approval → RFQ → supplier quotations → comparison and award → LPO.

Route B, quick local purchase: LPR → (optional price check with a supplier) → LPO.

After the LPO, both routes meet: LPO issued → supplier delivers with a delivery note → stores record a GRN → accounts receive the supplier invoice and match it to the order and the receipt → the supplier is paid.

Some companies add a step between the GRN and the invoice, a goods receipt report (GRR). The GRN records what physically arrived; the GRR is the back-office document that accepts the goods into stock and books them. Splitting the two keeps the person counting boxes separate from the person posting value.

Worked example: one purchase, start to finish

Here is a fictional purchase traced through every document, in AED with UAE VAT at 5%.

The trail shows why Supplier B won, what was ordered, what arrived and why the invoice is lower than the LPO.

What are the most common mix-ups, and how do you avoid them?

Most purchasing disputes trace back to a few habits, each with a simple fix.

• An RFQ is treated as an order. Print “This is not a purchase order” on every RFQ and leave prices blank.
• The LPO is raised after delivery. A retrospective LPO hides an unapproved purchase. Track each one as an exception.
• Changes are agreed by phone. If quantities or prices change, issue a revised LPO with a revision number and a reason, so the supplier’s invoice has something to match.
• The LPR lane is used to dodge approval. Set a value limit and a list of what may be bought through an LPR.
• Delivery notes and invoices don’t quote the LPO number. Make the LPO number a condition of acceptance at the gate and in accounts.
• One delivery covers several LPOs. Record every LPO number on the GRN, so each order is received against correctly.

For the full process from request to payment, read the procure-to-pay guide.

How 1flux handles this

1flux uses the vocabulary your buyers and storekeepers already use, and connects each document to the next in 1flux Inventory, which includes purchasing and receiving.