1. Revenue Recognition
  2. Features
  3. Review evidence
Feature · Review evidence

Review evidence

Keep human decisions and executed action receipts traceable.

OverviewReview Exceptions
Revenue Recognition · Review evidence

Review Exceptions

Review decisions

New
Decision numberSubject typeSubject referenceDecisionReason codeReviewer
RD-27149PlanPlan rd-686ReturnedApproved as Submitted
RD-22965Plan LinePlan Line rd-989ReturnedAmount Variance
RD-47737Revenue ScheduleRevenue Schedule rd-494ReturnedMissing Documentation
RD-22607Billing RunBilling Run rd-565ReturnedRevenue Policy
RD-13422InvoiceInvoice rd-138ReturnedTerms Mismatch
6 of 6 records
Plan rd-686Review decisions · RD-27149
Plan
DecisionReturned
Reason codeApproved as Submitted
Decided at05 Oct
Example screen with sample data

What you can do

Review evidence in practice

A review decision identifies its subject, result, reviewer, time and reason. It can reference a plan, billing run, invoice or revenue schedule. Evidence documents carry a title, kind, file location, uploader and timestamp for a parent record. Operation receipts describe a performed action, actor, outcome and related record. Together, these records let Finance inspect what someone decided and what an action actually did.

How the work is organized

  • Decide. Finance Approver records a decision against the subject and explains a return or rejection.
  • Attach. Evidence documents identify their parent record, file location, kind and uploader.
  • Trace. Operation receipts show the action, actor and result; a Skipped result does not advance the subject.

A plan approval creates a review decision and an operation receipt. Compare their subject and related record with the plan, then inspect the recorded time and reviewer. For a billing run advance, follow the operation receipt back to the run and check whether it succeeded or was skipped. A returned or rejected decision belongs in Review Exceptions so the owner can act on the stated reason.

What to agree during setup

Agree document retention, file access and who may record each decision. Decide which evidence kind is useful for contracts, approvals and remittances. Ensure reviewers identify the actual subject they inspected before deciding. A URL to a document is useful only when the permitted person can retrieve the correct version from its owning store.

Choose an in review plan and a Draft billing run for the first evidence review. Confirm that the plan decision points to the plan and the operation receipt identifies the attempted action. On the run, compare its state with the receipt result before reporting that validation occurred.

Check the handoff on an actual case

Finance Approver opens a review exception, follows the subject reference and reads the reason code and notes. Revenue Accountant checks evidence associated with a schedule; Billing Operations Manager checks receipts for a run. During rehearsal, inspect both a successful transition and a refused transition. The different receipt results should remain attributable to the actor and the target record.

Have the reviewer open the same subject from Review Exceptions and check the reason code and reviewer. Then follow the document link and its parent record identifier. If the file or subject differs from what the decision describes, correct that reference before the next review.

What your team sees

  • Review Exceptions — Investigate Returned and Rejected decisions by subject and reason.
  • Plans Awaiting Approval — Open the in review plan behind a pending finance decision.
  • Billing Runs Open for Validation — Compare a Draft run with the receipt from its latest attempted advance.

Follow the work through

Use decision and evidence review to compare a subject, human decision and action receipt. Review the data model when mapping source identifiers and roles when assigning the people who may act.

What it keeps track of

Data model
Review decisions
Approval decisions on plans, billing runs, invoices and revenue schedules.
Evidence documents
Evidence files attached to any parent record with kind, uploader and timestamp.
Operation receipts
Executed-operation evidence with operation type, actor, result and document URL.
Plans
Budget and forecast plan headers with period, owner, version and approval status.
Billing runs
Billing cycle headers with period, invoice counts, total and validation status.
Invoices
Customer invoices with issue and due dates, subtotal, tax, total and status.
Revenue schedules
Revenue recognition schedules with method, recognized to date and deferred balance.

Who uses it

Permissions
Finance Approver
Owns plan decisions and their review evidence.
Billing Operations Manager
Checks receipts from billing run advances.
Revenue Accountant
Checks schedule evidence; Admin maintains access to the linked records.

Set up Revenue Recognition your way.

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

How to get started