Invoice verification

Invoice verification in SAP is a solid and efficient process.


Select Logistics  Materials Management  Logistics Invoice Verification  Document Entry  Enter Invoice.- MIRO



Invoice frication allows you to capture the details of vendor invoices. If the details of an invoice match the expected details that are specified by any related purchase order and goods receipts, the invoice can be automatically made available for payment. Unmatched invoices are excluded from the payment run and need to be investigated and released before payments can be made.

The main aim of any invoice-verifrication process is to ensure that vendors are paid the correct amount at the right time ( not too late but also not too early ). The process should have a high incidence of first-time matching, to ensure that as little time as possible is spent trying to manually match invoices that appear to be incorrect. It is important to include as few steps as possible in the process, considering that the process of handling payments does not in itself add value to the company or to the vendor.

The Main Steps

1. The capture of the vendor’s invoice details (T code: MIRO)

Note: This also includes the automatic release for payment if the match is successful.

- First ensures that the details entered add up mathematically.

- Second checks to see if the invoice should be blocked or made available for payment.

2. Handling of mismatched invoices (T code: MRBR)

The handling of mismatched invoices occurs in transaction MRBR , which also includes the release for payment if the invoice is successfully matched. Mismatched invoices are those where the details on the invoice do not match the details expected according to the purchase order. This transaction lists all of the invoices that have been blocked for payment.

MRBR should be checked regularly, and this transaction should be seen as the sole transaction for managing the release of blocked invoices . You can list blocked invoices by vendor , by date, by purchasing group , or by user, among other criteria. The system will then display the blocked invoices that match the selection options, and you will then be able to release invoices manually.

Using Workflow when Mismatches Occur:

MIRO can trigger a workflow message ( normally an SAP mail or email message that can be formatted to suit your needs ) to an appropriate user whenever a mismatch occurs. This is normally a request to correct a price or complete a goods receipt to make the details match the invoice.

Parking Invoices

Menu option> Edit > Switch to Document Parking

This option is used to address situations where, for whatever reason, the user does not wish to complete the invoice-verification transaction but wishes to keep the data entered so far.

The other option is to start off by using the Invoice Parking function directly, instead of MIRO, using transaction MIR7 . This is used in situations where you know that you will not want to process the invoice at this stage.

Automatic invoice release

There is actually no setting for automatic invoice release for payment as such. If you have an invoice that is blocked because the goods receipt has not yet been posted and then the goods receipt is posted, the invoice will not be automatically released for payment. However you can use transaction MRBR in a scheduled job with the flag release automatically set on, and this will then release all invoices where the blocking reason is no longer relevant. This will then act the same as an automatic release, but will only release when the job has run. Ideally, this should be at least once a day.



3. The release for payment of matched invoices

4. Posting of accounting entries involved

a. During Invoice Verification

G/R I/R Account - Dr

Vendor – Cr

b. during Goods Receipt

Stock Account - Dr

G/R I/R Account – Cr