Every session ends with an entry in the log
The bookkeeping session leads with what it recorded and links to the ledger entries it wrote. Plus register edits that stop clobbering suspense bridges, and a review queue that got about twice as fast.
The bookkeeping inbox is where a session of work happens. A stack of documents or feed items comes in, gets classified, gets coded, gets posted. What was missing is the part a bookkeeper does by hand at the end of the day: writing down what was done and why.
The session leads with what it recorded
The inbox session page leads with the narrative. What this session recorded, in order, with the items in a panel beside it. The session count is what it recorded, not what’s still sitting in it. The old count went down as you worked, which is backwards.
Every session ends with a work-log entry, written automatically. You can walk from a session to the log entries about it and back, and from the narrative to the ledger entries it wrote. Six weeks later, “who did this and what were they thinking” has a paper trail, and the paper trail links to the postings.
An item can be split across accounts and cost centers from inside the session, so it no longer has to be posted whole and repaired afterwards.
Register corrections that don’t do damage
Three ledger fixes worth naming, all found in daily use:
- Editing a transaction in the register could clobber the journal-entry suspense bridge it was part of, unbalancing something elsewhere without saying so. It can’t now.
- Editing a reconciled row is still allowed, because sometimes it’s the right thing to do, but it warns first, before the next reconciliation turns it up.
- A journal entry leg in the register shows its contra account instead of a placeholder, which is the whole reason anyone looks at that column.
Speed, where it was being felt
The review queue’s chip counts ran a scan the database couldn’t index: 259ms to render the header. Rewritten to be sargable, they take 112ms. Every transaction query was eager-loading the full ledger graph whether the caller wanted it or not, and no longer does. Bank-feed review responds to your pick and your approve immediately, rather than after the refetch that follows them.
We also stopped firing the Manager.io sync on every approve and every invoice save, which was outbound work nobody had asked for.
Live for every organization. [email protected].