Most companies with 50 to 200 employees don’t have a procurement problem in the formal sense. They have a spending control problem that sits between department heads, finance, and whoever happens to notice the invoice. That’s what procurement to payment is meant to fix, and when it’s loose, money leaks through delay, duplication, and poor timing rather than dramatic fraud or one bad deal.
What Procurement to Payment Actually Is
Procurement to payment is the operating process for how a company decides to spend money, records that decision, confirms it received what it bought, and pays the vendor. Textbook diagrams make it look administrative. In practice, it is one of the main ways a growing company keeps cost discipline without slowing work to a crawl.
For a company without a formal procurement team, this process usually starts long before accounts payable sees an invoice. Someone wants a new software tool, engages an agency, renews a contractor, or orders equipment. From there, the company either captures that decision in a controlled way or lets it disappear into email, card spend, and chat threads.
That distinction matters more than most finance teams expect. If the request, approval, contract terms, invoice, and payment record don’t line up, the company loses visibility into what it is buying and why. The damage shows up later as duplicate vendors, missed cancellation dates, weak budget discipline, and painful board reporting.
A useful way to think about procurement to payment is as the spending layer beneath accounting. Accounting tells a company what it spent. Procurement to payment tells it whether it meant to spend it, whether the terms were acceptable, and whether the payment happened at the right time.
For teams trying to connect spend control with wider systems thinking, application portfolio management is closely related. Both disciplines force the same question. Which vendors are still earning their place?
Procurement to payment isn’t a flowchart problem. It’s the difference between recognised spend and unmanaged spend.
The Five Stages and Where Your Money Leaks
The standard five stages are requisition, purchase order, receiving, invoicing, and payment. In a mid-sized company, each stage has a predictable failure mode. The leak usually isn’t one huge mistake. It’s small losses repeated across dozens of vendors and hundreds of approvals.
Requisition
This is the point where someone asks to buy something. In healthy companies, that request includes a business reason, budget owner, expected cost, and vendor name. In messy ones, the process is a Slack message, a forwarded quote, or a manager saying yes on a call.
That’s where duplicate software, overlapping agencies, and shadow renewals start. If the company can’t see demand before purchase, it can’t challenge whether an existing vendor already covers the need.
Purchase order
A purchase order matters less because of formality and more because it creates a reference point. It ties price, quantity, timing, and approval to a known record. Without that record, spend moves straight from intention to invoice.
Growing companies often skip POs for anything that isn’t inventory or equipment. That sounds efficient until finance has to reconcile service invoices with no owner, no agreed scope, and no clear approval path. Teams considering lighter controls can review free purchase order software options without adopting enterprise procurement overhead.
Receiving
For physical goods, receiving means confirming delivery. For software and services, it means confirming that access was granted, work was performed, or milestones were met. This stage is often ignored because service businesses assume the invoice itself proves delivery.
It doesn’t. Agencies bill before output is reviewed. Contractors keep working under old terms. Software renews because nobody confirmed whether the tool still has users. If no one verifies receipt in a structured way, invoices drift into “pay it because it’s probably right”.
Invoicing
Weak processes have measurable consequences. According to Planergy’s overview of procure-to-pay challenges, siloed operations in the P2P cycle result in up to 30% of invoices being processed manually, with average processing times of 10 to 15 days and error rates of 2% to 5% due to manual entry and mismatched documents.
Those numbers explain why finance teams feel permanently behind. Manual invoice handling doesn’t only waste time. It creates ambiguity over cost centres, approval status, and contract alignment. Once that ambiguity enters the ledger, every spend review becomes slower and less reliable.
Payment
The payment stage looks like the end of the process, yet it is at this point that bad upstream decisions become cash consequences. According to Medius on supplier payment challenges, 25% of mid-sized enterprises miss early payment discounts worth 1% to 2% of invoice value, and manual processes lead to onboarding delays averaging 2 to 4 weeks per vendor.
Missing a discount is one problem. Paying late is another. Paying the wrong invoice because the company rushed a backlog is worse. Payment should be a controlled release of cash, not the moment finance discovers what everyone else committed to.
A broken procurement to payment process usually wastes money before the payment leaves the bank. The payment only reveals where control was already lost.
Common P2P Failures in Growing Companies
The stage-by-stage leaks usually trace back to three structural issues. None of them are unusual. They’re the default condition for companies that have grown faster than their operating model.
Ownership is split, but accountability isn’t
Operations often owns intake. Department heads choose vendors. Finance owns invoice processing and payment. Legal may review contracts. IT may discover the software only after it’s already live. Everyone touches the process, but nobody owns the full chain from request to renewal.
That structure makes spend review reactive. A finance lead can see cash out the door, but not the reasoning that caused it. A COO can see vendor sprawl, but not always the payment pattern behind it.
Spreadsheets hide as systems
Spreadsheets are useful until they become the only memory the company has. They break when one owner leaves, when a contract renews in a buried tab, or when invoice data lives in one file and vendor terms live in another.
The result is familiar. Vendor records don’t match. Reporting depends on manual cleanup. Teams argue over which file is current. By the time finance has a clean view, the quarter has moved on.
Rogue spend becomes normal
Company cards, direct debit renewals, and department-level buying create speed, which is why companies tolerate them. They also create a second procurement system outside formal approval paths.
That’s the core trade-off. Loose controls help teams move, but they also make total vendor cost invisible until the business is large enough to feel the drag. At that point, point solutions won’t help much unless the company fixes who approves spend, where contracts sit, and how vendors are tracked.
Key Metrics to Track Even Without a Team
A mid-sized company doesn’t need a dense procurement scorecard. It needs a few metrics that show whether spend is controlled, cash is moving on time, and vendors sit inside a known process.
Invoice cycle time
This measures how long it takes an invoice to move from receipt to approval and payment readiness. Long cycle times usually point to missing approvals, weak coding, or poor document matching. Even if the company can’t automate everything, it should know where invoices stall.
If cycle time is inconsistent across departments, that usually means the problem is not workload. It is process design.
On-time payment percentage
This metric is less about politeness than supplier trust and cash planning. According to Ivalua’s discussion of procure-to-pay best practice, in Australia, US companies paid small businesses an average of nine days late in the first half of 2024, based on Xero reporting. Late payment is common enough that many teams normalise it. They shouldn’t.
A low on-time payment rate often means approvals arrive too late, invoices enter the system too slowly, or payment runs are detached from operational reality.
Spend under management
This asks a blunt question. How much vendor spend moves through a known process with a known owner, agreed terms, and visible reporting? That number matters more than a stack of policy documents.
For teams using accounting systems as the core record, accounting integrations matter because they reduce the gap between spend visibility and payment data. If spend under management is low, the company isn’t short on software. It’s short on control.
The right metrics don’t prove procurement maturity. They show where cash leaves faster than management attention.
A Practical P2P Implementation Checklist
Most companies at this stage don’t need a procurement transformation programme. They need a tighter operating rhythm and a lighter system that records decisions before they become invoices.
Start with process, not software
A few low-overhead changes solve more than is commonly expected:
- Create one invoice inbox so supplier bills don’t land in personal email and disappear during leave or turnover.
- Write a simple approval matrix that states who can approve spend by category and level.
- Keep one vendor register with vendor name, owner, contract location, renewal date, and payment method.
- Require a named budget owner before a new vendor starts work.
- Review recurring payments monthly rather than waiting for quarterly budget cycles.
None of that is glamorous. All of it reduces leakage.
Add controls where manual work is expensive
Once the basic process exists, the next step is to reduce the parts that consume finance time without improving judgement. Invoice capture, approval routing, contract storage, and payment status visibility are the usual priorities.
Tooling becomes a significant factor. According to Credence Research on the P2P solutions market, the global procure-to-pay market is projected to grow from USD 7.4 billion in 2024 to USD 13.6 billion by 2032. The useful takeaway isn’t market size. It’s that more companies are deciding manual coordination is too expensive to keep.
Choose tools that fit the company you are
A 120-person company usually doesn’t need enterprise procurement software built for large sourcing teams. It needs visibility across software, agencies, contractors, and service vendors, tied back to the accounting record and contract terms.
That’s where a lighter vendor operating layer helps. Ensurva is a vendor management platform that tracks software and human service vendors in one system. For companies without a dedicated procurement function, that kind of system is often more practical than trying to force enterprise procurement methods onto a lean team.
The hard truth is that procurement to payment discipline doesn’t come from policy alone. It comes from making the approved path easier than the informal one.
Frequently asked questions
What’s the difference between procurement to payment and source to pay
Procurement to payment covers the transactional flow from request through payment. Source to pay is broader and includes supplier selection, negotiation, and contracting. Companies without a procurement team usually need to fix procurement to payment before they worry about full source to pay maturity.
When should a company hire a dedicated procurement manager
Usually when vendor count, contract complexity, and departmental buying have outgrown part-time ownership. If finance spends too much time cleaning vendor data and leaders can’t tell who owns key suppliers, the company may need a dedicated owner.
How should non-PO invoices be handled
They shouldn’t be treated as harmless exceptions. The company should assign an owner, confirm the service or goods were received, and record why the invoice arrived without a prior approval trail. If non-PO invoices become normal, spend control is already weak.
Does procurement to payment apply to software and service vendors
Yes, and often more than to physical goods. Software renewals, agency scopes, contractor terms, and usage drift create quiet leakage because delivery is less visible than a shipped item. Those categories need ownership, receipt checks, and contract awareness.
What’s the first sign that the process is breaking
It’s usually not a failed audit. It’s when finance can’t produce a clean vendor view without manual digging, or when a renewal surprises the business even though the payment history was sitting in the accounting system the whole time.
