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.
- Legal Billing & Time Tracking
- Features
- Review and evidence
Review and evidence
Preserve the actor, reason and revision behind every decision.
OverviewDecision history×
Legal Billing & Time Tracking · Review and evidence
New
Decision history
Review decisions
| Parent | Reviewer | Source revision | Decision | Decided at | Reason | |
|---|---|---|---|---|---|---|
| AD-58324 | 270 | Approve | 15 Oct | Approve rd-583 | ||
| AD-63482 | 760 | Return | 06 Oct | Reject rd-339 | ||
| AD-61533 | 950 | Approve | 06 Oct | Return rd-713 | ||
| AD-73275 | 220 | Return | 13 Oct | Approve rd-362 | ||
| AD-93564 | 300 | Approve | 06 Oct | Reject rd-181 |
6 of 6 records
Approve rd-583Review decisions · RD-38771
ApproveParentAD-58324
Source revision270
Decided at15 Oct
Operation keyOK-159
What you can do
Review and evidence in practice
An approval is an explicit decision by a different person from the preparer. The reviewer inspects the document’s organization, owner, counterparty, amount, revision and attached evidence. A decision record retains the reviewer, source revision, decision, time, reason and operation key. That trail is more useful than a status alone when the document is questioned later.
Attachments keep a title, uploader, upload time, evidence type and visibility with the parent document. Choose visibility carefully for supporting financial material. Operation receipts record what action was requested, the expected revision, an external reference when present and the actual effect references. A pending receipt can become completed only after the claimed effect is found in local records. A discrepancy belongs in a review state with a reason; repeating the same operation should not create a second financial effect.
How the work is organized
- Freeze the basis. The reviewer checks the current document revision and supporting material.
- Record the decision. Keep the actor, reason, time and operation key with the parent.
- Verify the outcome. Compare a receipt with its actual effect before closing it.
What to agree during setup
Agree which documents require a second person’s decision, what evidence is sufficient, and how a returned request is revised. Set a reason convention that allows an auditor to understand a rejection without contacting the original reviewer. Define how external references are captured and who investigates a failed or unresolved receipt. Keep protected evidence read only after acceptance or posting.
Check the handoff on an actual case
Take a document in review with a supporting attachment. Ask its owner to attempt self-approval and confirm the request fails. Have an independent reviewer approve the exact revision and inspect the decision row, reason and receipt. Repeat the same command with the same operation key; it should return the same effect rather than create another decision or posting. Change the amount and check that an old decision cannot carry over.
The handoff should show who made each decision and which record changed. Ask a preparer and reviewer to repeat the case from their own access. Confirm the auditor can reconstruct the sequence without changing the source records. If a provider result is involved, compare the external reference and persisted effect before closing the case.
What your team sees
- Decision history — Read the actor, reason and exact revision for each recorded decision.
- Document attachments — Inspect the title, evidence type, uploader and visibility of source files.
Follow the work through
Continue through document preparation, independent review and reconciliation. Use the data model to confirm the record links before an import.
What it keeps track of
Data model- Review decisions
- Independent approver decisions recorded against a frozen instruction revision.
- Record attachments
- Supporting documents attached to a banking instruction.
- Operation receipts
- Idempotent operation receipts with stable operation keys and actual effect references.
- Accounting documents
- Central accounting document: readable record number, subject, lifecycle status, business date, gross amount USD, revision and counterparty.
Who uses it
Permissions- Accounting Reviewer
- Decides.
- Accounting Preparer
- Supplies evidence.
- Auditor
- Inspects the decision trail; Finance Lead investigates exceptions.
Set up Legal Billing & Time Tracking your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.