MRRL — Evaluated Receipt Settlement
MRRL is used to create supplier invoices automatically from eligible goods receipts under Evaluated Receipt Settlement. It is most useful when agreed suppliers and POs allow self-billing based on receipt data instead of a supplier invoice. 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 MRRL — Evaluated Receipt Settlement — 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· 579 words
Esta página aún no está disponible en español.
Purpose
create supplier invoices automatically from eligible goods receipts under Evaluated Receipt Settlement. The key is to treat MRRL 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
MRRL is typically used when agreed suppliers and POs allow self-billing based on receipt data instead of a supplier invoice. 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
- Confirm vendor and PO are configured for ERS.
- Run a test/selection and review eligible receipts.
- Investigate missing receipts before changing master data.
- Execute settlement for the approved population.
- Reconcile generated invoices with PO history and vendor account.
Key data objects
These fields and business objects usually explain the result in MRRL. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- vendor — verify the exact value, status, organizational context and date relevance.
- PO/GR — verify the exact value, status, organizational context and date relevance.
- ERS indicators — verify the exact value, status, organizational context and date relevance.
- settlement date — verify the exact value, status, organizational context and date relevance.
- generated invoice 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
MRRL remains supported for ERS in S/4HANA and can be highly automated when purchasing master data is governed correctly. 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
- Using ERS where supplier agreements do not permit self-billing. Check the complete document flow before applying a workaround.
- Changing ERS flags after receipts without understanding eligibility impact. Check the complete document flow before applying a workaround.
- Assuming 'No documents selected' means the program failed rather than selection/master data excluding them. 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/mrrlERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.