Blog

We've reworked the Settings area so the most common controls are within reach without paging through tabs. General and Members are now a single tab, the layout is tighter on smaller screens, and destructive actions live in a dedicated danger zone instead of hiding next to everyday toggles.

Soft-deleting an organization is now reversible for a window, and the personal-credit fallback toggle moved to your profile so it follows you across orgs. Credit balance is visible directly on the profile page, and a top-up button is one click away when you're running low.

Small thing, but the cumulative effect is a settings page that looks and feels like the rest of the product, and a credit flow that doesn't make you hunt for the right screen.

Bank exports come in every shape imaginable. Some put debits and credits in separate columns, some use a single signed Amount, and some hide the header three rows down with a logo on top.

The new import flow handles all of these. A stepper lets you point at the actual header row, a signed Amount column is now always selectable alongside Debit/Credit, and we fall back to the org/account currency instead of defaulting to USD when the statement doesn't declare one.

Sign parsing is more forgiving — parentheses, trailing minus, leading minus, and bracketed CR/DR markers all map to the right direction. Less manual cleanup, fewer reversed entries.

Every core report — Balance Sheet, Profit & Loss, Trial Balance — now has a one-click PDF export. We added a shared set of PDF primitives so all three look like they came from the same template, with consistent typography, totals, and section breaks.

We also added an edit-order mode: drag rows on the Balance Sheet or Trial Balance to control the export ordering, and the change persists for everyone in the org.

Until now, document access followed org membership. That was too coarse for orgs with auditors, advisors, or part-time bookkeepers who only need a few specific items.

You can now share a document with specific members directly from the document panel. Recipients get notified, see the doc in their Shoebox and pickers, and can attach it to journal entries without seeing the rest of the org's files.

If the person you want to share with isn't a member yet, you can invite them and pre-share the document in the same flow. The share takes effect the moment they accept, with no extra steps. Owner-role grants are blocked server-side, and the share matrix is exposed in the access-rights view.

Roles like Owner, Admin, and Member are convenient defaults, but real teams need finer control: an external bookkeeper who can post journals but not change the Chart of Accounts, an investor who can only read reports, a manager who can edit one feature and view another.

The new access-rights tab gives each member a full permission matrix. Toggles are organized by feature area, edit implies view automatically, and switching someone's role hydrates the matrix from the role template instead of clobbering custom settings.

Generic AI agents are fine for generic accounting. But every company has its own quirks: how it splits cost of revenue, how it handles inter-company allocations, when it capitalises vs expenses.

Company instruction files let you upload that context once and have every AI run reference it. Markdown, PDF, and plain text are all supported. We summarise what's been provided in the company files tab, and the agents respect cross-org boundaries, fence-escape attempts, and a size cap.

Crucially, the agents can also push back. If an entry doesn't fit your stated policy, they emit a 'needs review' refusal with a decoded reason instead of guessing. You're in control; the AI just knows your house rules.

Reconciliation is judgment work as much as matching work. Two orgs with identical statements can want very different bookings: one wants the Stripe fee netted, another wants it on its own line; one wants Uber rides categorized by passenger memo, another doesn't care.

Org-specific recon instructions let you give the agent your house style as a markdown block. The CSV schema is documented in the prompt, prompt-injection protections are in place, and the auth path is hardened so only org admins can edit.

The Shoebox search dialog now has a text/AI toggle. Text search is the fast keyword path you'd expect. Switch to AI and we run semantic search across embeddings, then layer an LLM relevance filter on top so genuinely-irrelevant hits drop out.

Embedding text is richer now — vendor names, doc summaries, and key extracted fields all feed in — so 'last quarter's flight receipts' finds the right items even if the words 'flight' and 'quarter' aren't anywhere in the file.

Filter extraction means natural-language queries can also pin date ranges, currencies, or accounts without you having to fill out a separate form. It's the search bar we wished accounting software had.

WhatsApp has been one of our quietest-but-stickiest input channels. The original flow took text-only messages; this update adds first-class support for photos and PDFs sent with captions.

When you send media with a caption, the caption becomes the journal-entry instruction and the media is attached as supporting documentation. Images get compressed client-side so big phone-camera shots upload fast and store small. We also auto-save in-progress captures and send a confirmation message after each booking so you know it landed.

It's the closest thing we have to a 'snap your receipt' workflow — and the one that makes Ringbook feel less like accounting software and more like a chat thread that happens to keep books.

Until now, every ring you posted was visible to everyone in the org. That worked for the everyday — coffee receipts, client lunches, software subscriptions — but it didn't fit cases where the entry itself was sensitive: a director's reimbursement, a confidential vendor payment, a payroll-adjacent transaction.

Private rings let you choose who sees the ring at post time. Pick one or more members, and only they (plus owners and admins) will see the ring in the feed, in search, and as a source on the resulting journal entry. Everyone else sees the booked numbers in the ledger as usual — the audit trail isn't hidden, just the human-readable note attached to it.

Visibility is enforced server-side, so the ring never reaches the wrong member's client even briefly. Attached documents inherit the same audience, and you can change who's on the list later if circumstances shift.

It's the smallest change that makes Ringbook usable for the conversations that don't belong on the company-wide feed.