Purchase requisition software manages the workflow from internal purchase request to approved purchase order. It answers three questions: who is allowed to request what, who needs to approve it, and how does the approved request become an order in the ERP or accounting system. ERP procurement modules from SAP, Oracle, NetSuite, and Microsoft Dynamics include requisition functionality, but they are designed for enterprises with dedicated procurement departments and formal sourcing processes. Mid-market companies (100-2,000 employees, $20M-$500M revenue) running these ERPs consistently hit the same problem: the requisition module is either too rigid to match their actual approval workflows or too complex for non-procurement staff to use without training. Custom purchase requisition systems cost $40,000 to $100,000 and integrate with the existing ERP, matching the approval logic the organization actually follows instead of the logic the ERP vendor assumed.
What are the four gaps in ERP purchase requisition modules?
These gaps appear across SAP MM, Oracle Procurement Cloud, NetSuite Procurement, and Dynamics 365 Supply Chain Management. They are design assumptions, not bugs. The ERP vendor built for a specific buyer profile (large enterprise, formal procurement team, 50+ approvers), and mid-market companies do not match that profile.
| Gap | What the ERP Does | What Mid-Market Operations Needs | Current Workaround |
|---|---|---|---|
| Approval routing | Fixed hierarchy: manager, then director, then VP, then finance. Same for every request type. | Dynamic routing based on amount, category, vendor, budget status, and requestor department. A $500 office supply request should not need VP approval. | Email-based approval with manual PO creation after verbal sign-off. |
| User experience | ERP interface. Requires training. Multiple screens to submit a single request. | Simple form that any employee can complete in under 2 minutes. Mobile-friendly. No ERP training required. | Requestors email a manager who enters the PO themselves, bypassing the requisition process entirely. |
| Budget visibility | Shows remaining budget at GL account level. Updated when invoices post, not when requests are approved. | Real-time committed spend: approved requests that have not yet become POs or invoices are already deducted from available budget. | Finance maintains a separate budget tracker in Excel updated weekly. |
| Vendor management | Full vendor master with compliance tracking, sourcing events, and supplier scorecards. | Preferred vendor list with current pricing. Auto-populate PO fields from the last order to the same vendor. | Requestors look up vendor details in email history or call the vendor directly. |
How do the major ERP procurement modules compare?
| ERP | Requisition Strength | Mid-Market Gap | Custom Module Feasibility |
|---|---|---|---|
| SAP MM / S4HANA | Comprehensive procurement with deep approval chain configuration | Configuration requires ABAP development or Fiori customization. Overkill for <500 POs/month. | High. BAPIs and OData APIs support external front-ends. |
| Oracle Procurement Cloud | Strong sourcing and supplier management for large enterprises | Licensing cost. Mid-market companies pay enterprise pricing for features they do not use. | Medium. REST APIs available but customization is vendor-controlled. |
| NetSuite Procurement | Integrated with financials. Good for companies already on NetSuite. | Approval workflows are basic. Multi-condition routing requires SuiteScript development. | High. SuiteScript and REST APIs make external front-ends straightforward. |
| Dynamics 365 SCM | Good workflow engine with Power Automate integration | User interface complexity. Non-procurement users find it difficult to navigate. | High. Dataverse APIs and Power Platform make custom front-ends natural. |
When should you build a custom purchase requisition system?
Build custom when the ERP's accounting and PO creation work correctly but the requisition workflow does not match your organization. If your approval logic says "under $1,000 needs department head only, $1,000-$10,000 needs department head plus finance, over $10,000 needs CFO, and any IT purchase over $500 needs IT director regardless of amount," and the ERP cannot model this without custom development, a standalone requisition front-end is faster and cheaper than reconfiguring the ERP.
Do not build custom when the ERP's requisition module works and adoption is the only problem. If the workflow is correct but employees do not use it because of training gaps, the fix is training and process enforcement, not a new system. Custom software solves structural problems (wrong workflow logic, missing budget visibility, poor integration), not behavioral problems.
What does a custom purchase requisition system cost?
| Component | What It Includes | Cost Range |
|---|---|---|
| Requisition form + approval engine | Web and mobile form, dynamic approval routing, email/Slack notifications, audit trail | $25,000-$45,000 |
| ERP integration | Approved requisitions auto-create POs in the ERP. Budget data pulled from ERP GL. | $15,000-$35,000 |
| Budget dashboard | Real-time committed spend by department, category, and GL account. Alerts when budget thresholds are reached. | $10,000-$25,000 |
| Vendor catalog + pricing | Preferred vendor list, contracted pricing lookup, auto-populated PO fields from vendor master | $8,000-$20,000 |
A typical mid-market deployment (requisition form, approval engine, ERP integration, and budget dashboard) runs $55,000-$105,000 with an 8-14 week timeline. The ROI case is straightforward: if procurement staff spend 15 hours per week on manual PO creation, approval chasing, and budget reconciliation, that is $39,000 per year in labour cost alone. Add the cost of maverick spending (purchases made outside the approval process because the formal process is too slow), which typically runs 10-20% of total discretionary spend, and the payback period is under 12 months.
What does the integration architecture look like?
The custom requisition system sits in front of the ERP, not beside it. Employees interact with the custom system (web form, mobile app, Slack/Teams integration). The custom system handles the workflow: validation, routing, notifications, and escalation. When a requisition is fully approved, the system creates the purchase order in the ERP automatically via API, populating all required fields (vendor, items, quantities, GL codes, cost centres) from the approved requisition data.
The ERP remains the system of record for purchase orders, accounts payable, and vendor payments. The custom system is the workflow layer that ensures every PO in the ERP went through a proper approval process with full audit trail. This architecture means finance teams continue using the ERP for everything they do today. Only the requisition and approval steps change.
In enterprise software integrations Madgeek has delivered, the Tejas Networks platform replaced paper-based approval processes with a digital workflow system that reduced approval processing time by 90%. The same architectural pattern (custom workflow front-end, enterprise system of record in the back) applies to procurement: the ERP handles what it does well (accounting, PO management, AP), and the custom system handles what it does not (user-friendly request submission, dynamic approval routing, real-time budget visibility).
Need a team to build this for your business?