SAP MM Invoice Verification

You are a SAP Materials Management (MM) expert. The user wants to process logistics invoice verification in SAP using transaction MIRO with automated tolerance checks to prevent overpayment and quantity discrepancies.

What to check first

• Verify the invoice document number and vendor master data exist in SAP using transaction FK04 or FK03
• Check the purchase order (PO) and goods receipt (GR) are posted using transaction ME23N (view PO) and MIGO (check GR)
• Run transaction OMRJ to review configured tolerance limits (price variance %, quantity variance %, amount limits)

Steps

1. Open transaction MIRO and enter the invoice document number (Invoicing tab)
2. Enter the vendor code and invoice date; SAP auto-matches POs and GRs if available
3. Review the Line Item tab for quantity, unit price, and line amount — verify against PO/GR data
4. Check Amount Tolerance field (appears automatically if variance exceeds OMRJ thresholds) and decide to accept or block
5. Verify the GR/IR Account (Goods Received/Invoice Received staging account) balances match before posting
6. Navigate to Logistics Invoice Verification tab to see blocking reasons (if any) from OMRJ tolerance rules
7. Clear blocking by adjusting quantity or price, or post with approval override if variance is acceptable
8. Click Post to update the vendor invoice and move funds to accounts payable

Code

*&---------------------------------------------------------------------*
*& Report: SAP MM Invoice Verification (MIRO) Tolerance Check
*&---------------------------------------------------------------------*
REPORT zmm_invoice_verification.

DATA: lt_invoices TYPE TABLE OF bsik,
      ls_invoice  TYPE bsik,
      lv_vendor   TYPE lifnr,
      lv_tolerance_check TYPE c,
      lv_price_var DECIMAL(5,2),
      lv_qty_var DECIMAL(5,2),
      lv_message TYPE string.

SELECTION-SCREEN BEGIN OF BLOCK b01 WITH FRAME TITLE 'Invoice Verification'.
  PARAMETERS: p_vendor TYPE lifnr OBLIGATORY,
              p_inv_no TYPE miro-mblnr OBLIGATORY,
              p_inv_dt TYPE miro-budat DEFAULT sy-datum.
SELECTION-SCREEN END OF BLOCK b01.

START-OF-SELECTION.

  " Fetch invoice header from MIRO table
  SELECT SINGLE * FROM bsik INTO ls_invoice
    WHERE lifnr = p_vendor
      AND invnr = p_inv_no.

  IF sy-subrc = 0.
    WRITE: / 'Invoice Found:', ls_invoice-invnr.
    WRITE: / 'Vendor:', ls_invoice-lifnr.
    WRITE: / 'Amount:', ls_invoice-wrbtr.
  ELSE.
    MESSAGE '

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change