Navigation of the GR/IR complexities!

Navigating the Complexities of GR/IR Reconciliation in SAP Procurement

Table of Contents

1. Introduction
2. Standard Procurement
   • Standard Purchase Order (PO)
   • Subcontracting
   • Consignment Procurement
   • Stock Transfer
   • Third-Party Procurement
3. Service Procurement
   • Service Purchase Orders
   • Framework Orders
4. Procurement with Advanced Payment
   • Down Payments
   • Retention Payments
5. Returns and Reversals
   • Goods Returns
   • Invoice Reversals
6. Intercompany Procurement
   • Cross-Company Procurement
7. Procure-to-Pay (P2P) Scenarios
   • Integration with SAP Ariba
   • Logistics Invoice Verification (LIV)
8. Special Procurement Scenarios
   • Drop Shipment
   • Purchase for Projects (WBS Elements)
   • Internal Orders or Cost Centers
9. Multi-Currency Procurement
   • Foreign Currency POs
10. Taxation and Pricing
    • Tax Code Differences
    • Price Variance
11. Period-End Scenarios
    • GR/IR Clearing at Period Close
    • Accruals for Open Items
12. Supplier Consortia
    • Group Purchasing
13. Asset Management
    • Capital and Operational Procurement
14. Conclusion

1. Introduction

GR/IR (Goods Receipt/Invoice Receipt) reconciliation is crucial in SAP procurement for accurate financial reporting and operational efficiency. However, various procurement scenarios can introduce complexities. This article explores these scenarios and their impact on GR/IR, providing practical use cases for better understanding.

2. Standard Procurement

• Standard Purchase Order (PO): The most common scenario involves ordering, receiving, and invoicing goods. Timing differences between goods receipt (GR) and invoice receipt (IR) often lead to temporary GR/IR balances.
  • Use Case: A company orders 100 laptops. The goods are received in full, but the invoice arrives a week later, creating a temporary GR/IR balance until the invoice is posted.
• Subcontracting: Components are sent to a vendor for processing, and the finished goods are received back.
  • Use Case: A car manufacturer sends engine parts to a subcontractor for assembly. The GR/IR process tracks the components sent, the subcontractor's service charges, and the final assembled engines received.
• Consignment Procurement: Goods are received but remain the vendor's property until used.
  • Use Case: A retailer receives a consignment of clothes. GR/IR entries are only created when items are sold or transferred to own stock.
• Stock Transfer: Movement of goods between company codes or plants.
  • Use Case: A company transfers raw materials from its warehouse to its production facility in another location. This creates intercompany GR/IR entries.
• Third-Party Procurement: The vendor ships goods directly to the customer.
  • Use Case: An online retailer uses a dropshipping model. The retailer receives the customer order and relays it to the vendor, who ships the product directly. The retailer handles the invoice and payment, but no physical goods receipt occurs in their system.

3. Service Procurement

• Service Purchase Orders: Services are ordered and confirmed with service entry sheets.
  • Use Case: A company hires a consultant for IT services. The consultant's work is confirmed through service entry sheets, which trigger GR/IR entries.
• Framework Orders: Blanket POs for ongoing services or materials.
  • Use Case: A company has a framework agreement with a cleaning service for regular office cleaning. Services are performed and invoiced periodically, leading to ongoing GR/IR reconciliation.

4. Procurement with Advanced Payment

• Down Payments: Partial or full payment before goods receipt.
  • Use Case: A company makes a down payment for a custom-made machine. The GR/IR account reflects the down payment and is adjusted upon final delivery and invoice.
• Retention Payments: A portion of the payment is withheld until project completion or other conditions are met.
  • Use Case: A construction company agrees to a retention payment clause in a project contract. The GR/IR reconciliation needs to account for the retained amount until it is released.

5. Returns and Reversals

• Goods Returns: Returning goods to the vendor after GR or IR.
  • Use Case: A company receives a shipment of defective products and returns them to the vendor. This requires adjustments to the GR/IR account.
• Invoice Reversals: Correcting incorrect invoices.
  • Use Case: An invoice contains an incorrect quantity. The invoice is reversed, and a new corrected invoice is issued, impacting the GR/IR balance.

6. Intercompany Procurement

• Cross-Company Procurement: Purchase orders between different company codes within the same organization.
  • Use Case: A subsidiary orders goods from its parent company. This generates intercompany GR/IR entries that need to be reconciled.

7. Procure-to-Pay (P2P) Scenarios

• Integration with SAP Ariba: Automating invoice processing through Ariba.
  • Use Case: Invoices are automatically received and processed through Ariba, reducing manual effort. However, any discrepancies between the invoice and the PO or GR will require reconciliation.
• Logistics Invoice Verification (LIV): Matching invoices with GR and PO data.
  • Use Case: LIV helps identify and resolve discrepancies between invoices and other documents. Automated matching rules can streamline the process, but exceptions require manual intervention.

8. Special Procurement Scenarios

• Drop Shipment: Direct delivery from the vendor to the customer.
  • Use Case: As mentioned earlier, an online retailer using a dropshipping model will only have an IR entry, requiring reconciliation against the customer's order.
• Purchase for Projects (WBS Elements): Procurement linked to specific projects.
  • Use Case: A construction company procures materials for a specific building project. The GR/IR postings are linked to the project's WBS element for accurate cost tracking.
• Internal Orders or Cost Centers: Goods procured for internal use.
  • Use Case: A company purchases office supplies for its marketing department. The GR/IR entries need to be assigned to the correct cost center.

9. Multi-Currency Procurement

• Foreign Currency POs: Exchange rate fluctuations between GR and IR.
  • Use Case: A company orders goods from a foreign vendor. The exchange rate at the time of goods receipt may differ from the rate at the time of invoice receipt, creating a GR/IR variance.

10. Taxation and Pricing

• Tax Code Differences: Discrepancies in tax rates between PO and invoice.
  • Use Case: A change in tax legislation occurs between the PO creation and invoice receipt, leading to a difference in the tax amount.
• Price Variance: Differences in unit price between PO and invoice.
  • Use Case: The vendor increases prices after the PO is issued, but before the invoice is sent.

11. Period-End Scenarios

• GR/IR Clearing at Period Close: Reconciling open GR/IR items.
  • Use Case: At the end of the accounting period, the company reviews all open GR/IR items and performs necessary adjustments or clearing.
• Accruals for Open Items: Accounting for goods received but not invoiced.
  • Use Case: Goods are received near the period-end, but the invoice is expected in the next period. An accrual is posted to reflect the expense in the correct period.

12. Supplier Consortia

• Group Purchasing: Procurement through group suppliers with complex pricing and invoicing.
  • Use Case: A hospital participates in a group purchasing organization for medical supplies. Invoices may be split among multiple suppliers, requiring careful reconciliation.

13. Asset Management

• Capital and Operational Procurement: Procuring assets like machinery or buildings.
  • Use Case: A company purchases a new production machine. The GR/IR process is linked to the asset capitalization process.

14. Conclusion

Understanding these diverse procurement scenarios and their impact on GR/IR allows organizations to implement effective controls and leverage SAP S/4HANA's capabilities to streamline reconciliation, ensure financial accuracy, and optimize procurement processes.