MB5S — List of GR/IR Balances
MB5S is used to analyze goods-receipt/invoice-receipt balances for purchasing documents and identify unmatched GR or IR quantities/values. It is most useful when period-end reconciliation or invoice troubleshooting requires proof of open GR/IR positions. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for MB5S — List of GR/IR Balances. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 597 words
Esta página aún no está disponible en español.
Purpose
analyze goods-receipt/invoice-receipt balances for purchasing documents and identify unmatched GR or IR quantities/values. Treat MB5S as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
MB5S is typically used when period-end reconciliation or invoice troubleshooting requires proof of open GR/IR positions. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Run for the required company/plant and period scope.
- Identify aged or material GR/IR differences.
- Drill into PO history to separate timing from true mismatch.
- Correct source GR, invoice or PO data through the proper business transaction.
- Re-run and reconcile the remaining GR/IR balance.
Key data objects
These are the fields and business objects that most often explain the result in MB5S. Record them in support evidence so the next person can reproduce the same outcome.
- purchase order/item — verify the exact value, validity/date context and relationship to the source document.
- goods receipt — verify the exact value, validity/date context and relationship to the source document.
- invoice receipt — verify the exact value, validity/date context and relationship to the source document.
- quantity/value difference — verify the exact value, validity/date context and relationship to the source document.
- company code/plant/date — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the MB5S document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
GR/IR reconciliation remains a major S/4HANA close process; newer Fiori jobs/apps may complement classic MB5S-style analysis. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Posting manual FI entries to the GR/IR account to hide logistics differences. Reconcile the exact business document and date before applying a workaround.
- Comparing values without considering planned delivery costs or reversals. Reconcile the exact business document and date before applying a workaround.
- Treating recent timing differences as permanent exceptions. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the MM/P2P team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mb5sERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.