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

M8 504 means the quantity being invoiced is greater than the goods-receipt or accepted service quantity relevant to the invoice-verification check. SAP support specifically documents the message for partial invoice receipt on service items and for scenarios where GR-based invoice verification is intended to prevent over-invoicing. The check belongs to Logistics Invoice Verification, so it evaluates purchasing history and item settings rather than simply comparing the typed invoice quantity with the original PO quantity.

The supplier may invoice more quantity than has been received or accepted. For service items, the service entry sheet or acceptance quantity may be lower than the invoice quantity. A goods receipt may have been reversed after an earlier invoice. GR-based or service-based invoice verification settings may make the item stricter than users expect. Prior invoices can already have consumed the available received quantity. Unit-of-measure differences can make a legitimate business quantity appear excessive. In automated or cloud invoice processing, message handling may differ from online MIRO depending on configuration.

Review the purchase-order history item by item. Separate goods receipts, reversals, returns, service entry sheets, acceptances and prior invoices. Check whether GR-based invoice verification or service-based invoice verification is active. Compare PO, receipt/service and invoice units of measure. In service procurement, confirm that the service entry sheet is accepted and that the accepted quantity/value matches what is being invoiced. Review the M8 message configuration for online and background processing. If an external invoice platform sends the document, inspect the exact quantity and unit transferred to SAP rather than assuming the supplier PDF values were mapped correctly.

If the invoice is genuinely ahead of receipt or service acceptance, complete the legitimate receipt/acceptance process or reduce the invoice quantity. If a reversal was posted incorrectly, correct the document flow first. If service-based or GR-based invoice verification is not appropriate for the item category, change the process design prospectively with MM and Finance approval. Where the business deliberately wants to block over-invoicing, configure M8 504 with the intended severity through supported message-control configuration. For interfaces, fix quantity or unit mapping and retest both partial and full invoicing.

Changing M8 504 from error to warning is the fastest way to make a blocked invoice post, but it can also allow invoices above accepted quantities and weaken three-way-match control. Another bad workaround is to create a temporary receipt or service acceptance only to satisfy the invoice and reverse it later. That distorts PO history and financial control. The correct response is to reconcile purchasing history and confirm whether the business actually received or accepted the quantity being invoiced.

MM Purchasing and Logistics Invoice Verification own item settings and message control. Service procurement owners are responsible for service entry and acceptance. Warehouse/receiving teams own goods-receipt accuracy. Accounts Payable owns the invoice interpretation and control decision. Integration teams are involved if external invoice systems send wrong quantity or unit data. Because message severity is a financial control, Finance should approve any change from error to warning.

Do not confuse M8 504 with M8 081; both relate invoice and received quantities but can be triggered under different item/control contexts. For service items, do not look only at physical GR documents—service entry and acceptance are central. Check prior invoices and reversals. Verify units of measure. If you change message severity, test MIRO, parked invoices, background processing and external interfaces because the behavior may not be identical across channels.