Books
Post it. Lock it. Trust it.
A double-entry ledger for your workspace: post and reverse journals, lock periods, and read a trial balance and account detail that drill down to every posting.
Capabilities that matter in operation
The point of the product is not decorative screens. It is owning a useful slice of the operating stack and making it cleaner to run.
Chart of accounts
Start from a UK, US or generic chart, then add, rename and archive accounts.
Journals and periods
Post balanced journals, reverse them cleanly and lock a month when it is done.
Trial balance, audit trail
Drill from any balance to the entries behind it. Every change is recorded and tamper-evident.
Why teams would actually keep Books
Post balanced journals against a seeded chart of accounts and read a trial balance that always balances
Every posting is sequenced, hash-chained and reversible, never edited, with an audit trail that names who and what
Every workflow is a published action for the CLI and MCP, so agents keep the books under the same rules as people
First steps with Books
Create a Books workspace for your organization.
Apply a chart-of-accounts template and set your base currency and fiscal year.
Post your opening journal and read the trial balance.
Use Books as part of a cleaner operating stack.
Start with the surfaces that solve a real operational problem now, then add more of the Topolo stack without rebuilding the foundations underneath.
Shared identity
Auth keeps access, scopes, and app switching coherent across the suite.
Cleaner adoption
The goal is one operating surface, not another pile of disconnected tools.
Developer upside
TopoloOne is also the route into fairer distribution for external app creators.