Custom Purchase Order Automation Platforms for UK Businesses

Most businesses don’t go looking for purchase order software until something breaks. A spreadsheet gets too big to trust. An approval sits in someone’s inbox for a week and a supplier stops a delivery. An invoice gets paid twice. An auditor asks who approved a £12,000 order and nobody can say. Often the trigger is growth: a second site, a third department, a budget overspent without anyone noticing until month-end.

I build purchase order systems around how your team buys: your approval rules, your budgets, your suppliers and your accounting system. Senior-led means the developer who draws up your authorisation matrix with you is the one who codes it. The result has no per-user subscription, talks to your accounts package and stock system, and handles VAT, Making Tax Digital records and audit trails from the first release.

Why off-the-shelf PO tools disappoint

Procurify, Precoro and Fraxion are decent products and they do replace a spreadsheet. UK businesses outgrow them for recurring reasons:

• Per-user pricing punishes growth. Most of these tools charge per user per month. Finance teams react by limiting who gets a login, people share credentials, and the bottleneck and the broken audit trail come back.
• Approval logic is rigid. Off-the-shelf tools handle “manager, then finance, then FD” well. They struggle with rules like “escalate to compliance if the supplier is new”, “IT spend over £25k needs the CTO and procurement”, or an emergency order approved after the fact. Those orders bypass the system by email.
• Integration is shallower than it looks. A thin connection to Xero or QuickBooks breaks cost-centre mappings, syncs nightly so budgets lag, and lets the supplier list drift apart between the two systems. Finance ends up re-keying goods receipts anyway.
• Three-way matching is too blunt. Tolerances often can’t be tuned per supplier, so a small price variance that should pass gets flagged and finance spends hours clearing false exceptions.
• Supplier portals go unused. Suppliers asked to log into yet another portal keep emailing PDFs, so manual entry continues.
• Industry rules don’t fit the template. CIS and retention in construction, NHS framework terms, batch traceability for food and pharma, donor-restricted funds for charities.

If your approval chain is two levels deep, your suppliers are standard and your team size is stable, ApprovalMax or Precoro may be all you need. A build earns its place when your process is what makes the off-the-shelf tools awkward.

What I build instead

Process first, code second

I start by mapping how procurement works in your business: who can request, who approves what value, where the exceptions are, and the workarounds nobody wrote down. The authorisation matrix is agreed in writing with the people who own it, so disagreements about approval limits surface before go-live. Conditional routing is part of the build, not an upgrade tier.

You pay once

A fixed build price and an optional monthly plan. Adding requesters and approvers costs nothing, so everyone who should be in the system can be. The software, the source code and the data are yours.

Inside your accounting setup, not on top of it

Approved POs and matched invoices post to Xero, QuickBooks or Sage as bills without re-keying, against your nominal codes and cost centres, and budgets update in real time. Where you run NetSuite, Dynamics, an in-house ERP or a stock system, that connects too, and suppliers who need EDI rather than a portal can have it.

VAT and audit built in

Supplier VAT validation, line-item VAT, reverse charge, Making Tax Digital compatible records, and an audit log that can’t be edited after the fact.

The modules most builds include

The first release covers the core, and the rest follows once it has bedded in.

1. Purchase requisitions, so requests start in a form rather than an email, with templates for repeat orders.
2. PO generation from approved requisitions, with your numbering and branded PDFs sent to the supplier.
3. Multi-level approvals by amount, department, category, project or supplier risk, with parallel approvers and escalation when someone sits on a request too long.
4. Budget checks against department, project or cost-centre allocations, showing committed spend (POs raised but not yet invoiced) separately from actual spend, with the option to block or flag an order that would overspend.
5. A supplier record with contacts, payment terms, VAT number, bank details, certificates, insurance expiry and performance data.
6. Goods receipt, including partial deliveries, damaged goods, and batch or serial numbers where you need traceability.
7. Three-way matching between PO, goods receipt and invoice, with tolerances set per supplier.
8. Spend reporting by supplier, category, department or site, plus approval cycle times and budget variance, with a feed to Power BI if you use it.
9. Reorders triggered when stock hits a threshold.
10. Mobile approvals, so a manager out of the office isn’t the hold-up on a £400 order.
11. Segregation of duties, so the person who raises a requisition can’t also approve it, receive the goods and authorise payment.

The data the system holds

Procurement is mostly a data problem. Getting these records and their links right is what lets the system answer the questions that matter later: who approved this, against which budget, and did the invoice match what arrived.

• Suppliers: contacts, VAT number, payment terms, bank details, category and a risk rating.
• Requisitions: the request, the requester, the department or project, and the approval chain.
• Purchase orders: line items with quantities, unit prices, VAT rates and nominal codes, delivery details and currency.
• Goods receipts: what arrived, including partial deliveries and condition.
• Invoices: supplier bills with line items and VAT, linked to the PO and the receipt.
• Matches: the reconciliation record, any variance, and whether it falls inside tolerance.
• Budgets: allocations by department, project or cost centre, with committed and spent amounts.
• Audit log: every creation, amendment and approval, with timestamp, user and the values before and after.

Purchase order software for construction

Generic PO tools assume one office buying from a stable supplier list. A contractor buys for several live sites at once, from merchants, plant hire firms and subcontractors, against budgets that change with every variation. The parts a construction PO system needs:

• Budgets per project and cost code. Every PO is raised against a job and a cost code, so the commercial manager sees committed cost against budget for each project while the job is running, not after the invoices land.
• Variations. A change to scope raises a variation against the original order, with its own approval, so the order value, the budget and the final account stay in step.
• Subcontractor orders with CIS. Subcontractors are verified with HMRC under the Construction Industry Scheme before they are paid, and the deduction (20% for registered subcontractors, 30% for unregistered, none with gross payment status) is applied to the labour element of each payment and carried into the monthly return.
• Retention. A percentage held back from each subcontractor payment until practical completion and the end of the defects period, tracked per order so releases aren’t missed.
• Domestic reverse charge. VAT on construction services between VAT-registered businesses in the CIS chain is accounted for by the customer, so invoices and bills have to carry the right VAT treatment.
• Site deliveries. Site managers book goods in on a phone, against the PO, with a photo of the delivery ticket, so the three-way match has a receipt from the person who saw the lorry arrive.
• Supplier checks. Insurance, accreditations and health and safety documents held against each subcontractor, with expiry warnings before an order is placed.

How a project runs

1. First Gear, five days, £495. I map your process with procurement, finance and the people who raise POs, and build a working prototype of the requisition and approval flow on your own suppliers and budgets. A one-page plan with the fixed build price comes with it, and the £495 is deducted from that price if you proceed.
2. Data cleansing. Supplier data is rarely clean. Duplicate suppliers, inconsistent names and missing VAT numbers are normal, and this is the part of a procurement project that most often slips, so I scope it at the start.
3. First release, live within a month. Requisitions, one or two approval levels, PO generation, budget tracking, accounting sync and the audit trail.
4. Pilot and rollout. I check the accounting sync, routing and matching against real data, then run a pilot with a small group in parallel with the old process before everyone moves over.
5. Later phases and support. Three-way matching, conditional routing, mobile approvals, multi-entity consolidation or EDI, each about a month and fixed-price. Fixes are guaranteed for 30 days after launch and the first month’s hosting is on me, after which a monthly plan is optional. Training runs separately for requesters, approvers and finance.

What it costs and what you own

A typical PO build costs between £2k and £10k, with the figure fixed in the plan you get from First Gear. A first version with simple approvals, accounting sync and basic reporting usually fits in one build.

• SaaS cost scales with headcount and a build doesn’t. The more people you expect to add as requesters and approvers, the sooner a fixed-cost build makes sense.
• The total cost of SaaS is more than the subscription: setup fees, API charges above a free tier, premium support, custom reports and data migration.
• You extend the system on your own timetable, not a vendor’s roadmap.
• Your data stays portable, and the software, source code and data are yours.

When it makes sense

A bespoke build tends to make sense when:

• Your approval rules are conditional, not a simple ladder.
• You budget by project, site or product line, not just a flat cost-centre list.
• You need real-time links to an ERP or stock system.
• Suppliers work in different ways: some EDI, some API, some plain email.
• Per-user pricing is becoming a real cost as the team grows.
• You run several legal entities, often after an acquisition, and need separate ledgers with group reporting.

Sectors where this pays off

• Construction: see the section above.
• Manufacturing: raw material orders tied to bills of materials, reorder points or an MRP run, with lead times and supplier quality tracked on on-time delivery and defects.
• Food and drink: supplier certification, allergen checks, and batch and shelf-life records for HACCP traceability.
• Healthcare and pharmaceuticals: NHS framework terms, supplier qualification, batch numbers at goods receipt, and tighter controls on regulated items.
• Education: multi-department buying with firm budget limits and an audit trail for governors and auditors.
• Hospitality: food and drink purchasing across several sites with ordering by location.
• Retail and e-commerce: POs linked to stock and sales velocity so reorders happen before a product sells out.
• Charities: spend held to donor-restricted funds, with reporting by fund.
• Professional services: client-billable purchases tracked against project budgets.
• Logistics and facilities: fleet parts and maintenance purchasing across a portfolio, linked to service schedules.

If you’re sourcing new suppliers or running formal tenders rather than ordering from ones you already use, procurement management software is the closer fit. Tell me how purchasing works in your business today and I’ll tell you where a build would help.

Common Questions About Custom Purchase Order Automation Platforms

How does a custom PO system compare in cost to a SaaS subscription? ›

A build costs more up front than a monthly subscription. Most procurement tools charge per user per month, so every new requester or approver adds to the bill, and setup, migration and premium support are often extra. A custom system has no per-user fee. Most of my builds land between £2k and £10k, with the price fixed at the end of First Gear. The bigger your team of requesters and approvers, the sooner a fixed-cost build makes sense, and I'll work it through on your numbers.

Which purchase order system works with Xero, Sage or QuickBooks and handles UK VAT? ›

Several SaaS tools connect to all three. A custom build goes further on the mapping: approved POs and matched invoices post as bills against your own nominal codes and cost centres, supplier VAT numbers are checked, line items carry their VAT rate, and reverse charge is handled for construction services and services bought from abroad. The audit log keeps every requisition, approval and amendment for the six years HMRC expects.

What should a small business look for in PO software? ›

Multi-user approvals that follow your real limits, budget checks that show committed spend before a PO is raised, a clean link to your accounts package, and an audit trail of who approved what. If your approvals are one or two simple levels and your supplier list is short, ApprovalMax or Precoro may be all you need. A build earns its place when approvals depend on project, category or supplier, or when you budget by job or site rather than a flat cost-centre list.

Do you build construction purchase order software? ›

Yes. Construction POs need budgets held per project and cost code, variations tracked against the original order, retention held back on subcontractor payments, CIS checks on subcontractors, and goods received on site from a phone. I build those into the same requisition, approval and matching flow, and post the results to your accounts package.

What is three-way matching and can it be tailored to us? ›

Three-way matching checks a purchase order against the goods receipt and the supplier invoice before payment is approved, and holds anything that doesn't line up. In a custom build the tolerance rules are yours: a small price variance can pass for some suppliers while others need an exact match, so finance isn't buried in false exceptions. Low-value orders can match two ways or auto-approve below a threshold you set.

How long does a build take? ›

First Gear takes five days and gives you a working prototype of your requisition and approval flow on your own data. The first release, covering requisitions, one or two approval levels, accounting sync, budget tracking and the audit trail, then goes live within a month. Three-way matching, mobile approvals and conditional routing follow as further phases of about a month each.