Expenses and Invoices: new product names
Purchase invoices are now Expenses and sales invoices are Invoices. Existing integrations keep the same interfaces.
27 September 2026 — the product now uses Expenses for purchase records and Invoices for sales records. Navigation, actions, messages and maintained documentation use the same names.
What changes
Create, edit and find expenses under Expenses. The scanner creates an expense draft from the supplier document after your review. An expense is the product record; its invoice or receipt remains a fiscal supporting document. Invoice numbers, document types, tax rules and validation keep their meaning.
Existing integrations keep working
Only human-readable names and descriptions change. Keep using purchase_invoices, invoices, their existing scopes, MCP tool names, CLI commands and SDK methods. Published URLs, operation identifiers, fields, states, errors and webhook event names remain stable. No migration or new expenses resource is required.
The API reference describes the same invoice and expense operations with the new product terminology. The names inside executable examples stay unchanged. The assistant also understands the previous product names.
See the terminology mapping and the MCP expense tools.