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: Data format and storage

BusDK Design Spec: Data format and storage

This section is split into single-concept documents:

Account types in double-entry bookkeeping, Append-only updates and soft deletion, CSV conventions, and Workspace configuration (datapackage.json extension) define baseline data semantics.

Storage backends and workspace store interface, Data Package organization, Scaling over decades, Schema evolution and migration, and Frictionless Table Schema as the contract define long-term storage and evolution contracts.

← Shared validation layer (schema + logical validation) BusDK Docs Account types in double-entry bookkeeping →

Sources

  • Data section index
  • Schemas beside datasets
  • Data directory layout (principles)
Improve this page BusDK · GitHub · Releases · Issues © 2026 Heusala Group Ltd