Everything else lists or fetches, which suits an agent asked to answer accounting questions rather than to file them: what did we invoice in a period, what has a supplier billed, what sits on which account. `send_invoice` is the one to be careful with, since an invoice dispatched by email is not something a later call takes back. Vouchers go in as a date, a description and a `postings` array, so the correctness of a write rests entirely on the account numbers you resolved from `list_accounts` beforehand.
A Tripletex client exposing 15 tools over invoicing, the customer and supplier registers, ledger postings and journal vouchers, plus the chart of accounts, projects, employees, products and company details an entry has to reference.
- Invoices end to end: `list_invoices` filters on `invoiceDateFrom` and `invoiceDateTo` under a `count` cap, `get_invoice` opens one, and `send_invoice` dispatches it by email under a chosen `sendType`.
- The customer register as a working list: `list_customers` searches by `name`, `get_customer` returns one in full, and `create_customer` adds one with an organisation number, email, phone and postal address.
- The purchase side: `list_suppliers` returns suppliers and `list_supplier_invoices` returns what they have billed from an `invoiceDateFrom` cutoff.
- The ledger itself: `list_ledger_entries` returns postings across a `dateFrom`/`dateTo` range, `list_accounts` returns the chart of accounts, and `create_voucher` posts a journal voucher from a date, a description and a `postings` array.
- The registers a line has to point at: `list_projects`, `list_employees` and `list_products` return those lists, and `get_company_info` returns the company record itself.
A Tripletex company whose invoices, ledger and registers these calls are meant to act on.
One command — npx -y tripletex-mcp-server