The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/accounting/invoices/new | Select the member, terms and purchase reference, enter dues and event lines, and save. | CAP-ACC-TRX-001 | The draft retains customer context, derived due date and calculated charges without a number. | test |
| 2 | /console/{tenantId}/accounting/invoices/{invoiceId}/edit | Revise event quantity and save the working bill. | CAP-ACC-TRX-001 | A valid versioned replacement recalculates the draft. | test |
| 3 | /console/{tenantId}/accounting/invoices/{invoiceId} | Review the eligible batch and confirm issue. | CAP-ACC-TRX-001 | The numbered invoice recognizes the charges and their applicable tax. | test |
| 4 | emailInvoice | Submit invoice e-mail to the contact’s primary address through the service. | CAP-ACC-TRX-005 | Queued communication and its document event are retained together. | test services-accounting:modules/transactions/tests/integration/services/invoices/email-invoice.integration.spec.js#it goes to the bill-to contact’s primary address, from the template, with the document attached, in the transaction |
| 5 | /console/{tenantId}/accounting/payments/receive | Select both billed lines in settlement and record the matching check. | CAP-ACC-TRX-009 | One completed settlement links the receipt and its applications. | test |
| 6 | /console/{tenantId}/accounting/invoices/{invoiceId} | Inspect the invoice and combined transaction view. | CAP-ACC-TRX-016 | The paid bill has zero debt and both billing and receipt remain discoverable. | test |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | No explicit batch or assignment is available. | Issue leaves the working document unissued. | Staff can select a valid batch and retry without earlier numbering. | test services-accounting:modules/transactions/tests/integration/services/invoices/issue.integration.spec.js#it refuses the issue when the unit has no assignment rules (batch_required), the draft unchanged |
| alternate | 4 | The staff member uses only console screens. | No document-send or print action is available there. | Delivery requires the service path until the control is implemented. | observed |
| failure | 2 | Another editor has already saved a newer draft. | The obsolete version is rejected. | The newer saved state remains until a reconciled replacement succeeds. | test services-accounting:modules/transactions/tests/integration/services/invoices/update-draft.integration.spec.js#it refuses an update at a version the draft has moved past (stale) |
| Id | Statement | Provenance |
|---|---|---|
01 | Issue retains a stable invoice reference and recognizes its billed receivable. | test |
02 | Delivery records its communication event without changing invoice standing. | test services-accounting:modules/transactions/tests/integration/services/invoices/email-invoice.integration.spec.js#it records the invoice’s email event, with the request and the addresses, and no change of status |
03 | Completed settlement leaves the invoice paid with no balance. | test |
04 | A fully allocated receipt has zero net remaining receivable value. | test services-accounting:modules/transactions/tests/integration/services/payments/receive-offline.integration.spec.js#it writes the payment item’s facts: minus the whole amount, then plus each allocation, summing to minus the unapplied money |
End-to-end policy: required: Browser proof exercises invoice editing and settlement; delivery requires separate service proof because the staff screen has no send control.