XML Feeds

Search Big4Guy

Custom Search

Sponsored

« Audit Committee PreApproval of Services Related to Internal ControlPCAOB Proposes Revised AS2 for Internal Control Reporting »

Invoice Verification in SAP R3 - T-Codes MIRO and MRBR

Invoice Verification in SAP R3 - T-Codes MIRO and MRBR

Many of my SAP readers have asked "What is Invoice Verification in SAP R/3?". Though I had touched upon this in my earlier post on three way invoice matching, I am discussing invoice verification in SAP R3 in detail in this post. Simply speaking, invoice verification refers to matching the invoice to details of purchase order and goods receipt before a payment on that invoice can occur. Invoices which get matched get paid through the payment run and unmatched invoices are parked for investigation.

Let me explain the SAP invoice verfication process in SAP R3 step by step:

1. The first step is entering vendor invoice details received into SAP. This process is done using the transaction code "MIRO" Enter Incoming Invoice in SAP. All invoice details such as basic data, payment details, tax details etc can be entered using this t-code.

2. The next step involves matching the details of invoices with purchase order information and goods receipt information. This step is called matching in the process invoice verification and is done using t-code MIRO. This step can have two results. In case, the invoices match, same are automatically released for payment in SAP through a scheduled payment run. In case, invoices verification fails and there is a mis-match, then further investigation is required.

3. In case invoices do not match with PO and GR details, same can be further investigated and cleared off using the t-code MRBR. MRBR is the t-code for releasing blocked invoices for payment once they have been matched. Such blocked invoices can either be released manually or the same can be released automatically by activating automatic release flag.

4. Finally, as a last step, the accounting entries for invoice verification are updated at the time when the transactions MIRO and MRBR are posted to SAP FI.

Related Posts

SAP R3 Tolerance Groups
Implementing SAP BW Business Warehouse
Standard Document Types in SAP R3
SAP BW Infocubes


Feedback awaiting moderation

This post has 49 feedbacks awaiting moderation...

Leave a comment


Your email address will not be revealed on this site.

Your URL will be displayed.
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)