Purchase requisitions and payment requests are both crucial processes in the procurement cycle, helping manage and track spend, yet they serve different purposes and have distinct features. This article aims to clarify these two terms and help you understand each better.
In the corporate world, purchasing often involves complex workflows. To streamline these processes, organizations often use specialized software, further blurring the lines between these two closely related yet distinct concepts.
Purchase Requisition (PR)
A purchase requisition is the first formal step in the procurement process. It's a document generated by a department (like Marketing, IT, or HR) requiring certain goods or services from the Purchasing department.
Think of it as a shopping list that kickstarts the purchasing process. It helps Purchasing assess the need, negotiate with suppliers, and ensure purchases adhere to the organization's policies and financial constraints.
Purchase Requisition vs. Requisitions in Other Contexts
To avoid confusion, it's essential to differentiate PR from other types of requisitions, such as personnel requisitions in HR. A purchase requisition relates solely to procuring goods or services, not hiring employees.
Moreover, in some contexts, 'requisition' might refer to a request for internal resources (e.g., laptops for new hires). These are different from purchase requisitions, which are always external spend-related.
Purchase Requisition Workflow
The PR process typically begins when an employee identifies a need and creates a requisition using an internal system. It then moves through several steps: approval, sourcing (if necessary), purchase order generation, receipt of goods/services, and finally, payment request.
Each of these steps involves stakeholders (like department heads, budget owners, procurement personnel) and may require approvals, ensuring everyone stays informed and involved in the purchasing cycle.
Payment Request
A payment request is a direct ask to the Accounts Payable (AP) department to pay an invoice. It signifies the final stage in the procure-to-pay cycle, where services or goods have already been delivered, and payment is due.
Payment requests help AP settle liabilities accurately and on time. They may originate from the purchase order or, in some cases, directly from an accrued invoice entered into the system.
Payment Request vs. Purchase Requisition
The primary difference between these two lies in their timelines. Payment requests represent the tail end of the procurement process — the request to pay an invoice after receiving goods or services.
In contrast, purchase requisitions initiate the process, signaling the need to acquire something. Moreover, multiple purchase requisitions may culminate in one payment request, especially when consolidated based on payment terms or supplier.
Payment Request Workflow
The payment request workflow starts when an invoice hits the AP department. After matching it with the purchase order, the 'Invoice for Payment' status is updated. Subsequent steps include approval (based on organizational hierarchy and policies), payment execution, and recording in the general ledger.
.payment types vary depending on organizational preferences and negotiation with suppliers, ranging from checks and ACH to credit card payments or electronic funds transfers.
Understanding the nuances between purchase requisitions and payment requests enables better management of organizational spend, improved internal controls, and enhanced transparency across departments. Regularly reviewing and updating processes can maximize efficiency and ensure your organization benefits from the most effective procure-to-pay workflows.