Starting point
Every card payment, every transfer and every bank fee on the business account needs an invoice, and the tax adviser needs the complete list. The invoices arrive in different ways: as an attachment in one of several mailboxes, as a link to a billing page, or not by e-mail at all but only in the customer account on the vendor's website, behind a login and a two-factor code.
Many vendors bill in US dollars, the account books in euros, and the statement texts change from month to month. Fixed matching rules fail on this variety, and doing it by hand is painstaking work, one invoice at a time. An AI agent can take over the search. But it should not be given credentials for it, and it must not get around a security check.
Solution
The business account is connected read-only; every four hours the new transactions come in: card payments, refunds, transfers and the bank's own fees. For each expense an AI agent built on a language model searches the connected mailboxes, downloads attachments and linked invoices, and reads every PDF itself. Only when the amount in the original currency, the date and the vendor match does the document leave quarantine and get filed under a fixed naming scheme in its month's folder. A combined invoice covering several transactions is filed once and referenced by all of them.
The agent makes the match, because senders, amounts, currencies and texts vary too much. Everything else is done by small, deterministic, tested tools: mailbox search, downloads, file names, filing and browser control. Every step is recorded in the expense's history, including rejected finds with their reason, such as a payment confirmation that is not an invoice. When a person rejects a document, it is never filed for that expense again, and the reason goes with the agent to every further transaction from the same vendor.
When the invoice is not in a mailbox, the agent opens the vendor's customer account in a real, visible browser, with a persistent profile of its own for each login. It technically cannot fill password, code or payment fields, and it does not solve or get around a CAPTCHA. It sets the expense aside and carries on. After the run, the responsible person gets a single e-mail with a link: they log in in the same browser, live in the application, tell the agent where the invoices are if they like, and watch it catch up on that login's open expenses. They answer its questions right there.
The agent keeps its own notes per vendor: statement texts, senders, how the invoice is delivered and the way through the customer portal, never amounts or invoice numbers. The notes are hints, not a precondition; a new vendor without a note is searched just the same. Whether an expense has no invoice at all, such as salaries or taxes, is decided by a person with a reason, never by the agent. Salary and intra-group transfers are recognised by their payment reference as soon as the account is synchronised.
The application can only be entered with a passkey. The one-time password for the first sign-in can do nothing but set up a passkey, and a forwarded link is useless without the person's passkey. Content from e-mails and web pages is treated as untrusted input and never as an instruction; downloads reach public addresses only. For the tax adviser there is a ZIP: a CSV file in German Excel format with every expense in the filter, every status and every reason, plus the invoices, named consistently.
- Business account and mailboxes connected read-only
- An AI agent for the matching, deterministic and tested tools for everything else
- Amount in the original currency, date and vendor checked before an invoice is filed
- A real browser with its own profile per login; password, code and payment fields technically blocked
- Logins, two-factor codes and CAPTCHAs handed to a person by link, live in the same browser
- History per expense, rejected documents with their reason, and notes per vendor
- Sign-in by passkey only; hand-over as a ZIP with a CSV and every invoice
A look inside the product
Recreated view with sample data.
Result
The tool is in production use for Browserbite's own bookkeeping. Building it up to the first run over real expenses took about three weeks, from mid-October to early November 2026. After that run there were notes on 31 vendors, written by the agent itself.
The real data showed cases the plan had not foreseen: company cards without a fixed cardholder, and several identical charges on the same day. Each was handled the same day it turned up.
Three decisions carried this: leaving the judgement to the agent and putting everything repeatable into tested tools, handing every login and every security check to a person without the run getting stuck on it, and ending with a complete list rather than a hunt for gaps.
- In production use
- About three weeks to the first run over real expenses
- No password and no two-factor code for the agent
- A complete list with status and invoices for the tax adviser