Name: Managing Invoice Exception Types in SAP Ariba Buying and Invoicing
Uploaded: 2024-9-18
Duration: 270 s
Description: Learn how SAP Ariba Buying and Invoicing allows Accounts Payable specialists to manage invoice exception types to streamline the invoice reconciliation process.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div><div><div><div><div><div><div>Learn how SAP Ariba Buying and Invoicing allows Accounts Payable specialists to manage invoice exception types to streamline the invoice reconciliation process. </div></div></div></div></div></div></div></div></div></div></div></div>

Managing Invoice Exception Types in SAP Ariba Buying and Invoicing

This video focuses on invoice exception types and how administrators can manage them. Invoice exception types describe the situations that result in exceptions during the invoice reconciliation process. The default configuration defines typical validation rules for an extensive set of possible invoice exception types. These exception types handle situations such as matching exceptions such as those for unmatched invoice or line item. General exceptions, such as those for shipping charges or tax amounts. Purchase order exceptions, reflecting differences between an order and an invoice. Contracts exceptions, reflecting differences between a contract and an invoice. Payment exceptions, such as differences in payment terms. Tax calculation exceptions, used to verify the tax amount on invoice line items. Receiving exceptions define exception types based on received quantities. Administrators can manage invoice exception types using the invoice exception types task in the invoicing manager workspace of the SAP Ariba Invoice Management solution or the Procure to Pay Manager workspace for SAP Ariba Buying and Invoicing. You can create a new invoice exception type or modify an existing invoice exception type. Let us have a look at the main fields in the exception creation wizard. Unique name, the unique internal identifier for the invoice exception type. You cannot modify this field in edit mode. Name, the display name for the invoice exception type. Header only, if true, the validation considers only header level fields. Invoice source specifies the invoices to apply this exception type to based on the source document for the invoice, such as purchase order or no release contracts. A value of all documents means the exception type applies to invoices from all invoice sources. Refine invoice source by conditions, lets you further refine the type of source document to which you want to apply the exception type. For example, buyers might want to raise certain invoice exceptions for service order invoices and other invoice exceptions for invoices for material goods. Applied to specific invoice types, lets you limit the types of invoices the exception type applies to. Standard invoices, credit memos, line item credit memos, line item debit memos. Field path to validate is the field being validated, while field path to validate against is the field as though the invoice field to be used for comparison. This path often names a field on the purchase order, accessible from the invoice reconciliation document. Tolerance operation is a value that specifies how the tolerance is chosen. If the tolerance operation is not specified, the tolerance is not checked and only an exact match is valid. Absolute tolerance is typically combined with a percentage tolerance using the OR operator. For example, if you specify $5 or 1.05%, items with tax under $5 are ignored and items with tax over $5 are checked to make sure the amount is within the designated percentage. The absolute rank determines the order for checking exceptions when multiple exceptions exist on the invoice. Auto-reject indicates whether failure of the validation causes the automatic reconciliation engine to reject the invoice reconciliation document. A value of YES means an exception of this type causes the invoice to be auto-rejected. Ignore auto-accept indicates whether the exception type disables auto-accept. If this field is set to yes, auto-accept is disabled when exceptions of this type are present. If this field is NO, exceptions of this type have no effect on auto-accept. Group, the group field specifies the unique identifier of a group. Members of this group are authorized to reconcile exceptions of the invoice exception type. The Requestor-Allowed Rule determines whether the requester is given temporary permission to handle exceptions. Another aspect to note is that for exception rules to work, they must be active. If you need to add or modify multiple invoice exception types, SAP Ariba recommends you define your data in CSV files and run the Import Invoice Exception Types and Import invoice exception type validation data import tasks. This concludes our video on managing invoice exception types. Thank you for watching.