MR8M — Cancel Invoice Document
MR8M is used to cancel a Logistics Invoice Verification document and generate the corresponding reversal effects. It is most useful when an MIRO invoice was posted incorrectly and must be reversed through the proper MM/FI document chain. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains MR8M — Cancel Invoice Document — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 592 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
cancel a Logistics Invoice Verification document and generate the corresponding reversal effects. The key is to treat MR8M as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
MR8M is typically used when an MIRO invoice was posted incorrectly and must be reversed through the proper MM/FI document chain. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Display the invoice in MIR4 first and understand PO history and FI document.
- Confirm it is legally/accounting-wise permissible to reverse.
- Choose reversal reason and date in the correct open period.
- Post the cancellation and capture MM/FI reversal documents.
- Verify PO history and vendor open items afterward.
Key data objects
These fields and business objects usually explain the result in MR8M. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- invoice document/year — verify the exact value, status, organizational context and date relevance.
- reversal reason — verify the exact value, status, organizational context and date relevance.
- posting date — verify the exact value, status, organizational context and date relevance.
- follow-on/clearing status — verify the exact value, status, organizational context and date relevance.
- reversal documents — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
MR8M remains standard in S/4HANA Logistics Invoice Verification, with FI and PO history integration still critical. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Reversing after the invoice has downstream clearing without following the correct sequence. Check the complete document flow before applying a workaround.
- Using a credit memo as a shortcut when formal reversal is required, or vice versa. Check the complete document flow before applying a workaround.
- Choosing a reversal date that distorts a closed-period reconciliation. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with MM/P2P depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mr8mERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.