Managing Custom Invoice Hold for Partial PO Invoicing in Oracle Fusion Payables Using REST APIs

Purchase orders are essential in Oracle Fusion Cloud Payables for validating supplier invoices against received goods before payment. However, standard matching rules may not always meet specific business needs. For instance, if a purchase order is fulfilled but an invoice is only partially matching, the business might want to review the transaction before approving payment.

To address this, a custom invoice hold can be implemented using Oracle Fusion Payables and REST APIs. This approach enables the introduction of an additional validation step without altering the existing purchase order matching process.

Let's consider a transaction where 10 units are ordered, fully received, but only 4 units are invoiced. While this is typically acceptable under standard matching, the business requires an extra control. The invoice should be placed on hold for review until the discrepancy is addressed.

Standard Oracle Payables matching supports two, three, and four-way validation, ensuring invoices align with purchase orders and receipts. In our case, the custom requirement goes beyond standard matching. If the invoiced quantity is less than the received quantity, the invoice must be held for review. This evaluation will be achieved through a custom REST API integration.

The process involves several steps: creating a purchase order in Procurement, completing a receiving transaction, and generating an invoice in Payables. Following invoice creation, a REST API is used to retrieve the required data, compare the invoiced quantity with the received quantity, and apply the custom invoice hold. This final step ensures that the invoice remains unavailable for payment until the discrepancy is reviewed and resolved.

This solution allows organizations to enforce bespoke invoicing policies while maintaining the integrity of standard purchasing and payment procedures.