Codat logo

Codat + Memtro

Which invoices are overdue for this client, and how fresh is their data?

Codat is one API over the accounting software of the businesses you connect. Memtro reads companies and their connections, how fresh each data type is, invoices and bills with amounts due, customers and suppliers by name, the chart of accounts, profit and loss, balance sheet, and the status of each write. When asked and granted, it can create customers, suppliers, invoices, bills and journal entries, record payments, refresh data, and create or delete companies. Codat can tell Memtro when a connection links or a write fails, and a job can start on it. Contact details are never read.

In Memtro

What you can do with Codat in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Codat tool, reads what it needs, and answers with the source cited.

What it does

  1. 01List companies with their connections, platform, status and last sync, and how fresh each data type is.
  2. 02Read a company's invoices and bills with amounts due summed per currency, filtered by status, contact or outstanding only.
  3. 03See customers and suppliers by name, the chart of accounts, and profit and loss or balance sheet by month.
  4. 04When asked and granted, create customers, suppliers, invoices, bills and journal entries in a company's accounting software. Codat sends nothing to the customer.
  5. 05When asked and granted, record a payment against an invoice or bill (no money moves), delete records where the software allows, refresh data, or create or delete a company.
  6. 06With events on, a linked or disconnected connection, or a failed write of invoices in Codat, can start a job.

Acts when asked

When you ask it to

These tools change something in Codat. 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.

  1. 01Create a company in Codat (not yet connected to any software)
  2. 02Delete a company with its connections and cached data (permanent)
  3. 03Refresh all of a company's data from its software
  4. 04Refresh one data type of a company
  5. 05Create a customer in a company's accounting software
  6. 06Create a supplier in a company's accounting software
  7. 07Create an invoice in a company's accounting software
  8. 08Delete an invoice from a company's accounting software (QuickBooks Online only)
  9. 09Create a bill in a company's accounting software
  10. 10Delete a bill from a company's accounting software (where supported)
  11. 11Create a balanced journal entry in a company's ledger
  12. 12Delete a journal entry from a company's ledger (where supported)
  13. 13Record a customer payment against an invoice (no money moves)
  14. 14Record a payment of a bill (no money moves)

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Codat, choosing the same kinds; the tab shows Codat's own steps. Each event can start a job, with the event as its input. Codat signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01A company was created in Codat
  • 02A company was deleted from Codat
  • 03A business started connecting its software
  • 04A business's connection was linked
  • 05A connection was unlinked or de-authorised
  • 06A connection was reconnected
  • 07A connection failed to link
  • 08A connection was deleted
  • 09Codat finished reading a company's data
  • 10Codat finished the first read of a company's data
  • 11A write of invoices to the accounting software succeeded
  • 12A write of invoices to the accounting software failed
  • 13A write of bills to the accounting software succeeded
  • 14A write of bills to the accounting software failed
  • 15A write of customers to the accounting software succeeded
  • 16A write of customers to the accounting software failed
  • 17A write of payments to the accounting software succeeded
  • 18A write of payments to the accounting software failed
  • 19A write of billPayments to the accounting software succeeded
  • 20A write of billPayments to the accounting software failed
  • 21A write of journalEntries to the accounting software succeeded
  • 22A write of journalEntries to the accounting software failed
  • 23The daily request quota was used up
  • 24The daily request quota was reset
In practice

Ask it like you would a colleague

Once Codat 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.

Codat logoCodat + Memtro
  • Which invoices are overdue for Northwind?

  • How much does BigCo owe its suppliers right now?

  • What was Acme's revenue last quarter?

  • When did Codat last read Northwind's data?

  • Which companies have a connection that is not linked?

01

Overdue invoices for a client

Sarah Chen, a finance analyst at Acme Ltd, asked which of Northwind's invoices were overdue. Memtro checked how fresh Codat's copy was, then listed the outstanding invoices past their due date with the amount due summed per currency.

02

Recording a customer payment

Tom Reilly, a bookkeeper at BigCo, said a customer had paid invoice INV-1042 and asked Memtro to record it. Memtro recorded the payment through Codat, checked the write succeeded, and noted that no money moved and nobody was notified.

Teams

Where it fits

The teams that lean on Codat most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Codat 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.

Setup

How to connect

Connect withAPI key
  1. 1

    In the Codat Portal, open Developers → API keys and copy a key. Only Administrator or Developer users can see keys, and a key acts on every company.

  2. 2

    In Memtro, open Connections → Codat and paste the API key.

  3. 3

    An administrator grants the create, payment and delete actions by name only to the teams that keep the books. Events are turned on from the connection's Events tab, and the address is then added under Monitor → Webhooks in the Codat Portal.

  4. 4

    Ask which invoices are overdue for a company.

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Codat tools are the same everywhere.

FAQ

Questions

Can Memtro change anything in Codat?+

Only when you ask, and only what it has been granted: create a company in Codat (not yet connected to any software); delete a company with its connections and cached data (permanent); refresh all of a company's data from its software; refresh one data type of a company; create a customer in a company's accounting software; create a supplier in a company's accounting software; create an invoice in a company's accounting software; delete an invoice from a company's accounting software (QuickBooks Online only); create a bill in a company's accounting software; delete a bill from a company's accounting software (where supported); create a balanced journal entry in a company's ledger; delete a journal entry from a company's ledger (where supported); record a customer payment against an invoice (no money moves); record a payment of a bill (no money moves). 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.

Who can use a Codat connection?+

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.

Does Memtro store my Codat data?+

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.

How do I connect Codat?+

API key. In the Codat Portal, open Developers → API keys and copy a key. Only Administrator or Developer users can see keys, and a key acts on every company.

Can Codat start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Codat, choosing the same kinds; the tab shows Codat's own steps. 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.

Connect Codat in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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