Request to Pay Process Uses Technology To Gain An Edge
Published on: 6 February 2018
There are many stakeholders in the purchase cycle. “Who is responsible for what” is often muddled between layers of multple business processes and the various roles employees play.
It’s not that roles may be unclear about purchasing policies, but rather a lack of transparency by design. This is particularly relevant in organizations that are reliant on paper-based processes, or when their ERP does not have the ability to provide flexible approval workflows.
As a result, organizations are looking to optimize the purchase process to improve accountability as well as visibility. This can be done with automated Request to Pay.
Read full article
With Request-to-Pay automation, all of the stakeholders in the purchase cycle have a visible role to play. Visible in the sense that any relevant activity can be seen in real time – what changes were made, when they took place, and who made them.
The roles in a request to pay workflow include the following:
Requestor – asks for the goods and services
Approver – approves of the expenditure
Purchaser – acquires the goods or services
Receiver – receives the goods or services ordered
AP Staff – ensures that payment is made
Find out more about Rillion AP Automation here.