```json { "title": "Managing Purchase Requisitions and Budget Controls in ERPNext", "url": "https://aavatto.com/blog/purchase-requisition-software-erpnext/", "datePublished": "2026-10-24", "dateModified": "2026-10-23", "language": "en-US", "description": "How ERPNext works as purchase requisition software: Material Requests, approval workflows and budget checks that stop overspend before a PO.", "author": "Aavatto", "publisher": "Aavatto - Frappe & ERPNext Experts | Custom Development, Implementation & Support" } ``` # Managing Purchase Requisitions and Budget Controls in ERPNext If you're evaluating  **purchase requisition software, ERPNext**  probably already does most of the job. In ERPNext the requisition is a document called a Material Request. The Budget feature can check each request against a cost-centre or project budget before it becomes a purchase order. The open questions are how you configure both, and where the checks quietly don't apply. **What is purchase requisition software in ERPNext?**  ERPNext handles purchase requisitions through the Material Request document. A department raises a request for items, it moves through an approval workflow you define, and approved requests convert into RFQs or purchase orders. Budgets set against a cost centre or project can warn about or block requests that would exceed the allocated amount.This guide is for purchase heads at manufacturing and distribution companies. It covers how the requisition flow works, how budget control behaves at each stage, and the gaps we most often find when reviewing live setups. ## How ERPNext works as purchase requisition software A Material Request is the internal "we need this" document. It carries the items, quantities, required-by date, the requesting warehouse, and optionally a cost centre or project. It has a type, and the type decides what happens next: Material Request typeWhat it's forWhat it converts intoPurchaseBuying from a supplierRequest for Quotation, Supplier Quotation, or Purchase OrderMaterial TransferMoving stock between warehousesStock Entry (transfer)Material IssueIssuing stock for consumptionStock Entry (issue)ManufactureTriggering productionWork OrderCustomer ProvidedMaterial supplied by the customer Receipt against the customer For procurement, the Purchase type matters most. Once a Purchase request is submitted, the buying team can pull its lines into an RFQ to collect competing quotes, or straight into a purchase order for known suppliers. ERPNext tracks ordered and received quantity against each request line. A request shows Pending, Partially Ordered or Ordered, so you can see which needs are still open without chasing anyone. That traceability is the main reason to move off emailed indents. Every PO can be traced back to who asked for it, when, and for which cost centre. ## Designing the purchase requisition workflow Out of the box, a Material Request is simply drafted and submitted. Approvals come from ERPNext's Workflow feature, where you define states (Draft, Pending HOD Approval, Pending Purchase Approval, Approved, Rejected), which roles can move a document between them, and any conditions on those transitions. A practical starting design for a mid-sized manufacturer or distributor: **Requester drafts** the request with item, quantity, required-by date and cost centre. Make cost centre mandatory, because budget checks depend on it. **Department head approves** that the need is real and the quantity is sensible. **Purchase team reviews** whether the item can be met from existing stock elsewhere, or whether to consolidate it with other open requests. **Conditional escalation**. Requests above a value threshold, or for certain item groups such as capital goods, route to finance or a plant head. **Approved requests** become available for RFQ or PO creation. Keep the number of states small. Every extra approval adds days to a lead time, and people find workarounds when the process is slower than a phone call. Where the standard workflow conditions can't express a rule, for example approvers that differ by plant *and* item category, small extensions through [ERPNext customization](/services/erpnext-customization/) are usually cleaner than stacking more workflow states. ## How budget control works in procurement This is where ERPNext differs from standalone requisition tools that only record a budget figure. A **Budget** in ERPNext is set for a fiscal year against a cost centre or a project, with amounts per expense account. You can spread it across the year with a monthly distribution, so a March request is checked against the budget accumulated up to March rather than the full annual amount. You then choose, separately for each stage, what happens when a document would exceed the budget: StageAnnual budget exceededAccumulated monthly budget exceededMaterial RequestStop / Warn / IgnoreStop / Warn / IgnorePurchase OrderStop / Warn / IgnoreStop / Warn / IgnoreActual expenses (invoices, journal entries)Stop / Warn / IgnoreStop / Warn / Ignore **Stop** blocks submission. **Warn** shows a message but lets the user continue. **Ignore** skips the check. A common pattern is *Warn* at Material Request, so requesters see the problem early without being blocked on urgent needs, then *Stop* at Purchase Order, where the commitment is actually made. That puts the hard control with the purchase team, who can make the call on reallocating budget. Teams comparing budget control in procurement ERP options should know that this stage-by-stage choice is configurable in ERPNext without custom code. ## Where budget control quietly doesn't apply These are the gaps that catch teams out after go-live. Test each one against your own item and account setup, because behaviour depends on configuration and ERPNext version. Stock items booked to inventory Budgets work on profit-and-loss expense accounts. If a stock item's purchase posts to an inventory (balance sheet) account, the budget check may not cover it the way you expect. Raw-material buying is often exactly this case. Many companies budget consumables, services and spares tightly but control raw materials through planning and reorder levels instead. Blank cost centre No cost centre on the request means nothing to check against. Make the field mandatory or default it per department. Auto-generated requests ERPNext can create Material Requests automatically when stock falls below reorder levels. These still go through your workflow if one applies to the doctype, but review the auto-created requests with the same discipline as manual ones. Direct POs If buyers can create a PO without a Material Request, the requisition step becomes optional in practice. Decide whether that's allowed, and for which item groups. We see these gaps regularly when reviewing ERPNext setups that went live without the procurement rules being tested end to end. *If several of these sound familiar, it usually helps to map your current approval and budget rules on one page before changing any settings. That's a short exercise we're happy to do with you.* ## A setup checklist for purchase heads Cost centres reflect how budgets are actually owned (department, plant, or project) Cost centre is mandatory on Purchase-type Material Requests Budgets entered per expense account, with monthly distribution where spend is seasonal Stop / Warn / Ignore chosen deliberately for Material Request, PO and actual expenses Workflow states kept to the minimum that matches real approval authority Value or item-group thresholds defined for escalation Policy decided on POs raised without a Material Request Reorder-level automation reviewed, with an owner for auto-created requests Budget Variance report scheduled for monthly review with finance ## Frequently Asked Questions [Is a Material Request the same as a purchase requisition?](#collapse-1401) Yes, for buying purposes. A Purchase-type Material Request is ERPNext's purchase requisition. The same document type also covers transfers, issues and manufacturing requests, so set the type correctly. [Does ERPNext stop a PO if the budget is exceeded?](#collapse-1402) Only if you configure it to. Each stage can be set to Stop, Warn or Ignore, for both the annual and the accumulated monthly budget. [Can different departments have different approvers?](#collapse-1403) Yes. Workflow transitions can be restricted by role and by conditions on the document, such as cost centre or value. Very complex routing may need light customization. [Can one requisition become several purchase orders?](#collapse-1404) Yes. Lines from one Material Request can be split across suppliers, and ERPNext tracks the ordered quantity per line until the request is fully ordered. [Do we need a separate purchase requisition tool alongside ERPNext?](#collapse-1405) Usually not. Requisition, approval and budget checks are native to ERPNext. The work is in configuring them to match how your company actually approves spend. ## Getting the requisition-to-PO flow right ERPNext gives purchase teams a real requisition system: traceable requests, configurable approvals, and budget checks at the stages you choose. Value comes from the configuration decisions, such as which cost centres hold budgets, where to warn versus stop, and which purchases sit outside the check, not from switching the features on. Aavatto has worked hands-on with Frappe and ERPNext since 2020, implementing and repairing setups for manufacturers and distributors across India and the Middle East. If you're planning a [tailored ERPNext implementation](/services/tailored-erpnext-implementation/) or want your current procurement flow reviewed, **book a free ERPNext consultation** and we'll walk through your requisition, approval and budget rules with you.