![]() Approval workflow is triggered by changing the parking reason. Based on the parking reason workflow starts. After conversion of DP document into SAP parked invoice : Appropriate parking reason has to be provided.Approval workflow can be started by clicking ‘Submit for Approval’ option. DP processing stage : Process type needs to be configured accordingly (steps to configure the process type are written below).NOTE: Above mentioned roles are the basic roles involved in the IAP however one can create additional roles. AP Processor : Member of Accounts Payables team responsible for dealing with invoices.Approver : Person responsible for approving the invoices.Requester : Person who has requested the goods or services.Coder : Person responsible for entering accounting data.Important roles involved in invoice approval process: ![]() Approval process ends when the invoice is approved and posted or deleted or rejected. Approval can be delayed by sending the invoice to AP Processor first. PO invoices have only one step approval but can be customized for multilevel approval. ![]() Non-PO invoices support multilevel approval. Approval process is available for both PO and Non-PO based invoices. The approval system is easily configurable and highly customized with provision of multi-level approval. OpenText VIM provides the facility to approve the invoices before they are created in SAP. It also covers linkage of process types and chart of authority in invoice approval process along with their configurations. ![]() The document provides the overview of invoice approval process cycle in OpenText VIM for both PO and Non-PO invoices along with important configuration steps involved. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |