The platform you build on
— and that grows with you

Technically yes — the real question is not building it but running it: a provider contract for bank data, security, GDPR, backups, maintenance. You will find the honest self-built / COMMITLY / hybrid comparison, including everything running it involves, on Build your own cashflow tool.

The REST API follows OpenAPI 3.1. You will find the documentation here.

Open banking means regulated access to bank data and payment functions through standardised interfaces — in Europe governed by the PSD2 directive. At the account holder's request, banks make the data available through a secured interface. COMMITLY uses open banking to connect your accounts: balances and transactions flow into your cash flow planning automatically, updated up to four times a day.

A banking API is a programming interface through which software accesses bank data — balances, transactions and, depending on the provider, payment initiation as well. A pure banking API only delivers the data: forecast logic, planning, interface and the compliance chain are things you have to build and run yourself. COMMITLY offers the API on top of the finished platform — you get the planning layer as well and can still access it programmatically.

EBICS (Electronic Banking Internet Communication Standard) is the established standard for communication between companies and banks in German-speaking countries. It is built for corporate customers and is robust where the PSD2 interface reaches its limits — for instance with higher volumes or certain types of account. COMMITLY supports both routes: PSD2 for a fast open banking connection, EBICS for professional corporate banking processes.

Pay by bank means payments triggered straight from the bank account — with no card or payment service provider in between. Usually it refers to paying in e-commerce. COMMITLY uses the same principle somewhere else: when paying your incoming invoices. With COMMITLY Bills you approve invoices and trigger the payment straight from your bank account — inside your approval workflows, with the four-eyes principle and a full audit trail. One point of clarification: COMMITLY is not a payment service provider and does not offer pay by bank as an interface for third parties. The payment is part of the invoice and approval process, not a payment product in its own right.

More than 5,000 banks across Europe, through PSD2 (open banking) and EBICS (professional corporate banking). COMMITLY uses several regulated aggregators for this rather than just one — if one aggregator's connection to a bank fails, another can step in. That is not a numbers record, it is a question of day-to-day reliability.

No. You start with the cash flow platform as the core and only add on when your process calls for it — for instance Bills for incoming invoices and payments, Card & Wallet for company cards or AI Connect for MCP/API access. You can extend at any time but do not have to decide anything in advance.

Access is part of the COMMITLY editions or can be booked as an add-on. Details on the prices page.

Yes. COMMITLY supports multiple clients, client data is kept separate, and reporting across all clients can be built through the REST API. Instead of maintaining one Excel file per client, you set it up once and serve many with it.

No, and that is deliberate. COMMITLY is not an enterprise TMS, not an ERP replacement and not a pure API workshop. It adds the cash flow layer to DATEV, lexoffice, sevDesk and your ERP and pulls the data from there — through ready-made integrations, the API or MCP.