Invoice exceptions
Summarize
Summary of Invoice Exceptions
Invoice exceptions are discrepancies detected during invoice processing by the Accounts Payable Operations exception engine in ServiceNow. These exceptions are automatically identified and listed in the Source-to-Pay Workspace, allowing Accounts Payable Specialists to analyze and resolve them effectively. The exception engine processes PO invoices in the "PO matching completed" or "Exceptions found" states, and Non-PO invoices in the "Accepted" or "Exceptions found" states.
Show less
Common Invoice Exception Types and Resolution Steps
- Invalid or Blocked Supplier: Occurs when supplier information is missing, mismatched with the purchase order, absent in the Supplier Legal Entity Mapping table, or supplier holds are active. Resolution involves updating supplier details or removing holds with appropriate roles.
- Insufficient Funds (Quantity or Line Amount Variance): Happens when invoice quantities or amounts exceed purchase order limits. Specialists must edit the purchase order to resolve.
- Insufficient Goods Receipt: Raised when receipts are insufficient for invoice lines. Resolution varies depending on whether Sourcing and Procurement Operations (PSM) is installed—either by completing receipt tasks or manually creating exception tasks.
- Valid Coding Required: Triggered by missing ledger account, tax code, or cost center on invoice lines; specialists must populate these fields.
- Missing Required Information: Header-level exception for missing payment terms, invoice type, supplier, amount, date, or legal entity; specialists must enter the missing data.
- Missing or Invalid Business Owner: Occurs if the business owner is missing, inactive, or mismatched; update the business owner field accordingly.
- Tax Amount Variances (Over or Under): When supplier tax and system tax amounts differ; specialists can adjust and accept either tax amount.
- Invoice Not Balanced: When the sum of invoice line subtotals does not match the header subtotal; corrections are needed to balance amounts.
- Line Unit Price Variance: Due to differences between invoice and PO line unit prices; update invoice line prices to match PO.
- Credit Memo Exceptions: Include incomplete credit memo data and insufficient billing amounts; require updating original invoice references and correcting amounts.
- Invoice Cost Allocation: When cost allocation on lines does not equal line subtotals; specialists must correct invoice line amounts.
Exception Engine Operation
The exception engine is configured to run every 5 minutes by default through the Exception Monitoring Job, which is initially inactive. Customers can activate this scheduled job or run the engine manually on individual invoices for targeted checks. Manual runs focus on single invoices, while the automated engine covers all eligible invoices.
Managing and Resolving Exceptions
- Exceptions appear in the Source-to-Pay Workspace under Accounts Payable Workspace lists for easy tracking.
- Accounts Payable Specialists analyze exceptions, create and assign tasks to relevant users for resolution.
- Specialists can bypass exceptions when not applicable.
- Related tasks and detailed invoice line information help clarify the reasons behind exceptions, especially for issues like Insufficient Goods Receipt.
Practical Benefits for ServiceNow Customers
This functionality enables your Accounts Payable team to automate the detection of invoice discrepancies, streamline exception management, and ensure accurate invoice processing. By leveraging defined roles and workspace tools, you can reduce payment delays, enforce compliance with purchase orders, and maintain data integrity across invoice processing workflows.
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 are missing the following information:
This exception is a line-level exception. |
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 |
| 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 |
| Invoice cost allocation | This exception occurs when the cost allocated on invoice lines is not equal to the sub total of the invoice lines amount. | To resolve this invoice exception, do the following:
|
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.