Evidence and exceptions

A guarded operation leaves an operation receipt with its key, action, expected revision, result state and occurrence time. It may also hold an external reference, effect references or failure reason. That record lets Exception Reviewer ask what actually happened when an acceptance, release or correction does not return a clear result. The Distribution Operations page brings accepted orders, fulfilled portions, pending dispatch decisions and failed operations into one exception queue that opens the underlying record.

Reconciliation begins by reading the receipt and its linked local effects. The reviewer compares scope, identity, quantity and revision, then checks an external reference if one applies. Completion is recorded only when the expected effects match. A pending or failed receipt is not an instruction to repeat an external action.

• Operation receipt. Preserve the action identity, expected revision and result for each guarded transition.
• Independent review. Keep reviewer decisions, source revisions and reasons connected to the parent order.
• Supporting evidence. Attach files with their visibility, evidence type, uploader and upload time.

Decide which evidence types the team uses for acceptance, release, refund and correction, and who may see a shared or internal attachment. Name the Exception Reviewer for each organization. Agree how the reviewer verifies a provider reference and how a failed action is escalated. Keep the provider’s payment event identity and verified state with the payment evidence so a duplicate refund request can be recognized.

For a ticket release that times out, the reviewer opens the operation receipt before doing anything else. If the distribution event exists and matches the expected revision and quantity, the receipt can be reconciled to that effect. If it does not, the team investigates the failure reason and external reference before deciding on a new action.

Select an order with a failed or review-needed receipt. Trace its operation key to the parent order, current revision, dispatch ticket, review decision and distribution events. Compare the recorded effect references with the actual records. Attach the supporting file and retain who uploaded it. If a compensating correction is needed for already executed scope, obtain independent review and preserve the original records.

For a cancellation that includes payment activity, read the provider-issued authorization, capture, refund or void evidence and its verification state. The workflow asks for an approved refund and checks provider evidence, so a second request for the same outcome must not create a second refund. Partially served orders retain the served portion history even when remaining scope is cancelled.

• Operation Exceptions — Failed and review-needed receipts with the action and reason.
• Pending Operation Receipts — Guarded actions awaiting effect verification.
• Unverified Payment Evidence — Provider events still requiring review.

Use corrections and reconciliation for the read-first review and dispatch review for ticket authority.