A journal entry changed.

Group: Accounting › Journal Entries

Event accounting/journalEntries/updated, delivered as a POST to the webhook endpoint of a subscription to it.

Delivered whenever an existing entry changes. That covers rather a lot: approval and posting, rejection, voiding, being stamped as reversed when its reversal posts, and an edit to its header or its lines.

Line edits reach you for a slightly indirect reason worth knowing: an entry's lines are always rewritten together with the entry itself, so a change to a line is reported through the entry's own record rather than through the line. The effect is the same — you get a delivery — but it means the volume stays one event per edit rather than one per line, which matters for month-end entries carrying hundreds of them.

Two things are NOT reported. An attachment added or removed publishes nothing, and it would not be observable anyway — attachments are not part of this resource. And the reportingTags on a line are resolved from value-accounting records held elsewhere, so editing an allocation can change what a line returns without a delivery; read the entry on a schedule if you depend on its tags.

This is a change notification rather than a description of the change. Re-read the entry and take its current status, approval status and reversal status from there; the payload names the entry but not what moved, and there is no before-and-after.

Two things are worth knowing when you re-read. An entry's lines are reconciled by deleting and recreating them, so line identifiers are not stable across an update and should not be used as durable keys. And voiding does not remove an entry: its status becomes voided and the row stays, which is what cancelling a posting means here.

Several changes in quick succession are several deliveries, and a re-read after the first may already show the last. Deduplicate on event.uuid and treat the read as the source of truth.

Payload

Required, application/json: object.

Field	Type	Required	Description
`subscription`	object	yes	The subscription this delivery was made for.
`subscription.uuid`	string	yes	Stable identifier of the subscription.
`subscription.type`	string	yes	Transport the subscription delivers through; `webhook` for deliveries carried by this request.
`subscription.name`	string	yes	Authored name of the subscription.
`event`	object	yes	The emitted event being delivered.
`event.uuid`	string	yes	Stable identifier of this emission — the idempotency key for a receiver, since a delivery may be retried.
`event.identifier`	"accounting/journalEntries/updated"	yes	Public identifier of the event type.
`event.emittedAt`	date-time	yes	When the event was emitted (ISO 8601).
`event.data`	accounting_journalEntries_updatedPayload	yes
`event.data.id`	string	yes

{
  "subscription": {
    "uuid": "<uuid>",
    "type": "<type>",
    "name": "<name>"
  },
  "event": {
    "uuid": "<uuid>",
    "identifier": "accounting/journalEntries/updated",
    "emittedAt": "2026-01-15T09:30:00.000Z",
    "data": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
    }
  }
}