Expected Payment Webhooks

EventDescription
createdAn expected payment has been created.
reconciledThe expected payment has been reconciled to a posted transaction and the sum of the posted transactions reconciled to the expected payment is within the expected payment's amount range. The reconciled transactions can be viewed by filtering on expected payment id with the LIST transactions endpoint.
This event will occur when the bank transaction is created. At most banks, this occurs when Modern Treasury ingests the BAI2 file in the morning.
When this event is sent, the status is reconciled.
partially_reconciledThe expected payment has been reconciled to a posted transaction and the sum of the transactions reconciled to the expected payment is less than the expected payment's amount range. The reconciled transactions can be viewed by filtering on expected payment id with the LIST transactions endpoint.
When this event is sent, the status is partially_reconciled.
tentatively_reconciledThe expected payment has been reconciled to a pending transaction. The pending transaction ID will be included in the data provided.
This can be a helpful webhook to process if you are confident the pending transaction will correspond to the posted transaction. For example, wires will always post. But sometimes ACH transactions can appear pending, but never post. See the guide for more information.

When this event is sent, the status is unreconciled since the posted transaction has not come in yet. The expected payment's status does not change.
overdueThe expected payment was not reconciled to a transaction. This will be sent at 6am Pacific Time when the date_upper_bound is passed, which indicates the payment was not received by the expected date. For example, if you expected a payment to come in on Monday but it does not arrive, this webhook will be sent on Tuesday at 6am PT.
When this event is sent, the status is unreconciled.
archivedThe expected payment has been archived. This action can only be performed by a user in the dashboard or using the API. Modern Treasury will not automatically archive expected payments.

Archived expected payments will not be considered during future reconciliation attempts.
{
  "event": "reconciled",
  "data": {
    "amount_lower_bound": 400000,
    "amount_upper_bound": 400000,
    "counterparty_id": null,
    "created_at": "2019-12-12T22:58:14Z",
    "currency": "USD",
    "date_lower_bound": "2019-12-12",
    "date_upper_bound": "2019-12-13",
    "description": null,
    "direction": "credit",
    "id": "46141eca-7362-4a25-8f71-cf942423e450",
    "internal_account_id": "b9fc1ae0-d493-4f01-a7b3-b39104e802b5",
    "metadata": {},
    "object": "expected_payment",
    "remittance_information": null,
    "statement_descriptor": null,
    "status": "reconciled",
    "transaction_id": "30dd4826-732f-4fe5-ab15-fc903f85ffdd",
    "transaction_line_item_id": null,
    "type": "ach",
    "updated_at": "2019-12-12T23:01:32Z"
  }
}