Paid a Vendor for Goods Never Received — How It Happens and How to Prevent It

Q: How does paying for goods not received typically happen in organisations?

It happens when the accounts payable function processes vendor invoices without verifying that the goods were actually received. In the most common scenario, the vendor sends an invoice referencing a valid purchase order. Accounts payable matches the invoice to the PO — the amounts match, the vendor is correct, the PO is approved. They process the payment. But nobody checked whether the goods were actually delivered. There may be no goods receipt note in the system, or the GRN exists but was created without physical verification. In some cases, the goods were partially delivered but the invoice was for the full PO quantity. Without a mandatory GRN step between PO and payment, the invoice-to-PO match creates a false sense of verification.

Q: What is three-way matching and why does it prevent overpayment?

Three-way matching compares three documents before a payment is processed: the purchase order (what was ordered), the goods receipt note (what was actually received), and the vendor's invoice (what the vendor is charging). A payment is only authorised when all three documents agree — or when any discrepancies have been explicitly reviewed and resolved. Without three-way matching, organisations typically do two-way matching (PO versus invoice) which only confirms that the invoice matches what was ordered — not what was received. The GRN is the critical third document because it represents physical reality. If the PO says 100 units, the invoice says 100 units, but only 80 were received, three-way matching catches the 20-unit discrepancy before payment.

Q: What should I do immediately after discovering payment was made for undelivered goods?

First, gather all documentation: the purchase order, any delivery challans or transport receipts, the vendor invoice, payment records, and any internal correspondence about the delivery. Second, send a formal written demand to the vendor — not an email or phone call, but a letter on company letterhead — requesting either delivery of the goods or refund of the payment within a specified period (typically 15 to 30 days). Third, check internally whether this is an isolated incident or a pattern: pull all transactions with this vendor and cross-reference invoices against GRNs. Fourth, assess the internal control failure — was there a GRN process that was bypassed, or is there no GRN process at all? The answer determines whether this is a process violation or a process gap.

Q: How does gate entry inspection fit into payment fraud prevention?

Gate entry is the physical verification point — it confirms that goods physically arrived at the organisation's premises. When a vendor's delivery vehicle arrives, the gate entry process records what was delivered: the vendor, the PO reference, the items, and the quantities. This happens before the goods move to the warehouse and before any GRN is created. Gate entry inspection can include quality checks — verifying that the items match the PO specification, checking for damage, and confirming quantities against the delivery challan. Without gate entry, a GRN can be created based solely on the vendor's delivery challan or invoice, without independent verification that the goods actually arrived. Gate entry adds a physical control layer that paper-based processes cannot provide.

Q: What is a vendor debit note and how does it help recover overpayments?

A vendor debit note is a formal document issued by the buyer to the vendor, debiting the vendor's account for a specific amount. It is used when the buyer has overpaid — whether due to goods not received, goods returned, price discrepancies, or quality issues. The debit note creates a receivable from the vendor that can be adjusted against future payments or collected directly. In a structured system, the debit note references the original PO and the specific discrepancy — for example, 20 units invoiced but not received on PO number X. The debit note flows through to accounting, creating the appropriate ledger entries and adjusting the vendor balance. Without a formal debit note process, overpayment recovery depends on informal follow-up, which vendors can dispute or ignore.

Published: April 14, 2026

The reconciliation reveals a discrepancy. A vendor invoice for twelve lakh rupees was processed and paid three months ago. The purchase order exists. The invoice references a valid PO number. The amounts match. But the goods were never delivered. The warehouse has no record of receipt. The vendor, when contacted, claims delivery was made and provides a delivery challan — but nobody at the organisation signed for it, and there is no entry in the gate register.

In another case, the goods were partially delivered — 60 units out of 100 ordered — but the invoice was for the full quantity. The payment was processed for 100 units. Nobody noticed the shortfall because there was no formal goods receipt process that compared delivered quantities against invoiced quantities.

These are not hypothetical scenarios. They are among the most common procurement failures in organisations that lack a structured receiving process. The money is gone. Recovery is difficult, time-consuming, and uncertain.

1. What Happened

The payment was made because the accounts payable process relied on matching the vendor's invoice against the purchase order — a two-way match. The logic seems sound: the PO was approved, the invoice references the PO, the amounts agree, therefore the payment is valid.

The problem is that a two-way match only confirms that the invoice matches what was ordered. It does not confirm what was received. The critical missing document is the Goods Receipt Note (GRN) — the record of what physically arrived at the organisation's premises, inspected and counted by someone independent of both the ordering and paying functions.

Without a GRN in the process, several failure scenarios become possible:

Complete non-delivery: The vendor sends an invoice without delivering goods. The invoice matches the PO. Payment is processed.
Partial delivery, full invoice: The vendor delivers 60 units but invoices for 100. Nobody records the actual received quantity. Payment is for 100.
Duplicate invoicing: The vendor sends two invoices for the same delivery. Without GRN quantities to reconcile against, both invoices are paid.
Quality shortfall: Goods arrive but are defective or do not match specifications. Without an inspection step, they are accepted and paid for.

2. Why It Happened

The root cause is the absence of segregation between three functions that should be independent: ordering (procurement), receiving (warehouse/operations), and paying (accounts payable). When any two of these are conflated or when one is missing, the control breaks down.

No mandatory GRN process. Many organisations treat goods receipt as informal — someone in the warehouse acknowledges delivery verbally, or the vendor's delivery challan is treated as proof of receipt. There is no formal GRN document that is created, reviewed, and matched against the invoice before payment.

No gate entry inspection. Goods arrive at the premises without a structured gate entry process. There is no independent verification at the point of physical entry — no recording of what arrived, in what quantity, and in what condition.

No three-way matching. Accounts payable matches invoices against POs (two-way) rather than against both POs and GRNs (three-way). The GRN is the document that represents physical reality. Without it in the matching process, the organisation is paying based on promises (PO) and claims (invoice), not on verified receipts.

No separation between ordering and receiving. In some cases, the same person who ordered the goods also confirms receipt. There is no independent verification. If that person colludes with the vendor — or simply makes an error — there is no second check.

3. What to Do Now

If you have discovered that payment was made for goods not received, the immediate steps are:

Gather documentation. Collect the purchase order, any delivery challans or transport receipts, the vendor invoice, the payment record (bank statement, cheque copy, or NEFT reference), and any internal communication about the delivery.
Send a formal demand to the vendor. Issue a written demand on company letterhead — not an email — requesting either delivery of the goods or a full refund within a specified period (15 to 30 days). Include copies of the PO, invoice, and payment proof. If the vendor claims delivery was made, request their proof — signed delivery challan, transporter receipt, or gate entry acknowledgement.
Check for a pattern. Pull all transactions with this vendor over the past 12 to 24 months. For each, verify whether a GRN exists and whether the GRN quantities match the invoiced quantities. If overpayments are found on multiple transactions, the issue is systemic — not a one-time error.
Assess the internal control failure. Was there a GRN process that was bypassed, or does no GRN process exist? Was the payment approved by someone who could have verified receipt? The answer determines the corrective action.
Issue a vendor debit note. A formal vendor debit note creates a documented receivable from the vendor. This is stronger than an informal follow-up — it is an accounting document that adjusts the vendor's balance and can be set off against future payments.

4. How to Prevent Recurrence

Prevention requires inserting physical verification controls between the purchase order and the payment — and making those controls mandatory, not optional.

Mandatory GRN before payment processing

The most fundamental control is requiring a goods receipt note before any invoice can be processed for payment. The GRN records what was actually received — item, quantity, condition — and is created by someone in the receiving function, independent of procurement and accounts payable. Without a posted GRN, the invoice cannot progress to payment.

Gate entry inspection

A gate entry process adds a physical verification layer at the point of delivery. When goods arrive, the gate entry records the vendor, the PO reference, the items, and the quantities — before the goods move to the warehouse. This creates an independent record of what physically entered the premises. Gate entry can include quality inspection — checking that items match PO specifications, identifying damage, and flagging discrepancies against the delivery challan.

Three-way matching

Three-way matching compares three documents: the purchase order (what was ordered), the GRN (what was received), and the vendor's invoice (what the vendor charges). Payment is authorised only when all three agree — or when discrepancies have been explicitly reviewed and resolved. This eliminates the scenario where an invoice is paid based solely on matching the PO, without confirming receipt.

Mismatch resolution before posting

When mismatches are detected — quantity differences between PO and GRN, price differences between PO and invoice, or GST differences — they must be resolved before the GRN can be posted. Resolution options include accepting the vendor's figures, disputing them, or processing a partial acceptance. Until the mismatch is resolved, the transaction is blocked from reaching the books. This prevents incorrect amounts from flowing to accounts payable.

Over-receipt guards

The system should enforce limits on how much can be received against a PO line. If the PO says 100 units, the total received across all GRNs for that line should not exceed the ordered quantity (or a configurable tolerance). This prevents scenarios where a vendor delivers — and invoices for — more than was ordered, and the excess is paid for without question.

Vendor debit notes for recovery

When overpayments are identified, a formal debit note process creates the accounting entries to recover the amount. The debit note references the original PO and the specific discrepancy, adjusts the vendor balance, and flows through to accounting. This is more effective than informal recovery attempts because it creates a documented, auditable trail.

Every organisation that pays for goods not received has the same structural gap: the payment was authorised without independent confirmation that the goods arrived. The fix is not better people or more careful review — it is a mandatory step in the process that physically cannot be skipped. When a GRN is required before payment, and the GRN requires physical verification at gate entry, the gap between "ordered" and "received" becomes visible and auditable.

5. Frequently Asked Questions

How does paying for goods not received typically happen in organisations?

It happens when accounts payable processes invoices by matching them against purchase orders (two-way match) without verifying actual receipt. The invoice references a valid PO, amounts match, so payment is processed. But nobody checked whether goods were delivered. Without a mandatory GRN step between PO and payment, the PO-to-invoice match creates a false sense of verification.

What is three-way matching and why does it prevent overpayment?

Three-way matching compares the PO (what was ordered), GRN (what was received), and invoice (what the vendor charges). Payment is authorised only when all three agree or discrepancies are explicitly resolved. Without it, organisations do two-way matching (PO vs invoice) which confirms what was ordered, not what was received. The GRN represents physical reality.

What should I do immediately after discovering payment was made for undelivered goods?

Gather all documentation (PO, challans, invoice, payment records). Send a formal written demand to the vendor requesting delivery or refund within 15 to 30 days. Check for a pattern by pulling all transactions with this vendor. Assess whether a GRN process was bypassed or does not exist. Issue a vendor debit note to create a formal receivable.

How does gate entry inspection fit into payment fraud prevention?

Gate entry is the physical verification point confirming goods arrived at the premises. It records the vendor, PO reference, items, and quantities before goods move to the warehouse and before any GRN is created. It can include quality checks and specification verification. Without gate entry, a GRN can be created based solely on the vendor's challan without independent physical verification.

What is a vendor debit note and how does it help recover overpayments?

A vendor debit note is a formal document debiting the vendor's account for a specific amount — overpayment, goods not received, returns, or quality issues. It creates a receivable that can be adjusted against future payments. The debit note references the original PO and discrepancy, flows through to accounting, and creates an auditable trail. Without it, recovery depends on informal follow-up that vendors can dispute or ignore.

Invoice Matching Goods Receipt Gate Entry & Inspection Vendor Debit Notes

Close the Gap Between Ordering and Paying

If payments are being made without verifying receipt of goods, share a brief overview and we will evaluate how three-way matching and GRN controls apply to your procurement process.

Book a Consultation