Transaction Record

What It Models

Transaction Record describes common financial-document identity, accounting context, history and available work. Individual document kinds retain their own storage and lifecycles.

Identity and Attributes

The shared shape supports workspace-scoped references, document numbering and dated financial evidence. Retry completion and document history are related records with command-specific behavior.

Relationships

Billing, receipt and credit records use this structure, while the customer account derives financial position from their facts. Batch management owns the referenced posting groups.

Invariants

The structured guarantees identify isolation, retry, history and batch protections. They account for no-op edits, commands affecting several documents and event deliveries with no resolvable workspace.

How It Is Stored and Shared

Transactions owns receivable facts, document events and consumed integration events. Registered datasets and exports expose financial records, while change events provide the Commerce integration surface.

Open Design Questions

Document lock ownership and a record-history read surface remain unresolved. Reconciliation of receivable facts against the posting control balance and Commerce’s position view still lacks independent proof.