Chasing overdue invoices
Sarah Chen, bookkeeper at Acme Ltd, asked which customer invoices were overdue. Memtro listed them with customer, due date and balance still owed.
Which customer invoices are overdue, and what do we still owe suppliers?
Billy shows you the books of a Danish small business: invoices and credit notes with balances and overdue status, and supplier bills. Memtro also reads customers and suppliers, products and prices, the chart of accounts and tax rates. When asked and granted, it can create and edit contacts, and create, edit or approve draft invoices and credit notes. It can email an invoice to a contact person, send it as an e-invoice, or delete a draft. It can also record or void a payment, create and approve bills, and manage products. Each token belongs to one company only.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Billy tool, reads what it needs, and answers with the source cited.
These tools change something in Billy. 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.
Once Billy 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 invoices are overdue?
What do we owe suppliers this month?
What lines are on invoice 1042?
What is the unit price of the consulting day product?
Create a draft invoice for Northwind for two consulting days.
Sarah Chen, bookkeeper at Acme Ltd, asked which customer invoices were overdue. Memtro listed them with customer, due date and balance still owed.
Dan Fletcher, owner of a small design studio, asked Memtro to record a bank transfer against invoice 1042. With the action granted, Memtro booked the payment, and the invoice's balance in Billy showed it as paid.
The teams that lean on Billy most, a question each of them asks, and what they connect beside it.
A record in Billy 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 Billy, open Settings → Access tokens → Create access token at mit.billy.dk and name it Memtro. The token never expires and has no scopes.
Open Connections → Billy in Memtro and paste the Access token. A second company needs its own token and connection.
An administrator grants actions such as approve an invoice or email an invoice by name to the teams that may use them.
Ask which invoices are overdue.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Billy tools are the same everywhere.
Only when you ask, and only what it has been granted: create a contact (customer or supplier); edit or archive a contact; add a contact person to a contact; create a draft invoice or credit note; edit a draft invoice's message, terms or attention; approve a draft invoice into the books (permanent); email an invoice to a contact person (the customer receives it); send an approved invoice as an e-invoice by GLN (the receiver gets it); delete a draft invoice (permanent); record a payment against an invoice or bill; void a payment (permanent); create a draft bill; approve a draft bill into the books (permanent); create a product with prices; edit or archive a product. 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.
Access token. In Billy, open Settings → Access tokens → Create access token at mit.billy.dk and name it Memtro. The token never expires and has no scopes.
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