Before the invoice run
At month end the bookkeeper asks which Acme time entries are still open. Memtro lists fourteen not yet invoiced, with person, project and minutes, totalling 31 hours, and notes that six of them are not marked billable.
Ask which Moneybird invoices are still open, and how many hours were logged for a client.
Connect Moneybird with a personal API token and Memtro reads contacts, sales invoices with state, due dates and amount unpaid, estimates, projects, time entries and users. Addresses, phone numbers, bank and tax details are not returned. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can add notes and to-dos, create and edit contacts, projects and time entries, and draft or credit invoices. Sending an invoice, estimate or payment reminder emails the customer and cannot be recalled. Deleting an invoice or time entry is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Moneybird tool, reads what it needs, and answers with the source cited.
These tools change something in Moneybird. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Moneybird for you. Each event can start a job, with the event as its input. Moneybird signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Moneybird is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which sales invoices are late, and how much is unpaid on each?
How many hours were logged for Northwind this month?
Which time entries for Acme have not been invoiced yet?
Send a payment reminder to Globex for their two overdue invoices
Record two hours for Dan Fletcher on the BigCo website project yesterday
At month end the bookkeeper asks which Acme time entries are still open. Memtro lists fourteen not yet invoiced, with person, project and minutes, totalling 31 hours, and notes that six of them are not marked billable.
Priya Nair asks Memtro to invoice Northwind for last week's workshop hours. Memtro drafts a sales invoice with those time entries, which Moneybird marks as invoiced, and once Priya approves the lines it sends the invoice to Northwind's invoice email, giving it its number.
The teams that lean on Moneybird most, a question each of them asks, and what they connect beside it.
A record in Moneybird is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Moneybird open moneybird.com/user/applications/new and create a personal API token with the sales_invoices, time_entries and settings scopes, and estimates if Memtro should read and send estimates
Copy the token, which is shown once and works like a password for every administration you can reach
In Memtro open Connections → Moneybird and paste the Personal API token. If it reaches more than one administration, add the Administration ID, the number after moneybird.com/ in the address, and connect
Ask which invoices are still open
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Moneybird tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note or to-do to a contact; record a time entry; create a contact; update a contact's details; archive a contact; create a draft sales invoice; send or schedule a sales invoice to the contact; register a payment on a sales invoice; send a payment reminder to a contact; delete a sales invoice (permanent); create a credit invoice from a sales invoice; send an estimate to the contact; change an estimate's state; stop a running time entry; edit a time entry; delete a time entry (permanent); create a project. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Personal API token. In Moneybird open moneybird.com/user/applications/new and create a personal API token with the sales_invoices, time_entries and settings scopes, and estimates if Memtro should read and send estimates.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Moneybird for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time