AWRA OpsHub Search
Procurement fulfillment

Purchase Orders, Receiving & Matching

Convert approved sourcing decisions into controlled purchase orders, capture supplier acknowledgement, receive goods accurately, handle mismatches, and close the buying cycle with inventory and finance aligned.

This is where procurement becomes operational truth: the order sent to the supplier, the goods received by the warehouse, the differences that need review, and the records finance can trust.

PO command view

Order status and receiving readiness

Matched flow

Issued POs

18

Sent to vendors

Acknowledged

12

Supplier confirmed

Partial receipts

4

Needs review

AWRA procurement purchase order flow screen
Purchase order lifecycle

A PO should carry the sourcing decision forward without losing context.

AWRA purchase orders can inherit approved request details, selected quotation lines, supplier information, delivery expectations, attachments, comments, approval evidence, and budget context. Buyers do not need to recreate the story once sourcing is complete.

The goal is simple: make the purchase order clear enough for the vendor, controlled enough for procurement, visible enough for receiving, and structured enough for finance review.

01

Create PO from award

Convert approved quote lines into a purchase order with supplier, items, quantities, prices, delivery notes, and evidence.

02

Send and track acknowledgement

Keep supplier confirmation, rejection, changes, and expected delivery timing visible to procurement.

03

Prepare receiving

Give warehouse teams the PO context they need before goods arrive: item, quantity, destination, and documentation.

04

Close or escalate

Close clean orders quickly and route partial, late, or mismatched orders for review.

Vendor acknowledgement and purchase order collaboration portal screen
Vendor acknowledgement

Supplier acknowledgement turns a sent PO into a managed commitment.

Sending a purchase order is not the same as knowing the supplier can fulfill it. AWRA helps procurement teams track acknowledgement, expected delivery, supplier comments, shipment updates, and exceptions before the warehouse is surprised.

When vendors respond through a structured portal or buyer-managed status update, the PO record stays current. Buyers can follow up earlier, receiving teams can plan space and staffing, and finance can distinguish open commitments from orders that are ready to move forward.

PO change orders

An issued order changes by revision, not by edit.

Suppliers run short, prices move and delivery dates slip. In AWRA a sent purchase order is never edited in place: the buyer proposes a change to its quantities, prices, lines or delivery date with a reason, and a second person who can approve purchase orders accepts or rejects it. Until then the order stands as it was.

When the change is approved the order moves to its next revision number, the supplier’s earlier acknowledgement is cleared — they accepted the old order, not this one — and, with purchase-order emails switched on, the revised order is sent to them again. The audit log records the old and new totals and the reason.

Two people, always

Whoever proposes a change cannot approve it. The approver sees a line-by-line before and after, and the totals either side.

Never below what arrived

A line cannot be cut below the quantity already received, and a part-received line cannot be removed. A closed, paid or cancelled order cannot be revised.

Increases pass the budget check

Only the increase is new spend, so only the increase is checked against the budget — and refused in block mode unless someone with the override permission gives a reason.

No change applied over another

If the order changed after a revision was proposed, approving it is refused and the change is proposed again against the order as it now is.

Receiving and matching

Receiving should match what was ordered, what arrived, and what needs review.

AWRA supports real-world receiving: full deliveries, partial deliveries, damaged items, quantity differences, substitute items, late shipments, missing documents, and price or tax questions that should not quietly pass into inventory or finance.

Ordered

100 units

The PO says what the supplier committed to deliver.

Received

72 units

Warehouse records what actually arrived and where it was stored.

Mismatch

28 pending

Procurement reviews shortages, backorders, damage, or vendor follow-up.

Inventory updates and closeout

Close procurement only when operational records agree.

A purchase order is not finished just because it was issued. AWRA helps teams decide when stock can be updated, when partial receipts should stay open, when a mismatch needs escalation, and when the PO is ready for finance, reporting, or final closeout.

Inventory update

Post received quantities into the right warehouse or location only when receiving is accepted.

Mismatch handling

Route shortages, overages, damaged goods, wrong items, or missing documents for procurement review.

Finance handoff

Keep PO, receipt, tax, landed cost, and vendor evidence ready for invoice or accounting checks.

Backorder visibility

Track remaining quantities and expected delivery dates without closing the order too early.

Reporting

Expose open POs, received value, delayed suppliers, and mismatch patterns in procurement reports.

Closeout

Close a PO only when order status, receiving, supplier response, and review requirements are complete.

AWRA inventory dashboard after receiving updates AWRA accounting sync context after procurement receiving

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center