Cash flow at the core, add-ons for your processes, API and MCP for your own logic—all built on a backbone of banking, forecasting, and compliance that you don't have to manage yourself.
AI Connect gives you external access to your COMMITLY data. Through the MCP server, you can connect your own AI tool—Claude, ChatGPT, Gemini, or your own model—directly to your accounts, budget figures, and forecasts. You ask questions in plain language, and the answers are based on your actual numbers.
If you prefer the traditional approach, use the REST API and the documentation at developer.commitly.com. Both methods provide access to the same data—access rights, approvals, and the audit trail remain in COMMITLY.
And COMMITLY operates both of them. The MCP server is hosted and runs continuously; we update and monitor it. You don't install anything, start anything locally, or keep track of anything. That, too, is part of the backbone that you don't have to operate yourself.
Your language model accesses your COMMITLY data directly via the MCP server—regardless of the model, whether it's Claude, ChatGPT, Mistral, or your own model, and whether it's local or hosted.
Ask questions in natural language, and answer based on your actual numbers.
User access rights and permissions are managed through COMMITLY.
The first question shows why this matters: You want to analyze personnel expenses, but you don't want to share them with everyone.
The COMMITLY MCP server is linked to a role-based access account. The model sees exactly what the person using that account is authorized to see—down to the category level—and every access event is logged in the audit trail.
In a spreadsheet, there's no such line: A file is always the entire file. If you share it, you share everything. If you don't want to do that, don't share anything at all.
If you connect a language model to it, it inherits exactly this all-or-nothing logic—the model itself does not include any rights management. It simply reads whatever is there.
Over 5,000 banks, ERPs, and financial software solutions are integrated into a single platform. And where no ready-made connection exists, APIs and MCP servers connect to any system that has an interface. At COMMITLY, integration doesn’t stop at the list of connectors.
COMMITLY isn't a monolithic solution that you have to buy in its entirety. You start with the cash flow platform and add whatever your process requires—one add-on at a time. And where the modules end, the API begins: your own logic, your own workflows, and your own interfaces all connect to the same backbone.
COMMITLY AI identifies risks earlier and turns numbers into decisions. With AI Connect, you can also apply your own language model to your data—the intelligence isn't limited to what we've built in.
You don't have to decide everything at once. The cash flow platform is the foundation. You can add the add-ons as the process requires them.
Enter, approve, and pay invoices directly from COMMITLY—within the approval workflow, with an audit trail
Corporate cards and accounts, fully integrated into cash flow
MCP Server and REST API — Access for Your Own AI Tool and Systems
Monthly Liquidity Memo with Expert Approval (Beta)
The point isn't the construction, but the operation.
Vibe Coding has made building the system affordable, but not running it. If you build your own banking setup, you'll have to run everything yourself afterward:
"Built over the weekend" becomes "maintained every week." COMMITLY takes care of this entire stack for you—you build your logic on top of it, on a foundation that you don't have to maintain yourself.
This extends all the way to the interface: COMMITLY also operates the MCP server.
It runs on a hosted, persistent, and monitored platform—not as a local package that only runs as long as your computer is on.
Added to that is continuity.
With a homemade application, in the end, often not even the developer fully understands what has been created—it’s buried in a chat history and in code that no one has ever reviewed. A cash flow plan that only one person understands is not an asset. It’s a risk with access to a bank account.
If you're considering building your own system:
We've compiled the security and compliance considerations involved into a checklist—from bank access to roles and audit trails to retention requirements.
One point of contact instead of five. If something goes wrong, you call COMMITLY—not five different support hotlines. We manage the entire stack; you have one contract and one point of contact.
REST API (OpenAPI 3.1), MCP server for AI agents, webhooks, OAuth 2.0. Read and write, model-agnostic. The MCP server is hosted by COMMITLY—no installation, no maintenance required. Plus Zapier, Make, and n8n.
A language model connected via MCP can only see what the user whose access credentials it uses is authorized to see—down to the category level. Roles, access permissions, the dual-control principle, and a continuous audit trail apply equally to both users and models.
You start with the core cash flow features and add add-ons as the process requires them—Bills, Card & Account, AI Connect. The platform grows with your setup, rather than forcing you into a complete package.
Over 5,000 banks across Europe via PSD2 and EBICS, connected through several regulated aggregators. If an aggregator’s connection to a bank fails, another can step in.
Bank connections are provided exclusively through BaFin-regulated aggregators. Hosting in Germany. AI use is entirely opt-in. Top ratings.
Pure banking APIs provide account data. COMMITLY provides forecasts, plan-to-actual comparisons, scenarios, and multi-entity consolidation—calculated using the direct method in accordance with IAS 7 / IDW and thus compatible with financing discussions and auditors.
MCP (Model Context Protocol) is an open standard that allows language models to access external data sources and functions. An MCP server provides this connection: Instead of exporting or copying data, your AI tool queries the system directly. With COMMITLY, this means your language model (Claude, ChatGPT, Gemini, or your own) accesses your accounts, budget figures, and forecasts via the COMMITLY MCP server. Access rights, approvals, and the audit trail remain within COMMITLY.
No. Many MCP servers are delivered as a local package that you start, configure, and keep up to date yourself—and that only runs as long as your computer is running. The COMMITLY MCP server is hosted and operated by COMMITLY; it’s always available, monitored, and updated. You connect your AI tool once and get to work. There’s nothing to install, nothing to deploy, and nothing to maintain.
No—it sees exactly what the account it’s connected to has access to. The MCP server is linked to a COMMITLY account with a role and permissions down to the category level. If a user who is not authorized to view personnel costs connects, their language model will not see any personnel costs either. Every query is subject to the same permissions and access controls as work within the application. With a table or a custom-built app, this level of control does not exist: in those cases, the model sees everything contained in the file.
Yes, regarding roles and permissions in COMMITLY—the same ones that apply to people. For each user, you specify which clients, accounts, and categories are visible; the MCP server adheres to these settings. Write operations also go through the usual approval processes. Access can be revoked at any time—unlike a shared file, which becomes a copy once it’s been shared.
All models that support the MCP Server protocol—Claude, ChatGPT, Gemini, Mistral, and custom models, whether local or hosted. The MCP Server is model-agnostic.
The REST API complies with OpenAPI 3.1. You can find the documentation here.
Open Banking refers to regulated access to banking data and payment functions via standardized interfaces—governed in Europe by the PSD2 Directive. Banks provide the data via a secure interface at the account holder’s request. COMMITLY uses Open Banking to connect your accounts: Balances and transaction history are automatically imported into your Cash flow planning and updated up to four times a day.
A banking API is a programming interface that allows software to access banking data—balances, transaction history, and, depending on the provider, payment initiation. A basic banking API provides only the data: you have to build and operate the forecasting logic, planning, user interface, and compliance workflow yourself. COMMITLY offers the API in addition to a ready-to-use platform—you get the planning layer included and can still access the data programmatically.
EBICS (Electronic Banking Internet Communication Standard) is the established standard for communication between businesses and banks in German-speaking countries. It is designed for corporate customers and performs reliably in situations where the PSD2 interface reaches its limits—such as with higher transaction volumes or certain account types. COMMITLY supports both approaches: PSD2 for fast open banking integration, and EBICS for professional corporate banking processes.
"Pay by Bank" refers to payments initiated directly from a bank account—without a card or payment service provider involved. This term is most commonly used in the context of e-commerce payments. COMMITLY applies the same principle in a different context: when paying your incoming invoices. With COMMITLY Bills, you approve invoices and initiate payment directly from your bank account—all within your approval workflows, with dual-control and a complete audit trail. Important to note: 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 invoicing and approval process, not a standalone payment product.
A pure API (e.g., Nevlo) provides banking data—you build and operate everything else yourself: forecasting logic, database, UI, compliance, hosting, security, ongoing maintenance of the PSD2 interfaces, bug fixes, and scaling. And operation is the expensive, ongoing part—not the initial build. COMMITLY provides the ready-to-use planning layer AND operates the regulated banking, data, and compliance stack. You also get the API/MCP to integrate your own logic—without having to maintain the underlying infrastructure yourself.
Over 5,000 banks across Europe, via PSD2 (Open Banking) and EBICS (professional corporate banking). COMMITLY uses multiple regulated aggregators for this purpose instead of just one—if one aggregator’s connection to a bank goes down, another can step in. This isn’t about breaking records; it’s about reliability in everyday use.
No. You start with the Cashflow platform as your core solution and add add-ons only when your process requires them—such as "Bills" for incoming invoices and payments, "Card & Account" for corporate cards, or "AI Connect" for MCP/API access. You can expand at any time, but you don't have to decide anything in advance.
Access is included in the COMMITLY editions or can be purchased as an add-on. See the pricing page for details.
Yes—that's exactly what the hybrid model is. COMMITLY serves as the backbone for banking, forecasting, and compliance, and your own logic integrates via API/MCP.
Yes. COMMITLY is multi-tenant; client data is kept separate, and you can use the REST API to build reports that span all clients. Instead of maintaining a separate Excel file for each client, you set it up once and use it for many.
Nothing—that’s exactly why COMMITLY is a collaborative application and not a file. Multiple people work on the same version, with roles and permissions; every change is traceable in the audit trail; and backups and restores are managed. With a self-built model, on the other hand, the planning depends on the person who built it: If that person is unavailable, the planning falls through.
No, and that's by design. COMMITLY is not an enterprise TMS, not an ERP replacement, and not just an API provider. It complements DATEV, lexoffice, sevDesk, and your ERP by adding a cash flow and liquidity layer and retrieves data from those systems—via pre-built integrations, API, or MCP.
Technically, yes, and bank access isn’t the obstacle here: Regulated aggregators sell PSD2 account access as a service, so you don’t need your own license. COMMITLY integrates with banks in the same way. What you’re purchasing, however, is a provider contract that includes onboarding, a data processing agreement, ongoing costs starting with the first account, and dependence on a single provider. And what you get is account data—you’ll have to build the forecasts, plan-vs.-actual comparisons, scenarios, and consolidation yourself. On top of that comes operations: encryption, key management, roles and permissions, audit trails, backups with tested restores, updates in response to security vulnerabilities, GDPR documentation, a 72-hour reporting deadline for data breaches, and commercial and tax-related retention requirements. Each point can be addressed individually. Together, they’re not a one-time project but an ongoing task.