Learning contextDemo Retail Group LLC12 stores · 2 distribution centres · AED/SAR/USD · omnichannel replenishmentChange scenario details →
Skip to content

Purchase Order field guide ​

The Purchase Order (PO) is an approved commitment to buy goods or services. It is not a receipt, supplier invoice, or payment. OSERP uses the PO to control budget, quantity, price, delivery, tax, quality, landed cost, and three-way matching.

Header fields ​

Open Purchasing → Workspace → New Order.

FieldExamplePurpose and impact
PO numberPO-2026-004281Immutable commitment key
CompanyDemo Retail Group LLCLegal purchasing scope
BranchDXB-MAINResponsibility and tax location
SupplierNovaBio GmbHPayable and supplier statement
Supplier referenceNB-Q-88210External traceability
Order date2026-09-17Commitment and audit date
Required date2026-10-02Planning and SLA
CurrencyUSDSupplier price and FX
Exchange rate3.6725Functional value
BuyerAisha KhanOwnership and approval
WarehouseDXB-COLDReceiving destination
IncotermCIP DubaiFreight, risk, and customs
Payment termNet 30Due date and cash forecast
Tax treatmentImport / standardTax and landed-cost rules
StatusDraft / approvedCommitment gate

Header also stores quotation, contract, project/WBS, budget, freight method, carrier, quality requirement, supplier contact, notes, attachments, and approval route. Supplier, company, currency, and external reference must be validated before lines are added.

Detail fields ​

FieldExamplePurpose and impact
Line number10Stable detail reference
Item/serviceMED-INS-100Product or service identity
DescriptionInsulin Pen 5-packPrinted line text
Ordered quantity500Supplier commitment
Purchase UoMCARTONQuantity interpretation
Base quantity2,500 PACKInventory conversion
Unit priceUSD 42.00Commercial value
Discount2%Cost and approval
Tax codeIMPORTTax calculation
Promised date2026-10-02Delivery planning
Warehouse/binDXB-COLD / A-03Put-away proposal
Batch expectedYesReceipt traceability
Quality statusQuarantineRelease control
Cost centreProcurementSpend reporting
Project/WBSHOSP-2026Budget and margin

Line totals should show gross, discount, net, tax, freight allocation, landed cost estimate, received, invoiced, and open quantities. A partial receipt leaves the open quantity visible.

Supplier and budget controls ​

Before approval, OSERP validates supplier active status, tax and bank records, blocked status, duplicate PO, price validity, budget availability, required date, item status, and permission. If the PO is AED 600,000 against a restricted grant, fund and programme dimensions are mandatory.

Commitment reporting shows approved budget, prior commitments, current PO, receipts, invoices, actual cost, and remaining forecast. Cancelling a PO releases its unreceived commitment with reason and approval. Editing price or quantity after approval creates an amendment version.

Currency, tax, and landed cost ​

Store supplier currency, transaction rate, rate date/source, functional value, tax code, freight, insurance, duty, brokerage, and other charges. A 500-carton PO at USD 42 is USD 21,000; at 3.6725, functional value is AED 77,122.50 before other charges.

Landed-cost allocation records component, amount, basis (quantity, weight, value), item/batch, and approval. The final cost flows to inventory or expense according to item policy. Do not change the original PO rate to compensate for payment-date FX.

Approval and amendments ​

Approval may depend on amount, category, fund, project, supplier risk, discount, or currency. The event records reviewer, decision, timestamp, comment, and PO version. A rejected PO returns to draft with reason.

An amendment records old/new value, reason, initiator, impact on budget and supplier commitment, and approval. A material change may require re-quotation. Posted receipts and invoices remain linked to the prior version.

Receipt and quality linkage ​

The goods receipt references PO, supplier, warehouse, delivery note, date, receiver, carrier, and status. Lines record ordered, received, accepted, rejected, damaged, batch/serial, expiry, certificate, bin, and discrepancy. Receiving 480 against 500 creates shortage/open quantity; 20 damaged cartons create claim evidence.

Receipt posting debits inventory, expense, or GRNI and credits receipt accrual. Quality release is a separate event. A quarantined batch cannot be allocated to a sale. Supplier claims reference receipt, photos, quantity, and resolution.

Three-way match and payment ​

Invoice matching compares PO quantity/price, receipt quantity/quality, and supplier invoice amount/tax. A price or quantity variance shows tolerance, value, owner, reason, and approval. It cannot be hidden by changing the receipt.

Once approved, the invoice credits payable and clears GRNI or accrual. Payment proposal uses due date, bank verification, currency, discount, withholding, and cash availability. Failed payments retain bank reason and retry state.

API mapping and practice ​

Use immutable PO ID, company, supplier, warehouse, currency, external reference, lines, and idempotency key. Include source quotation or contract and explicit tax/dimension objects. A timeout retry uses the same key; duplicate creation is not acceptable.

json
{"companyId":"company_uae","supplierId":"supplier_novabio","warehouseId":"warehouse_dxb",
 "currency":"USD","exchangeRate":"3.6725","externalReference":"NB-Q-88210",
 "lines":[{"itemId":"item_med_ins_100","quantity":"500","uom":"CARTON","unitPrice":"42.00","taxCode":"IMPORT"}]}

Practice: create a budget-controlled USD PO, approve a discount exception, receive a shortage and damaged batch, allocate landed cost, match an invoice with a variance, amend the delivery date, pay the supplier, and reconcile commitment to GL. Explain every header/detail field, format, owner, status, permission, tax, FX, stock, journal, API ID, and audit event.

Related: Procure to pay, Inventory field guide, Journal Entry field guide, Advanced GL Mapping, and API cookbook.

Purchase-to-pay implementation worksheet ​

During configuration, have procurement, warehouse, finance, tax, and the budget owner sign the same example. For Demo Retail Group LLC, use a USD import PO for 500 cartons of a batch-managed item and capture the result at each boundary.

BoundaryFields that must be evidencedExpected result
Supplier masterLegal name, tax, bank, currency, risk, blocked stateSupplier is active and payable-safe
RequisitionRequester, need date, item/service, quantity, budget, projectDemand is approved before commitment
PO headerCompany, branch, supplier, currency, Incoterm, warehouse, termsCorrect legal and logistics defaults
PO linesUoM, conversion, price, tax, batch, promised dateQuantity and value are reproducible
ApprovalThreshold, reviewer, decision, version, commentSegregation and exception evidence
ReceiptDelivery note, actual quantity, batch, quality, binStock/GRNI reflects physical receipt
Landed costFreight, duty, insurance, basis, batch allocationInventory cost is explainable
InvoiceSupplier reference, tax, rate, three-way resultAP liability is valid
PaymentBank, due date, withholding, reference, allocationSupplier statement clears
CloseOpen quantity, commitment, GRNI, AP, FX, GLNo unowned balance remains

Three-way-match decision matrix ​

The match engine should display the comparison, not only a pass/fail badge. A quantity shortage with an accepted partial receipt may pass within policy; a price variance may require buyer approval; an invoice for a rejected batch must block regardless of tolerance.

ConditionExampleDefault decisionRequired action
PO = receipt = invoice500 / 500 / 500PassPost AP and clear GRNI
Receipt below PO480 received / 500 orderedPass partialKeep 20 open or cancel with reason
Invoice above receipt500 invoiced / 480 acceptedBlockCorrect invoice or approve exception
Price within toleranceUSD 42.00 vs USD 42.20Warn/pass by policyRecord tolerance and owner
Price above toleranceUSD 42.00 vs USD 46.00BlockAmend PO or approve variance
Quality rejected480 received, 100 rejectedBlock rejected quantityClaim, replace, or disposition
Tax mismatchPO import, invoice domestic VATBlockCorrect tax evidence and code
Duplicate invoiceSame supplier number and dateBlockResolve duplicate before posting
Closed periodInvoice posting date lockedBlockUse permitted date or reopen authority

Landed-cost walkthrough ​

For 500 cartons at USD 42, goods value is USD 21,000. Add freight USD 1,200, insurance USD 180, duty AED 7,900, and brokerage AED 1,100. At USD/AED 3.6725, freight plus insurance is AED 5,066.70 and goods value is AED 77,122.50. Total landed cost before brokerage is AED 90,089.20; including brokerage it is AED 91,189.20. The allocation record must state whether each component is allocated by value, weight, quantity, or a mixed policy, and which lots receive it.

Do not put duty into the supplier unit price merely to make the item cost look complete. The PO price remains the commercial price; landed-cost documents explain additional cost and their posting accounts. If tax is recoverable, keep it separate from inventory cost. If freight is expensed by policy, do not capitalise it. The same numerical total can be wrong if the component policy is wrong.

Amendments, cancellations, and closure ​

An approved PO is a commitment. An amendment to price, quantity, currency, supplier, warehouse, or required date must show old value, new value, reason, initiator, budget effect, receipt effect, and approval route. If receipts exist, the amendment must not retroactively change received history. Cancelling an unreceived line releases commitment and records the supplier communication. Closing a line with open quantity requires a cancellation reason; otherwise the commitment remains misleading.

Refusal and replay tests ​

Test a duplicate supplier reference, inactive supplier, missing tax code, missing project on a restricted fund, over-capacity warehouse, expired batch, receipt above open quantity, invoice above accepted quantity, changed payload with an existing idempotency key, and payment to an unverified bank account. Each refusal must be atomic: no partial stock, commitment, or journal should remain. Save request ID, response, user, timestamp, and audit event for the handover pack.

OSERP™ Atlas · Understand every field. Master every workflow.