Ada without industry ballast — for consulting, agencies and services
Not every company manages properties or services technical installations. Firms that sell advice, support or services mainly need three things: clean quotes, legally sound invoices, and billing that arrives every month on its own. That is exactly what this configuration of Ada is — the same platform, the same EU sovereignty, but only the surfaces you actually use. Properties, tenants, assets and the dispatch board are not hidden; they are simply not booked.
Quotes from building blocks and templates, with validity periods and automatic follow-up. An accepted quote becomes the invoice — no retyping, no second set of records.
Record the retainer once: client, amount, cadence, term. For each period Ada creates a new invoice with its own number and the correct service period — always as a draft for review, never a silent send.
Every invoice is produced as ZUGFeRD/Factur-X to EN 16931, with the generator continuously verified against the official KoSIT checker. Incoming e-invoices are validated against the same standard on arrival. Gap-free numbering, DATEV revenue accounts per line, cancellations and corrections with a clean reference to the original.
Ada knows payment terms and due dates, tracks open items and prepares the three-stage dunning run. Here too: Ada writes the draft, you decide what goes out.
The two terms get mixed up in everyday use but mean different things — and Ada does both. A standing invoice is a single document with a fixed number describing a cadence: "500 euros monthly, until revoked". You issue it once and the client keeps paying against it. A recurring invoice instead produces a new document for each period, with its own number and service period — the normal case when each period is to be posted, dunned and reconciled separately.
These surfaces are not lost, only unbooked. If your business grows into an industry configuration, we switch the matching module on — same instance, same data, no migration.
Yes. You record a billing agreement per client with amount, cadence, start date and an optional end of term. On each due date Ada creates a new invoice with its own number and the service period covered. Each period is billed exactly once, even if a run has to catch up. The invoice is created as a draft — a human reviews and finalises it.
Yes, at no extra cost and without an add-on module — in both directions. Outbound, every invoice is produced as ZUGFeRD/Factur-X to EN 16931, and the generator is held to the official KoSIT checker: nothing ships that fails the Schematron test. Inbound, Ada validates every e-invoice it receives against the same standard on arrival. The checker is self-hosted, not a third-party service.
They are not booked. They do not appear in your interface, and the server refuses every request to an unbooked area — including an administrator’s. The boundary therefore does not sit in the menu structure but in the permission itself: for an unbooked area there is no data anyone could be shown.
Yes. Ada runs in EU hosting or on-premise on your own infrastructure, with EU language models. For particularly sensitive content there is the Datenschild, which blocks any flow to non-EU models rather than merely regulating it by contract.
This page shows the industry-neutral configuration. The main Ada page shows the full concept: AI inbox with draft suggestions, human release, EU language models and the on-premise option.
Find the right starting point for AI, blockchain, or custom software in under 2 minutes – with a concrete next step and a price indication.