POS Document Flow
POS session Open/Close and transaction Pending, Completed, Voided, Refunded lifecycles.
POS Document Flow
Point of Sale uses session and transaction statuses. Row Actions are primarily icon buttons and dialogs, not a full MudMenu Submit/Approve pattern.
Hub: Target Document Flow. Overview: Point of Sale.
Sessions
#Statuses
Open, Closed
| UI control | Behavior |
|---|---|
| Open Session | Opens register session dialog |
| Close Session | Closes open session |
| X-Report / Open Register / Refresh | Session operations |
Transactions
#Statuses
Pending, Completed, Voided, Refunded
Transaction lifecycle — sale, void, refund
flowchart TB Start((Sale)) --> Pending[Pending] Pending -->|Complete sale| Completed[Completed] Completed -->|Void| Voided[Voided] Completed -->|Refund| Refunded[Refunded] class Start egkStart class Pending egkDraft class Completed egkSuccess class Voided,Refunded egkTerminal
| UI control | Gate |
|---|---|
| View detail | Always |
| Void | When CanVoid(row) |
| Print receipt | When printable |
Actions menu: Not implemented as a MudMenuItem list on the transactions grid — void/print use inline icon buttons and dialogs.
#Post-action sync
After void/close/open, lists refresh. Failed void leaves prior status (Completed).
#ERP integration: e-receipt, ledger and stock
A completed POS sale is one business transaction with exactly one of each downstream effect:
| Effect | Behavior |
|---|---|
| E-receipt | Composed once per transaction (key POS:{id}) and linked by PosTransactionId; a return produces a return receipt against the sale receipt. POS sales are always e-receipts, never e-invoices. The transaction detail links to the receipt and the E-Receipt page links back (/pos/transactions?id=). |
| General ledger | One balanced journal per sale (PosSale|{id}): revenue and VAT credited; the settlement debited to Cash on hand for cash and to Card clearing for card, wallet, bank-transfer, gift-card and store-credit tenders (when the clearing role is mapped). Returns (PosReturn|{id}) and voids (PosVoid|{id}) reverse the same split. Redelivered events post nothing. |
| Inventory | One stock issue per sale line, one receipt back per return line, referenced to the POS transaction. |
| Accounting source | The e-receipt itself never posts revenue, tax, receivables or cash — the POS transaction is the only accounting source. |
Findings such as a completed sale without an e-receipt, without a journal or with a duplicate stock movement appear in E-Invoices → Back-fill → ERP / ETA linkage audit with a link to the transaction.