Payments and fulfillment

Payment evidence records provider event identity, reference, type, amount, time and verification state. Fulfillment events record a product, quantity, event type, occurrence time and external event identity against the meal order. The Service Manager can follow allocation, picking, shipping, delivery or return observations separately from the kitchen status.

A local order status and a provider receipt answer different questions. Keep the external event identity so a replay does not create another fulfillment or payment fact. When an expected receipt is absent or conflicts with the order, send it to review with the linked operation receipt.

The team uses the order and its linked records as the shared reference. Changes belong to a known actor and the current revision. A status records progress, while the dated record and its evidence explain what happened.

• Named ownership. Finance Reviewer verifies provider evidence; Service Manager follows fulfillment events.
• Exact scope. Provider event ID and external fulfillment event ID identify distinct outside observations.
• Visible result. Type, amount, quantity and occurrence time remain attached to the parent order.

Agree which provider issues each payment reference and which source supplies fulfillment events. Map both identities to the same order without merging them into a single outcome. Rehearse a repeated event and a delivery whose capture receipt is still unverified. Review the original event before saving another effect.

For a delivery order, the Service Manager sees a Shipped event followed by a Delivered event for the product and quantity. The Finance Reviewer sees a Capture receipt from the provider and checks its reference and amount against the order before marking the evidence verified. A later Refund receipt remains a separate event with its own provider identity.

Have the Finance Reviewer compare a Capture amount and reference with the order, then mark the evidence verified only after checking the provider record. The Service Manager checks product, quantity and time on the Delivered event. A later Refund keeps its own provider event identity and review history.

• Unverified Payment Evidence — Check provider events that still need the Finance Reviewer verification.
• Delivered Fulfillment Events — Inspect dated delivery observations and their external event IDs.

• See the operating process for the order of actions and decisions.
• Review the data model before importing active records.