Invoice
What It Models
Invoice covers customer billing and the documents that adjust that billing. Credit and debit memos, write-offs and billing reversals remain distinct records within this concept. A pro forma represents a quotation before receivable recognition.
Identity and Attributes
The attributes describe the billed party, commercial terms, charges and financial position. Recognition separates editable preparation from protected commercial content; posting account selection belongs to batch management.
Relationships
Allocations and credit applications connect receipts and customer credit to invoice lines. CRM supplies customer context, Books supplies configuration, and batch management supplies the posting boundary.
Invariants
The invariant rows distinguish database protections from command eligibility checks. Their cited evidence identifies which conditions are tested and which are read from implementation or recorded architecture.
How It Is Stored and Shared
Transactions owns billing and correction storage. Authorized console reads, service-function calls and dataset queries provide distinct access surfaces. Receivable change events provide the financial integration surface for Commerce.
Open Design Questions
Staff billing without an order still needs a tax-ownership decision. The approved amendment direction lacks a working console connection, and memo editors assume draft behavior that the commands do not implement. Recognition-based protection also requires clearer treatment of issued pro formas.