Procura Flow

Purchasing & purchase orders

From request to purchase order without the email thread

A requisition anyone can raise, an approval that routes itself, and a purchase order generated from exactly what was approved — with receipting that takes one tap.

Book a demoSee pricing

Today

  • Requests arrive in chat, email, and hallway conversations.
  • Purchase orders are typed manually, often after the supplier already started work.
  • Nobody logs deliveries, so accounts payable reconstructs them from memory.
  • Finance discovers the commitment when the invoice arrives.

With Procura Flow

  • One request form with category, cost centre, and budget attached.
  • Approved requisitions convert to purchase orders automatically and send themselves.
  • Partial and full receipts logged by the person who raised the request.
  • Committed spend visible the moment the order is placed.

Capabilities

What you get

Two-minute requisitions

Short forms with category defaults, suggested preferred suppliers, and budget remaining shown before submission. Requesters do not need finance training.

Purchase orders generated, not retyped

POs inherit line items, pricing, terms, and delivery details from the approved request, then send to the supplier with your branding and terms attached.

Preferred suppliers and catalogues

Surface negotiated agreements inside the request form, where the decision is being made — the single most effective way to reduce off-contract buying.

Receiving that actually happens

One-tap receipting with partial deliveries, quantity variances, and photo evidence, prompted automatically on the expected delivery date.

Two- and three-way matching

Invoices match against the PO and receipt within tolerances you set by category. Exceptions route to the budget owner, not a shared inbox.

Clean data into accounting

Coded, approved transactions sync to your ledger with cost centre and category intact, and sync failures raise an alert rather than queueing silently.

How it runs

The workflow, step by step

  1. 01

    Request

    An employee raises a requisition with need, quantity, cost centre, and estimated value.

  2. 02

    Approve

    Routing by amount and category, in parallel where two reviewers are needed.

  3. 03

    Order

    An approved request becomes one or more POs, issued to suppliers automatically.

  4. 04

    Receive & match

    Receipts logged against the PO; invoices matched within tolerance before payment.

9 → 1 day

Northbay Logistics, median requisition-to-PO time, first quarter after rollout

2 min

Median time to raise a request in our own instance, 30-day sample

70%

Invoices clearing untouched once PO coverage passes 80%

These are figures from named deployments, not averages across a customer base. The third depends entirely on your PO coverage rate — below 50% coverage, expect touchless rates in the teens no matter what software you run.

Limitations

Where this will not help you

Cases we handle badly or not at all. Better you read them here than find them in week three of an implementation.

No punchout to supplier webstores

We support hosted catalogues and free-text requests. If your buyers need live punchout sessions into distributor storefronts, we are the wrong tool today and it is not on the near roadmap.

Light on manufacturing planning

No MRP, no bills of material, no production scheduling. If purchase quantities are driven by a production plan, that plan has to live in your ERP and reach us as a request.

Inventory is receipt-level only

We record what arrived against a purchase order. We do not run stock levels, bin locations, or reorder points, so warehouse teams still need their own system.

Further reading

Guides on this topic

Resource library →

See Procura Flow on your own purchase orders

A 30-minute walkthrough using your categories, approval thresholds, and supplier list.

Book a demo