Core Concepts

What is OpenBooks

Financial transparency infrastructure for organizations whose money has to be explained to a regulator or the public.

The short version

OpenBooks is a system of record for organizations whose money has to be explained to somebody else — a regulator, a member, a donor, a court, or the public. It keeps a ledger in which every financial event is a permanent entry, classifies each entry against the rules that govern the organization, and publishes the result in a form that a stranger can check without asking anyone's permission and without trusting OpenBooks.

What a ledger is here

In ordinary bookkeeping a ledger is a working document: entries are added, corrected, reclassified, and closed, and the record you see is the record as it stands today. That is a reasonable design when the ledger's job is to produce a correct balance.

It is a poor design when the ledger's job is to be believed. If the current state is all that survives, then the record cannot answer the question that matters most to an outside reader: not “what does it say now,” but “has it always said this?”

An OpenBooks ledger is append-only. An entry, once written, is never edited and never removed. A correction is a new entry that refers to the one it corrects, so the mistake and the fix both survive. The history is not a log kept alongside the record — the history is the record. See The Ledger.

What makes this ledger different

Two properties, and they are worth stating separately because they are often conflated.

It is cryptographically verifiable. Every entry is hashed with SHA-256 over a canonical serialization of its contents, and each entry's hash includes the hash of the entry before it. The entries form a chain. Changing any field of any entry changes its hash, which breaks the link to every entry after it. This is checkable arithmetic, not a claim: anyone can recompute the chain and see for themselves. The Hash Chain describes the construction, and Verification is candid about what a passing check does and does not establish — which is a narrower thing than most readers assume.

It is maintained automatically. Transactions are classified against the organization's governing rules as they land, each classification carrying a confidence score and a record of the reasoning that produced it. Work that clears a confidence threshold is applied; work that does not is routed to a person. The officer's job is to supervise decisions, not to perform bookkeeping. See The AI Treasurer — which is also explicit about which parts of that automation are running today and which are designed but not operating.

Who it is for

Organizations that hold or spend money on behalf of people who are entitled to an account of it, and that answer to a specific regulator or constituency:

• Hawaii political committees, which register with and file disclosure reports to the Campaign Spending Commission under Hawaii Revised Statutes chapter 11.
• Community and condominium associations, whose reserve-study and disclosure duties in Hawaii sit in HRS §514B, and whose members are generally entitled to inspect the association's books.
• Nonprofits, most of which file an annual return in the IRS Form 990 series that is itself a public document.
• Labor unions and trust accounts, which owe an accounting to members and beneficiaries respectively.

What these have in common is not their size or their software. It is that somebody outside the organization has standing to ask where the money went, and the organization bears the cost of not being able to answer.

What “infrastructure” means

Infrastructure is the part of a system that other things are built on and that is judged by whether it holds. The claim in “financial transparency infrastructure” is a claim about the load: that a published OpenBooks record is sound enough for a journalist to quote, an auditor to start from, a member to rely on, and an automated agent to read without a human intermediary — because its integrity can be checked by the reader rather than asserted by the publisher.

That is a strong claim, and the honest form of it is bounded. A verified chain proves the records have not been altered since they were written. It does not prove they were true when written. Those are different guarantees, and conflating them is the most common error made about systems of this kind. Verification sets out the boundary in detail.

What OpenBooks is not

It is not a general-ledger accounting package, and it is not trying to be one. It does not compete on chart-of-accounts depth, payroll, or invoicing.

It is not a blockchain. There is no token, no consensus mechanism, and no distributed set of validators. A hash chain is a much older and much simpler construction, and it is the appropriate one here.

It does not move money. It has no payment rails, and it initiates no transfers. And it does not transmit filings to any government agency — see Filings, which states that plainly, because the opposite is a natural assumption for a reader to make and it is not true.

It is non-partisan and non-sectarian by construction. The system classifies transactions against rules; it holds no view about the organizations it serves.