These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Petty Cash Management
- Features
- Review and evidence
Review and evidence
Keep decisions, attachments and guarded action outcomes traceable.
OverviewReview Decision History×
Petty Cash Management · Review and evidence
New
Review Decision History
Review decisions
| Parent | Source revision | Decision | Decided at | Reason | Reviewer | |
|---|---|---|---|---|---|---|
| AD-34794 | 400 | Approve | 18 Oct | Approve rd-377 | ||
| AD-18366 | 70 | Return | 05 Oct | Reject rd-171 | ||
| AD-65150 | 880 | Approve | 20 Oct | Return rd-263 | ||
| AD-20029 | 20 | Return | 22 Oct | Approve rd-501 | ||
| AD-85943 | 640 | Approve | 11 Oct | Reject rd-590 |
6 of 6 records
Approve rd-377Review decisions · RD-45087
ApproveParentAD-34794
Source revision400
Decided at18 Oct
What you can do
Show what was decided
Review is tied to an accounting document and its source revision. The decision records who reviewed it, when, the decision and the reason. An Accounting Reviewer can approve, reject or return a document revision. The reviewer must examine the source and its evidence independently of the Accounting Preparer who submitted it. This gives an Auditor a usable trail from the document to the person and version behind the decision.
Attachments keep the receipt or other support with the document. Each attachment has a title, evidence type, upload date, visibility and uploader. Use these details to make the review packet understandable months later. A title such as the purchase receipt is more useful than an unexplained file name. Internal and Shared visibility should reflect who needs to see the material during review.
How the work is organized
- Assemble evidence. The Accounting Preparer attaches the supporting file to the source document before requesting review.
- Record the decision. The Accounting Reviewer checks the current revision and records Approve, Reject or Return with a reason.
- Inspect action outcomes. Operation receipts show whether a guarded action is Pending, Completed, Failed or needs review.
Operation receipts are also the place to see why an action needs attention. Their operation key, action, expected revision and effect references tie an attempt back to a document. A failed attempt should be investigated from its reason, rather than repeated without checking whether it already made a local effect.
What to agree during setup
Define which evidence types the team uses and when an attachment may be Shared. Agree the minimum reason expected from an Accounting Reviewer, especially on a rejected or returned revision. Decide who investigates Failed and needs review operations and how they hand a finding back to the Accounting Preparer. Keep reviewer independence in the assignment practice as well as in the decision record.
The review queue should have a named owner each day. It is easy for a document to remain in Review when the reviewer assumes someone else is handling it. A clear queue routine makes the pending decision visible without changing the underlying source record.
Check the handoff on an actual case
Prepare a document with a receipt attachment, then send it to Review. Ask the Accounting Reviewer to read the attachment, line detail and gross amount before deciding. Record a reason that would still make sense to an Auditor reviewing the same revision later. Repeat with a receipt that disagrees with the amount and return or reject the revision. The preparer should correct the source and submit the new revision for a fresh decision.
For an action exception, inspect the operation key and effect references before retrying. Confirm whether the intended document, journal or application exists. Record the discrepancy so another reviewer can see why the action remained under attention.
What your team sees
- Documents Awaiting Review — The current documents waiting for an independent decision.
- Review Decision History — Prior decisions with reviewer, source revision and reason.
- Operations Needing Attention — Failed or needs-review actions with their reasons and parent documents.
Follow the work through
Continue with document approval and reconciliation.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions per document revision
- Record attachments
- Evidence files attached to accounting documents
- Operation receipts
- Idempotent operation receipts for guarded commands
- Accounting documents
- Core accounting documents with lifecycle and revision
- Team members
- Staff with organization membership and role scope
Who uses it
Permissions- Accounting Reviewer
- Makes document decisions and investigates action outcomes.
- Accounting Preparer
- Supplies source evidence and corrections.
- Auditor
- Reads the trail.
- App Administrator
- Maintains membership scope.
Set up Petty Cash Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.