Expense Events — Proposed Guide

Expense Events: Expense events could describe draft creation, submission or a reviewed correction. Each should reference the expense version that produced…

Overview

Expense events could describe draft creation, submission or a reviewed correction. Each should reference the expense version that produced the fact.

Key concepts

Distinguish creation from approval and include stable expense identity. Use timestamps for occurrence, not delivery ordering alone.

Implementation considerations

An out-of-order draft event must not overwrite a newer approved view. No event payload here represents a real customer expense.

Illustrative data model

This local fixture shows a possible representation for the concepts above. It is not an endpoint response, production configuration or a claim that the described capability is implemented.

{
  "reference_only": true,
  "topic": "Expense Events",
  "event_id": "event_example_123",
  "expense_id": "exp_example_123",
  "event_type": "expense.updated",
  "version": 1
}

Design review checklist

• Document which organization owns the expense events representation and which actor may view or change it.
• Test the boundaries of event id, expense id, event type, version using synthetic values, including missing or inconsistent references.
• Before future implementation, obtain an approved contract and review failure behavior. This documentation does not authorize production activation.

Proposed data types

Related documentation