Decision ReceiptProcurement ApprovalDR-K7M9-2P4Q
Verified- Decision
- Approved by Risk Committee
- Policy
- Third-party risk — Tier 1, v7
- Evidence
- 3 attestations, 2 documents
- Integrity
sha256:0xdead…beef
Use casesProcurement approvals
Procurement approvals you cannot prove.
Approvals are routed every day. When asked to explain them later, most organisations cannot produce a verifiable Decision Receipt.
MeshQu changes that.
Signals
Request
Supplier
Spend tier
Policy
Approver actor
Decision
Procurement decision at execution
Approve · Reject · Escalate
Proof
Decision Receipt
Verified
01The moment
An approval is made.
A supplier is selected. A spend threshold is crossed. An exception is requested.
A decision is made: Approve, Reject, or Escalate.
Approval requested
Renewal · Acme Cloud Services Ltd.
- Spend
- £284,000 / yr
- Tier
- > threshold
- Exception
- Sole-source Waiver
ApproveRejectEscalate
02The failure
You are asked to explain it later.
Why was this supplier approved? Why was the threshold exception granted? Who accepted the risk? Which policy applied?
The answer is reconstructed from email threads, procurement systems, spreadsheets, and approval notes. It takes time. It depends on memory. It doesn't hold up.
Reconstructing the approval…
- Search email threads45 min
- Pull ERP export20 min
- Find approval spreadsheet30 min
- Recover approver notes40 min
- Build justification60+ min
That's not proof.
03The reason
It was never captured at execution time.
Procurement systems are built to route approvals and record status — not to produce verifiable evidence of the decision itself. No Decision Receipt is produced.
The approval happens. The proof doesn't.
Signals received
Logs written
The gap
No verifiable proof captured
04The shift
Approvals should produce proof.
Not email trails. Not screenshots. Not reconstructed justification.
A procurement decision should leave behind a verifiable record at the moment it is made.
Signals received
Logs written
Decision + Proof
At execution
05At execution
Captured as it happens.
Most procurement systems capture approval status after the decision.
MeshQu captures the decision at execution time.
After the fact is audit. At execution is control.
REPOAP
MeshQu Decision Layer
Decision Receipt
Verified
06The receipt
Every approval produces a receipt.
A Decision Receipt contains the request, the supplier and spend context, the policy applied, the threshold or exception rules, the outcome, and the actor.
Quotes, contracts, exception waivers — bound to the receipt by hash. The document, not the document copy. The receipt proves which version was in front of the approver.
Signed. Verifiable. Replayable. No reconstruction required.
07A new layer
It works with what you already use.
Procurement platforms. Approval workflows. ERP systems. Supplier management tools. MeshQu doesn't replace them.
Your systems route the approval. MeshQu proves the decision.
ERP
Procurement
Workflow
Supplier mgmt
MeshQu
— receipt
decisionapprove
policyPROC-v2.7
actorcfo+cmt
sealverified ◎
08Consistency
Human or system. Same proof.
Automated threshold check. Manager approval. Committee sign-off. Exception review. Every decision produces the same receipt.
Automated threshold
Spend + policy
Manager approval
Single approver
Committee sign-off
With exceptions noted
Same receipt, every time.
09The result
You can answer immediately.
The receipt resolves in seconds — what happened, why, under which policy, with what evidence, and who approved it. Verifiable.
Asked
Why was this approved?
RCP-01H7M12B7G6P3CR VerifiedResolved in 2.0 seconds
Does this replace our procurement or ERP system?
No. MeshQu captures the decision your procurement and ERP systems already produce.
10Close
You already make these decisions.
The question is — can you prove them?
Decision AssuranceCapture every decision. Prove every time.