Procurement breakdowns explained through the record that someone will need six months later.
FILE 01
The Quote on Ravi’s Phone
The supplier quote exists, but only in one employee’s chat. The approval record has no copy and the award cannot be reconstructed.
Accountable workflow: Attach each invited response to the sourcing event and keep the comparison with the decision.
FILE 02
The Corridor Approval
A manager verbally approved the purchase between meetings. Months later, no one can prove scope, value or authority.
Accountable workflow: Route the request to the accountable approver and retain the attributable decision.
FILE 03
The Missing Eight
Ordered: 40. Received: 32. Invoiced: 40. The invoice moved forward because the receipt exception was not visible.
Accountable workflow: Match order, accepted receipt and invoice; hold the exception until evidenced or corrected.
All scenarios above are fictional or composite. No customer claim or identifiable procurement record is implied.
SYNTHETIC AUDIT PACK COMPLETENESS EXPLAINER
A trustworthy pack says what is present—and what is not.
EVIDENCE AVAILABLE
Approval decision
A named approver, decision and timestamp are present and traceable to the synthetic request.
EVIDENCE UNAVAILABLE
Second supplier response
The pack records the missing response instead of implying that competitive evidence is complete.
NOT APPLICABLE
Goods receipt
This synthetic example is a service purchase; the reviewer records why service acceptance evidence applies instead.
EXCEPTION OPEN
Invoice versus acceptance
The unresolved difference remains visible with an owner and review status.
SAMPLE MANIFEST
Generation ID: SAMPLE-AP-2026-001
Organisation: Fictional Example Services
Scope: one synthetic transaction
Transactions included: 1 · excluded: 0
Missing evidence: 1 · unresolved exceptions: 1
Pack version: synthetic-explainer-v1
BOUNDARY
This explains the disclosure model; it is not an audit opinion. It does not claim every live RAQOZ export includes future framework, period, location or Control Pack fields. The existing transaction Audit Pack and SHA-256 source manifest remain governed by their released scope.