Purchase Request to Goods Receipt: Keep the Audit Trail

A distributor can know that stock arrived and still be unable to explain why its supplier invoice differs from the purchase order. The missing evidence may be an approval for a higher price, a receiving note for damaged cartons, or a second invoice that references the same delivery. We would design a Philippine procurement and inventory workflow around those questions. Each handoff needs an owner, a dated record, and a clear next action so purchasing, warehouse, and finance can resolve differences before payment or resale.

Follow one order from request to receipt

Imagine a Laguna distributor whose Cavite branch requests 100 cartons of packaging material. The branch requester records the item, quantity, needed date, destination, and reason. An authorized manager checks the request against planned demand and budget before a buyer approaches the vendor. Approval should identify the exact version of the request; a later quantity change should not silently inherit the original sign-off.

The buyer then records the supplier quotation, agreed unit price, delivery date, tax treatment for invoice review, and purchase order reference. A vendor confirmation matters because the requested date and the vendor's promised date can differ. In our sample, the vendor confirms 100 cartons at the agreed price but can initially ship only 70. The order remains open for the balance; it does not become a complete receipt because a delivery truck reached the gate.

On arrival, the receiving clerk counts the goods against the delivery document and records what was actually accepted. Suppose 68 cartons are usable, two are damaged, and 30 have not yet arrived. The receiving record should distinguish those states. Posting all 70 to sellable stock would hide the damage; posting all 100 would create phantom stock. The buyer can then ask the supplier whether replacement, credit, or a second delivery is appropriate, while finance sees the unresolved difference.

Give each role a narrow decision

The requester knows the business need but should not approve their own spend by default. The approver authorizes the commercial commitment within policy. The buyer owns vendor communication and the purchase order. The receiving clerk attests to physical quantity and condition. Finance reviews the supplier bill and proposed payment. Some small companies combine roles; when they do, record the compensating review that checks the same evidence.

Write a short responsibility table before selecting software:

Event	Record to keep	Decision owner
Branch asks for stock	Request, item, quantity, destination, needed date	Requester
Spend is approved	Approved request version and approver	Manager
Order is placed	Quotation, vendor, agreed terms, PO	Buyer
Delivery arrives	Count, condition, delivery proof, receiver	Warehouse
Bill is reviewed	Invoice reference, differences, resolution	Finance

This table is useful even if the team currently runs on email and spreadsheets. It exposes where information disappears. A signed delivery receipt, for example, may prove that packages were handed over but may not prove that all items inside were accepted in good condition.

Investigate differences before they become payables

Three-way comparison of purchase order, accepted receipt, and supplier invoice is a useful control. It is a review method, not a promise that every ERP performs a one-click match. For the sample order, finance should see that an invoice for 100 cartons conflicts with the accepted quantity of 68 and the two damaged cartons. The buyer must obtain a corrected bill, credit, or documented agreement rather than changing the goods receipt to make the numbers align.

Test four exception paths. First, the vendor increases price after the order: who can approve the revised terms, and what happens to the earlier PO? Second, a short shipment arrives: does the remaining quantity stay visible without inflating stock? Third, goods are damaged: who decides whether they are returned, held for inspection, or accepted at a discount? Fourth, the same invoice number is entered twice: what review catches the duplicate before payment? Each test should leave a timestamp and a reason, not merely a revised total.

If a carrier delivers to a branch rather than the central warehouse, specify who confirms receipt at that branch. A transfer from a Laguna depot to a Metro Manila store is a different transaction from a supplier delivery. Mixing the two can make supplier performance and internal shrinkage impossible to separate.

Build a compact audit packet

For every disputed order, we want to retrieve a small packet: the original request, approved changes, supplier quotation, purchase order, vendor confirmation, delivery document, receiving count, damage evidence, invoice, and resolution note. Link the records with stable references. If a buyer forwards a replacement PDF, retain the old version so the reviewer can see what changed. Record who entered each exception, who approved it, and when the decision took effect.

The weekly exception review can ask five questions: Which open orders are past their promised date? Which receipts have not been invoiced? Which invoices exceed accepted quantity or agreed price? Which damaged items are still awaiting disposition? Which bills repeat a vendor invoice reference? These are operational questions, not vanity dashboard metrics. Assign an owner and due date to each open difference.

Evaluate software with the sample order

ERPat's public module directory describes Procurement from purchase requests and vendor management through approvals and receiving, alongside Inventory, Warehouse, and Finance. Use that scope to frame a demonstration, then verify the exact behavior in the deployment offered to you. Ask the presenter to enter the 100-carton request, receive only the acceptable 68, record the two damaged cartons, leave the remainder open, and explain what finance sees when the vendor bills 100.

Bring your own approval limits, item naming rules, and delivery documents to the demo. A convincing result is a traceable explanation of the difference, plus an authorized correction path that keeps physical and financial records consistent. If you want help mapping the process and testing a system against it, explore our warehouse and logistics solutions. We can start with the order that currently takes your team longest to reconcile.