(Missing) validation that an invoice, that is not fully coded (mandatory fields not coded) can be distributed in workflow
Currently it is possible to send (distribute) an invoice into the workflow despite not all mandatory fields are coded. There is no validation that prevents such a distribution. In the next step it gets stuck, because if not all mandatory fields filled, the approver has only possibility to reject (and thus send back to accounting) the invoice. That is not useful from a logical and operational point of view.
Only in post control (when sent to ERP) a validation exists, that prevents to send invoice, that lacks mandatory fields in coding, cannot be sent to ERP.
There should be already in distribution such validation in place, that prevents to send (distribute) a not fully coded invoice, that is an invoice that lacks mandatory fields, into workflow.
Gerhard Bachl
shared this idea
-
Gerhard Bachl
commented
Thank you for the feedback!
In our case the invoice first goes to the accountants, which code and distribute the invoice. So it applies for us, that "he person working in that step has knowledge about all details.". So we would like to force via settings (validation), that the invoice is fully coded before sending in workflow.
For other customer this might not apply. So what we recommend is, to have a possibility to set (activate) such validation in the company settings (e.g. like it exists for the same topic in the post control or other validation that are performed in distribution step like invoice is balanced). Then it can be activated when needed (as in our case) -
Thanks for your comment
The reason for being able to distribute the invoice from the distribute step without complete code string is because the approver might be the person adding for instance the cost center (but the account was added already in the distribute step)By forcing a complete coding string already in distribute will require that the person working in that step has knowledge about all details.
