Skip to docs content

Reference

Concepts for developers

What the reads and changes assume: books and entities, accounts, posted entries, date ranges, signs, locked periods, rules and review, and what a preview guarantees.

Books and entities

  • A book is one set of books, called an entity in the tools and the REST API. Every read but the listing takes one as entity. How 42six works explains books in the app.
  • An API key reads one workspace, and only the books it was given; list_entities lists them. An app signed in with 42six reads the books the person approved, which list_books lists, and they can sit in more than one workspace.
  • An entity id the caller cannot read is answered the same as one that does not exist: 404 on the REST API, and on the MCP server a JSON-RPC error -32602, "No such entity."
  • Each book has a kind: business, rental or personal. The change tools refuse a personal book.

Accounts

  • list_accounts gives each account its id, code, name, type, subtype, parent, whether it is a bank account and whether it is active.
  • Codes are not the same from one book to another, so do not assume a code names the same account in every book. Read type and subtype to tell what an account is.
  • A change tool takes an account by its id, its role key, its code or its exact name. A name that matches more than one account is refused with the choices.

Posted entries only

  • Journal entries, journal lines, the trial balance and the statements count posted entries only.
  • A bank transaction is not in the ledger until it is posted. It carries posted_entry_id once it is posted, and excluded_at once it is set aside.
  • A row with pending true has not settled at the bank: its amount and description can still change, or it can disappear. list_bank_transactions shows it for information; needs_review leaves it out, and preview_categorize excludes it with the code pending until it settles.

Dates and ranges

  • Dates are YYYY-MM-DD.
  • A range is half-open, [from, to): from is included and to is not. January 2026 is from=2026-01-01 and to=2026-02-01.
  • balance_sheet takes one date, as_of, and includes it. The dashboard reads end their window on as_of, today in UTC by default.

Signs and money

  • Money is a decimal string such as "1250.00", never a floating-point number.
  • In journal lines and the trial balance a debit is positive.
  • In bank transactions a positive amount is money out, the bank feed convention.
  • The statements show each line as the app does: revenue, liabilities and equity positive.

Locked periods

  • period_locks lists the locked periods of a book. Nothing posts, moves or changes inside one.
  • A book is locked through one date. period_locks shows that lock as a row from 0001-01-01 to the locked-through date, so the latest period_end of a locked row is the date to compare against. Reopening the books removes or moves that date back.
  • A preview leaves out what falls in a locked period, or refuses the change, with the reason. A plan whose period was locked after its preview is not applied.
  • An app never locks or reopens a period. Reconcile and close explains locking in the app.

Rules and review

  • needs_review lists the bank transactions that are neither posted nor excluded, including ones with a category picked but not finalized.
  • A rule matches a bank description by keyword (contains, starts_with, exact or regex), optionally only one direction or one bank account, and names an account or a split. list_rules shows each rule with its priority and how often it has matched.
  • Applying a preview_rule creates the rule only. To categorize what it matches, preview_categorize those transactions.
  • Rules and Bank feeds and transactions explain how rules work in the app.

What a preview guarantees

  • A preview changes nothing in the books. It checks the change the way the app would, and keeps it as a plan for 10 minutes.
  • apply_change checks everything again, then makes the change exactly as previewed, all or nothing.
  • If the plan expired, or what it changes (the transactions it categorizes or the entry it moves or reverses) changed since the preview, nothing changes. The checks the app makes at posting, such as a locked period, run again at apply.
  • Applying the same plan again returns its first result. A change is never made twice.
  • Every apply is recorded with the user and the app. Changes: preview and apply has the details.