SINV-13111

Previously, external cXML invoices imported into SAP Ariba Buying and Invoicing or SAP Ariba Invoice Management that contained errors were being submitted, but they couldn't be approved until the errors were resolved. When the approver denied the invoice, the preparer/requester was unable to resolve the errors, or add any comments or attachments. This created more work for the approver and invoices were often stuck in the approval process or had to be recreated. Now, cXML invoices can't move forward in the approval flow until the errors are resolved, and if an invoice is denied, the preparer/requester can resolve the errors, add comments or attachments, and submit it again.

Customers who use the cXML API have all invoices getting automatically created in "Submitted" status, even if they contain validation errors. These invoices then go through the invoice approval process without the validation errors being fixed. As a consequence, the preparer/requester is unable to resolve the errors, or add any comments or attachments. These invoices have then to be re-created from scratch, creating limited efficiency in the process.

Now, cXML invoices can't move forward in the approval flow until the errors are resolved, and if an invoice is denied, the preparer/requester can resolve the errors, add comments or attachments, and submit it again. Customers benefit from increase efficiency and flexibility when leveraging the cXML invoice import API.

Buyer

https://help.sap.com/docs/SAP_Ariba/978b7e36451a4c2c85321a3ef6f3a7e5/ba97239000da43fdbed4cd5ee8dc2707.html?locale=en-US&state=PRODUCTION&version=cloud

Automatically On