C_TS452_2022 Invoice Verification

Invoice Verification Detailed Explanation

The Invoice Verification module in SAP S/4HANA bridges procurement and finance, ensuring that invoices are accurately matched with purchase orders and goods receipts. This process is essential for maintaining consistency between what was ordered, what was received, and what is paid for, making it a key control point in the procurement-to-pay cycle.

Overview: Importance of Invoice Verification

In SAP, invoice verification is the process that confirms the accuracy of supplier invoices against the related purchase orders (POs) and goods receipts (GRs). By verifying invoices, businesses can catch discrepancies between the ordered, received, and invoiced amounts, preventing incorrect payments and financial inaccuracies. This module also handles adjustments for variances, additional freight or delivery costs, and credit memos, ensuring that procurement, inventory, and financial records are aligned.

1. Invoice Verification

• Definition: Invoice verification is the process of matching supplier invoices to corresponding POs and GRs. This step ensures that what is being paid matches the agreed-upon terms and the actual goods or services received.
• Key Functions:
  • Variance Handling: SAP identifies variances between the invoice amount and the expected amount from the PO and GR. Variances may arise from differences in quantity, price, or additional costs.
    • Example: If a supplier invoices a higher amount than agreed in the PO, SAP flags the variance and may require manual approval before payment.
  • Blocking Invoices: If variances exceed certain thresholds, SAP can automatically block the invoice until it is reviewed and approved by authorized personnel.
  • Delivery Costs: Additional costs, such as freight or handling fees, can be added during invoice verification. These costs can be posted directly to specific accounts or allocated across multiple items.
• Purpose: Invoice verification ensures financial accuracy and prevents overpayments by addressing discrepancies between what was ordered, received, and invoiced.

2. Credit Management

• Definition: Credit management in the context of invoice verification involves managing any credits or adjustments to an invoice after it has been processed. This may include handling credit memos, subsequent debits, and delivery cost adjustments.
• Key Components:
  • Credit Memos: A credit memo is issued by the supplier if an invoice was overpaid or if goods were returned. This credit can be used to offset future payments or reimburse the buyer.
    • Example: If goods were damaged upon delivery and returned to the supplier, the supplier may issue a credit memo to reduce the amount owed.
  • Subsequent Debits and Credits: Sometimes, additional charges (debits) or reductions (credits) are needed after an invoice has been paid. SAP allows these adjustments to be recorded and linked to the original invoice.
  • Delivery Cost Adjustments: When delivery costs are recalculated or corrected after the initial invoice, SAP allows users to adjust these amounts to reflect the true cost of the goods.
• Purpose: Effective credit management ensures that any adjustments to payments are accurately recorded, maintaining integrity in financial accounts and aligning with actual costs.

Exam Objectives

For the SAP C_TS452_2022 exam, you should be able to:

• Manage invoice verification efficiently, handling variances, blocking rules, and the application of additional costs.
• Handle credit memos and subsequent debits/credits, ensuring that any post-invoice adjustments are accurately reflected in procurement, inventory, and financial accounts.

Invoice Verification (Additional Content)

Invoice verification is a crucial part of the Procure-to-Pay (P2P) process in SAP S/4HANA, ensuring accurate financial reconciliation between purchase orders (POs), goods receipts (GRs), and supplier invoices.

1. Three-Way Matching in Invoice Verification

Three-Way Matching is a key principle in Invoice Verification, ensuring that the supplier’s invoice aligns with the purchase order (PO) and goods receipt (GR).

1.1 Components of Three-Way Matching

Component	Purpose
Purchase Order (PO)	Defines ordered quantity, price, and supplier terms.
Goods Receipt (GR)	Confirms received quantity and updates inventory.
Supplier Invoice	Specifies billing amount; SAP verifies it against PO and GR.

1.2 Purpose of Three-Way Matching

• Prevents overpayment – Ensures the invoice matches the agreed PO price.
• Avoids paying for undelivered goods – Blocks invoices if GR is missing.
• Automates reconciliation – SAP flags discrepancies and applies tolerance rules.

1.3 Example Scenario

• A company orders 100 units of raw materials at $10 per unit (Total = $1,000).
• The supplier delivers 100 units, and the company posts a GR.
• The supplier sends an invoice for 110 units ($1,100 instead of $1,000).
• SAP detects the quantity variance and blocks the invoice for further review.

1.4 SAP Transactions

• MIRO – Enter Incoming Invoice.
• MIR4 – Display Invoice.
• MIR7 – Park Invoice.

2. Invoice Verification Variances

Invoice variances occur when the invoice details do not match the PO or GR. SAP can block invoices with significant variances or allow them within predefined tolerances.

2.1 Common Variance Types

Variance Type	Description	SAP Handling
Quantity Variance	Invoice quantity differs from GR quantity.	SAP may block the invoice until corrected.
Price Variance	Invoice price exceeds PO price.	SAP applies price tolerance limits (e.g., ±5%).
Invoice Before GR	Invoice arrives before goods are received.	SAP can hold the invoice until GR is posted.

2.2 Example Scenario

• A PO for 100 units at $10/unit is issued.
• Supplier invoice shows 100 units at $11/unit (Total = $1,100 instead of $1,000).
• If price tolerance is set to ±5%, the invoice is blocked because 10% exceeds the threshold.

2.3 SAP Transactions

• MRBR – Release Blocked Invoices.
• OMR6 – Configure Tolerance Limits.

3. Tolerance Limits in Invoice Verification

Tolerance limits define acceptable variance thresholds before SAP blocks an invoice for manual approval.

3.1 Types of Tolerance Limits

Tolerance Type	Purpose
Price Tolerance	Allows minor price differences (e.g., ±5%).
Quantity Tolerance	Allows minor quantity differences (e.g., ±2%).
Small Amount Tolerance	Auto-clears invoices if variance is within a small amount (e.g., ≤ $10).

3.2 Example Scenario

• A $1,000 invoice has a $10 price variance.
• If the tolerance limit is set to $20, SAP auto-approves the invoice.
• If the variance exceeds the limit, SAP blocks the invoice.

3.3 SAP Configuration Path

• SPRO → Materials Management → Logistics Invoice Verification → Invoice Block.
• Transaction Code: OMR6.

4. GR/IR Clearing Account

The Goods Receipt/Invoice Receipt (GR/IR) account is a temporary clearing account that helps track unmatched GRs and invoices.

4.1 When Does GR/IR Account Come Into Play?

Scenario	GR/IR Posting
GR posted before invoice	Debit: GR/IR Account, Credit: Inventory.
Invoice posted before GR	Debit: GR/IR Account, Credit: Accounts Payable.
Invoice and GR match	SAP clears the GR/IR account.

4.2 Example Scenario

• A PO for 50 units is created.
• The supplier delivers 50 units, and a GR is posted.
• The invoice for 50 units is posted one week later.
• SAP automatically clears the GR/IR account, ensuring no outstanding liabilities.

4.3 SAP Transactions

• F.13 – Automatic GR/IR Clearing.
• MR11 – Manual GR/IR Clearing.

5. Automatic Invoice Verification & Background Processing

SAP allows automated invoice verification to reduce manual work and improve efficiency.

5.1 Key Features

• Batch Processing – SAP automatically processes multiple invoices in the background.
• Logistics Invoice Verification (LIV) – Uses three-way matching to validate invoices.
• Electronic Data Interchange (EDI) – Allows automatic invoice entry from suppliers.

5.2 Example Scenario

• A company receives 100 supplier invoices per day.
• Instead of manually entering invoices, SAP automatically processes them via EDI.
• The system validates prices, checks GRs, and posts approved invoices.

5.3 SAP Transactions

• MRRL – Invoice Verification in Background.
• WE20 – Maintain EDI Partner Profiles.

Conclusion

Effective Invoice Verification in SAP S/4HANA ensures financial accuracy and compliance through:

1. Three-Way Matching – Ensures that PO, GR, and Invoice align before processing.
2. Invoice Variance Handling – Detects and manages quantity, price, and timing mismatches.
3. Tolerance Limits – Allows small variances while blocking major discrepancies.
4. GR/IR Clearing – Tracks unmatched invoices and receipts for proper accounting.
5. Automated Invoice Processing – Uses batch verification and EDI integration to speed up invoice handling.