Chasing late invoices
Maya Okafor, finance manager at Acme Ltd, asked which invoices were late. Memtro listed the late invoices with customer, due date, total and amount paid, with totals per currency.
Which invoices are late, and what tax do we charge this customer?
Quaderno connects Memtro to your invoicing and tax records. It reads invoices with state, dates, totals and amount paid, expenses with supplier and payment method, and contacts with country and tax status. It works out the tax Quaderno would apply to a sale to a given country, recording nothing. When asked, and once an administrator has granted the action by name, it can create invoices, contacts and expenses, record payments, email an invoice to its customer, and void an invoice, issue a credit note or delete a contact, all permanent. Contact addresses, phone numbers and tax ids are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Quaderno tool, reads what it needs, and answers with the source cited.
These tools change something in Quaderno. 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 Quaderno for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Quaderno signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Quaderno 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 Quaderno invoices are late?
What VAT do we charge a German customer for SaaS?
How much did we spend with our hosting supplier this quarter?
What have we invoiced Northwind this year?
Record Northwind's bank transfer against invoice 118
Maya Okafor, finance manager at Acme Ltd, asked which invoices were late. Memtro listed the late invoices with customer, due date, total and amount paid, with totals per currency.
Tom Reilly, founder of Northwind, said Globex had paid invoice 118 by bank transfer. Memtro recorded the payment against the invoice in Quaderno, no money moved, and as the payments now reached the total Quaderno marked the invoice paid.
The teams that lean on Quaderno most, a question each of them asks, and what they connect beside it.
A record in Quaderno 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 Quaderno at quadernoapp.com, open Profile → API Keys and copy the private API key. A sandbox key works only with a sandbox account.
In Memtro, open Connections → Quaderno and paste it into API key.
Leave Account name blank and Memtro reads it from the key, or enter ACCOUNT from https://ACCOUNT.quadernoapp.com.
Ask your first question: which Quaderno invoices are late?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Quaderno tools are the same everywhere.
Only when you ask, and only what it has been granted: create an invoice (takes the next legal invoice number, nothing is sent); email an invoice to its customer; void an invoice, which issues a credit note against it (permanent); mark an invoice uncollectible; record a payment against an invoice; change an invoice's tags, payment details, notes or metadata; issue a credit note refunding all or part of an invoice (permanent); record an expense; create a contact; edit a contact's details; delete a contact (permanent). 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.
API key, and the account name if you choose. In Quaderno at quadernoapp.com, open Profile → API Keys and copy the private API key. A sandbox key works only with a sandbox account.
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 Quaderno 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