Payment and Corrections

Online payment evidence records a provider event identifier, authorization or capture or refund or void type, amount, time and verification state. Corrections begin with the current order revision and its meal lines. The team distinguishes an unexecuted draft change from accepted or served work so a cancellation preserves the original service history.

• Read the original scope. Order Owner compares the current revision with requested and served portions before changing an order.
• Review compensation. Service Supervisor decides which remaining scope is eligible; the earlier service and decisions stay in history.
• Verify the provider event. Reconciliation Analyst matches any refund or void receipt to the order before closing the operation.

Agree who can request a refund, who reviews compensation and how provider references are matched to the order. A provider receipt is evidence of the external event, not permission to infer service completion. Waste belongs in ingredient movements, while served portions remain on the meal line. Keep each operation key stable across a retry.

Service Supervisor reviews compensation against the current order revision and prior service. Reconciliation Analyst checks the provider event identifier and amount before confirming a refund. Keep the original operation key when a request is repeated so the team can find its prior effect.

Take an order with one served line and one unprepared line. Cancel only the eligible remainder and keep the served portion on the first line. If a refund is approved, match the provider refund event to the order and verify it before closing the case. Repeat the correction request and confirm it returns the prior result without issuing another refund.

Read the earlier service and operation receipt after the cancellation. The served quantity must remain visible. Check the provider event identifier on a refund before resolving its receipt. A repeated correction should return the earlier result instead of creating a second provider request.

• Unverified Online Payments — Provider receipts still awaiting verification.
• Fulfilled Order Lines — Requested and served quantities for the affected order.
• Operation Exceptions — Failed or disputed actions requiring a receipt check.

The analyst sees unverified provider events. Order Owner can locate the remaining order scope. Service Supervisor reviews the requested compensation with the prior decisions and receipts in view. A failed or uncertain operation remains in the exception queue until the local and provider effects agree.

Follow order acceptance, kitchen preparation, ticket release and reconciliation to rehearse the handoffs around this module.