Purchase order process in ERP: from request to receipt, invoice, and payment

What this guide helps you decide

This guide helps purchasing, warehouse, and finance teams define a practical purchase-to-pay workflow, including data ownership, approvals, partial transactions, matching, exceptions, and performance measures.

Weak purchasing processes often appear as price variance, unauthorized commitments, late receipts, duplicate invoices, inaccurate inventory, unexplained accruals, and supplier disputes. The solution requires connected controls rather than a more attractive purchase order form.

Capture and qualify demand

Demand may originate from replenishment, production, a project, maintenance, or an approved request. The system should preserve the source so buyers understand why an item is needed and can detect duplicate or conflicting supply.

Define requester, required date, location, item or service specification, quantity, unit, project or cost dimension, suggested supplier, and supporting evidence. Validate availability and open supply before creating a new commitment.

Practical checks

• Retain the demand source and requester
• Check stock and existing orders
• Validate unit and delivery location
• Require justification for non-catalogue requests

Control supplier and price selection

Approved supplier status, contracts, price lists, currencies, lead times, minimum quantities, units, tax treatment, and quality history should inform selection. Buyers need effective dates and comparison context.

Document when competitive quotations are required and when sole-source justification is acceptable. Changes to supplier bank details or sensitive commercial terms require stronger authorization than ordinary descriptive updates.

Practical checks

• Use approved and active supplier records
• Validate effective price and currency
• Record quotation or source justification
• Protect sensitive supplier changes

Design purchase order approval

Approval should reflect value, category, project, risk, and exception - not merely route every order to the same manager. Define how changes after approval are handled and which changes require reapproval.

The approver needs sufficient context: demand source, budget, price variance, supplier, prior spend, attachments, and delivery impact. Preserve decision time, comments, delegate, and rejection reason.

Practical checks

• Set threshold and exception rules
• Require reapproval for material changes
• Support delegation and escalation
• Retain complete approval evidence

Receive goods and services accurately

Receiving should identify order line, quantity, unit, warehouse, location, lot or serial information, damage, quality status, and receiving date. Partial and over receipts require explicit tolerance rules.

Separate physical arrival from accepted inventory when inspection is required. For services, define objective evidence of completion rather than using a goods receipt that provides no meaningful confirmation.

Practical checks

• Receive against an authorized order
• Control over, short, and duplicate receipts
• Record quality hold and damage
• Support partial and final receipt status

Match invoice to commitment and receipt

Invoice matching compares supplier invoice details with the purchase order and receipt. Tolerances for quantity, price, freight, tax, and rounding should route meaningful exceptions without blocking harmless differences.

Prevent duplicate invoices using supplier, invoice number, date, amount, and supporting attributes. Define how credit notes, prepayments, non-PO invoices, and disputed charges are controlled.

Practical checks

• Configure meaningful matching tolerances
• Detect duplicate supplier invoices
• Route exceptions to named owners
• Preserve dispute and resolution history

Allocate landed cost and update value

Freight, duty, brokerage, insurance, and other acquisition costs may need allocation to received inventory. Choose a defensible basis such as quantity, weight, volume, value, or a category-specific rule.

Preserve provisional and final cost treatment where invoices arrive later. Reconcile inventory valuation and cost of goods sold effects, particularly when goods have already been issued or sold.

Practical checks

• Define eligible landed-cost categories
• Choose and document allocation bases
• Handle late cost adjustments
• Trace value changes to source charges

Settle payment with appropriate controls

Approved liabilities should flow into payment selection using due date, terms, discount opportunity, hold status, cash priority, and bank controls. Separate preparation, approval, release, and reconciliation where risk requires it.

Supplier master changes, payment file generation, and bank confirmation are high-risk points. Use least privilege, dual control where appropriate, and exception reporting.

Practical checks

• Respect holds and payment terms
• Separate payment preparation and release
• Verify sensitive supplier changes
• Reconcile payment to bank and ledger

Measure purchasing performance

Useful measures include requisition-to-order time, approval delay, price variance, supplier on-time delivery, receipt accuracy, match exception rate, expedite cost, and spend outside approved channels.

Segment by supplier, buyer, category, location, and cause. Pair speed metrics with control and quality so teams are not rewarded for processing quickly while creating downstream rework.

Practical checks

• Publish formula and owner for every KPI
• Track exception cause and resolution time
• Review supplier and category trends
• Connect measures to corrective actions

What is the purchase order process in ERP?

The ERP purchase order process begins when a valid need is approved and ends when the supplier obligation is settled and the accounting result can be traced. The operational chain normally includes request, approval, purchase order, supplier acknowledgement, receipt, invoice matching, payment, and reconciliation. Each stage changes a different business fact, so combining them into one editable status weakens control.

A purchase order records an authorized commitment. It is not proof that goods arrived, that a service was accepted, or that an invoice is correct. Those events require their own dates, quantities, owners, evidence, and correction paths.

Map the high-level ERP buying process

Keep receipts, invoices, and payments separate

One order may arrive in several shipments. A shipment may contain damaged items, a substituted product, an over-delivery, or a quantity that belongs at another warehouse. The ERP should preserve ordered, received, accepted, returned, invoiced, and remaining quantities independently. Closing the order should require an explicit decision when an open balance will never arrive.

Services need a receipt concept as well. The responsible person may confirm a milestone, period, or deliverable before Accounts Payable accepts the invoice. This prevents staff from creating a fictional goods receipt merely to release payment.

Resolve invoice matching exceptions without rewriting history

Three-way matching compares the supplier invoice with the authorized order and accepted receipt. Differences in quantity, price, tax, freight, currency, or terms should create a visible exception. A tolerance may automate a low-risk decision, but the tolerance needs an owner, rationale, and report. Repeated small variances can expose a supplier or master-data problem even when each invoice falls below the approval threshold.

• Detect duplicate supplier invoice numbers and near-duplicate amounts.
• Block payment when invoiced quantity exceeds accepted quantity.
• Route price and tax differences to the appropriate owner.
• Preserve credit notes, prepayments, partial payments, and reversals.
• Record why an exception was accepted instead of editing the original order.

Connect payment posting to the original purchasing decision

The query "payment posting to ERP" points to a downstream concern that many purchasing diagrams omit. Posting should reduce the approved supplier liability, update the supplier account, create the appropriate bank and ledger entries, and retain the allocation to one or more invoices. A rejected or reversed payment must reopen the correct balance without duplicating expense or inventory value.

Finance should be able to move from a payment to the invoice, receipt, purchase order, approval, and original request. Purchasing should be able to see whether an order is committed, received, invoiced, paid, returned, or still disputed without relying on a separate spreadsheet.

Acceptance scenarios for purchase-to-pay

Test a normal stock purchase first, then introduce difficult conditions: partial receipt, rejected quantity, changed price, cancelled remainder, invoice before receipt, service acceptance, credit note, and payment reversal. Verify inventory, commitment, payable, tax, landed cost, journal entry, supplier balance, and status after each step.

Permission tests should confirm that changing supplier, quantity, price, bank details, or approval-relevant fields cannot bypass authorization. A material change can return the document to approval while retaining the earlier version and decision.

How Simor ERP supports the buying process

Simor ERP connects suppliers, purchase orders, purchase receipts, inventory, landed costs, supplier invoices, payments, journal entries, and financial reporting. A live product review can follow a partial receipt and invoice variance through the connected records so purchasing, warehouse, and finance stakeholders see the same transaction from their own responsibilities.

Simor Soft can configure warehouses, locations, units, price lists, tax, roles, and approval responsibility, then customize forms, fields, reports, integrations, or exception routes where the organization has a valid requirement. The QA review can include duplicate invoices, unauthorized changes, excess receipts, returns, period locks, and reconciliation to the general ledger.

Ownership continues after posting. Define who may reopen, cancel, or correct each purchasing document and how a genuine error is reversed after settlement or period close without erasing the original evidence.

Related erp guides