Automatic effects and module connections
| Action | Current effect | Separate work |
|---|---|---|
| Add draft | Captures User-derived unit, initial due and approval tier | Evidence/approval/posting |
| Change draft total | Updates due and resets/recalculates decision | Recheck retained included tax |
| Edit other draft fields | Merges non-null fields; may retain approval decision | Material-change re-review |
| Approve tier | Saves current decision metadata | Separate lifecycle APPROVED action |
| Employee posting | Creates recognition journal and link; expense POSTED | Record reimbursement |
| Company posting | Creates journal/full IN_PROCESS payment; expense PAID label | Verify counters/settlement/clearing |
| Record reimbursement | IN_PROCESS payment and immediate counter change | Validate and verify settlement |
| Cancel/reset payment | Changes payment state | No automatic expense balance repair |
| Reset/confirm journal | Changes linked journal state | No full expense rollback/repost orchestration |
| Change User unit | Affects future ownership resolution | Existing expense stays in captured unit |
Current boundaries
There is no automatic receipt upload/OCR, mileage rate, per-diem calculation, tax recovery engine, card feed, bank initiation, supplier remittance delivery, Payroll reimbursement run, expense resubmission queue or configurable approval-threshold editor in these screens.
Account codes 2010/2020 and GBP/rate-1 posting values come from current implementation, not a general tenant-configurable posting policy page. The payment method label does not execute that method with an external provider.
Vendor references use Supplier IDs with Party display identity. Employee/Manager references remain User IDs. The payment structure's customerPartnerId recipient field is temporarily reused; no new Partner/customer identity is created by the documented form.
Recommended operational discipline
Follow the guided UI sequence, arrange independent review where required by policy, coordinate mutations and verify saved outcomes. Do not treat confirmation prompts, state ribbons or available buttons as proof that a complete server-side financial-control matrix or immutable audit workflow exists.
Example: Selecting BANK_TRANSFER records the method. Recording a reimbursement creates IN_PROCESS and changes the expense counter. Neither action sends money to a bank or provides an external settlement confirmation.
Future functionality should be documented only after its implemented screen, API policy and effects are verified. This package changes documentation and navigation only; it does not implement any missing accounting, balance, scoping or approval behaviour.