Commerce events into Accounting
The Commerce Events page monitors events flowing from Commerce into Accounting for the active tenant.
Monitor the pipeline
Summary cards show total, processed, pending, and failed counts. The event table loads up to 100 entries and shows event date, type, source, status, linked journal-entry ID when present, and an error message when processing failed.
Statuses include pending, processing, processed, skipped, and failed. A processed event may link to the journal entry created from it; a skipped event did not require a posting under the current handler rules.
When failures exist, Retry Failed asks the service to retry failed events and refreshes the table. Review recurring errors by event type before repeatedly retrying. The AI signal buttons open Accounting chat with pipeline counts and failure context; they do not retry events directly.
The current MCP catalog does not expose the historical commerce-event listing, statistics, or retry tool names.