Approvals before month end
Tom Reilly, finance manager at Northwind, asked which purchase orders were still waiting for approval. Memtro listed them with supplier, amount and approval progress, and the budget each one draws on.
Which purchase orders are waiting for approval, and how much budget is left?
Precoro shows you purchase orders, purchase requisitions, invoices and receipts by status or date, with their lines and approval progress. It reads suppliers and their terms, budgets with what is used and available, payments, and the locations, taxes and units the actions need. When asked and granted, it can create a requisition, purchase order or supplier, and submit, approve, reject, return or reopen a document. It can also record or cancel an invoice payment and receive goods. The key sees only what its user's roles, locations and departments allow, and approving needs that user to hold the matching role.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Precoro tool, reads what it needs, and answers with the source cited.
These tools change something in Precoro. 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 Precoro 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 purchase orders are waiting for approval?
How much of the marketing budget is still available?
Show the lines on purchase order PO-1042.
Which invoice payments were recorded last week?
What payment terms does our stationery supplier have?
Tom Reilly, finance manager at Northwind, asked which purchase orders were still waiting for approval. Memtro listed them with supplier, amount and approval progress, and the budget each one draws on.
Maya Okafor, office manager at Acme Ltd, said the new desks had arrived and asked Memtro to receive them. With the action granted, Memtro read the purchase order's lines and created a receipt in Precoro for the delivered quantity.
The teams that lean on Precoro most, a question each of them asks, and what they connect beside it.
A record in Precoro 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 Precoro open Configuration, then Integrations, then API Key, press Generate API Key and copy it. It is shown once.
In Memtro open Connections → Precoro and paste the API key and the Email of the key's user. Set Region to us if you sign in at app.precoro.us.
The key's user needs the matching Precoro role to approve, reject or create documents. An administrator grants those actions by name to the teams that may use them.
Ask: which purchase orders are waiting for approval?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Precoro tools are the same everywhere.
Only when you ask, and only what it has been granted: create a purchase requisition (as a draft); edit a draft purchase requisition; create a purchase order; submit a draft document for approval; approve a document at its current step; reject a document; return a document for revision; reopen an approved document for editing; create a supplier; approve or reject a supplier; record a payment against an invoice; cancel a payment; receive goods against a purchase order. 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 email of the key's user. In Precoro open Configuration, then Integrations, then API Key, press Generate API Key and copy it. It 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