Invoice exceptions
Invoice exceptions are issues that are identified in an invoice during invoice processing.
The Accounts Payable Operations exception engine automatically identifies discrepancies in invoices and lists them as invoice exceptions in the Source-to-Pay Workspace workspace. The Accounts Payable Specialist can analyze the identified invoice exceptions and take appropriate action to resolve them.
The Accounts Payable Operations exception engine is run for the PO invoices that are in either the PO matching completed or Exceptions found state.
The Accounts Payable Operations exception engine is run for Non-PO invoices that are in the Accepted or Exceptions found state.
| Invoice exception | Description | Do these steps to resolve the invoice exception | Applicable to | |
|---|---|---|---|---|
| Invalid or blocked supplier | This exception occurs in one of the following scenarios:
This exception is a header-level exception. |
To resolve this invoice exception, do the following:
|
PO invoice and Non-PO invoice | |
| Insufficient Funds (Quantity variance) | This exception occurs when the total quantity of previously billed invoices and the current invoice, which is in-process becomes more than the respective purchase order line quantity. This exception is a line-level exception. To resolve this invoice exception, you must edit the purchase order. For more information, see Edit a purchase for an Insufficient Funds invoice exception. |
To resolve this invoice exception, you must edit the purchase order. For more information, see Edit a purchase for an Insufficient Funds invoice exception. | PO invoice | |
| Insufficient Funds (Line amount variance) | This exception occurs when purchase order lines don't have sufficient funds left to process the current invoice, which is in-process. This exception is a line-level exception. |
To resolve this invoice exception, you must edit the purchase order. For more information, see Edit a purchase for an Insufficient Funds invoice exception. | PO invoice | |
| Insufficient Goods Receipt | This exception occurs when one or more lines of an invoice don’t have sufficient receipts to process the invoice. This exception is a line-level exception. |
|
PO invoice | |
| Valid coding required | This exception occurs when one or more lines of an invoice cost is distributed across multiple cost centers or general ledger accounts. When the cost is split across multiple cost centers, the cost center field on the
invoice line is read-only and allows one type of allocation type in the cost. This exception is a line-level exception and applies for general ledger account. |
To resolve this invoice line exception, do the following:
|
PO Invoice and Non-PO invoice | |
| Missing required information | This exception occurs when one or more fields of the following are missing on the invoice:
This exception is a header-level exception. |
To resolve this invoice exception, do the following:
|
PO Invoice and Non-PO invoice | |
| Missing or Invalid Business Owner | This exception occurs when the business owner of the invoice is missing or inactive or is different from the business owner mentioned in the purchase order (if invoice is of type PO). This exception is a header-level exception. |
To resolve this invoice exception, do the following:
|
PO Invoice and Non-PO invoice | |
| Over tax amount variance | This exception occurs when the supplier tax amount is greater than the system tax amount. | To resolve this invoice exception, do the following:
|
PO Invoice, Non-PO invoice, and Credit memo | |
| Under tax amount variance | This exception occurs when the supplier tax amount is lesser than the system tax amount. | To resolve this invoice exception, do the following:
|
PO Invoice, Non-PO invoice, and Credit memo | |
| Tax validation failed | This exception occurs when the tax is not validated due to integration error | To resolve this invoice exception, do the following:
|
||
| Tax validation expired | Tax information is changed after the invoice execution, then Tax validation expired failed exception is raised. |
|
||
| Under tax amount variance (Invoice line) | Tax amount on an invoice line is lesser than the tax response received for the line item through tax engine |
|
||
| Under tax amount variance (Invoice header) | Total tax amount on the invoice header is lesser than the total tax for the invoice received through tax engine |
|
||
| Over tax amount variance (Invoice header) | Total tax amount on the invoice header is greater than the total tax of the invoice received through tax engine |
|
||
| Over tax amount variance (Invoice line) | Tax amount on the invoice line is greater than the tax of the invoice line item of the invoice received through tax engine |
|
||
| Invoice isn’t balanced | This exception occurs when sum of the subtotals of the invoice lines must match the sub total amount in the header. | To resolve this invoice exception, do the following:
|
PO Invoice, Non-PO invoice, and Credit memo | |
| Insufficient Funds (Header amount variance) | This exception occurs when purchase order doesn’t have sufficient balance left to process the invoice. | To resolve this invoice exception, do the following:
|
PO invoice | |
| Line unit price variance | This exception occurs due to difference in unit price of invoice line and PO. | To resolve this invoice exception, do the following:
|
PO invoice, Credit memo | |
| Incomplete credit memo | This exception occurs when any of the following are missing on a credit memo invoice:
|
To resolve this invoice exception, do the following:
|
Credit memo | |
| Insufficient billing amount on purchase order | This exception occurs when purchase order doesn't have sufficient billing quantity or amount to process the credit memo invoice. | To resolve this invoice exception, do the following:
|
Credit memo | |
| Missing tax information | This exception occurs when tax line information is missing in an invoice. This is a header level exception. | To resolve this invoice exception, do the following:
|
PO Invoice, Non-PO invoice, and Credit memo | |
| Missing tax code details | This exception occurs when tax code details are missing in one or more invoice lines. This exception applies to PO invoice, non-PO invoice and credit memo. This is a line level exception. | To resolve this invoice exception, do the following:
|
PO Invoice, Non-PO invoice, and Credit memo | |
| Currency mismatch | This exception occurs when the currency on an invoice does not match the currency on the associated purchase order when purchase order mapping is disabled and the invoice is still in draft state. The cost allocation data is preserved even when the purchase order mapping is turned off. | To resolve this invoice exception, do the following:
|
PO invoice, Credit memo |
By default, the exception engine is configured to run once every 5 minutes through the Exception Monitoring Job. This is a scheduled job, which is inactive in the state by default. For information on how to activate the scheduled job, see Activate the Exceptions Monitoring Scheduler.
However, you can also run the exception engine manually. For more information, see Check for invoice exceptions on a single invoice.
When you run the exception engine manually on a single invoice, it checks for exceptions only on that invoice, whereas the automated exception engine checks for exceptions on all the invoices that are valid for exception check.
You can bypass an exception in situations where that exception is not applicable to an invoice. For more information, see Bypass an invoice exception.
The Accounts Payable Operations exception engine finds exceptions and lists them in the list page of the Source-to-Pay Workspace. View the list of exceptions by navigating to .
- Navigate to .
- Navigate to .
The Accounts Payable Specialist can analyze the invoice exceptions, create exception tasks, and assign these tasks to the relevant individuals to fix the exceptions and resolve the case. For more information, see Work on an invoice exception.