A smarter inbox and the brain behind it
Attach documents to records that already exist, content-hash duplicate guards, and a single entity resolver, the "brain," that keeps every correction you make. Plus statement-driven AI reconciliation.
In April we consolidated every inbound document onto one pipeline and said the improvements riding on it would land soon. Here they are. The document inbox proposes more and asks less, and underneath it is a shared component we’ve started calling the brain: the part of Zeno that decides what a document is and who it belongs to.
Attach to a record that already exists
A document no longer has to become a new record. When something arrives that matches a transaction you already have, whether a bank-feed item, a posted payment, or an open bill, you can attach it to that record. Receipts get the clearest version of this. The inbox offers attaching to an existing line or creating a new one, and you pick.
Duplicates caught at the door
Every inbound file is fingerprinted with a content hash, so an exact re-send of a document you already have is caught on arrival. It doesn’t sit in the queue as a near-twin waiting for someone to notice and merge it. Duplicate-candidate warnings are collapsed into one alert with an attach action in it.
Vendor payments that post correctly
Paying a vendor from the inbox requires an explicit paid-from bank account and routes the posting to it. A quick payment can’t leave a hole in the ledger for someone to find later.
The brain: one resolver, with a memory
All of this runs on a single entity resolver that takes the signals on a document and works out the vendor, customer, property, or project it points to. Classification and matching go through that one resolver instead of a tangle of per-module special cases, so they behave the same way everywhere and improve in one place.
The resolver keeps what you tell it. Confirm or correct a match and Zeno saves that pairing for your organization. Confirm once that the Con Ed bill on this account belongs to the Oak Street building, and the next one arrives with Oak Street proposed.
Statement-driven reconciliation
Next to the inbox, the AI bookkeeper gained statement-driven reconciliation. Hand it a bank or card statement and the matcher pairs lines against your register, staging them as proposals for you to approve. File uploads wire straight into the agent, so the statement and the matching happen on one screen.
The inbox and the resolver behind it are live for every organization. Tell us where it still gets a match wrong; your corrections are what it saves: [email protected].