Create a Requisition
Overview
Creating a requisition is the first operational step in the Procure-to-Pay lifecycle. A requisition formally requests approval to purchase goods or services from a supplier and ensures the request aligns with organizational policies and budget controls.
This article explains how requisitions are created in relation to SupplierGateway, what role SupplierGateway plays in the process, and how internal users ensure suppliers are ready before a requisition is submitted.
How Requisitions Are Created in Relation to SupplierGateway
Requisitions are not created directly in SupplierGateway. They are created in the organization’s enterprise procurement or ERP system. SupplierGateway supports the requisition process by ensuring that supplier records are established, active, and ready for engagement before a requisition is submitted.
SupplierGateway acts as a supplier readiness and enablement checkpoint, reducing delays later in the Procure-to-Pay process.
Prepare to Create a Requisition
Before creating a requisition, internal users should confirm that the supplier exists and is active in SupplierGateway.
Directional Guidance
Open the Supplier Management app from the main menu
Navigate to Supplier Status
Locate the supplier associated with the planned requisition
Outcome:
You can confirm that the supplier exists in the platform and review their current status.
Confirm Supplier Readiness
From the Supplier Status view, users verify that the supplier:
Has completed required registration steps
Is in an active status
Does not have outstanding issues that would block engagement
Outcome:
The supplier is confirmed as ready for use in a requisition.
If the supplier is not ready, follow supplier management processes before proceeding.
Create the Requisition in the Enterprise System
Once supplier readiness is confirmed, the requisition is created in the organization’s procurement or ERP system.
At a high level, this typically includes:
Selecting the supplier
Defining the goods or services requested
Entering quantities and estimated costs
Providing a business justification
Approval routing is applied according to enterprise rules.
Outcome:
The requisition is submitted for approval in the enterprise system.
How SupplierGateway Supports the Requisition Process
Although requisitions are created externally, SupplierGateway supports the process by:
Providing authoritative supplier identity and status
Preventing requisitions from being created for inactive or unregistered suppliers
Reducing downstream issues during purchase order and invoicing stages
SupplierGateway data is often referenced or integrated into enterprise systems during requisition creation.
Key Terms
Requisition
A formal request to purchase goods or services that must be approved before purchasing can proceed.
Supplier Status
An indicator in SupplierGateway that reflects whether a supplier is active and ready for engagement.
Supplier Management Application
The area of SupplierGateway where internal users review supplier records and supplier readiness.
Enterprise Procurement System
The external system where requisitions and approvals are created and managed.
Summary
Creating a requisition begins with confirming supplier readiness in SupplierGateway and then submitting the requisition in the organization’s enterprise procurement system. SupplierGateway does not create requisitions directly but plays a critical role by ensuring suppliers are properly onboarded and active, helping prevent delays and issues later in the Procure-to-Pay lifecycle.
Metadata
Domain: Procure-to-Pay
Article Type: Procedure
Audience: Administrators, internal enterprise users, procurement stakeholders
Comments
0 comments
Please sign in to leave a comment.