Case Management Software for German Law Firms: beA, GDPR Hosting and Costs
In Germany, a practice platform has to handle beA filings, RVG fee math, Section 43e BRAO outsourcing contracts and GoBD audits. Here's how to test vendors on each, and what a rollout typically costs.
Why German Firms Can't Shortlist Like Everyone Else
If you run or advise a German law firm, or a German office of an international one, you face one choice before any feature demo. Either you buy domestic Kanzleisoftware that already handles German rules, or you buy an international platform and add the German pieces yourself. Elsewhere that choice comes down to taste and budget. For law firm case management software in Germany, four rules decide which systems can work at all.
- beA: the special electronic lawyer mailbox (besonderes elektronisches Anwaltspostfach), run by the Federal Bar (BRAK). Lawyers must be able to receive through it, and filings to most German courts must be made electronically.
- RVG: the statutory fee law (Rechtsanwaltsvergütungsgesetz). Fees are calculated from the value in dispute and numbered fee items, and German clients and courts expect invoices built that way.
- Section 43e BRAO: the professional-code rule on sharing client secrets with service providers, cloud hosts included. It works alongside criminal confidentiality under Section 203 of the Criminal Code (StGB) and the GDPR.
- GoBD: the tax administration's principles for electronic books and records. They decide whether your billing and accounting data survives a tax audit.
These rules should shape the shortlist before anything else does. A system that looks great but needs a separate beA client, a spreadsheet for RVG fees and a manual export to the tax adviser will cost more in staff time than it saves in licence fees. The sections below show how to test each requirement, what costs look like, and how long rollout takes.
This is a buyer's guide, not legal or tax advice. Before you sign hosting or outsourcing contracts, have your data protection officer and tax adviser check the specifics, and consult your bar chamber's guidance.
Testing beA Integration Beyond the Checkbox
Nearly every German vendor lists "beA integration," but the term covers very different things. At one end, the software just opens the separate beA web application. At the other, it connects to the official beA interface, so incoming messages land in the right matter automatically, outgoing pleadings go out from the file, and the electronic receipt acknowledgment (elektronisches Empfangsbekenntnis, eEB) is handled in the workflow.
Depth matters because a missed beA message is a deadline problem, and deadline problems turn into professional liability claims. Active electronic filing to civil courts became mandatory in 2022, and comparable duties apply in other court branches such as labor, administrative and social courts. Firms organized as professional companies also have a company mailbox to monitor.
Questions to put to every vendor
- Does the system use the official BRAK beA interface, or does it automate the web client? Interface-based integrations tend to survive BRAK updates better.
- Are incoming messages matched to matters automatically, by court reference number or XJustiz structured data, and what happens to messages that don't match?
- Can staff prepare filings while only the lawyer signs and sends? Does the software support both the qualified electronic signature and the route for a lawyer sending personally?
- Do eEB requests appear as tasks, and can the lawyer return them from inside the system?
- How are deadlines from incoming court documents proposed, and who confirms them? Software should suggest deadlines, not finalize them without review.
- How does it handle several lawyers, substitutes during absences, and the firm's company mailbox?
Red flag: a vendor that can't show a live demo of an incoming court message turning into a calendared, assigned deadline. If that workflow isn't smooth in the demo, it won't be smooth on the Friday before a holiday.
Identity costs are small but real. Each lawyer needs a beA card or software certificate, and lawyers who sign with qualified signatures need a signature card and reader, usually with modest annual certificate fees. Budget per lawyer and put them on the onboarding checklist for new hires.
What RVG Billing Software Has to Calculate
RVG billing is a calculation engine, not a template. A typical civil matter means determining the value in dispute (Gegenstandswert), looking up the base fee from the statutory table, and applying fee items with their multipliers. Common examples are the out-of-court business fee (VV 2300), the procedural fee (VV 3100), the hearing fee (VV 3104) and the settlement fee (VV 1000). Expense flat rates and VAT come on top, along with credits where an out-of-court fee partly counts against a later court fee.
Good RVG software does all of this from matter data and records how each figure was reached. Test these points:
- Table updates: statutory fee tables change, most recently with an increase in 2025. Ask how quickly past updates shipped and whether open matters are calculated under the transitional rules that depend on the mandate date.
- Crediting rules: have the vendor calculate a matter that moves from out-of-court work into litigation, then check the credit against a manual calculation.
- Fee agreements: many commercial firms bill hourly or by fixed fee. The system must handle time-based billing alongside RVG, and flag when an agreed fee falls below the statutory minimum in court matters.
- Cost reimbursement: applications for cost assessment (Kostenfestsetzung) and legal-aid billing should come from the same data.
- Invoice formality: RVG invoices must meet the content requirements of Section 10 RVG, including fee items and values. Templates should enforce this.
E-invoicing adds another layer. German businesses must already be able to receive structured electronic invoices, and mandatory issuance for business-to-business invoices phases in over the following years, depending on turnover. Ask whether the vendor can produce XRechnung or ZUGFeRD output today, and how it handles invoices to corporate clients versus consumers, who fall outside the mandate.
For firms that mainly do German litigation and insurance-funded work, native RVG billing is non-negotiable. A purely advisory firm billing hourly to multinational clients can rely less on RVG depth, but it still needs the engine for the occasional court matter and for cost recovery.
Section 43e BRAO, Section 203 StGB and GDPR-Compliant Hosting
German lawyers may use cloud hosting, with conditions. Section 43e BRAO lets lawyers disclose client secrets to service providers to the extent the service requires. The lawyer must choose the provider carefully, and the contract must be at least in text form. The provider has to be bound to confidentiality, told of the criminal consequences of a breach, and limited to the information it needs. Subcontractors must be bound the same way. Section 203 StGB backs this up with criminal liability for unauthorized disclosure.
Two further points matter for cloud buyers:
- Services abroad: using a provider abroad is generally allowed only if the protection of secrets there is comparable to Germany's. EU and EEA hosting is usually treated as comparable. Hosting elsewhere needs a documented assessment.
- Matter-specific services: where a service is tied to a single mandate rather than general firm operations, check with your professional advisers whether client consent is needed.
GDPR sits on top. You need a data processing agreement under Article 28 GDPR, a list of subprocessors, technical and organizational measures, and a transfer assessment if any data or support access leaves the EEA. Many German firms also ask about non-EU laws that can compel providers to hand over data, such as the US CLOUD Act. That's a risk-assessment question, not an automatic disqualifier, but it explains why domestic vendors stress German data centers and German-owned operators.
Contract checklist for any hosted system
- Section 43e-compliant confidentiality clauses that extend to subprocessors.
- An Article 28 GDPR processing agreement with a current subprocessor list and a notice period for changes.
- Data center and support-access locations named in the contract, not just on the website.
- Encryption at rest and in transit, with clarity on who holds the keys.
- Recognized certifications such as ISO 27001 (including on the basis of BSI IT-Grundschutz) and a BSI C5 attestation where available.
- An exit clause: full export in usable formats within a defined period, followed by certified deletion.
International firms with German offices should expect this standard to go further than the global cloud policy. A platform approved in London or New York may still need a German contract addendum.
GoBD Record-Keeping in Practice
The GoBD govern any electronic system that produces tax-relevant records: invoices, fee ledgers, trust-money movements and the accounting entries behind them. Auditors look for complete records, entries that can't be changed without a trace, retention for the statutory period, and machine-readable access during an audit.
In practice, your Kanzleisoftware should:
- Lock posted invoices and entries, so corrections are made by reversal and new entry, never by overwriting.
- Keep a change log showing who changed what and when.
- Retain records for the required periods. Accounting vouchers now generally carry a shorter period than the ten years that still applies to books and annual financial statements, and matter files (Handakten) have a separate six-year professional retention duty under Section 50 BRAO. Confirm current periods with your tax adviser.
- Export data in formats auditors and tax advisers can use, which in Germany usually means the DATEV interchange format.
- Support a process documentation (Verfahrensdokumentation) describing how documents are captured, processed and archived. Vendors that supply templates save you real time.
Give the DATEV export a hard test. Most German tax advisers work in DATEV, so a clean booking export, with the right accounts, tax keys and client-trust separation, removes hours of monthly reconciliation. Ask for a sample export file and have your tax adviser review it before you sign.
Red flag: any system where a user with ordinary permissions can edit a sent invoice. That's a GoBD finding waiting to happen.
Domestic Vendors Versus International Platforms: Fit and Cost
The German market is led by long-established domestic vendors. RA-MICRO offers modular on-premises and hosted editions. DATEV Anwalt comes out of the DATEV cooperative ecosystem and is strongest where the firm's accounting already runs through DATEV. Advoware is popular with small and mid-sized firms, on-premises or hosted. Wolters Kluwer's AnNoText and Kleos, and newer cloud-native entrants such as Actaport, also appear on many shortlists.
International platforms like Clio, and enterprise stacks built on iManage or NetDocuments with Intapp or Aderant for finance, are strong on usability, document management and multi-country reporting. Most don't ship native RVG calculation or full beA workflows. Confirm the current status with each vendor, because roadmaps change.
| Option | Best fit | beA and RVG | Indicative cost (USD per user per month) |
|---|---|---|---|
| RA-MICRO | Small to mid-sized litigation-heavy firms | Native | 60–150, depending on modules and hosting |
| DATEV Anwalt | Firms already using DATEV accounting | Native | 50–130, plus DATEV membership and service fees |
| Advoware | Solo to mid-sized firms wanting on-premises or hosted | Native | 40–110 hosted; perpetual licences may also be offered |
| Cloud-native German entrants | New or modernizing small firms | Native, varies in depth | 40–100 |
| International practice platforms | German offices of cross-border firms | Usually via third-party add-ons or separate tools | 50–150, plus add-ons |
| Enterprise DMS and finance stacks | Large firms with 100+ lawyers | Through German connectors | Often 150–400 all-in, quoted per project |
These are typical 2026 market ranges. Real pricing is in euros, varies by contract, seat count and modules, and must be confirmed with vendors.
Cost drivers beyond the licence
- Data migration: moving matters, contacts, open items and documents from an older system often costs USD 3,000–25,000 for small and mid-sized firms, more where document volumes are large.
- Training: usually 1–3 days per role group, priced per day or bundled.
- Hosting and IT: on-premises installs need servers, backup and a local IT partner. Hosted installs fold that cost into the subscription.
- Add-ons: dictation, speech recognition, document assembly, e-invoicing and mobile access are often extra.
Hypothetical example: say a 12-lawyer litigation firm in Cologne has 20 users and chooses a hosted domestic system at around USD 90 per user per month. Licences come to about USD 21,600 a year. Add a one-off migration of USD 10,000–15,000, training of USD 4,000–6,000, and beA and signature hardware for the lawyers. First-year spend lands at roughly USD 36,000–44,000, and later years settle near the subscription cost plus add-ons.
Here's where we come down. For a firm whose revenue depends mostly on German courts, a domestic vendor is the better fit, because beA, RVG and DATEV are built in rather than bolted on. For a German office of an international firm doing mostly transactional work, a global platform plus a dedicated beA and RVG tool can be justified, but only if someone owns the integration and the deadline-control process.
Rollout Timelines and a Selection Sequence That Works
Most German migrations take longer than vendors suggest, mainly because of data cleanup and deadline-control validation. Plan around these typical ranges:
| Firm size | Selection | Implementation and migration | Parallel running |
|---|---|---|---|
| Solo to 5 users | 2–4 weeks | 2–6 weeks | 1–2 weeks |
| 6–30 users | 1–2 months | 2–4 months | 2–4 weeks |
| 30–100 users | 2–3 months | 4–8 months | 1–2 months |
| 100+ users or multi-country | 3–6 months | 6–12 months or more | Phased by office |
A practical selection sequence
- Write down your non-negotiables: beA depth, RVG coverage, DATEV export, hosting location and Section 43e contract terms.
- Shortlist three vendors that meet all of them, including at least one hosted option even if you plan to stay on-premises.
- Run scripted demos with your own scenarios: an incoming court message with a deadline, a litigation matter with fee crediting, a fee-agreement invoice, and a month-end DATEV export.
- Review the contracts with your data protection officer, and check hosting terms against the Section 43e list above.
- Test migration on a sample of 50–100 matters before signing the full order.
- Plan the cut-over outside peak deadline periods. Keep the old system read-only and run deadline control in parallel until the new calendar is verified.
Use this decision rule: if a vendor can't run your incoming-court-message and fee-crediting scenarios live, without slides, drop it. Of everything a German firm asks of case management software, beA deadlines and RVG accuracy are the two that cost real money when they fail. Book scripted demos with two domestic vendors and one international platform this quarter, and ask each for a sample DATEV export to send to your tax adviser.
Frequently asked questions
Can a German law firm legally use a US-based cloud practice management platform?
Generally yes, but it needs more care than an EU-hosted option. Section 43e BRAO requires that protection of secrets abroad be comparable to Germany's, and the GDPR requires a transfer assessment for any non-EEA access. Many firms choose the vendor's EU hosting region and document their risk assessment. Have your data protection officer and bar chamber guidance review the specific setup.
Do we need separate beA software if our Kanzleisoftware has beA integration?
Each lawyer still needs their own beA access credentials, such as a beA card or software certificate. With a full interface integration, daily sending, receiving and eEB handling can happen inside the practice software. With shallow integrations, staff may still use the BRAK web client for some tasks, so confirm which workflows happen where.
Is DATEV Anwalt only worth it if our tax adviser uses DATEV?
That's its strongest advantage, but not the only one. It also offers native RVG billing and beA support. If your tax adviser uses DATEV, the shared ecosystem removes most of the export and reconciliation work. If not, compare it on equal terms with RA-MICRO, Advoware and cloud-native alternatives.
Written by the Lexstack Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.