For consulting, agencies and services
Quotes, invoices and recurring billing
Alois without industry ballast.
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 Alois 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.
What this configuration does
Quotes that become invoices
Quotes from building blocks and templates, with validity periods and automatic follow-up. An accepted quote becomes the invoice, with no retyping and no second set of records.
Recurring billing per client
Record the retainer once: client, amount, cadence, term. For each period Alois creates a new invoice with its own number and the correct service period, always as a draft for review, never a silent send.
E-invoicing that passes
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.
Open items and dunning
Alois knows payment terms and due dates, tracks open items and prepares the three-stage dunning run. Here too: Alois writes the draft, you decide what goes out.
Standing invoice or recurring invoice?
The two terms get mixed up in everyday use but mean different things. Alois 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. That is the normal case when each period is to be posted, dunned and reconciled separately.
Typical use cases
- Bill a monthly consulting or support retainer per engagement
- Write a quote, follow up, and convert it into the invoice
- E-invoicing for public sector and large clients
- Keep open items in view and have dunning levels prepared
- Pre-sort incoming invoices and receipts in the inbox
- Draft recurring correspondence from templates
What this configuration includes and what it does not
Included
- Quotes, article and service catalogue, client records
- Invoices, e-invoicing to EN 16931, cancellations and corrections
- Billing agreements for recurring invoicing
- Open items, payment terms, three-stage dunning
- Inbox, files, document studio, assistant, dates and deadlines
Not booked
- Properties, units, tenants, service charges, condo assemblies
- Assets, maintenance contracts, inspection reports, statutory duties
- Dispatch board, scheduling, time recording, stock and purchasing
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.
Frequently asked questions
Can Alois bill monthly retainers automatically?
Yes. You record a billing agreement per client with amount, cadence, start date and an optional end of term. On each due date Alois 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.
Is e-invoicing included?
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, Alois validates every e-invoice it receives against the same standard on arrival. The checker is self-hosted, not a third-party service.
What happens to the industry features I do not need?
They are not booked. They do not appear in your interface; opening their address returns an explicit refusal rather than the surface, including for an administrator. The server declines every request to them as well. 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.
Does our data stay in Europe?
Yes. Alois runs in EU hosting with EU language models. On request we prepare operation on your own hardware. For particularly sensitive content there is the Datenschild, which blocks any flow to non-EU models rather than merely regulating it by contract.
Alois as an AI back office across industries
This page shows the industry-neutral configuration. The Alois home page shows the full concept: AI inbox with draft suggestions, human approval, EU language models and hosting in the EU.