A home page for the books, and one address per record
An organization-wide financial home where every number is a door, one full-page route every transaction resolves to, invoice numbering that stops resetting, and multi-invoice PDFs split into discrete bills.
Two complaints we heard often enough to act on: there was nowhere to land, and there was no way to send someone a link to a thing.
Somewhere to land
Books opens on an organization-wide financial home: cash and credit balances by account, what’s outstanding on both sides, what’s waiting in review, and what reconciled through when. Every panel is navigable. Click a balance and you’re in that account’s register. Click a review count and you’re in the queue with that filter applied. It’s a dashboard in the useful sense, where the numbers are doors.
Next to it is a quick-add menu built from the same registry the app uses to define record types, so everything your organization can create appears there, including Bank transaction with an account picker in the form. Quick-add for a module-owned document routes into that module’s own flow rather than a generic form that gets it half right.
One address per record
Transactions used to render inside whatever page you found them on. Any transaction now resolves to a single full-page route, /books/transactions/{id}, with typed layouts for the ones that need them. A transaction has a URL you can paste into an email, a chat message, or a note, and whoever opens it sees the whole posting group. That includes header-less types, which previously showed one leg of themselves.
Journal entries are editable in place. Attachments live on the full page. Created-by resolves the id to a name.
Work-log entries got the same treatment: comments, share links, search, and preview, so a note about why something was done is something you can point at.
Invoice numbers that keep counting
Invoice numbering used to reset in circumstances that made sense to the code and to no one else. ZS- and INV- sequences are continuous and non-resetting now. If you have ever had to explain to an auditor why invoice 1041 was issued twice, you know why this matters.
Multi-invoice PDFs, split
Vendors that bill monthly often send one PDF containing eight invoices. The inbox can split that document into discrete bills, keeping the children grouped under the parent so the queue shows one arrival rather than eight orphans. Credit memos in the stack route to the credit path.
Also in this release
Registers got top-and-bottom pagination with jump-to-page, date presets, and a sort toggle. Bank-feed items take multiple attachments. Creating a payee from an inline field carries the module scope of wherever you created it, so it no longer lands unscoped and needs repair. The trial balance PDF is styled as a prepared statement.
Live for every organization. [email protected].