Month-end export check
Sarah Chen, finance manager at Acme Ltd, asked which approved invoices were still waiting to be exported. Memtro listed them with amount, supplier and expense date, oldest first.
Which approved invoices have not been exported to accounting yet?
Moss holds your company's spend, and Memtro reads it so finance questions get quick answers. It reads card transactions, supplier invoices and reimbursements by type, approval status, export status and date, with amounts. It reads suppliers with payment method and terms, teams, departments, accounting dimensions with their items, and expense accounts. When asked and granted, it can create or update suppliers and create or update dimensions and dimension items. Bank details, balances, receipts, people, and merchant or cardholder text are never read. Only a Moss administrator can create the key.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Moss tool, reads what it needs, and answers with the source cited.
These tools change something in Moss. 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 Moss 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 approved invoices have not been exported yet?
What did we spend on card transactions last month?
Which suppliers are paid by direct debit?
What items sit under the Project dimension?
Add a dimension item for the Northwind rollout project.
Sarah Chen, finance manager at Acme Ltd, asked which approved invoices were still waiting to be exported. Memtro listed them with amount, supplier and expense date, oldest first.
Dan Fletcher, financial controller at Northwind, asked Memtro to add a cost centre for the new Leeds office. Memtro created the dimension item, and the finance team could book expenses to it straight away.
The teams that lean on Moss most, a question each of them asks, and what they connect beside it.
A record in Moss 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 Moss, go to Settings, then Platform, then API Keys, and choose Create API Key. Only administrators can do this, and you confirm it in the Moss mobile app.
In Memtro, open Connections → Moss and paste the Key ID (kid_...) and the Secret Key (sk_...).
The key reads and writes for the whole organisation, so an administrator grants the supplier and dimension actions by name only to finance.
Ask which approved invoices have not been exported yet.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Moss tools are the same everywhere.
Only when you ask, and only what it has been granted: create a supplier; update or deactivate a supplier; create an accounting dimension; rename a dimension or change its ERP name; create a dimension item; rename, recode or deactivate a dimension item. 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.
Key ID and Secret Key. In Moss, go to Settings, then Platform, then API Keys, and choose Create API Key. Only administrators can do this, and you confirm it in the Moss mobile app.
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