MIR7 — Park Invoice in Logistics Invoice Verification

MIR7 records a vendor invoice against a purchase order without creating the corresponding financial document. The invoice header and line items are saved exactly as they would be for a posted invoice, with PO reference, quantities, amounts and tax, but no entry hits BKPF or BSEG and no vendor open item is created. The structural fact that explains most of the confusion around this transaction: parking does not require the document to balance. A user can park an invoice with a difference between invoice amount and PO/GR value, save it, and walk away. Posting later, whether through MIR4 or a workflow step, is the point where the balance check and full duplicate/tolerance validation actually bite. Anyone treating a parked invoice as a completed transaction is working from an incomplete document.

MIR7 is reached for whenever the person entering the invoice does not have authority to post it directly, or whenever a discrepancy (price variance, quantity variance, missing goods receipt) means the invoice cannot be posted cleanly yet but the clock is running on payment terms and the data should not sit unrecorded. It is common in shared service centers where junior AP staff key invoices and a senior clerk or approver posts. It is also used deliberately to pre-stage an invoice ahead of an expected goods receipt. MIRO is the direct-post equivalent and is preferred when the invoice is clean and the user has full authority. On S/4HANA the same decision is made inside the 'Create Supplier Invoice' Fiori app, where parking is one of the save options rather than a separate transaction code.

Open RBKP for the company code and fiscal year in question and filter on the status field to isolate parked documents rather than posted ones. Take the resulting document number and fiscal year into RSEG to pull the line items and confirm the PO reference and amounts. Cross-check against BKPF for the same document number and fiscal year: if no FI document exists, the invoice is still parked regardless of what a report elsewhere is showing. A missing entry in EKBE for that PO item confirms the invoice has not yet touched purchase order history.

MIR7 still works in the S/4HANA back end and the underlying tables are unchanged, since a parked document has not yet generated a Universal Journal entry. The forward-looking equivalent is the 'Create Supplier Invoice' Fiori app, where parking is a save option rather than a separate transaction, and approval of parked invoices is typically handled through a workflow-driven inbox rather than a manual MIR4 lookup. No data model change has to be accounted for when diagnosing a parked invoice on S/4HANA.

This is a functional AP/MM issue in the large majority of cases: tolerance settings, release strategy configuration, and workflow routing for parked invoices are all invoice verification configuration. Basis involvement is limited to authorization object assignment when a user cannot park or post. A clean handover includes the invoice document number, company code, fiscal year, current balance status, and whether a workflow step is pending.

MIR4 is the natural next stop, since it displays, changes, and posts the parked document created here. MIR5 and MIR6 give list views of invoice documents and parked invoices respectively, useful for finding what has been sitting unposted. ME53N is worth checking whenever a parked invoice disagrees with what purchasing expects, since PO status and outstanding quantity live there rather than in the invoice tables.