1. Ghost Kitchen Aggregator
  2. Features
  3. Exceptions and reconciliation
Feature · Exceptions and reconciliation

Exceptions and reconciliation

Work delivery exceptions and external amount differences against their source order.

OverviewMy Follow Up Actions
Ghost Kitchen Aggregator · Exceptions and reconciliation

My Follow Up Actions

Follow up actions

New
TitleDue dateStatusSourceResolution
Open fua-33617 OctOpenKO-62974RSL-792
In progress fua-27110 OctIn progressKO-38858RSL-745
Completed fua-99524 OctCompletedKO-33409RSL-208
Cancelled fua-76427 OctOpenKO-58995RSL-897
Open fua-31408 OctIn progressKO-63513RSL-872
6 of 6 records
Open fua-336Follow up actions · FUA-81847
Open
Due date17 Oct
SourceKO-62974
ResolutionRSL-792
Example screen with sample data

What you can do

Work delivery exceptions and external amount differences against their source order

An external outcome reports a lower confirmed amount than the order expected. The analyst keeps the reconciliation linked to the source order, records the evidence reference, and assigns a due action to the person who can investigate. The difference remains traceable after the action is completed. The work starts with external reference and expected amount. Those details let the next person open the same order or partner context instead of relying on a message thread. The team then checks confirmed amount, evidence reference and assigned action. The important decision is whether a difference remains visible until it is investigated and resolved.

The records here separate an operating fact from its review. An order can have a status, an observation can have an outcome, and a run can have an execution result. Each answers a different question. When the team sees a missing receipt or unexplained difference, it keeps the action resolution and original operation key beside the source order so a later reviewer can reconstruct what happened.

How the work is organized

  • Identify the source. Start from external reference and expected amount and keep the related organization, partner and order visible.
  • Check the decision. Review confirmed amount, evidence reference and assigned action before resolving the difference.
  • Keep the trail. Record the action resolution and original operation key with the same source identity when a question needs investigation.

What to agree during setup

Agree who investigates a Difference and who owns each due action. Reconciliation Analyst should keep the external reference, value date, currency, expected amount and confirmed amount on the record linked to the order. Fulfillment Coordinator should leave an uncertain event visible until its evidence is checked.

Give the Reconciliation Analyst a case with expected and confirmed amounts. Walk through an accepted case and a missing receipt or unexplained difference. Check that the person responsible for the next step can find the linked source record and its current status. Keep earlier revisions, outcomes and reasons available when the team investigates a change.

Check the handoff on an actual case

An external outcome reports a lower confirmed amount than the order expected. The analyst keeps the reconciliation linked to the source order, records the evidence reference, and assigns a due action to the person who can investigate. The difference remains traceable after the action is completed. Ask Reconciliation Analyst to explain the amount difference from the source order and evidence reference. The assigned person should show a due date and eventual resolution on the follow-up action. Keep the reconciliation in Difference until the team has evidence for another status.

Rehearse the case with a returned or uncertain outcome as well. The team should keep that result visible, assign an action with a due date where needed, and close the action with a resolution that points back to the order. The order trail should still show what happened before the correction.

What your team sees

  • Pending External Reconciliations — Compare expected and confirmed amounts that still need investigation.
  • Run Exceptions — Find failed or uncertain operation runs with the recorded reason.

Follow the work through

Follow the worked process and agree the implementation sequence before the first operating cycle.

What it keeps track of

Data model
External reconciliations
Expected versus confirmed external order outcomes.
Follow up actions
Open and completed actions required to resolve order exceptions.
Kitchen orders
Parent order revisions routed through kitchen partners and pooled drivers.
Order fulfillment events
Observation-level fulfillment and delivery events linked to an order.
Operation runs
Durable idempotent workflow runs and actual results.
Operation steps
Numbered workflow trace with input, output, and receipt evidence.

Who uses it

Permissions
Reconciliation Analyst
, Fulfillment Coordinator and Admin.
The first named role owns the daily handoff; the others review the context or investigate exceptions.

Set up Ghost Kitchen Aggregator your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started