How to Create a Procurement Intake Process for a Mid-Market Company

Here's a situation that will sound familiar

Your company has grown. Headcount has doubled in two years. Revenue is up. And somewhere along the way, the way people buy things, software, services, equipment, contractors, has become completely unmanageable.

What it actually looks like in practice

Someone buys a SaaS tool on a personal card and expenses it. A department head commits to a six-month services contract over email without looping in finance. A new laptop gets ordered directly from a supplier your IT team has never heard of. And by the time any of this reaches accounts payable, the commitment has already been made, the vendor is expecting payment, and finance is reconciling spend they had no visibility into.

Why getting this right is so high-leverage

Getting this right is one of the highest-leverage things a mid-market finance or procurement team can do. Not because it adds bureaucracy, but because done well, it removes it. It gives people a clear, fast path to get what they need, while giving finance the visibility and control it needs before money leaves the organisation. This guide walks through exactly how to build one, from what a procurement intake process actually is, to the specific steps, forms, approval logic, and common mistakes to avoid.

What is a procurement intake process?

A procurement intake process is the structured path a spend request follows from the moment someone identifies a business need to the moment a formal commitment, a purchase order, a contract, an approved expense, is raised with a vendor.

It's the front door to your procurement function

Before intake, someone has a need: a new software subscription, a piece of equipment, an external consultant. The intake process captures that need in a structured way, routes it to the right people for review and approval, validates it against budget and policy, and converts it into a formal commitment only after those checks have happened.

What a procurement intake process is not

• It's not a purchase order system. The PO comes after intake, it's the output of a successful intake process, not the intake itself.
• It's not an expense reimbursement process. Expenses cover spend that's already happened. Intake governs spend before it happens.
• It's not just a form. A form is a component. The intake process is the full workflow, capture, routing, review, approval, and handoff to procurement or AP.

Why mid-market companies specifically need this

Small companies don't need a formal intake process. When you have 20 people and a founder who knows every vendor relationship, informal controls work fine. Large enterprises have procurement infrastructure, dedicated teams, sophisticated ERP configurations, established supplier management programmes. Mid-market companies, roughly 200 to 2,500 employees, $20M to $500M in revenue, are in the hardest position. They've grown past the point where informal controls work. They haven't yet built the infrastructure of a large enterprise. And the gap between those two states is where spend goes uncontrolled.

The specific problems this creates for mid-market finance teams

• Maverick spend. Research consistently shows that 40 to 60% of enterprise spend originates outside formal financial workflows. In mid-market companies with no intake process, that figure is often higher. People buy what they need through whatever channel is fastest, and finance finds out when the invoice arrives.
• Budget overruns that aren't caught in time. When spend commitments aren't captured at the point of intent, budget holders don't know what they've committed until it hits the P&L. By then, it's too late to reforecast meaningfully.
• Vendor proliferation. Without intake controls, companies accumulate vendors rapidly, multiple subscriptions for the same category, duplicate tools across departments, shadow IT that creates security and compliance risk.
• AP exceptions. Invoices that arrive without a corresponding purchase request or PO are the single biggest driver of AP exceptions. No PO reference. No budget approval. No record of who authorised the spend. Every one of these costs the AP team time to resolve.
• Audit exposure. When a spend commitment can't be traced back to an authorised request with documented approval, you have an audit finding. In regulated industries, healthcare, financial services, consumer goods, this isn't theoretical risk. It's a recurring problem.

A properly designed intake process addresses all of these at the source.

The rest of this guide is how to design one.

The six components of an effective procurement intake process

Every effective procurement intake process has six components. The tools and complexity vary by company size and maturity. The components don't.

Component 1: The Intake Channel

This is how people submit spend requests. It needs to be one place, not email, not Slack, not a shared spreadsheet. One channel that everyone uses, every time. For early-stage mid-market companies, this is often a simple form, Google Forms, Microsoft Forms, or a form within your ERP or procurement tool. For more mature operations, it's a dedicated intake portal or the request module in a procurement platform.

The channel needs to be

• Accessible: available on any device, requires no special training to use
• Fast: submitting a request should take under three minutes for a standard purchase
• Consistent: everyone submits through the same channel regardless of spend type or department
• Tracked: every submission is logged with a timestamp, submitter, and request ID

Adoption is a design problem, not a culture problem

If people find the intake channel difficult or slow, they'll bypass it. Make it easier to go through the process than around it.

Component 2: The Intake Form

The intake form captures everything needed to evaluate and approve a spend request. Not everything that could theoretically be useful, everything that's actually required to make a decision.

Core fields for every intake form

• Request date: automatically populated
• Requestor name and department: automatically populated if using SSO
• Vendor name: who you're buying from
• Spend category: software, professional services, equipment, marketing, facilities, other
• Description of need: what you're buying and why, in plain language (2 to 3 sentences)
• Estimated amount: total commitment value, including any recurring costs
• Currency: particularly important for companies with international operations
• One-time or recurring: and if recurring, what's the annual commitment value
• Required by date: when the purchase needs to be in place
• Budget owner: who owns the budget this will be charged against
• GL code or cost centre: where this spend should be allocated
• PO required: yes or no, based on vendor and amount
• Existing contract or new vendor: is this covered by an existing MSA, or is this a new relationship
• Attachments: vendor quote, SOW, or supporting documentation

Conditional fields, only shown when relevant

• If new vendor: vendor contact details, payment terms requested
• If above your contract review threshold: legal review required checkbox
• If IT software or SaaS: IT security review required checkbox
• If above your approval threshold: additional approver field

Keep the form short

Keep the form as short as possible while capturing everything required. Every field that isn't genuinely necessary to make an approval decision is a field that slows adoption.

Component 3: The Approval Workflow

This is where most mid-market intake processes break down. Either they have no defined approval workflow, requests go to a manager, then to finance, and nobody knows in what order, or they have an overly rigid one that creates bottlenecks and delays. Effective approval workflows are tiered by value and risk. Here's a practical framework for mid-market companies:

Principles that make approval workflows actually work

• Parallel approvals where possible. If the department head and the budget owner both need to approve, they should be able to do so simultaneously, not sequentially. Sequential chains double or triple cycle times unnecessarily.
• Defined SLAs for each tier. Tier 1: 24 hours. Tier 2: 48 hours. Tier 3: 5 business days. If an approver misses the SLA, the request escalates automatically. Approvals that have no deadline get treated as optional.
• Delegation rules. Every approver needs a named delegate for when they're out of office. An approval chain that stops because someone is on leave is a process failure, not an absence problem.
• Context travels with the request. The approver should see vendor, amount, business justification, budget availability, and the relevant policy in the approval notification, not a link to a form they have to open. Everything they need to approve, on one screen.

Component 4: Budget Validation

Approval and budget validation are separate steps. An approver can confirm a spend request is justified. Only a budget check can confirm the money is actually there. Budget validation should happen automatically, ideally triggered as soon as the intake form is submitted, before it even reaches the first approver. If the budget doesn't exist or has already been committed, the requester should know immediately rather than after a three-day approval cycle. For mid-market companies without a real-time budget visibility tool, the practical version of this is a monthly budget tracker that the finance team maintains, plus a clear process for the budget owner to confirm availability before approving. It's manual, but it works if it's consistently applied.

The number that actually matters

The key data point to track isn't just remaining budget, it's remaining budget after committed but not yet invoiced spend. Most budget tracking tools show actuals. What you need is actuals plus open commitments. That's the true available balance.

Component 5: Vendor Onboarding Integration

Every time a new vendor appears in an intake request, it should trigger a lightweight vendor onboarding check before the PO is raised. This doesn't need to be a lengthy due diligence process for every $500 purchase. But it does need to confirm, at minimum:

• Vendor legitimacy: the vendor exists, has a verifiable address, has been engaged intentionally
• Payment details: bank account, payment terms, preferred method
• Tax documentation: W-9 or equivalent for your jurisdiction
• Compliance flags: sanctions screening, restricted party check, where relevant
• Contract or terms on file: either your standard vendor terms or a signed MSA

Why this step exists

For low-value, low-risk vendors, this takes 10 minutes. For strategic vendors, it takes longer. The point is that it happens before commitment, not after. Skipping this step is how fictitious vendors end up in your AP system. It's also how you end up paying a vendor whose bank account has changed without your knowledge, one of the most common invoice fraud vectors. (AI vendor risk scoring is a useful read here.)

Component 6: Handoff to Procurement and AP

A completed, approved intake request should flow seamlessly into purchase order creation and eventually into AP. The handoff data should include:

• Approved vendor details
• Approved amount and payment terms
• GL code and cost centre confirmed by finance
• PO number assigned
• Contract or terms reference
• Required delivery date
• Any special instructions for invoicing

When the handoff is clean vs when it isn't

When this handoff is clean, the AP team receives invoices against known, approved commitments. Three-way matching works. Exceptions are rare. The invoice-to-payment cycle is fast. When it isn't clean, when invoices arrive without PO references, or POs exist without corresponding intake approvals, the AP team spends its time reconstructing context that should have been captured upstream. This is the most common driver of AP team overload in mid-market companies.

Common mistakes mid-market companies make

Six mistakes show up in almost every mid-market intake rollout. Knowing them in advance is the cheapest way to avoid them.

• Building the form before the workflow. Most companies start by designing an intake form. The form is the easy part. The workflow, who approves what, in what sequence, under what conditions, is where the real work is. Design the workflow first. The form follows from it.
• Setting thresholds too high. A common instinct is to keep the intake process lightweight by setting the approval threshold high, only requiring formal approval for purchases above $10,000. The problem is most maverick spend happens below that threshold. Recurring SaaS subscriptions at $200 a month across 50 departments add up to $120,000 a year with no procurement visibility. Thresholds need to account for annualised recurring costs, not just one-time transaction values.
• No policy for existing vendors. Many intake processes apply only to new vendors. But over-billing, contract drift, and unauthorised scope expansions happen with existing vendors too. Any spend outside a current contract or above contracted rates should go through intake, regardless of whether the vendor relationship is established.
• Treating intake as a finance process, not a company process. Procurement intake only works if everyone uses it, not just the departments that finance has trained. Adoption requires executive sponsorship, clear communication about why the process exists, and critically, a fast enough experience that going through the process is easier than finding a workaround.
• No feedback loop for requestors. If a request is declined or sent back for more information, the requestor needs to know immediately, with a clear explanation and a path forward. Intake processes that decline requests without explanation teach people to bypass the process next time.
• Launching without a pilot. Roll out to one department first. Find the gaps in the form, the bottlenecks in the approval chain, the fields nobody fills in correctly. Fix them before the company-wide rollout. A poorly designed intake process rolled out to the whole company creates more resistance than no process at all.

How to measure whether your intake process is working

Once the process is live, track these five metrics monthly:

• Intake compliance rate: percentage of new vendor spend that went through the intake process vs arrived as an unmatched invoice. Target: above 85% within 90 days of launch, 95%+ within six months.
• Average intake cycle time: how long from submission to approved PO. Target: under 24 hours for Tier 1, under 48 hours for Tier 2, under 5 business days for Tier 3.
• AP exception rate on new vendor invoices: percentage of invoices from vendors onboarded through intake that arrive without a PO reference or with a discrepancy. Target: under 5%. Above 10% suggests the handoff from intake to AP is broken.
• Budget overrun frequency: how often approved intake requests result in invoices above the approved amount. Chronic overruns suggest the budget validation step isn't working or requestors are underestimating at intake.
• Maverick spend as percentage of total spend: the lagging indicator everything else feeds into. A working intake process should show a measurable decline in maverick spend within two to three budget cycles.

Building this in stages: a practical roadmap

You don't need to build the full process on day one. Here's a practical phased approach for mid-market companies starting from scratch.

• Phase 1 — Weeks 1 to 4 (Foundation). Design the approval workflow tiers. Build the intake form. Identify one department for the pilot. Train approvers on SLAs and delegation rules. Launch the pilot.
• Phase 2 — Weeks 5 to 8 (Refinement). Review the pilot for friction points. Adjust form fields, threshold values, and routing logic based on real usage. Document the process formally: a one-page guide for requestors, a one-page guide for approvers.
• Phase 3 — Weeks 9 to 16 (Rollout). Roll out to all departments in waves, highest-spend departments first. Communicate the why, not just the what. Measure compliance rate weekly and address exceptions immediately.
• Phase 4 — Month 5 onwards (Optimisation). Add vendor onboarding automation if not already in place. Integrate with your ERP for budget checking. Build the reporting layer: maverick spend dashboard, cycle time tracking, exception rate by department.

The next step beyond manual intake

Everything in this guide can be built and run manually or with general-purpose tools. For most mid-market companies starting from scratch, that's the right approach. Get the process discipline in place first. Understand your own intake patterns. Identify where the friction and the exceptions are.

But there's a ceiling on what a manually-run intake process can do

It can't validate spend requests against your contracts in real time. It can't score vendor risk continuously and feed that into approval routing. It can't detect when a committed spend is trending above the approved amount before the invoice arrives. And it can't give the CFO a live view of committed but unpaid spend across every department and every vendor simultaneously.

Where Blackbee AI picks up where manual intake stops

That's where a purpose-built agentic Intake-to-Pay platform picks up. Blackbee AI is built specifically for mid-market companies that have outgrown spreadsheet-based intake and need a system that governs every spend decision from the first request through to payment. The Intake Agent captures requests from any channel. The Procurement PO Agent governs the commitment layer so no spend slips through. The Approval Orchestration Agent routes by policy, risk score, contract status, and spend context, simultaneously. The Contract Intelligence Agent holds contract terms as live guardrails. The Spend Intelligence Agent gives the CFO a real-time view of committed but unpaid spend. If your team is processing 200+ procurement cycles a month and the intake process you've built is hitting its limits, see how Blackbee AI works.