this+that for finance teams
The approval, the invoice and the renewal all arrive as email.
Finance runs on systems of record, but the work that feeds them starts as a message. An invoice attached to a supplier email, an approval someone is waiting on, a renewal date mentioned once in a thread nine months before it matters. this+that reads those as they arrive, turns each into tracked work with an owner, and keeps a link back to the message it came from.
The ledger is tidy. Everything upstream of it is not
Your accounting system is accurate about what it has recorded. It knows nothing about the invoice sitting unopened in someone’s inbox, the approval waiting on someone who is on leave, or the supplier who emailed to say the invoice is wrong. That work sits in email until a person moves it, and the month-end chase exists because people are busy and forget.
Then there are the dates. Auto-renewals, annual price increases, notice periods and expiry dates almost always arrive in writing, months before they take effect, and then get copied into a spreadsheet or a calendar or, often, nowhere. Missing one rarely creates much work. It creates a contract that renewed at the supplier’s price, or a cancellation window that closed.
Every open item in one place, without anyone entering it
DoBox reads across the mailboxes and channels finance already uses and pulls the open items out of them, whether that is an invoice awaiting approval, a query nobody answered, or a payment a supplier is chasing. You’re not typing tasks in, and nothing depends on the message having been flagged when it arrived.
Each item carries an owner and a link back to the original message, so the reason a payment is on hold is one click away rather than a question you have to ask. Work that belongs to someone outside finance goes to them from the same view, so the approval chain stops being a forwarding chain.
Finance routine that stops needing a person to start it
You describe a workflow in plain English and it’s running in minutes. Every step that sends or commits anything can wait on approval. Some that finance teams reach for first:
The close does not have to live in one person’s head
In a small finance team the sequence of the close, and the reason behind each recurring exception, are usually known rather than written. That works until the person who knows is on leave in the last week of the quarter. The Brain holds that operating knowledge in a shared layer, and workflows update it as the work happens, so it stays current without anyone maintaining it.
Why this supplier is an exception
The side agreement on payment terms, the reason one account is reconciled differently, the thing that was agreed on a call and written down nowhere. That context becomes shared rather than a single point of failure, and it stays attached to the supplier it belongs to.
Kept current by the work, not by a reminder
A wiki decays because updating it is a separate job somebody has to remember. Here the workflows that already run against your messages propose the updates, and a person accepts, edits or rejects each one. Maintenance is semi-automatic and a human stays in it.
It sits alongside your systems of record
Your ledger, your ERP and your payment rails stay exactly where they are, and the Brain holds the operational context around them: the terms, the exceptions and the reasoning. That context also grounds the actions this+that takes on your behalf.
How this reaches the systems finance actually runs on
this+that ships twenty MCP servers and supports arbitrary ones beyond them, so a tool your team already pays for can drive a workflow directly once it publishes a server. Stripe is the clearest example in finance today. Connect it and a workflow can reach invoices, subscriptions, payouts, disputes and balance transactions, and the same will hold for your accounting system when it ships one.
Twenty built in
Box and Dropbox for filing originals, HubSpot for logging against the customer record, Notion and Confluence for documentation, Snowflake for warehouse queries against your own instance. They cover the paperwork and the record around a transaction.
Bring your own server
When a tool you already pay for publishes an MCP server, connect it and it reaches workflows exactly like a built-in. That keeps pace with a standard the finance stack is adopting quickly, rather than waiting on us to ship an integration for each one.
It runs the other way too
this+that exposes its own MCP server, so an agent your team already uses can read and write the task list directly. The finance work this+that extracts is reachable from whatever you already run in your own terminal.
Nothing here starts with somebody noticing the email
Automation platforms run a finance sequence well once you have described it and connected the systems. What they wait on is a person. Somebody has to read the message, decide it matters, and start the process. this+that reads what arrives and triggers the workflow you built, recognizing that an invoice is an invoice and a renewal date is a deadline, so the sequence starts from the message rather than from somebody noticing it. A person approves anything that sends or commits, for as long as you want that, and you can let a workflow run unattended once it has earned it. For work that runs on a file that isn’t going into a SaaS tool, a model or a schedule, you can hand the task to an agent on your own machine instead, which currently means an Apple Silicon Mac, with Windows and Linux in progress.
Find the approvals and renewals you’ve already read past
Connect a mailbox and watch them come out as tracked work, each one linked to the message it came from. Free during beta, no credit card required.