MIR5 — Display List of Invoice Documents

MIR5 produces a list of logistics invoice verification documents based on selection criteria entered on the initial screen: company code, vendor, fiscal year, posting date range, document number range, or reference document. It is a pure reporting transaction, no document is created or changed here. The structural fact that causes most confusion is that MIR5, MIR6, and MIR4 all sound like they do the same thing but do not: MIR4 displays one specific invoice document, MIR6 is the newer ALV-based invoice overview with more flexible layout and filter options, and MIR5 is the older classic list report with a fixed selection screen. Consultants who reach for MIR5 out of habit sometimes miss functionality that only exists in MIR6, and vice versa.

MIR5 gets used when someone needs to find one or more existing invoice documents fast, without knowing the exact document number: checking whether a vendor's invoice was already posted, listing all invoices for a purchase order, reconciling a batch of invoices during month-end, or supporting an audit request for a date range. It sits downstream of MIRO and MIR7 in the process, after invoices have already been entered or parked. For anything beyond simple lookup, such as bulk release of blocked invoices or a more configurable layout, MIR6 or a Fiori invoice monitoring app is the better tool. MIR5 is the quick, no-frills option when the consultant just needs to see what exists.

Run SE16N or SE16 on RBKP filtered by BUKRS and GJAHR, then narrow by LIFNR or a BELNR range to match what MIR5 was asked to select. If a document is missing from the MIR5 list but the user insists it exists, check RBKP-RBSTAT (document status) and BUKRS/GJAHR combination first, since a wrong fiscal year or a parked-only status can silently exclude it from a selection that assumes posted documents. Cross-check RSEG on the same BELNR/GJAHR key to confirm line items exist, and join to EKPO via EBELN/EBELP if the PO reference looks wrong.

MIR5 remains available on S/4HANA as a compatible transaction, and the underlying RBKP and RSEG tables are unchanged in structure and purpose. SAP's direction is toward Fiori-based invoice monitoring and management apps that offer richer filtering, mass actions, and a modern list UI, but no S/4HANA release has removed MIR5 outright. Consultants working in a Fiori-first shop should expect the classic transaction to still work as a fallback, particularly for quick ad hoc lookups during troubleshooting.

This is functional AP/invoice verification territory, not Basis or ABAP, since MIR5 involves no configuration and no code path beyond standard selection logic. A good handover to the functional owner includes the exact selection criteria used, the expected document number if known, and whether the missing document is parked, posted, or blocked, so the owner can check RBKP status directly rather than re-running the same search.

MIR4 is the natural next stop from any MIR5 result line, showing the full invoice document including tax and FI posting detail. MIR6 covers the same ground as MIR5 with a more flexible ALV layout and is worth learning alongside it to know which tool fits which situation. MIR7 is upstream, since parked invoices found in MIR5 originated there. MB03 is useful when the invoice verification question turns into a three-way match check against the goods receipt document.