BusDK Docs
BusDK Docs
  • Get started ▸
    • Overview
    • Design goals and requirements
    • Cost summary
  • Workflows ▸
    • Accounting workflow overview
    • Sale invoicing (sending invoices to customers)
    • Example end-to-end workflow
    • Finnish payroll (monthly pay run)
    • CLI tooling and workflow
  • FAQ ▸
    • What are bus and BusDK?
    • Getting started and adoption
    • Workspaces, datasets, and compliance boundaries
    • AI assistants, automation, and safety
    • Modules, repositories, and contribution model
    • Purchasing and pricing
  • Modules ▸
    • Modules overview
    • Module capabilities
    • aiz
    • bus
    • bus init
    • bus config
    • bus data
    • bus api
    • bus sheets
    • bus dev
    • bus agent
    • bus secrets
    • bus bfl
    • bus accounts
    • bus entities
    • bus customers
    • bus vendors
    • bus period
    • bus preferences
    • bus files
    • bus attachments
    • bus invoices
    • bus journal
    • bus bank
    • bus reconcile
    • bus assets
    • bus loans
    • bus inventory
    • bus payroll
    • bus budget
    • bus reports
    • bus validate
    • bus vat
    • bus pdf
    • bus filing
    • bus filing prh
    • bus filing vero
    • bus gateway
  • Design ▸
    • System architecture
    • Data formats and storage
    • Data directory layout
  • Reference ▸
    • Master data
    • Integration and future interfaces
    • Extensibility model
    • Testing
    • References and foundations
  • Compliance ▸
    • Finnish bookkeeping and tax-audit
    • Finnish balance sheet and income statement regulation
    • Finnish reporting taxonomy and account classification
    • Household accounting and personal finance
    • Finnish closing deadlines and legal milestones
    • Finnish closing checklist and reconciliations
    • Finnish closing adjustments and evidence controls
    • Finnish company reorganisation (yrityssaneeraus)

BusDK Design Spec — CLI tooling and workflow

BusDK Design Spec: CLI tooling and workflow

This section is split into single-concept documents:

Extensible CLI surface and API parity, Git commit conventions per operation (external Git), Command structure and discoverability, Standard global flags, and CLI command naming define command design conventions.

Minimum required command surface (end-to-end workflow), Error handling, dry-run, and diagnostics, Non-interactive use and scripting, and Reporting and query commands define operation behavior.

For .bus usage, follow .bus files — getting started step by step, .bus getting started — multiple commands together, and .bus script files (writing and execution guide). Installation guidance for syntax highlighting in common editors is in Editor support for .bus files. Validation policies are in Validation and safety checks.

← VAT area (reference data and filed summaries) BusDK Docs Extensible CLI surface and API parity →

Sources

  • BusDK module CLI reference
  • Standard global flags
  • CLI command naming
Improve this page BusDK · GitHub · Releases · Issues © 2026 Heusala Group Ltd