Cash flow starts before the invoice

Most companies talk about cash flow as though a purchase becomes real when the invoice arrives. That is when finance sees the number, the supplier expects payment, and the question becomes immediate. Yet APQC tracks an important benchmark: the percentage of purchase orders created only after the associated supplier invoice has already been received. The existence of that metric points to a common weakness in modern organisations: commitments are often documented after the business has, in effect, already made them.

Professional procurement body CIPS draws the line more clearly. A purchase requisition, it says, is the internal permission to spend; a purchase order is the formal external confirmation to the supplier. CIPS also defines procure-to-pay as the integration of purchasing and accounts systems to improve visibility and control. Put those ideas together and the lesson is straightforward: cash may leave later, but financial exposure often begins much earlier, when the company first approves the spend.

Seen through that lens, procurement software is less an efficiency story than a control story. In growing businesses, purchases often begin in chat threads, email chains and departmental workarounds. The result is not usually fraud or drama. More often it is a slow loss of control: commitments build up in different corners of the company while finance gets only a partial view, usually when invoices start arriving. That helps explain why procurement transformations so often return to the same issue: visibility across stages, not simply speed at one stage. In a KPMG case study on procurement redesign, some business units used purchase orders while others did not, review steps varied, and approval thresholds were so poorly calibrated that a $50 software renewal passed through the same review chain as a $100,000 IT purchase.

That broader problem is the most useful way to understand Precoro. According to its own materials, the company was founded in 2015 and positions itself around centralised procurement and procure-to-pay workflows, including requisitions, approvals, purchase orders, invoice handling and three-way matching. None of that is unique on its own; the category is crowded with software vendors promising smoother purchasing. What makes Precoro more interesting is the narrower argument implied by its structure: that procurement matters not because it makes paperwork tidier, but because it can show commitments before they become invoices and payment obligations.

That distinction matters. A requisition is not just an internal form. It is the point at which an informal idea becomes a formal request. Once a request is captured early, the business can still ask useful questions: Is this necessary now? Is there budget for it? Should it be combined, delayed or rejected? Once the supplier has invoiced, those questions become harder and more expensive to ask. In that sense, good procurement discipline does not simply record spending. It keeps options open for managers.

This is where Precoro’s design fits the wider shift in procurement thinking. Its product logic links requests, approvals, orders, invoices and payment status into one process rather than leaving them scattered across departments. That matters because many finance teams do not struggle for lack of invoice data. They struggle because earlier commitments are fragmented across people and systems. A platform that connects request, approval, order, receipt and invoice can close that gap and turn procurement into an earlier signal of budget pressure rather than a late administrative clean-up exercise.

There is, however, an important limit to this argument. More process is not automatically better process. As the KPMG case shows, badly designed controls can create friction, push minor purchases through oversized review chains and make procurement feel like bureaucracy rather than discipline. The case for tools such as Precoro is strongest when controls are proportionate: tight enough to surface commitments early, light enough not to create unnecessary friction. Visibility is useful; administrative delays are not.

That is why Precoro is best understood not simply as another software vendor promising efficiency, but as one example of a wider shift in how companies control spending. The interesting question is no longer only how quickly an invoice can be processed. It is how early a company can see that tomorrow’s cash obligation is already being created today. On that question, procurement starts to look less like back-office administration and more like a core part of financial control.