Skip to main content

3. Procure-to-Pay & Supply

What this flow tells you​

Whether you can deliver consistently and profitably — does demand have matching supply, do suppliers perform, do you pay them on time at agreed terms? In a SaaS-first business this is dominated by cloud and tool spend; in a service-first business it is contractor and partner payments; in a physical business it is inventory and raw materials.

Data sources​

  • Demand-to-purchasing — forecasts, reorder points, capacity plans, purchase requisitions, POs
  • SaaS vendor spend — subscriptions per tool, seat counts, usage-tier billing, renewal dates
  • Supplier performance — confirmations, delivery dates, actual receipts, quality issues, SLA breaches
  • Payables — supplier invoices, approval state, 3-way match status, payment runs, cash-out timing

Decision gates​

  • Approve or reject PO — within budget, within sourcing policy, vendor in good standing. Owner: budget owner + procurement.
  • 3-way match — PO + receipt + invoice must reconcile before payment. Owner: AP automation.
  • Payment release — within terms, fraud-checked, treasury has funds. Owner: finance ops + treasury.
  • Vendor offboard — repeated SLA breach triggers replacement workflow. Owner: procurement.

AI capabilities required​

  • Perception — read invoices (structured + PDF), receipts, contract terms; detect duplicate-billing, anomalous pricing.
  • Decision — reorder triggers on consumption; 3-way match auto-clear vs flag for human; payment-batching for cash optimisation.
  • Action — issue PO, route invoice for approval, schedule payment, post AP entry.
  • Escalation — flag SLA breach, contract drift, fraud signal, working-capital crunch.

Crypto-rail instruments​

  • UCP vendor checkout — Google's Universal Commerce Protocol exposes vendor capabilities (catalog, pricing, fulfilment) for agent-to-vendor purchase without scraping. See UCP protocol.
  • On-chain BOL / receipt — bill of lading or service-receipt minted on chain; immutable proof of delivery for 3-way match.
  • Multi-sig payables wallet — payment-release authorisation distributed across approver set; cryptographic enforcement of payment policy.
  • Supplier-finance pools — on-chain pools that early-pay supplier invoices at a discount; transparent rate, no banking friction.
  • Stablecoin cross-border payment — pay international suppliers in USDC; settlement minutes, not days.

Gauge​

Cycle time from PO to payment, by vendor class. Drift up = process friction; drift down with quality intact = optimisation. SaaS variant: % of SaaS spend with active utilisation > 50% (avoid shelfware).

Kill signal​

Stockout rate > 2% (physical) OR critical SaaS tool fails renewal OR > 10% of supplier payments late by > 30 days. Each triggers cash-flow drift downstream.

Skill coverage​

Shipped: kyc-screener — vendor identity + sanctions check at onboarding. Vendor-spend visibility lives in the financial flow.

Green-field: UCP-aware procurement agent (browse catalog → quote → PO → settle); 3-way-match auto-clearer with on-chain BOL ingestion; multi-sig payables runner with policy-as-code; supplier-finance pool participation broker.

Full matrix: skills-matrix.

Upstream / downstream​

5P slice​

5P inspection: Principles (no rekeying, no manual approval below policy threshold), Performance (cycle time + leakage), Platform (procurement + AP automation + treasury + wallet), Process (forecast → PO → receipt → invoice → match → pay), Players (procurement + finance + budget owners + AI agent on perception and decision).