From procurement signals to governed action.
GroundWorks is the foundation for building a cohesive source-to-pay platform for each client: one map of five stages, nine domain Workblocks, 45 business modules, 191 execution flows and 686 tasks; one shared vocabulary; one governed way to tailor and run.
GroundWorks composes five stages, nine domain Workblocks and 45 business modules into one governed source-to-pay map for partners to adapt and run.
Workblocks are integrated with client systems in days, not weeks, and working Workblocks are built in the same timeframe.
By the numbers
- 5
- of The whole source-to-pay map. · GroundWorks framework 5.3.0 · as of 2026-08-17
- 9
- of Every outcome boundary across the five stages. · GroundWorks framework 5.3.0 · as of 2026-08-17
- 45
- of Exactly five inside each domain Workblock. · GroundWorks framework 5.3.0 · as of 2026-08-17
- 686
- of 686 typed units compose the 191 execution flows. · GroundWorks framework 5.3.0 · as of 2026-08-17
Five stages, nine domain Workblocks
Plan and govern
Category Management: A live category agenda where every opportunity has an owner and a source.
Request and source
Intake Management: Every request arrives complete, routed and owned, without manual triage. Sourcing & Negotiation: Sourcing decisions you can defend line by line: every score opens the response behind it.
Contract and assure
Contract Lifecycle Management (CLM): Every clause, control and obligation stays attached to its contract, with a named owner for each one. Supplier & Third-Party Risk Management (TPRM): Every risk decision has an owner, a case file and a proportionate response.
Buy and pay
Purchasing & Ordering: The compliant route is the easiest one, and every exception reaches a named owner. Invoicing & Payment (AP): A payment queue where every exception carries its records and its owner.
Perform and realise
Supplier Relationship Management (SRM): Reviews end in commitments someone accepted, and the next review starts from what happened to them. Savings & Value Realisation: A savings number finance can trace to the records that produced it.
The nine domain Workblocks
- 01
Category Management · GroundWorks Radar
A live category agenda where every opportunity has an owner and a source.
Open the Workblock - 02
Intake Management · GroundWorks Gateway
Every request arrives complete, routed and owned, without manual triage.
Open the Workblock - 03
Sourcing & Negotiation · GroundWorks Dealroom
Sourcing decisions you can defend line by line: every score opens the response behind it.
Open the Workblock - 04
Contract Lifecycle Management (CLM) · GroundWorks Accord
Every clause, control and obligation stays attached to its contract, with a named owner for each one.
Open the Workblock - 05
Supplier & Third-Party Risk Management (TPRM) · GroundWorks Sentinel
Every risk decision has an owner, a case file and a proportionate response.
Open the Workblock - 06
Purchasing & Ordering · GroundWorks Buyline
The compliant route is the easiest one, and every exception reaches a named owner.
Open the Workblock - 07
Invoicing & Payment (AP) · GroundWorks Clearway
A payment queue where every exception carries its records and its owner.
Open the Workblock - 08
Supplier Relationship Management (SRM) · GroundWorks Alliance
Reviews end in commitments someone accepted, and the next review starts from what happened to them.
Open the Workblock - 09
Savings & Value Realisation · GroundWorks Value Hunter
A savings number finance can trace to the records that produced it.
Open the Workblock
Workblocks can be versioned and changed independently, enabling continuous client tailoring.
One invoice mismatch, end to end
When a match result shows a quantity difference, the AP processor needs to know whether the delivery, the receipt or the invoice is wrong, so that the case reaches the person who can correct the source record instead of bouncing between teams.
A failed check lands in a worklist as a code that names the symptom. The processor works out the cause and the owner by hand, one system at a time.
One invoice mismatch, end to end
- 01
The failed check is a fact; the cause is a hypothesis
An exception signal records what failed, not why. The case keeps the two apart: the source failure is never overwritten, and competing causes stay visible until the evidence distinguishes them.
- 02
From queue codes to causal cases
The failed check arrives as one case: the competing causes, the evidence that separates them, the accountable owner and the next valid action. The case closes only when the source system accepts the change and reruns the check.
- 03
A readiness decision carries its evidence and its expiry
Every satisfied condition names its source and observation time. A changed invoice, payee, hold or screening result expires the decision and reopens only the dependent checks. Readiness is never payment: instruction, release and settlement stay with the system that owns them.
- 04
Resolution means the source accepts and revalidates
A sent message or a completed task is not resolution. A case closes when the authoritative system accepts the change and the controlling check reruns clean, or it stays truthfully blocked with a named owner and a reopening condition.
The source record is corrected or the invoice validly corrected, the match reruns clean, and the case closes with the receipt attached.
Material or novel commitments still escalate. Proposal is not commitment. Authority is a contract, not a score.
Every AI action has a named human owner, human evaluation drives learning and review is automatically reinstated when quality falls.
Beyond Work execution rails are a European, AI-first, enterprise-native foundation, SOC 2 Type II audited and ISO 27001 certified.
One permissioned data plane carries records, documents, analytics and run history with one audit trail, and can connect to the client's existing warehouse.
One record model, 87 canonical entities in nine kinds of record.
What is built, and what is not
| Class | Definition | Count |
|---|---|---|
| Reference build | Demonstrable on the execution rails at confirmed fidelity | 8 |
| Defined module | Business, data, authority and execution contracts are defined for client configuration | 9 |
| Roadmap module | Planned and not represented as running | 28 |
8 reference modules, 9 defined modules and 28 roadmap modules.