Bookkeeping status and review workflow
Bookkeeping status and review workflow
Bookkeeping needs minimal process metadata that turns operational records into a reviewable queue. These fields do not change the accounting meaning of an invoice or a bank transaction, but they make it clear what is ready to book, what has been booked, and what needs attention.
This workflow metadata is typically stored on sales invoices, purchase invoices, and bank transactions. Keeping it consistent across objects allows one unified “bookkeeping inbox” view even when the underlying objects differ.
Ownership
Owner: bus invoices. This module is responsible for implementing write operations for this object and is the only module that should directly change the canonical datasets for it.
Secondary read-only use cases are provided by these modules when they consume this object for validation, matching, posting, or reporting:
bus bank reuses the same status vocabulary for bank-transaction inbox workflows. bus reconcile uses status to separate matched and unresolved items, and bus validate checks workflow-field consistency where required.
Actions
Triage items for bookkeeping sets review state and evidence completeness so the inbox stays actionable. Book an item records finalized bookkeeping decisions with actor and timestamp. Lock an item prevents further edits after close/finalization.
Properties
Core workflow fields are accounting_status, booked_at, booked_by, accounting_note, and evidence_status.
Relations
Workflow metadata is stored on operational bookkeeping objects so they can share one review vocabulary and one “bookkeeping inbox” view.
Sales invoices typically carry workflow fields described on this page. Purchase invoices carry the same fields, and both invoice types commonly use the same evidence status rules through documents (evidence).
Bank transactions reuse the same status vocabulary so that invoice and bank reconciliation workflows can be reviewed together.