Evidence and exceptions

The evidence trail connects each financial action to the source revision and the actual effect. Attachments carry the documents a reviewer used, decisions identify the reviewer and reason, and operation receipts record stable keys and result states. The Operations Overview gives the team a place to see pending decisions and failed operations alongside posted value and ledger balance.

• Keep review evidence. Attach supporting files to the document with upload identity, time and visibility.
• Record each decision. Preserve source revision, reviewer, decision and reason as a distinct review record.
• Inspect uncertain actions. An operation receipt identifies the action, expected revision, effect references and any failure reason.

A completed operation has a different meaning from a pending or needs-review result. The team should inspect the persisted source and effects before repeating a failed action. Stable keys support a safe retry, while effect references help match a result to the journal, application or statement it affected. A provider reference matters only for an action that actually used a provider.

Define who can upload internal versus shared evidence and who can read each visibility level. Decide how long source evidence remains accessible for review. Assign the reviewer who may reconcile an uncertain operation and the controller who may authorize a financial correction. A preparer should not be able to erase accepted effects by editing the source record.

Agree how to distinguish unexecuted draft scope from executed scope. Draft work can be cancelled within its allowed route. Executed work needs a compensating journal approved by a reviewer, retaining the original source identity. Accepted work without an executed effect follows its eligible cancellation route. Document the reason so later readers can follow both the original and correction without mistaking them for duplicate activity.

Use a document whose first revision was rejected and second revision approved. Inspect both decisions, their reviewer identities and reasons. Follow the approved revision to its operation receipt and posted effects. Trigger a reconciliation of a pending or failed receipt and compare the recorded references with the actual local records before deciding whether it completed. If a provider was involved, check its reference only after local evidence is assessed.

Next correct an executed amount. Keep the original source and journal visible, request the independent approval, and inspect the compensating journal. A reviewer should be able to explain the net result and the reason from the records alone. This is also a useful access rehearsal: a viewer may read permitted evidence but cannot make the correction decision.

• Operations Needing Review — Actions whose effect identity and source revision need a reviewer check.
• Failed Operations — Failed actions with their recorded reason and parent document.
• Returned and Rejected Decisions — Review outcomes that call for correction or a new submission.

See correction and reconciliation and statement review.