Skip to content
05Enterprise Software / Procurement ManagementConcept Project

ProcureX

From requisition to payment — controlled, auditable purchasing for growing organisations.

Type
Enterprise web platform
Platform
Web console, mobile approvals
Scope
Product design, architecture, full-stack
Status
Concept Project

Procurement overview. Approval queue, spend by category, purchase-order pipeline and top suppliers.

01

Overview

ProcureX is a concept for an enterprise procurement platform for organisations that have outgrown email-based purchasing and need control without slowing teams down.

It covers the full procure-to-pay cycle — from a department's request through approvals, ordering, receiving and invoicing — with a complete audit trail at every step.

02

Problem & solution

The business problem

In many organisations, purchasing runs on emails, spreadsheets and signatures. It works until volume grows — then spend becomes hard to control and harder to explain.

  • Purchase requests stall in inboxes with no visibility into who needs to approve.
  • Approval rules exist on paper but are applied inconsistently.
  • Supplier details, contracts and compliance documents are scattered.
  • Invoices are paid without being checked against what was ordered and received.
  • Finance cannot see committed spend against budgets until it is too late.

Proposed solution

A procurement workflow platform where every purchase follows the organisation's rules automatically, and every decision is recorded.

  • Configurable approval workflows based on amount, department, category and budget.
  • Requisitions that become purchase orders once approved, with budget checks along the way.
  • Supplier onboarding with documents, verification and performance history.
  • Three-way matching of purchase order, goods receipt and invoice before payment.
  • Spend analytics by department, category, supplier and period.
03

Key features

  • 01

    Supplier onboarding

    Supplier self-registration with document collection, verification steps and approval.

  • 02

    Vendor management

    Supplier profiles, contacts, categories, ratings, contracts and compliance status.

  • 03

    Purchase requisitions

    Structured requests with line items, cost centres, budget codes and attachments.

  • 04

    Purchase orders

    Generated from approved requisitions, sent to suppliers and tracked through delivery.

  • 05

    Multi-level approval workflows

    Rule-based approval chains with delegation, escalation and reminders.

  • 06

    Invoice management

    Invoice capture and matching against purchase orders and goods receipts.

  • 07

    Contract management

    Contract terms, renewal dates and spend against contract value.

  • 08

    Spend analytics

    Spend by department, category and supplier, with budget versus actual.

  • 09

    Inventory integration (concept)

    Integration concept for syncing received goods with inventory systems.

  • 10

    Role-based access control

    Fine-grained permissions with separation of duties between requesters, approvers and finance.

04

Interface design

Supplier profile. Onboarding checklist, compliance documents, contracts and performance.
Approval on mobile. Multi-level approval chain with budget check and line items.
05

User roles & workflows

Any employee who needs to buy something for their team.

  1. 1

    Create a requisition

  2. 2

    Attach quotes and justification

  3. 3

    Track approval progress

  4. 4

    Confirm goods received

06

Architecture

L1Clients
  • Employee portal
  • Approver inbox (mobile)
  • Procurement & finance console
  • Supplier portal
L2API
  • REST API
  • RBAC & separation of duties
  • Audit log
L3Domain services
  • Workflow & approval engine
  • Requisitions & POs
  • Supplier service
  • Invoice matching
  • Spend analytics
L4Data
  • PostgreSQL
  • Redis — job queue
  • Document storage
L5Integrations
  • Email notifications
  • ERP / accounting export (concept)
  • Inventory sync (concept)
Architecture overview — proposed design

Policy as configuration

Approval chains are defined as data — conditions on amount, department and category mapped to approver roles — and evaluated by a workflow engine, so policy changes don't need code changes.

Snapshotting the rules

When a request is submitted, its approval chain is resolved and stored with it, so later policy changes never alter approvals already in flight.

Three-way matching with tolerances

Invoice lines are matched to PO and goods-receipt lines with configurable price and quantity tolerances; anything outside goes to an exceptions queue.

Audit by default

Every state change records who, what, when and why — a complete trail suitable for internal and external audits.

07

Technology stack

Frontend
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
Backend
  • Node.js
  • NestJS
  • REST API
  • BullMQ
Data
  • PostgreSQL
  • Prisma ORM
  • Redis
Infrastructure
  • Docker
  • S3-compatible storage
  • SSO — SAML / OIDC (concept)

Proposed stack for the concept; choices would be validated against a real client's constraints.

08

Engineering considerations

  1. 01

    Flexible but predictable workflows

    Every organisation's approval policy is different. The engine had to be configurable while still producing workflows people can read and reason about.

  2. 02

    Delegation and absence

    Approvers go on leave. Time-boxed delegation and escalation rules keep requests moving without bypassing controls.

  3. 03

    Separation of duties

    The same person should not request, approve and pay. Conflicting role combinations are detected and blocked at the API level.

  4. 04

    Designing for adoption

    Procurement tools fail when they slow people down. Forms default sensibly, and approvers can act from a focused, mobile-friendly inbox.

09

Project status

Concept Project

ProcureX is a self-initiated concept project, created to explore product design and engineering for enterprise procurement. It has not been delivered to or deployed for a client. The interface designs and architecture are presented as a case study, and all names, businesses and figures shown in the mockups are illustrative.