Share
ReportHello,
My company is experiencing an inconvenience in the vendor invoice workflow process. Our AP clerk creates the invoices and submit them to workflow. Workflow will send the invoice to another user for approval. The user approves the invoice and then workflow posts the invoice. During the posting process, several validations occur in \Classes\PurchInvoiceJournalCreate\Check. If any of these fail, the workflow stops with an error. The AP clerk does what is necessary to resolve the validation issues and then submits the invoice again. This goes back to the other user for approval. At this time, the approving user is either (a) confused if we are purchasing the same materials again or (b) annoyed that they have to go review and approve the same invoice that they already approved. To improve the quality of life for our vendor invoice workflow process, my company is suggesting that we add the validation checks which occur during the invoice posting process prior to the approval so that if a validation check fails then the submitting user can address it before it goes to the approving user.
Does anyone see any problems with this approach? I believe an invoice could get past the validation prior to approval and fail the validation at posting time for several reasons but a large number of the errors that we see would be caught by this. I'm looking for suggestions on whether there is any problem adding the invoice posting validations prior to the approval. I'm not sure exactly how I'll do this yet. My thought is to add a new automated task to the workflow to call my custom validation and somehow trigger the PurchInvoiceJournalCreate\Check logic. Throwing an exception to stop the workflow if the validation fails or allowing the workflow to continue on to the approval process if the validations are successful. Does anyone see a flaw with this approach?
All responses (
Answers (
35
