Payments and corrections

Payment evidence stores provider-issued authorization, capture, refund and void events against the service order. Each event has an external identity, amount, occurrence time, provider reference and verification state. Finance Lead uses those records to compare a proposed refund or correction with what the provider has actually confirmed. An order amount alone cannot establish that money moved.

A cancelled or changed meal requires careful scope review. The team distinguishes draft work that was never executed from accepted work, prepared lines and served portions. Service Lead keeps the original order and line history. Independent Reviewer decides a compensating action against the current revision, and Finance Lead checks any payment effect before concluding the case.

• Provider evidence. Finance Lead reviews the actual event identity, type, amount and verification state.
• Scope history. The order, lines and receipt show what was accepted, prepared and served.
• Independent decision. Review decisions retain the source revision, reviewer, reason and outcome.

Suppose a customer cancels the remaining portions after some food was served. Service Lead identifies the unprepared and unserved portion separately. Kitchen Lead records waste as a separate movement where applicable. Independent Reviewer approves or rejects the proposed compensating action. Finance Lead checks whether a verified refund already exists for the same scope before another refund is requested.

Identify the payment provider connection and its event identity rules. Agree how a verified receipt arrives and who can mark evidence verified. Set an operating rule for refunds that requires the same order, amount and provider event to be checked before another action. Keep the provider reference and occurrence time when importing a late event, because arrival time may differ from the actual payment event.

Define who prepares a correction and who independently reviews it. The reviewer should read the current order revision, line effects, prior decisions and operation receipts. Repeated requests for the same correction must return the prior result rather than generate another effect. Rejected or returned decisions retain a reason so the preparer knows what to resolve.

Start with an accepted order that has a partial served quantity and a provider capture. Request cancellation of the remaining portions. Inspect the line’s preparation time, ingredient movements and served portions, then record the proposed correction against the current revision. Independent Reviewer decides the scope. Finance Lead checks capture and refund evidence, including provider event identity, before accepting a refund outcome. The served history should remain visible throughout.

Repeat the same correction request. It should point to the previous operation receipt instead of issuing a second refund. If the provider response is uncertain, leave the effect open for reconciliation with actual evidence.

• Unverified Payment Evidence — Review provider events whose verification is still open.
• Review Decisions — Follow decisions and reasons against the order revision.
• Operation Exceptions — Inspect correction effects that failed or need review.

Correct or cancel covers the changed scope; reconcile an exception covers uncertain effects.