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.
- Restaurant Reservation System
- Features
- Review and evidence
Review and evidence
Keep decisions, guarded operation results and payment receipts attached to the work.
OverviewOperation Exceptions×
Restaurant Reservation System · Review and evidence
New
Operation Exceptions
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| MO-24032 | OK-251 | ACT-634 | 470 | Failed | 16 Oct | |
| MO-31629 | OK-104 | ACT-699 | 70 | Needs review | 24 Oct | |
| MO-70115 | OK-438 | ACT-805 | 260 | Failed | 09 Oct | |
| MO-96420 | OK-431 | ACT-290 | 680 | Needs review | 04 Oct | |
| MO-28537 | OK-292 | ACT-589 | 360 | Failed | 11 Oct |
6 of 6 records
OK-251Operation receipts · OR-82706
FailedParentMO-24032
ActionACT-634
Expected revision470
Occurred at16 Oct
Failure reasonCut to length
What you can do
Decisions and reconciliation
Keep decisions, guarded operation results and payment receipts attached to the work. Finance Reviewer compares provider-issued payment evidence with the parent meal order before marking it verified. Service Manager works failed and uncertain operation receipts from their expected revision, action and effect references. Kitchen Supervisor records independent decisions on submitted ticket scope in review decisions. These records explain different events and should remain linked to the same order.
A payment provider sends a capture receipt for a served order. The finance reviewer compares the provider event identifier, amount, type and parent order before marking the evidence verified. Separately, a failed operation receipt remains in the exception queue with its expected revision and failure reason. The reviewer checks linked effects before closing the issue.
How the work is organized
- Working scope. Finance Reviewer matches each provider event identifier, type and amount to its parent order.
- Decision point. Service Manager investigates a Failed or needs review operation before any retry; Kitchen Supervisor decides ticket scope.
- Evidence. payment evidence holds provider references, while operation receipts and review decisions retain outcomes and reasons.
What to agree during setup
Agree how provider references are mapped, which attachments may be shared and who can verify payment evidence. Keep operation keys stable when a command is retried. A review decision must identify the revision it judged and the reviewer; an operation receipt records whether the guarded effect completed. Those records answer different audit questions.
Write down the policy in the team’s operating procedure before the first service cycle. Give each role the access it needs for its step and rehearse denied access as well as the successful path. The organization and location on the order should match the staff and service work involved.
Check the handoff on an actual case
Rehearse a repeated provider event and a failed operation. The reviewer should identify the earlier event before verification and inspect the operation receipt before any retry. Attach the relevant evidence to the order. If the effect is still uncertain, leave the result needing review rather than claiming completion.
Have Service Manager compare the failed receipt with the current order revision and any recorded effect. Finance Reviewer should leave an unmatched provider event unverified and retain its original identifier.
What your team sees
- Operation Exceptions — Find failed or uncertain operations with their reason and expected revision.
- Unverified Payment Evidence — Check provider events that still need matching to an order.
Follow the work through
See the connected process for the handoff and the data model for record links.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions on submitted revisions.
- Operation receipts
- Durable receipts for guarded operations and their outcomes.
- Payment evidence
- Provider-issued authorization, capture, refund and void receipts.
- Record attachments
- Files and evidence attached to operational records.
- Meal orders
- Customer orders accepted and fulfilled by the kitchen and service team.
Who uses it
Permissions- Finance Reviewer
- , Kitchen Supervisor, Service Manager, Admin.
Set up Restaurant Reservation System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.