Oracle Fusion P2P Interview Scenario: PO Received but Supplier Invoice Is on Hold or Not Matching

Oracle Fusion Procure to Pay, also called P2P, is one of the most important interview topics for Oracle Procurement, Payables, SCM, Finance, OIC, BIP, and OTBI consultants. A common real-time interview scenario is: Purchase Order is approved, goods are received, but the supplier invoice is on hold or not matching. What will you check? This question tests more than theory. It checks whether you understand the complete flow from requisition to purchase order, receiving, invoice matching, invoice validation, holds, payment, and accounting. In this blog, we will explain the Oracle Fusion P2P flow, invoice matching concepts, common causes of invoice holds, troubleshooting steps, technical consultant points, and interview questions.

Oracle Fusion P2P Interview Scenario: PO Received but Supplier Invoice Is on Hold or Not Matching

Summary

Oracle Fusion Procure to Pay, also called P2P, is one of the most important interview topics for Oracle Procurement, Payables, SCM, Finance, OIC, BIP, and OTBI consultants.

A common real-time interview scenario is:

Purchase Order is approved, goods are received, but the supplier invoice is on hold or not matching. What will you check?

This question tests more than theory. It checks whether you understand the complete flow from requisition to purchase order, receiving, invoice matching, invoice validation, holds, payment, and accounting.

In this blog, we will explain the Oracle Fusion P2P flow, invoice matching concepts, common causes of invoice holds, troubleshooting steps, technical consultant points, and interview questions.

What is Procure to Pay in Oracle Fusion?

Procure to Pay is the end-to-end business process used by organizations to purchase goods or services and pay suppliers.

A simple P2P flow looks like this:

Business user raises a purchase requisition
Requisition goes for approval
Buyer creates or converts it into a purchase order
Purchase order is approved and communicated to supplier
Supplier delivers goods or services
Business receives the goods or confirms service completion
Supplier submits invoice
Invoice is matched with PO or receipt
Invoice is validated
Holds are resolved, if any
Invoice is approved
Payment is processed
Accounting is created and transferred to General Ledger

In Oracle Fusion, P2P usually connects:

Oracle Self Service Procurement
Oracle Purchasing
Oracle Receiving
Oracle Inventory
Oracle Payables
Oracle Payments
Subledger Accounting
General Ledger
Oracle Integration Cloud
BI Publisher
OTBI

For interviews, just saying “P2P starts with requisition and ends with payment” is not enough.

You should be able to explain what happens when something fails.

Why This Interview Question Is Important

Interviewers often ask:

PO is approved and goods are received, but invoice is not matching or invoice is on hold. What will you check?

This is a strong interview question because it connects multiple areas:

Procurement setup
Supplier setup
PO status
Receipt status
Invoice match option
Quantity tolerance
Amount tolerance
Invoice validation
Invoice holds
Payment readiness
Accounting impact
Integration errors

A candidate who only knows definitions may say:

“I will check invoice validation.”

But a strong consultant will explain the full troubleshooting path.

Understanding Invoice Matching in P2P

Invoice matching means comparing the supplier invoice against the purchase order or receipt before payment is made.

The purpose is simple:

The company should pay only for what it ordered, received, or consumed.

In Oracle Fusion, invoice matching may happen against:

Purchase order
Receipt
Consumption advice
Purchase order schedule
Purchase order distribution

Matching helps validate:

Supplier
Legal entity
Business unit
Quantity
Amount
Price
Receipt details
Tax
Distributions

If the invoice does not match the expected PO or receipt details, it may go on hold.

Common Matching Types in P2P

1. Two-Way Matching

Two-way matching compares:

Purchase Order vs Invoice

Example:

PO quantity: 100
Invoice quantity: 100

PO price: 500
Invoice price: 500

If the invoice quantity and price are within tolerance, the invoice can proceed.

This is usually used when receipt confirmation is not required for payment.

2. Three-Way Matching

Three-way matching compares:

Purchase Order vs Receipt vs Invoice

Example:

PO quantity: 100
Received quantity: 80
Invoice quantity: 100

Here, the invoice may go on hold because the supplier is billing for 100 units but only 80 were received.

This is very common in real projects.

For inventory items and goods-based procurement, three-way matching is usually more important because payment depends on receipt confirmation.

3. Four-Way Matching

Four-way matching compares:

Purchase Order vs Receipt vs Inspection/Acceptance vs Invoice

This is used when goods must be inspected or accepted before payment.

Example:

PO quantity: 100
Received quantity: 100
Accepted quantity: 90
Invoice quantity: 100

The invoice may go on hold because only 90 units were accepted.

Real Interview Scenario

Scenario

A purchase order is approved.

The supplier delivered the material.

The receipt is also created.

But when the supplier invoice is entered, the invoice is on hold or not matching.

What will you check?

Step-by-Step Troubleshooting Approach

Step 1: Check Purchase Order Status

First, check whether the purchase order is valid for invoicing.

Check:

Is the PO approved?
Is the PO open?
Is the PO communicated to supplier?
Is the PO canceled?
Is the PO closed for receiving?
Is the PO closed for invoicing?
Is there any hold on the PO?
Is the PO line active?
Is the PO schedule valid?
Is the PO distribution correct?

If the PO is not approved or not open for invoicing, invoice matching may fail.

In interviews, always start from the source document.

The PO is the foundation of the P2P process.

Step 2: Check Supplier and Supplier Site

Supplier setup is one of the most common reasons for invoice issues.

Check:

Supplier is active
Supplier site is active
Supplier site is valid for purchasing
Supplier site is valid for payment
Pay site exists
Invoice currency is correct
Payment terms are defined
Tax registration is correct
Supplier bank details are available, if payment is required

Sometimes the PO may be created against one supplier site, but the invoice is entered against another supplier site.

This can create matching issues or validation errors.

Step 3: Check Receipt Status

If the PO uses receipt-based matching or three-way matching, receipt status becomes very important.

Check:

Was receipt created?
Was correct quantity received?
Was receipt created against the correct PO line?
Was receipt created against the correct shipment/schedule?
Was receipt corrected or returned?
Was the receipt fully processed?
Was there any inspection or acceptance required?
Was the accepted quantity less than received quantity?

Example:

PO quantity: 100
Receipt quantity: 80
Invoice quantity: 100

In this case, the invoice may be placed on hold because the invoice quantity is greater than the received quantity.

Step 4: Check Invoice Match Option

Invoice match option decides whether the invoice should match against the PO or receipt.

Check whether the match option is:

Order
Receipt

If the invoice match option is receipt, but receipt is not available or not fully processed, matching will fail.

If the invoice match option is order, matching is generally based on the purchase order.

This is a very important interview point because many candidates directly check invoice validation but forget to check the match option.

Step 5: Check Quantity and Amount Tolerances

Invoice tolerances define how much difference is allowed between PO, receipt, and invoice.

Check:

Quantity tolerance
Amount tolerance
Price tolerance
Exchange rate variance
Tax variance
Freight or miscellaneous charge variance

Example:

PO price: 1000
Invoice price: 1100
Tolerance allowed: 5%

The invoice may go on hold because the supplier billed more than the allowed tolerance.

This is one of the most common P2P issues.

Step 6: Check Invoice Validation

Invoice validation is the process that checks whether the invoice is complete and valid for payment.

If invoice validation fails, the invoice may be placed on hold.

Check:

Invoice validation status
Validation errors
Holds applied
Missing information
Invalid supplier site
Invalid distribution
Invalid account
Tax errors
Duplicate invoice number
Matching variance
Period status
Business unit or legal entity mismatch

A strong answer should always mention invoice validation because many invoice holds are applied during validation.

Step 7: Check Invoice Holds

Invoice holds prevent the invoice from being paid.

Some holds may also stop accounting.

Common hold reasons include:

Quantity variance
Price variance
Amount variance
Missing receipt
Missing information
Tax issue
Distribution variance
Duplicate invoice
Invalid accounting
Manual hold
Approval hold

Do not say “release the hold” immediately.

First identify whether the hold is valid.

If the supplier billed incorrectly, the invoice should be corrected.

If the receipt is missing, receipt should be created or corrected.

If tolerance setup is incorrect, setup should be reviewed.

If the hold is manual, the authorized user can release it.

Step 8: Check Tax and Accounting Setup

Sometimes invoice matching is fine, but invoice validation fails due to tax or accounting setup.

Check:

Tax classification
Tax regime
Tax registration
Tax calculation
Charge account
Liability account
Accrual account
Distribution combination
Accounting period
Subledger Accounting rules

If accounting is not allowed because of a hold, the invoice may not move further in the payment cycle.

Step 9: Check Approval Workflow

Even after matching and validation, invoice approval may still be required.

Check:

Is invoice approval enabled?
Is invoice stuck with approver?
Was invoice rejected?
Is approval rule configured correctly?
Is the approver inactive?
Is the approval notification pending?

This is important for both Payables and Procurement processes.

Step 10: Check Payment Readiness

Once invoice is matched, validated, and approved, it becomes eligible for payment.

If payment is not happening, check:

Invoice due date
Payment terms
Payment method
Payment currency
Supplier bank details
Payment hold
Payment process request
Pay group
Supplier site payment setup

This is where P2P moves from invoice processing to payment processing.

Technical Consultant View

For Oracle Fusion Technical Consultants, P2P is one of the most important areas because many reports and integrations are built around it.

Common technical requirements include:

Purchase requisition reports
Purchase order reports
PO approval status reports
Receipt reports
PO vs receipt reconciliation
PO vs invoice reconciliation
Invoice hold reports
Unpaid invoice reports
Supplier payment reports
Accrual reconciliation
OIC integrations with suppliers
Third-party invoice import
Supplier portal integrations
Approval notification reports
BIP and OTBI dashboards

A technical consultant should understand the functional process behind the data.

For example, if a business asks for a “pending invoice report,” you should understand whether they mean:

Invoice not validated
Invoice on hold
Invoice not approved
Invoice not accounted
Invoice not paid
Invoice matched but blocked
Invoice imported with errors

This is why process knowledge matters even for technical consultants.

Common OIC Integration Scenarios in P2P

1. Supplier Invoice Import

Suppliers send invoice data through an external portal or third-party system.

OIC receives the data, maps it, validates it, and sends it to Oracle Fusion Payables.

Important checks:

Supplier number
Supplier site
Invoice number
Invoice date
PO number
PO line
Amount
Tax
Currency
Attachment
Duplicate invoice

2. PO Communication to Supplier

Oracle Fusion creates and approves a purchase order.

The PO is sent to the supplier through email, supplier portal, EDI, or integration.

Important checks:

PO status
Supplier communication method
Payload
Supplier site
Contact email
Integration response

3. Receipt Integration from WMS

A warehouse system receives goods and sends receipt confirmation to Oracle Fusion.

Important checks:

PO number
Item
Quantity received
Receipt date
Warehouse
Shipment reference
Error response

If receipt is not created correctly, invoice matching may fail.

4. Invoice Hold Notification

OIC can be used to notify business users when invoices go on hold.

Example:

Invoice validation fails due to quantity variance.

OIC sends an email or Teams notification to procurement and finance users.

This improves visibility and reduces payment delays.

Best Interview Answer

Question:

PO is approved and goods are received, but supplier invoice is on hold or not matching. What will you check?

Answer:

I will first check the purchase order status to confirm that the PO is approved, open, and valid for invoicing. Then I will check the supplier and supplier site used on the PO and invoice.

Next, I will verify the receipt details because if the invoice match option is receipt-based or three-way matching is enabled, the invoice quantity must align with the received quantity within tolerance.

After that, I will check invoice validation status and review the exact hold reason. The issue may be due to quantity variance, price variance, amount variance, missing receipt, tax issue, invalid distribution, duplicate invoice, or approval hold.

I will also review invoice options, matching setup, quantity and amount tolerances, tax setup, accounting setup, and approval workflow.

If the invoice or receipt is coming from an external system, I will check OIC integration logs, payload, mapping, response message, and failed records.

This approach helps identify whether the issue is in Purchasing, Receiving, Payables, setup, workflow, or integration.

Final Thoughts

Oracle Fusion P2P is not just a procurement process.

It is a complete business cycle connecting procurement, receiving, payables, payments, accounting, and integrations.

For interviews, do not prepare only the basic flow.

Prepare real scenarios like:

PO approved but not communicated
Goods received but invoice not matching
Invoice on quantity variance hold
Invoice on price variance hold
Receipt missing for three-way match
Invoice validated but not approved
Invoice approved but not paid
Payment processed but accounting not created

The strongest candidates are those who can explain what broke, where to check, and how to troubleshoot step by step.

Definitions help you answer basic questions.

Scenarios prove real project understanding.