Verdana Procurement · goods receipt
Goods receipt against the purchase order, full or partial
Verdana's goods receipt is the record of what arrived against the purchase order, with quantities, discrepancies, rejections and the reason for each, in full or in part. Your team stops arguing supplier performance from memory and gets an auditable, dated delivery history.
What recording every receipt saves your company
Delivery data that actually exists, instead of a checkbox that says “OK.”
Supplier performance backed by facts
Quantities, discrepancies, rejections and reasons are logged against the PO, so you know how often a supplier missed, how late and why.
Partial receipts without closing the PO
If half the order arrived, you record what came in and the balance stays tracked. Nobody has to keep the shortfall in their head.
Pay only for what arrived
The receipt is what gets matched against the PO and the invoice before payment is approved: an invoice for more than was received does not go through.
What a goods receipt looks like
An abstraction of a receipt against the purchase order and of the supplier's delivery history.
How goods receipt works in Verdana
From purchase order to payment, with the receipt as the record that backs it.
The purchase order sets expectations
Receiving starts from an approved PO: what was ordered, how much and by when.
Purchase orders →Expediting the committed date
Before delivery, Verdana asks the supplier for a committed date and flags it if it slips.
Expediting →Recording what arrived
The warehouse logs what was received and the department confirms the service, in full or in part, with discrepancies, rejections and a reason for each.
What is three-way match →Delivery performance
Verdana compares the current committed date with the actual date; on that basis you can build indicators such as DIFOT.
What is DIFOT →Matching the invoice
The supplier's invoice is matched against the PO and the receipt before it moves to payment.
Invoice capture →Supplier evaluation
Delivery history feeds the supplier's formal evaluation and repurchasing decisions.
Supplier performance evaluation →
Goods receipt in depth
The process in detail, and why it is designed this way.
Most discussions about supplier performance are settled on perception because the data does not exist: everyone knows the supplier “delivers poorly” but not how many times, how late or for what reason. Goods receipt is where that data is generated, and it is lost when the receipt is logged as a simple “OK.”
Verdana records the goods receipt against the purchase order, with quantities received, discrepancies, rejections and the reason for each, and allows partial receipts without closing the order. On that basis it calculates delivery performance by comparing the current committed delivery date with the actual date, and makes it possible to build indicators such as DIFOT, which requires the delivery to be both in full and on time.
That history feeds the supplier's formal evaluation and repurchasing decisions. It also feeds the conversation with the supplier, which stops being a complaint and becomes a series of dated facts.
Frequently asked questions
What teams usually ask when they evaluate how to record goods receipts.
What is a goods receipt in procurement?
It is the record of what actually arrived against the purchase order: quantities received, plus discrepancies and rejections with a reason. It is the basis for three-way match and for measuring supplier delivery performance.
Can you record a partial goods receipt without closing the PO?
Yes. In Verdana you record what arrived and the purchase order stays open with the remaining balance tracked until the rest is received.
How do you measure supplier on-time delivery?
By comparing the current committed delivery date with the actual receipt date. With quantities and dates on record you can build indicators such as DIFOT, which requires each delivery to be both in full and on time.
What happens when goods arrive damaged or defective?
The rejection is recorded against the PO with its reason. It stays in the supplier's history and feeds its evaluation instead of getting lost in an email thread.