Workflow takeaways (transparency, control, automation)

Workflow takeaways (transparency, control, automation)

Across this workflow, the same sequence repeats in different modules: write or import repository data with explicit commands, validate invariants, produce derived outputs, then record the reviewed result as a new revision. This makes the workflow script-friendly while keeping human review straightforward.

  1. Transparency comes from storing the authoritative tables and their schemas as repository data and reviewing changes through the revision history.

  2. Control comes from the rule that outcomes are expressed as explicit records rather than as silent adjustments, so journal impact is appended as balanced entries:

bus journal add --date 2026-02-14 --desc "Bank fee" --debit 6570=10.00 --credit 1910=10.00
  1. Automation comes from repeatable commands that compute outputs from stored data without losing traceability, and from closing workflows that lock the period boundary:
bus period close --period 2026-02 --post-date 2026-02-28
bus period lock --period 2026-02

Treating evidence as data and locking periods on close keeps the audit trail intact and ensures that “January stays January.”

← VAT reporting and payment BusDK Docs Year-end close (closing entries) →

Sources