SAP Procure to Pay — Lesson 3: Goods Receipt, Invoice Verification, Accounting Integration, and Blocked Invoices

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing goods-receipt and invoice matching.
• Perform and validate blocked-invoice root-cause analysis using reviewable system evidence.
• Evaluate the condition where a supplier invoice is blocked because quantity, price, and receipt evidence disagree and select proportionate corrective action.

Detailed Topics

• Goods Receipt applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Invoice Verification applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Accounting Integration applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Blocked Invoices applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a procurement team standardizing purchasing execution while protecting accounting accuracy and supplier service. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the procure-to-pay control and reconciliation workbook. It also tests the exception where a supplier invoice is blocked because quantity, price, and receipt evidence disagree.

Hands-On Exercise

Complete a controlled SAP exercise covering Goods Receipt, Invoice Verification, Accounting Integration, and Blocked Invoices and preserve the verified result in the procure-to-pay control and reconciliation workbook.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences goods-receipt and invoice matching.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the procure-to-pay control and reconciliation workbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “a supplier invoice is blocked because quantity, price, and receipt evidence disagree” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The procure-to-pay control and reconciliation workbook connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Goods Receipt, Invoice Verification, Accounting Integration, and Blocked Invoices, explain the resulting SAP behavior, and defend the outcome through the procure-to-pay control and reconciliation workbook.