M8 081 — M8 081 — Quantity Invoiced Greater Than Goods Receipt Quantity

M8 081 is raised when the invoice quantity is greater than the goods-receipt quantity available for invoice verification under the current PO/item control. It is particularly relevant when GR-based invoice verification is active because SAP expects invoicing to follow received quantities. The message can be configured with different severity depending on the system and process. The key point is that SAP is comparing purchasing history, not just the number visible on the current invoice screen. Reversals, returns, earlier invoices and the GR/IR setup all influence the result.

The supplier may invoice more than has been received, or a goods receipt may not yet have been posted. A previous GR may have been reversed or returned, reducing the eligible quantity. The PO may have GR-based invoice verification enabled even though the business process expects invoicing before receipt. Multiple invoices can consume the available received quantity. Unit-of-measure differences can also make the invoiced quantity appear excessive. In special processes such as customs or import invoicing, the standard GR/IV control may not match the intended design, causing M8 081 even though the business expects a different sequence.

Open the purchase order and review the full PO history for the affected item. Separate goods receipts, reversals, returns and invoice documents and calculate the effective received and invoiced quantities. Check whether GR-based invoice verification is active on the PO item. Compare the invoice unit of measure with the PO and receipt units. Review M8 message configuration to see whether 081 is warning or error in the relevant environment. If the issue is specific to a Fiori or localized invoice process, confirm whether the process has additional restrictions. Do not rely solely on the current GR quantity field without understanding historical reversals.

If the invoice is premature, post the correct goods receipt first or reduce the invoice quantity according to business policy. If a GR was reversed in error, correct the logistics document flow rather than weakening invoice checks. If GR-based invoice verification is not appropriate for the procurement scenario, change the PO/process design prospectively with MM and Finance approval. For import/customs or other special cases, follow the supported process configuration rather than using a generic workaround. If message severity is intentionally changed, document the control decision and test the effect on both manual and automated supplier invoices.

The easy workaround is to change M8 081 from error to warning so the invoice posts. That can allow invoices for quantities not yet received and weaken three-way-match control. Another workaround is to post a temporary goods receipt only to satisfy the invoice, then reverse it later; this distorts stock and GR/IR history. The safer approach is to determine whether the physical receipt, purchasing history or process configuration is wrong and correct that source. Message severity should reflect a deliberate control decision, not an incident bypass.

MM Purchasing and Logistics Invoice Verification own the PO and GR-based invoice-verification settings. Warehouse/receiving teams own the accuracy and timing of goods receipts. Accounts Payable owns the invoice quantity and supplier-document interpretation. Finance controls should be involved before changing message severity. Integration teams become relevant when invoices or receipts arrive through external systems and quantities or units are mapped incorrectly. ABAP is rarely needed unless custom code changes PO history interpretation or invoice quantities.

Do not compare invoice quantity only with the latest GR document; use net PO history after reversals and returns. Check units of measure carefully. Do not assume the message severity is identical across systems or processing channels. If multiple invoices exist, include prior invoiced quantity in the analysis. For special procurement and import scenarios, validate whether GR-based invoice verification is intended. Finally, after resolving the error, reconcile GR/IR and PO history so the fix does not leave a hidden quantity imbalance.