Reconciliation completed

Reconciliation completed

When a reconciliation is completed, either with or without deviations, the reconciliation is published.

The exported message contains information like the user id completing the reconciliation, the workstation id, timestamp when completed etc.

In addition, all tenders counted are included with information like actual counted, expected, deviation etc.

Since reconciliations in theory can span several dates, for instance a reconciliation active from 2200 in the evening to 0600 in the morning for 24/7 stores, a sum for each tender for each date is added at the end for accounting or reporting/statistics purposes.

Example

An example of a message published when the reconciliation is completed:

{
  "tenantId": "tenantId",
  "businessUnitId": "businessUnitId",
  "correlationId": "babf8065-8119-40c0-b3f0-41f6dfeca5e8",
  "reconciliationId": "55f6b0d2-aa02-4e69-9860-4035a83fa27b",
  "workstationId": "workstationId",
  "operatorId": "operatorId",
  "userId": "userId",
  "comment": null,
  "timestamp": "2022-10-28T07:22:53.588000000Z",
  "tenders": [
    {
      "tenderId": "72c524d7-80ee-4721-95b8-d28148c14a7b",
      "currencyId": "EUR",
      "initialBalance": 100,
      "expectedAmount": 95,
      "actualAmount": 90.2,
      "deviationAmount": 4.80,
      "allowedDeviationAmount": 10,
      "expectedQuantity": null,
      "actualQuantity": null,
      "deviationQuantity": null,
      "allowedDeviationQuantity": null,
      "denominations": []
    }
  ],
  "transactionIds": [
    "20e58dcd-3ab9-4fa2-a613-3c8ad0161439"
  ],
  "transactionTenderDates": [
    {
      "tenderId": "72c524d7-80ee-4721-95b8-d28148c14a7b",
      "dateValue": "2022-10-27",
      "amount": 50
    }
  ]
}

Subscriptions

Tech	Subscription
Pub/Sub	rec.public.event.reconciliation-completed.v2
External Events	rec.reconciliation-completed.v2

Format

The JSON format for reconciliation completed.