Procurement Software

When email purchase orders and manual invoice matching stop working

Most businesses start their procurement process in email: a department head sends a request, procurement raises an order, the supplier delivers, an invoice arrives, and finance pays it. For low volume this works. The process breaks down as volume grows: purchase orders get raised after the goods arrive, approvals get skipped, invoices don't match the PO because nothing was updated during the order process, and month-end is spent reconciling committed spend that no one had reliable visibility into. We build procurement systems for businesses that have outgrown email-based purchasing and need a process that enforces the right approvals, creates an accurate audit trail, and produces spend data the finance and operations team can act on.

  • PO creation from a supplier catalogue or free-text requisition with automated routing to the right approver based on value, category, and cost centre

  • Approval workflows with conditional routing reflecting your authority matrix: value thresholds, budget holder sign-off, and finance approval configured to your policy

  • Three-way matching of purchase order, goods receipt, and invoice with automatic approval for matched invoices and exception routing for discrepancies

  • Spend analytics showing committed and actual spend by category, supplier, cost centre, and period against budget

Bring the problem, the current workflow, or the existing code. We reply with a practical next step within one business day.

Trusted by

Vodafone logo
Aldi logo
Nike logo
Microsoft logo
Heineken logo
Cisco logo
Calorgas logo
Energia Rewards logo
GE logo
Bank of America logo
T-Mobile logo
Valero logo
Techstars logo
East Ventures logo
TuneClub logo

The brief

Start with what is not working.

Good software decisions begin with the constraint, not a list of features or a preferred technology.

01

Purchase orders raised by email or over the phone because the ERP purchasing module is too slow and too rigid for the way the business actually buys?

02

Invoices sitting in a queue for weeks because the three-way match fails and no one can see where the discrepancy is or who needs to resolve it?

Plain answer

RaftLabs builds custom procurement software for operations and finance teams: PO automation, approval workflows matched to your authority matrix, three-way matching, and spend analytics in one connected system. A first module launches as a validated v1 in 10 to 16 weeks at a fixed, agreed cost, then grows into the full platform.

What to remember

  • Approval routing reflects your actual authority matrix, value thresholds, category ownership, and CFO sign-off, with parallel approval and delegation for approvers on leave.
  • Three-way matching auto-approves invoices within tolerance and routes discrepancies with the specific quantity, price, or missing-receipt issue clearly presented for resolution.
  • Spend analytics distinguish committed spend (approved, not yet invoiced) from actual spend, giving finance real-time budget visibility instead of a month-end surprise.
  • A first module covering requisitions, approval routing, and PO creation starts around $25,000-$45,000 as a validated v1; the full platform with three-way matching, spend analytics, and ERP integration grows to $80,000-$150,000 over time.

Proof

Since 2015
shipping production software for operations and finance teams
RaftLabs delivery record
4.9/5
average client rating across delivered projects
Clutch, verified reviews
Fixed price
scope and cost agreed in writing before any development starts
Every RaftLabs engagement

When email purchase orders and manual invoice matching stop working

We build procurement systems that enforce the right approvals and create an accurate audit trail. The result is spend data your finance and operations team can act on. Process design is agreed during discovery, before any development starts.

Capabilities

What we build

  • 01
    PO automation and requisition management

    Catalogue or free-text requisitions converting to POs automatically, with blanket order support for recurring purchases.

  • 02
    Approval workflows and authority matrix

    Value- and category-based routing with parallel approval, delegation for absences, and a complete approval audit trail.

  • 03
    Three-way matching

    Automatic approval within tolerance, with clear discrepancy presentation and a documented resolution workflow.

  • 04
    Spend analytics

    Committed-vs-actual spend by category, supplier, and cost centre, with budget variance flagged before month-end.

  • 05
    Category management

    Category ownership, preferred-supplier designation, and savings tracking tied to sourcing strategy documentation.

  • 06
    Supplier catalogue

    Team-maintained approved items and prices with validity periods and multi-supplier listings for buyer choice.

Where the money leaks in a manual procure-to-pay process

Manual accounts-payable is expensive per transaction. Teams with automation process an invoice for around $2 to $3. Teams still matching by hand run closer to $10 or more (Ardent Partners, ePayables research). The gap is not the software licence but the time your finance team spends chasing approvals, keying data, and resolving exceptions a match rule could have caught.

The table below maps each procure-to-pay stage to where manual work costs you and what an automated workflow changes. Use it to locate your own biggest leak before you scope a build.

Procure-to-pay stageWhat goes wrong manuallyWhat automation changesWhere the saving comes from
Requisition and POOrders raised by email after goods arrive, with no commitment recordedCatalogue or free-text requisition routes for approval before the order is placedFewer maverick buys, duplicate orders, and off-contract spend
ApprovalSign-offs skipped, or stuck in an inbox for daysConditional routing on value, category, and cost centre, with delegation for absencesShorter cycle time and policy enforced on every order
Goods receipt and matchingInvoices matched by hand, exceptions found late in the monthThree-way match auto-approves within tolerance and routes only real discrepanciesLower cost per invoice and fewer late-payment penalties
Spend visibilityCommitted spend invisible until the month-end reconciliationCommitted vs actual spend by category, supplier, and cost centre in real timeBudget control and compliance with negotiated supplier rates
First module, $25,000-$45,000
Requisitions, approval routing against your authority matrix, and PO creation, launched as a validated v1 you can put in front of real buyers.
Full platform, $80,000-$150,000
Everything in the first module, plus three-way matching, spend analytics, category management, and integration with your ERP or finance system. Most teams grow into this over time, one workflow at a time.

How we work

From scope to live procurement system

  1. Week 1
    01

    Purchasing process scoping

    We map how your business manages purchasing today: the volume of orders, the approval process, and where the current approach creates problems. You leave week 1 with a written scope document and a fixed-price quote.

  2. Weeks 2-5
    02

    Authority matrix and matching rules design

    Approval routing, matching tolerances, and ERP integration designed against your actual purchasing policy.

  3. Weeks 6-14
    03

    Build and integrate

    Requisitions, approvals, and three-way matching built in parallel, tested against real purchasing scenarios.

  4. Final 2-3 weeks
    04

    Parallel run and launch

    The system runs alongside the existing process before full cutover, with the procurement team trained on catalogue admin.

Why us

Why operations and finance teams choose RaftLabs

  • 01
    Senior engineers build what they scope

    The engineers who assess your authority matrix also build the solution. No bait-and-switch, no offshore handoff after the contract is signed.

  • 02
    Fixed price before development starts

    We scope the work, calculate the cost, and lock it in writing before any development starts.

  • 03
    Shipping production software since 2015

    Real engagements across SaaS, fintech, healthcare, and logistics, not every one published as a named case study. Relationships, not vertical claims.

  • 04
    Built for audit and segregation of duties

    Every requisition, approval, and match is logged with who did what and when. Approval routing enforces segregation of duties, so the person who raises an order cannot approve it, the control auditors check under SOX.

  • 05
    We'll tell you when your ERP module is enough

    Custom is justified by real authority-matrix or catalogue complexity, not recommended by default.

  • 06
    Adoption designed in, not assumed

    A faster requisition experience and a parallel-run period address the real risk in any procurement rollout.

What we plan around

Most procurement rollouts fail on the same few things. Here is where they go wrong and how we design against each one before it happens.

Users route around the system
If the requisition flow is slower than email, people bypass it and the data stays incomplete. We build the buyer experience to be faster than the process it replaces, then run a parallel period before the old process is switched off.
Match tolerance set too tight
Zero-tolerance three-way matching turns every rounding difference into an exception, and the queue never clears. We set tolerances by category with your finance team so real discrepancies surface and noise does not.
ERP integration left to the end
Pushing approved POs and matched invoices back to SAP, NetSuite, or Dynamics is where timelines slip. We design that integration in week 2, not after the build is done.
The catalogue goes stale
Prices drift and approved suppliers change. We give the procurement team admin tools to maintain the catalogue and price validity without developer involvement.

What clients say

What our clients say

Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.

Gil Nugraha
Gil Nugraha
Indonesia flagIndonesia
Founder at UrShipper
I definitely recommend RaftLabs, especially to founders building complex platforms. They were transparent throughout the whole project.

We have not shipped a public, named procurement platform we can point to yet. The closest reference is adjacent supply-chain work: a multi-carrier shipping platform where the same disciplines apply, structured workflows, exception handling, and integrations that hold up under real transaction volume.

Useful next steps

More on retail & ecommerce

Frequently asked questions

Custom is right when your authority matrix is complex enough that the ERP's approval routing can't model it, when you need a catalogue and requisition experience fast enough that users actually adopt it, when your spend analytics go beyond standard ERP reports, or when the exception workflow your team needs doesn't match the module.

Yes. Common integrations include SAP, Oracle, Microsoft Dynamics, NetSuite, Xero, and QuickBooks, covering pushing approved POs to the ERP, receiving goods receipt confirmations, and pushing matched invoices to the payment queue.

We build a requisition and approval experience faster than the email process it replaces, and run a parallel period alongside the existing process so issues are resolved before the old process is switched off, plus admin tools so the procurement team manages the catalogue without developer involvement.

A first module covering requisitions, approval routing, and PO creation typically starts around $25,000 to $45,000, launched as a validated v1. Adding three-way matching, spend analytics, category management, and ERP integration grows the full platform to $80,000 to $150,000 over time.

Work with us

Have a procurement software project?

Tell us how your business manages purchasing today: the volume of orders, the approval process, and where the current approach creates problems. We'll scope a procurement system built around your actual purchasing operation.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.