Document statuses, approvals, and archives
How list tabs and status mutations are wired, including processing, accurate, approval, and archive transitions.
Status changes are actionable from list tables
The main data tables support status changes and even document type moves directly from list context. This is not a passive register; it is a triage workspace.
- Processing is shown as status `1`
- 100 Accurate is shown as status `3`
- Archive is shown as status `4`
- Approval-heavy flows infer additional states from approval columns and ready-for-payment flags
Approval state is stored separately from generic status
Approval does not rely on a single status code. Instead, the product combines `approval_1`, `approval_2`, rejection fields, and ready-payment flags. That is why approval lists and payment lists are separate views instead of generic filters.
Type moves and exports are part of daily operations
Tables support moving a record to another document family and exporting rows to CSV or Excel variants, including Xero-oriented formats. Documentation should treat these as core actions, not advanced extras.
Continue with adjacent workflows
Approval levels and rejection logic
The real two-step approval model in Datamonster, including role separation, counts, pending queues, and reject officer visibility.
Working with Vault and cross-type moves
How the Vault behaves as an operational catch-all and when moving a document type is useful.
Using the AI prompt workspace
What the in-product prompt assistant can do, how sessions are stored, and why exports are part of the chat workflow.