Bokforing.io

The challenge

An accounting system has to follow the law even when somebody tries not to. Put the rules in the interface and a single API call around it is enough to break them.

What we have built so far

• Multiple companies from the ground up

  Permissions per module, per user and per company, enforced at row level in the database.

• Financial years

  A choice of cash or accrual method, and periods that are guaranteed not to overlap.

• The BAS chart of accounts

  A system template with VAT codes and report boxes, provisioned per financial year.

• Journal entry

  Drafts, a keyboard-driven flow, account search and a running balance.

• Hard blocks on posting

  Debit must balance credit, only active accounts are allowed, and the date must fall inside the financial year.

• Gap-free sequence numbers

  Assigned atomically at the moment the entry is posted, never on a draft.

• Immutability

  The database blocks any change or deletion of a posted entry.

• Corrections as the law requires

  A reversing entry, a link between original and correction, and striking of an individual line with who, when and why.

• Period locking

  Can apply to everyone or to selected users, with an exception for the year-end series.

• A complete event log

  Append-only, with nothing that can be edited after the fact.

• An agent surface of its own

  An AI assistant can read the books with exactly the same permissions as the user it acts for.

Next steps

Reports, SIE import and export, a document inbox, bank imports and both sales and purchase invoices.

Why we are showing it anyway

This is the hard part. Reports can be built at any time. Compliance that lives in the database and cannot be bypassed, not even by us, is what decides whether an accounting system holds up.

Images