Information Needed Before Creating a Requisition
Before entering a requisition, gather the information needed to describe the purchase accurately. The exact fields available can depend on the organization's Costpoint configuration and purchasing policies, but the request should provide enough detail for reviewers to understand what is needed and why.
- Item or service: Describe what the organization needs and include specifications where relevant.
- Quantity and estimated price: Enter the expected quantity and reasonable estimated cost.
- Required date: Identify when the goods or services are needed.
- Project and accounting information: Associate the purchase with the appropriate project, organization, account, or cost classification.
- Supplier information: Include a preferred supplier when applicable and permitted by procurement policy.
- Business justification: Explain the operational or project requirement supporting the request.
Preparing these details first makes Purchase Requisition Creation more consistent and gives approvers the context required to evaluate the request.
Steps to Create a Purchase Requisition in Costpoint
The practical workflow starts by opening the relevant requisition function in Costpoint and entering the required header and line-level information. The requester should identify the purchasing need, select or enter the appropriate accounting and project information, and add the goods or services being requested.
Each line should contain sufficient information for procurement to understand the requirement. Quantities, estimated costs, required dates, descriptions, and applicable project or account assignments should be reviewed before submission.
After the requisition is completed, the requester submits it for the applicable approval workflow. Depending on organizational rules, approval can involve project managers, department managers, procurement personnel, finance teams, or other authorized reviewers.
A purchase requisition is therefore an internal authorization step rather than the same document as a purchase order. Understanding this distinction helps users follow the correct handoff from an approved request to purchasing execution.
Reviewing and Approving the Requisition
Approval reviewers should verify that the requested purchase is justified, correctly coded, appropriately estimated, and aligned with available project or organizational funding. They may also review supplier information, required dates, purchasing policies, and whether the requested goods or services require additional procurement controls.
Online Purchase Requisition Software can support accessible requisition workflows by giving authorized users a structured environment for submitting requests, reviewing status, and supporting approval processes.
Organizations implementing an AI Purchase Requisition Software System can also apply automated document processing, policy checks, and other workflow controls around requisition intake and approval. These capabilities can complement the underlying Costpoint purchasing process.
From Approved Requisition to Purchase Order
Once the requisition receives the required approvals, procurement can determine the appropriate sourcing and purchasing action. Depending on policy, procurement may obtain supplier information, validate pricing, consolidate requirements, or proceed toward purchase order creation.
The distinction between a requisition and a purchase order is important: the requisition communicates an internal purchasing need, while the purchase order represents the authorized order issued to a supplier. Keeping these stages connected creates better visibility from request through supplier commitment.
A Purchase Order Vendor Portal can further support procurement workflows by providing a structured channel for supplier communication and purchase order information after purchasing execution.
Tracking Purchase Requisition Status
After submission, requesters and procurement teams need visibility into whether a requisition is pending approval, approved, returned for changes, converted into purchasing activity, or otherwise progressing through the workflow.
Purchase Requisition Tracking helps organizations monitor these stages and provides visibility into the movement of requests from initial submission toward purchasing execution. Clear status information can help procurement teams prioritize approved requirements and allow requesters to understand where their requests stand.
For organizations improving the overall procurement lifecycle, connecting requisition intake, approval, sourcing, purchase order creation, receiving, and invoice processing creates a more continuous procure-to-pay workflow.
How Requisitions Connect to Finance and AP
A requisition establishes an expected purchasing requirement that can later become a purchase commitment and supplier invoice. Accurate project and accounting information at requisition creation therefore supports downstream financial processing.
Once goods or services are purchased and invoiced, invoice processing can capture, validate, match, code, approve, and post supplier invoices against purchasing information. AP Automation Software can automate invoice processing and payment planning while maintaining controlled accounts payable workflows.
Requisition information can also support period-end financial analysis. Where goods or services have been received but the related invoice has not yet been processed, organizations may need to recognize appropriate accruals based on their accounting policies and close procedures.
After invoice approval, payments complete the supplier settlement process. Connecting these downstream activities with the original requisition provides finance teams with greater visibility into the lifecycle of purchasing commitments and cash outflows.
Best Practices for Creating Costpoint Requisitions
Accurate requisition entry improves the quality of the purchasing information that follows. Requesters should use specific descriptions, realistic estimates, correct accounting assignments, and required dates that reflect the actual business need.
- Verify project, organization, and account information before submitting the request.
- Provide enough detail for approvers and procurement staff to understand the requirement without additional clarification.
- Use consistent descriptions and units of measure for frequently purchased items.
- Review estimated amounts against applicable budgets and purchasing thresholds.
- Monitor the request after submission so returned or pending requisitions can be addressed promptly.
- Maintain supporting documentation when the purchase requires justification, specifications, quotations, or other approvals.
Following these practices makes the requisition a reliable starting point for procurement controls, supplier purchasing, invoice matching, and financial reporting.
Summary
Creating a purchase requisition in Costpoint involves documenting the purchasing need, entering accurate item and accounting information, submitting the request for approval, and tracking it through the procurement workflow. A properly prepared requisition provides the foundation for sourcing, purchase order creation, receiving, invoice processing, accruals, and payments. Consistent requisition practices improve purchasing visibility, financial control, and the connection between operational requirements and business spending.