Short Delivery Penalties: The AP Control Indian Finance Teams Forget to Enforce
When a vendor delivers 180 units against a 200-unit PO and invoices for 200, two things happen: you overpay, and the shortfall penalty clause in the contract goes unenforced.
Verse HQ
A vendor is contracted to deliver 200 units per shipment at ₹450 each. The contract specifies a 2% penalty on the invoice value for any delivery below 95% of the ordered quantity. On March 15th, the warehouse GRN records 178 units received. The vendor invoices for 200 units at ₹450 — ₹90,000. The AP team approves the ₹90,000 invoice because the PO is for 200 units and the invoice matches the PO. Nobody calculates the overpayment for the 22 undelivered units. Nobody applies the 2% shortfall penalty. Both failures happen at the same moment, for the same reason: the invoice validation did not include the GRN.
Two Failures in One Transaction
The quantity overpayment: 22 undelivered units at ₹450 each is ₹9,900. If this vendor delivers short every month, that is ₹1.18 lakh per year paid for goods never received. The AP team would recover this if they compared the invoice quantity to the GRN quantity before approving payment — but the GRN is in a different system (often Tally's inventory module, or a separate warehouse log), and the invoice approval happens without that data in view.
The penalty non-enforcement: 178/200 = 89% delivery, which is below the 95% contractual threshold. The contract says a 2% penalty applies. On a ₹90,000 invoice, that is ₹1,800. It sounds small. This vendor delivers short 9 months out of 12. The annual unclaimed penalty is ₹16,200. Across 20 vendors with similar SLA clauses, the cumulative unclaimed penalties often run ₹2–₹5 lakh per year — not because the procurement team forgot to include penalty clauses, but because no one in AP is reading them.
Why This Happens in Practice
The person who approves the invoice is the AP team member or finance manager. They know what the PO says. They typically do not know what the contract says about penalty clauses — that knowledge sits with the procurement team who negotiated it.
The GRN confirmation comes from the warehouse team, through whatever channel they use to communicate — WhatsApp message, a sheet in the ERP inventory module, or a physical document. At invoice processing time, the AP team member may not have the GRN in front of them. If the invoice arrives before the GRN is formally entered, the match cannot happen.
This is the three-way matching gap. If the invoice is matched only against the PO (two-way matching), both the quantity overpayment and the penalty calculation are invisible. The third document — the GRN — is what activates the short-delivery check.
What Penalty Enforcement Actually Requires
Enforcing a short-delivery penalty at invoice processing time requires three things: the GRN quantity (from the warehouse confirmation), the contractual threshold (from the procurement contract, typically 90–95% of ordered quantity), and the penalty rate (from the penalty clause in the contract). The calculation is: if GRN quantity ÷ PO quantity is below the threshold, apply the penalty rate to the invoice value and generate a credit note request.
None of these calculations are complex. The data exists — in the GRN, in the PO, and in the contract. The gap is that these three documents are never in the same place at the same time during invoice approval.
The practical starting point: identify which vendor contracts have delivery SLA clauses, map those clauses to the vendor master, and run a historical GRN analysis to see which vendors have been delivering below threshold. The first analysis typically produces a recoverable amount that justifies building the enforcement process. Most finance teams find ₹2–₹8 lakh in historical unclaimed penalties in the first 12 months they look.
