Month-end expense reconciliation
Tom Reilly, finance controller at Northwind, asked which expenses were exported this month. Memtro listed them by export date with employee, category and amount.
Which expenses have been exported, and which trips need approving?
Rydoo shows you exported expenses with employee, category, project, amounts and approval dates, and any expense by id with its VAT lines. It reads trips with budgets and spend, Rydoo Card transactions, reimbursements, employees, groups, projects, categories and branches. When asked and granted, it can add an expense or trip for an employee, and mark expenses booked or unbooked. It can also reject expenses or mark them reimbursed, approve or reject trips, and add users, groups and projects. The only list of expenses the API offers is those already exported to accounting.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Rydoo tool, reads what it needs, and answers with the source cited.
These tools change something in Rydoo. 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 Rydoo 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 expenses were exported last week?
Which trips are waiting for approval?
What has been reimbursed this month?
What did the sales team spend on Rydoo Cards in October?
Which expense categories map to which accounting numbers?
Tom Reilly, finance controller at Northwind, asked which expenses were exported this month. Memtro listed them by export date with employee, category and amount.
Priya Sharma, team lead at Acme Ltd, asked Memtro to approve Dan Fletcher's trip to the Berlin conference. With the action granted, Memtro moved the trip to Approved, and Dan saw the change in Rydoo.
The teams that lean on Rydoo most, a question each of them asks, and what they connect beside it.
A record in Rydoo 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 Rydoo give the credentials' owner the API Manager role, then open Admin, then API Credentials, and create credentials. The secret is shown once.
In Memtro open Connections → Rydoo and paste the Client ID and Client Secret.
An administrator grants the expense, trip and user actions by name to the teams that may use them.
Ask: which expenses were exported last week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Rydoo tools are the same everywhere.
Only when you ask, and only what it has been granted: add an expense for an employee; mark an expense as booked (reported) in the ERP; undo an expense's booked (reported) status; reject expenses (the employee sees the reason); mark expenses as reimbursed; add a user (with enabled true, they are emailed an invitation); add a group (department); add a project; add a trip for an employee; change the status of trips (approve, reject, complete). 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.
Client ID and Client Secret. In Rydoo give the credentials' owner the API Manager role, then open Admin, then API Credentials, and create credentials. The secret is shown once.
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