e-Requisition
Purchasing software
Procurement software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if e-Requisition and its alternatives fit your requirements.
Free Trial unavailableFree version unavailable
Small
Medium
Large
-
What is e-Requisition
e-Requisition is a procurement requisitioning application used to create, route, and approve purchase requests before converting them into purchase orders. It is typically used by employees requesting goods/services and by procurement and finance teams enforcing approval policies and budget controls. The product focuses on requisition intake, approval workflows, and basic purchasing controls rather than full source-to-pay suite coverage. Implementations commonly emphasize configurable approval routing and auditability for internal purchasing compliance.
Structured requisition intake
The product standardizes how employees submit purchase requests, helping reduce ad hoc purchasing and incomplete request data. It typically captures requester, cost center, item/service details, and supporting documentation in a consistent format. This structure supports downstream purchasing processes such as PO creation and receiving. It also improves audit trails compared with email- or spreadsheet-based requisitions.
Configurable approval workflows
e-Requisition commonly supports multi-step approval routing based on rules such as amount thresholds, department, or category. This helps organizations enforce purchasing policies and segregation of duties. Approval history and timestamps provide traceability for internal controls. Workflow configuration can reduce manual follow-ups for procurement teams.
Policy and budget controls
Requisitioning tools often include controls such as required fields, spend limits, and justification prompts to support compliance. They can route exceptions for additional review and create an auditable record of approvals. This is useful for organizations that need tighter governance without deploying a broader procurement suite. It can also reduce rework caused by non-compliant requests.
Limited suite breadth
A requisition-focused product may not cover strategic sourcing, contract lifecycle management, supplier risk, or advanced spend analytics. Organizations needing end-to-end source-to-pay capabilities may require additional modules or separate systems. This can increase integration and process complexity. Fit-for-purpose depends on whether requisitioning is the primary gap or part of a broader transformation.
Integration dependency
Value often depends on integration with ERP/finance systems for vendor masters, chart of accounts, budgets, and PO/invoice processing. If integrations are not available out of the box, implementation can require custom work and ongoing maintenance. Data synchronization issues (e.g., cost centers, approvers, suppliers) can affect user experience and controls. Integration scope should be validated early in evaluation.
Unclear product provenance
“e-Requisition” is a generic product name used by multiple vendors and in-house solutions, which makes vendor verification and feature expectations difficult without a specific publisher. Product capabilities, security posture, and support model can vary significantly by seller. Buyers should confirm the exact vendor, version, and deployment model before comparing it to established procurement platforms. Documentation and public references may be limited depending on the provider.
Seller details
Unsure (product name used by multiple vendors)
Unsure
Unsure
