1. IT Procurement System
  2. Features
  3. Evidence and receipts
Feature · Evidence and receipts

Evidence and receipts

Read attachments, decisions and guarded action outcomes in one request context.

OverviewReceipt exceptions
IT Procurement System · Evidence and receipts

Receipt exceptions

Operation receipts

New
ParentOperation keyActionExpected revisionResult stateOccurred at
PR-46903OK-192ACT-707430Failed27 Oct
PR-27928OK-438ACT-622590Needs review19 Oct
PR-87936OK-767ACT-103590Pending12 Oct
PR-76750OK-988ACT-679510Failed27 Oct
PR-59688OK-100ACT-394180Needs review13 Oct
6 of 6 records
OK-192Operation receipts · OR-85739
Failed
ParentPR-46903
ActionACT-707
Expected revision430
Occurred at27 Oct
Failure reasonCut to length
Example screen with sample data

What you can do

Evidence and receipts in daily work

A request can carry files with title, evidence type, upload time, uploader and Internal or Shared visibility. An operation receipt records its action, operation key, expected revision, result state and time. A failed receipt can carry a failure reason; a completed receipt may carry an external reference.

Attachments and operation receipts are separate kinds of evidence. The attachment records a file, uploader and visibility. An operation receipt records the result of an action against an expected request revision. A failed result calls for a person to inspect the parent before deciding what to do next.

How the work is organized

  • Ownership. Buyer uploads request evidence. Purchasing Approver reconciles operation outcomes. Auditor reads authorized evidence.
  • Record context. Use the parent request and its organization when checking a related record, then confirm the selected supplier and owner where relevant.
  • Evidence. Keep the decision, accepted quantities, attachments and operation outcomes with the same purchase context so later review has the facts in order.

What to agree during setup

Agree which evidence can be Shared and who may upload it. Keep an operation key distinct for each guarded action and compare its expected revision with the parent request before taking a follow-up action. Preserve the failed receipt so the investigation has a dated record.

Rehearse a failed operation receipt. The Purchasing Approver reads its expected revision, failure reason and effect references beside the parent. Agree who investigates an external effect and who records the conclusion before any further action.

Check the handoff on an actual case

Open a failed or needs-review receipt beside its parent request. Compare the operation key, expected revision, action and result with the current request and review decision. Read the failure reason and any effect references. Record the reviewer conclusion before another action is attempted.

The Purchasing Approver should compare the receipt with the parent revision and any decision. The Auditor should find the same failure reason and attached evidence. A request marked received does not, by itself, explain a failed operation result.

What your team sees

  • Receipt exceptions — Inspect failed, pending and needs-review action results with their parent requests.
  • Completed operations — Read completed action results and external references.
  • Shared attachments — Find files marked Shared with uploader and evidence type.

Follow the work through

Read request preparation, review and order and receipt reconciliation. The data model shows how the records connect.

What it keeps track of

Data model
Record attachments
Uploaded evidence files linked to a purchase request with visibility scope.
Operation receipts
Idempotent operation receipts recording the actual result of each guarded action.
Review decisions
Independent reviewer decisions recorded against a purchase request revision.
Purchase requests
IT purchase requests with lifecycle status, owner, counterparty and requested USD amount.
Team members
Authenticated platform identities with an active membership and role in an organization.

Who uses it

Permissions
Buyer
Uploads request evidence.
Purchasing Approver
Reconciles operation outcomes.
Auditor
Reads authorized evidence.
App Administrator
Maintains organization membership and supplier configuration.

Set up IT Procurement System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started