You recently processed a payment for a vendor and later discovered that the payment was made in error and needs to be voided. While voiding the payment, you selected Cancel as the Invoice Action. After performing the invoice voiding, you notice that the invoice is not cancelled; instead, it has an Invoice Cancel hold applied to it. What is the reason for this?

When voiding a payment and selecting the 'Cancel' invoice action, the system attempts to change the invoice status to 'Canceled'. However, if the invoice has other payments applied to it (i.e., it was partially paid by the payment being voided and also by another payment), it cannot be canceled. Canceling it would create a data integrity issue, as a portion of the invoice would remain legitimately paid. In this scenario, the system prevents the cancellation and instead applies a system-generated "Invoice Cancel" hold, signaling that manual review and resolution are required.

A. An invoice date in a closed period would prevent accounting but not necessarily the cancellation itself; the system would post accounting in the next open period.
B. While an existing hold would prevent payment, it would not be the primary reason the system applies a specific "Invoice Cancel" hold during a void action.

1. Oracle Fusion Cloud Financials Documentation, "Using Payables Invoice to Pay," Chapter: "Processing Payments," Section: "Voiding Payments." (Explains the outcomes of voiding payments and the associated invoice actions).

2. Oracle Fusion Cloud Financials Documentation, "Using Payables Invoice to Pay," Chapter: "Processing Invoices," Section: "Invoice Holds and Releases." (Describes the different types of system-generated holds, including those related to payment actions).