MB5L — Stock Value vs G/L Balance Comparison
MB5L compares the material stock value calculated from MM valuation data against the balance of the corresponding G/L stock account for a given plant, valuation area and key date. It is a read-only reconciliation report used at period close to detect mismatches between inventory accounting and the general ledger, not a posting transaction and not the tool that explains why a difference exists.
This page covers what MB5L actually reports, when a consultant runs it in the period-close cycle, and the real diagnostic order for chasing a stock-to-GL difference. It also covers which tables the comparison draws from and how the S/4HANA universal journal changes the underlying data model without changing the transaction's purpose.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,008 words
Purpose
MB5L lists, per plant and valuation area, the stock value that MM calculates from material valuation data alongside the balance of the G/L account that inventory postings are supposed to hit, and shows the difference. The structural fact that causes most confusion: MB5L is purely a comparison report. It does not post, correct, or explain a discrepancy - it only surfaces that one exists as of the key date entered. Consultants who run it expecting an audit trail of what caused the gap are disappointed; the actual root-cause work happens in separate transactions against movement history and FI documents. MB5L is the alarm, not the investigation.
When it is used
MB5L is run in the period-end closing cycle, typically before the material ledger or accounting period is closed, when finance needs assurance that the inventory G/L account matches what MM thinks stock is worth. It is also reached for during cutover reconciliation on go-live weekends, and whenever finance raises a balance sheet variance on a raw material or trading goods account. It is not used for day-to-day stock checking - that is MB52 or the stock overview app - MB5L is specifically the MM-to-FI comparison, so it gets pulled out when someone asks 'why doesn't the ledger match the warehouse'.
How to use it in practice
- Enter company code, plant or valuation area, and the key date to compare as of.
- Restrict optionally by material, valuation class, or specific G/L account to narrow the run.
- Execute the report and review the list showing MM stock value, G/L balance, and the calculated difference per account.
- Drill into any nonzero difference by cross-checking the material's movement history and the corresponding FI document line for the same period.
- Repeat the comparison after any correction posting to confirm the difference cleared before closing the period.
Key data objects
- MBEW - standard material valuation data per plant, holding stock quantity and value used for the MM side of the comparison.
- QBEW - valuated project stock, included when project stock exists for the material.
- EBEW - valuated sales order stock, included when sales order stock exists for the material.
- GLT0 or FAGLFLEXT (classic/new GL) or ACDOCA (S/4HANA universal journal) - the totals table MB5L reads to get the G/L account balance for comparison.
How to prove it in the data
Pull MBEW for the plant and valuation area, filtering on the material or valuation class in question, and sum the stock quantity times the standard or moving price to reproduce the MM-side figure MB5L shows. Separately pull the FI totals for the reconciliation G/L account from GLT0 or ACDOCA, filtered on company code and the same posting period. Line the two figures up side by side; the delta should match what MB5L reported. If it does not, the report's key date or scope selection is the first thing to re-check before assuming a data error.
ECC vs S/4HANA
The transaction itself is unchanged on S/4HANA and remains available. What changed underneath is the FI side of the comparison: the totals it reconciles against now come from the universal journal (ACDOCA) rather than the classic or new GL totals tables, so the same reconciliation logic runs against a single line-item table instead of separate summary tables. There is no dedicated Fiori app that replaces MB5L's specific stock-to-GL comparison function.
Common pitfalls and how to diagnose them
- Timing mismatch - a goods movement posted in one period but the corresponding FI document parked or posted in the next; check the posting date and document date on both sides before concluding there is a real gap.
- Account determination error - the valuation class or movement type maps to the wrong G/L account in the automatic account assignment configuration, so postings land on an account MB5L is not comparing against; verify the account determination table entries for the valuation class involved.
- Manual FI postings bypassing MM - someone journal-entered directly to the stock account outside a goods movement, which changes the G/L balance without touching MBEW; search the FI document for the account with no corresponding material document reference.
- Split valuation or multiple valuation types - MB5L totals can hide a mismatch that only appears at the valuation type level; rerun restricted to a single valuation type to isolate it.
- Reflex fix that makes it worse - posting a manual FI adjustment to force the balance to match, or forcing period close (MMPV) with the difference unresolved; both bury the discrepancy into the next period where it resurfaces larger and harder to trace.
- Currency mismatch - comparing local currency stock value against a G/L balance pulled in a different currency view, especially with parallel valuation active; confirm which currency and valuation view MB5L is using before treating the delta as real.
Whose problem this is
Joint MM and FI functional problem, since the discrepancy sits at the boundary between inventory accounting and the general ledger. A good handover states the plant, valuation area, key date, the G/L account and difference amount, and whether the gap traces to a specific material document, a manual FI entry, or an account determination setting - not just a screenshot of the report.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mb5lERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.