In part one of our three part series, we explored the business process and it’s

execution in SAP for three way match. In this second part, we’ll work through
one way of managing variances for logistics invoices. There are two core
approaches that can be used for managing variances. In this article, we’ll use
the older approach of blocking invoices for payment.

Motivation on handling MIRO Invoices

Consider the following example, where our company order 80 units of

inventory at a price of $12.50 per each. The vendor short shipped our
company and only sent 60 units. When the invoice is received, it is for 80
units. The AP processor posts the invoice. From a financial reporting
perspective, the GR/IR control and the AP account will roll up under the same
group account. That ensures that only the balance that has been received is
reported.

At the same time, since there is a dispute with the vendor on the correct
amount owed, the company should not pay the invoice. The invoice processor,
the purchaser, and the warehouse manager should collaborate with the vendor
to establish what is correctly owed. In our scenario, the vendor agrees to
reduce the amount owed for the 20 units at a price of 250. The invoice
processor posts the credit memo and we have:
Now, the GR/IR control account balances to zero and the vendor balance in
AP balances to $750 – the expected value of what our company will pay the
vendor. In this process, there are a few keys:

1. Despite a variance occurring, the invoice was posted immediately and

put onto the company’s books.

2. The vendor was not paid until the GR/IR account balances in both value
and quantity. The payment was blocked.

3. A credit memo was posted to solve the discrepancy

4. At the end of the process, the GR/IR account equaled zero.

As we review the technical process in SAP, it will be critical to consider the

above points.

Blocking invoices in MIRO in SAP

The below configuration determines when a payment will be blocked. This

configuration is fairly complicated but at the core, for each company code, one
or more variance types should be defined. Each variance type has a particular
formula for calculating it. The help text attached to the configuration screen
has each of the variance calculations laid out. One key note is that a small
difference (variance type BD) should always be configured otherwise every
variance will be written off to the small difference write-off account. Here,
we’ve configured a tolerance to block for price variances over $5 or 5% for
unfavorable and $10 or 5% for favorable.
(1)

Now, when an invoice that is posted exceeds those limits, the invoice will be
blocked. Consider our above example above.
(2)

Now, the invoice is received and posted with the vendors values. Notice that
the line up values and quantities are overwritten to match those of the invoice.

(3)
Resolving the variance

To resolve the variance, the vendor will issue a credit memo. This credit memo
will be booked through MIRO by selecting the “Credit Memo” transaction at
the top. Use the below table based on whether the price or quantity is wrong to
decide on the correct transaction.

Transaction Value Adjustment

Invoice Increase Amt Owed

Credit Memo Decrease Amt Owed

Subsequent Debit Increase Amt Owed

Subsequent Credit DecreaseAmt Owed

(4)

Now that our GR IR balances, transaction MRBR will release the invoice from
block.
(5)

Now, if you look in MIR5, you would see the payment block released. The
invoice is paid and the GR/IR is clean.

T-Codes, Config Paths, etc

1. ↑ SPRO -> Materials Management -> Logistics Invoice Verification -> Invoice Block -> Set Toler

2. ↑ Displayed with ME23N, entered via ME21N and MIGO

3. ↑ MIRO

4. ↑ Credit memo entered through MIRO

 5. ↑ MRBR
Tags: AP, FICO, Invoices, MIRO
« Invoices with 3-Way Match in SAP MM-LIV (Part 1)
0 COMMENTS

LEAVE A REPLY

You must be logged in to post a comment.

Recent Posts

 Invoices with 3-Way Match in SAP MM-LIV (Part 2)

 Invoices with 3-Way Match in SAP MM-LIV (Part 1)
 The dangerous transaction: SE16
 Quick note about the site
 SAP GL Document Splitting Part I

Recent Comments

 David Schenz on SAP GL Document Splitting Part I

 Sergio Cecchin on SAP GL Document Splitting Part I
 Invoices with 3-Way Match in SAP MM-LIV (Part 2) - Slide
Blue on Invoices with 3-Way Match in SAP MM-LIV (Part 1)
 Sanjay on Currencies in SAP FI
 Imran Mohammed on House Bank Accounts in SAP FICO
© 2019 Slide Blue - Theme by Ritesh Sanap

SLIDE BLUE
An SAP Knowledge Hub

CATEGORIES
 Reporting (1)

 SAP FI (14)

o AP (2)
o AR (1)

o Bank (1)

o FA (1)

o GL (8)

 Uncategorized (1)

RECENT POSTS
 Invoices with 3-Way Match in SAP MM-LIV (Part 2) July 4, 2016

 Invoices with 3-Way Match in SAP MM-LIV (Part 1) July 3, 2016

 The dangerous transaction: SE16 June 27, 2016

 Quick note about the site June 26, 2016

 SAP GL Document Splitting Part I March 17, 2015

LOGIN
 Register

 Log in

 Entries RSS

 Comments RSS

 WordPress.org