## TL;DR
MIRO will not let the invoiced quantity exceed the quantity covered by goods receipts on the purchase order, and subcontracting POs make this easy to trip because the receipt quantity, the component consumption and the invoiced quantity are three different numbers that must line up. Open the PO history and compare ordered, delivered and already-invoiced quantities line by line. Usually the invoice covers units whose goods receipt is still parked in the warehouse, was posted to the wrong PO item, or was partially reversed. Either reduce the invoice to the received quantity and process the remainder when the receipt posts, or correct the missing receipt first if the goods physically arrived. For subcontracting, also check the component issue: an unconsumed component stock position can block the receipt quantity the invoice expects.

```text
SAP invoice verification "quantity invoiced is greater than the goods receipt quantity" error on the subcontracting PO
```

## Use this when
- Invoice verification in MIRO stops with quantity invoiced greater than goods receipt quantity on a subcontracting purchase order.
- The supplier invoiced the full order while deliveries arrived in partial lots.
- PO history shows receipts, reversals or component issues that do not match the invoice story.

## Not for this skill when
- The block is a price or amount tolerance, not quantity. Work the price variance path instead.
- The goods genuinely never arrived and the invoice is wrong. Reject the invoice to the vendor rather than adjusting receipts.

## Steps
1. Display the PO history for the item and list ordered, goods receipt, reversal and already invoiced quantities in posting order. Verify: the quantity waterfall is clear and the uncovered invoiced amount is quantified
2. Check subcontracting component postings for the same period: components issued, consumed and returned against the receipt. Verify: component consumption agrees with the finished quantity received, or the gap is named
3. Confirm physically with the warehouse or subcontractor which quantity was actually delivered and accepted for this invoice. Verify: the delivered quantity is confirmed from goods-in evidence, not the invoice alone
4. Choose the correction: post the missing goods receipt if goods arrived, or reduce the MIRO invoice quantity to the received quantity and park the balance. Verify: invoice quantity no longer exceeds receipt quantity in the system
5. Complete invoice verification, check the PO history updates, and confirm the GR/IR account for the item reflects only the true open quantity. Verify: the invoice posts and GR/IR shows the correct residual, if any

## Variant phrasings
### SAP quantity invoiced greater than goods receipt quantity subcontracting
The verbatim MIRO quantity error.
### MIRO invoice quantity exceeds GR quantity PO history fix
The PO-history diagnostic phrasing.
### subcontracting PO component consumption invoice verification SAP
For the component side of the same failure.

Compatibility: SAP ECC 6.0 and S/4HANA materials management invoice verification (MIRO), subcontracting item category L purchase orders and movement types 101, 102, 543 and 545.

## Why it happens
The three-way match exists to stop paying for goods never received, so the invoiced quantity is capped by accepted receipts. Subcontracting adds a twist: the receipt of finished goods consumes components, and any break in that chain - late warehouse posting, receipt against the wrong item, a reversed movement nobody re-posted - leaves the invoice pointing at quantity the system believes never arrived, even when pallets are physically sitting at the subcontractor or the dock.

## Edge cases / pitfalls
- Returns and quality rejections reduce the accepted receipt quantity after the invoice was printed; expect this error and split the invoice.
- Free-of-charge or sample lines with quantity but zero price still consume receipt quantity in the match.
- If receipts post in a different unit of measure than the invoice, a conversion rounding can show a small false excess; check units before escalating.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vt8bEOR2CrdRTvSItKCBVQ