The warehouse keys 480 units against a release on Thursday. On Friday a cycle count finds 450. Under evaluated receipt settlement, the supplier was already on its way to being paid for 480, and no invoice ever crossed AP’s desk to catch it.
In most AP processes the supplier’s invoice is the trigger, and the receipt is the check. In the three arrangements here, the receipt or consumption record becomes the trigger. That moves the control point from AP to the dock, the stockroom, and the buyer who maintains the release schedule.
| Arrangement | What triggers payment | Where errors start |
|---|---|---|
| Evaluated receipt settlement (ERS) | Goods receipt against an eligible PO line | Wrong receipt quantity or outdated PO price |
| Consignment | Consumption (or another agreed ownership-transfer event) | Missing or reversed consumption records |
| Blanket orders with scheduled releases | Supplier invoice against a specific release | Billing against the wrong release, rate, or quantity |
Evaluated receipt settlement
With ERS, the supplier agrees that you can settle an eligible delivery from the purchase order and goods receipt. The supplier doesn’t send a separate invoice for that transaction. A wrong receipt can therefore become a wrong payment without AP ever seeing an invoice. SAP’s ERS documentation
Check the receipt before settlement
The supplier agreement and PO line determine whether a delivery qualifies. Before settlement runs, confirm:
- The delivery qualifies under the agreement and the PO line is flagged for ERS.
- The price on the PO is the agreed price for this delivery.
- The warehouse recorded the quantity actually accepted, not the quantity on the packing slip.
- Rejected or disputed quantities are out of the routine settlement path until their owner resolves them.
In SAP S/4HANA Cloud, the documented ERS setup includes the ERS indicator and goods-receipt-based invoice verification on the relevant PO items. SAP also documents credit memos for return deliveries after settlement. Test those cases in your configuration. SAP’s ERS setup guide
Illustrative example: a receipt corrected after settlement
The PO price is $3.10 per unit. The receipt is entered for 480 units and settles at 480 × $3.10 = $1,488.00. A cycle count shows 450 were actually received. The correct settlement is 450 × $3.10 = $1,395.00, and the supplier has been overpaid by $93.00 (30 × $3.10).
The correction should reduce the original settlement, typically through a reversal or credit tied to that receipt, not create a second settlement for 450 that leaves the first one standing. Test that the correction changes the right settlement without paying twice.
ERS test cases
| Test case | What the reviewer should see |
|---|---|
| Partial delivery | Accepted quantity and units still outstanding |
| Price amendment | Approved price and which deliveries it applies to |
| Supplier sends an invoice for an ERS delivery anyway | The related PO and settlement record before any separate bill is approved |
| Return after settlement | Original receipt and the adjustment for the returned quantity |
| Receipt corrected or reprocessed | Evidence the correction changed the right settlement, once |
The third row is a real duplicate-payment risk. Suppliers who are new to ERS, or whose billing system doesn’t know about the arrangement, sometimes keep invoicing. See duplicate payments and vendor master controls.
Give suppliers a way to check what was settled
Agree on the reference the supplier will receive, how they report a quantity or price error, and who responds. Compare each disputed line against the receipt and PO before the next payment run. At close, review any accepted receipt that remains unsettled and any return still waiting on an adjustment; the GR/IR reconciliation guide shows how to assign those differences.
Consigned inventory
The warehouse receives a pallet of consigned stock on Friday. Production uses part of it on Monday. Before paying the supplier, check the agreement for the event that transfers ownership. The receiving date and the settlement date can fall in different periods.
Oracle describes a consignment workflow in which the supplier keeps ownership at receipt and a consumption advice lists transactions for settlement. Check how your ERP records the transfer and which dates your agreement uses. Oracle Fusion Cloud SCM inventory management guide
Roll the consigned stock forward
Keep supplier, item, lot or location, quantity, and date on each record. Reconcile opening consigned stock plus receipts, less consumption and returns, to what remains on hand. Then compare the supplier’s bill with eligible consumption for the period.
Illustrative example. An item settles on consumption at $18 per unit.
| Movement | Units |
|---|---|
| Opening consigned stock | 20 |
| Received this period | 100 |
| Consumed by production | (35) |
| Returned to supplier | (5) |
| Closing consigned stock | 80 |
20 + 100 − 35 − 5 = 80. The settlement for the period is 35 × $18 = $630. The 80 units on hand still belong to the supplier and stay off your balance sheet as owned inventory, assuming the agreement transfers ownership on consumption. If a physical count of consigned stock shows a different number, resolve that before approving settlement.
If a consumption entry was reversed, trace the reversal before approving settlement. At close, give missing consumption records to inventory control and disputed rates to purchasing. AP should be able to see which units the supplier billed and why any balance remains open.
Blanket orders and scheduled releases
A blanket order sets terms for a series of deliveries. A release tells the supplier what to ship now. When an invoice arrives, check it against the specific release and the goods actually accepted. The blanket quantity alone doesn’t tell AP what’s payable.
Reconcile the release at a common cutoff
| Record | What to check |
|---|---|
| Latest approved release | Part, delivery date, unit of measure, quantity authorized |
| Receipts and reversals | Net quantity accepted against that release |
| Prior bills and credits | Quantity already billed after corrections |
| Current invoice | Quantity and price the supplier wants paid now |
Illustrative example. A release calls for 100 units. Receiving has accepted 80. AP has already recorded bills for 60. A new bill arrives for 30.
- Accepted but not yet billed: 80 − 60 = 20
- Billed this time: 30
- Unsupported by receipts: 30 − 20 = 10
Before approving, ask whether a later receipt or correction explains the 10. Keep units still on order (100 − 80 = 20) separate from units received and not yet billed.
Rate changes on blanket orders in NetSuite
A buyer updates the price on a NetSuite blanket purchase order. Then AP receives a bill for a release placed before the change. Oracle documents that changing the blanket rate doesn’t update existing linked purchase orders, while new linked orders use the new rate. Oracle’s blanket purchase order documentation
Illustrative: the old release was placed at $8.00 per unit for 500 units. The blanket rate is later changed to $8.40. The supplier bills the old release at $8.40, or $4,200 against an order value of $4,000. The $200 difference goes to the buyer, who decides whether the new price was meant to apply to that release.
Work the bill this way:
- Identify the released PO and line the supplier billed. Record the approved rate and any later amendment.
- Compare receipts and reversals on that line with quantities already billed. If a shipment covers several releases, confirm which quantity belongs to each.
- Check whether the bill exceeds the quantity supported by receipts or uses a rate not approved for that order.
- Send price differences to the buyer and receipt differences to receiving, with the source records attached.
Price questions on releases are covered in more depth in purchase price variance.
What goes wrong
- Receipt quantity from the packing slip. Under ERS, that number is what gets paid.
- Settlement runs before inspection. Rejected units are settled, then need a credit.
- Supplier invoices an ERS delivery. AP approves it as a normal bill and pays twice.
- Consumption reversed after settlement. Nobody claims the credit back.
- Bill matched to the blanket, not the release. The total quantity looks fine while one release is overbilled.
- Return after settlement with no credit. Track it like any other return; see supplier rebates, returns, and debit memos.
Before you move a supplier onto receipt-based settlement
- Written agreement states which deliveries qualify, the price basis, and the ownership-transfer event
- Receipts are entered from counted, accepted quantities within an agreed time
- Inspection holds keep rejected units out of settlement
- Supplier knows not to invoice ERS deliveries, and AP checks for settlement before approving any bill that arrives
- Receipt corrections and returns adjust the original settlement, once
- Consigned stock is rolled forward and counted each period
- Bills against blanket orders are matched to the specific release and its rate
- Unsettled receipts and pending return adjustments reviewed at close
For a broader view of receipt-heavy AP in plants, see AP automation for manufacturers.