A trainee returns an electronic acknowledgment of service using his lawyer's beA card. The appeal deadline runs from the date entered, the appeal arrives late, and there is no reinstatement: the lawyer owns his staff's clicks (Federal Social Court, B 3 KR 2/21 R). The case is a few years old, but it describes precisely what beA, the mandatory electronic mailbox for German lawyers, means for small firms: a compulsory channel that costs hours every day and turns organizational mistakes directly into liability.
Since 2022 lawyers must file with courts electronically (§ 130d ZPO), and since 2018 there has been a passive duty to take note of the inbox (§ 31a Abs. 6 BRAO). No statute fixes a checking frequency; the practice recommendation is every working day. Bavaria's justice system alone now receives around 250,000 electronic messages per week. The mailbox is daily life. The only question is how much of that daily life your team handles by hand.
The case law has cleared away the excuses
Whoever cannot meet a deadline electronically may file on paper instead, but the Federal Court of Justice has systematically raised the bar over the last two years. A PIN locked after failed entries and a missed software update are operator errors, not a technical outage (XII ZB 88/23). Merely asserting a persistent beA failure is not enough; the court demands a coherent, self-contained account of what happened when and what was attempted (VI ZB 19/24). And in late 2025 even a genuine router failure was rejected because the account did not rule out operator error (VIII ZB 17/25). The reliefs: an outage logged by the bar association substitutes for individual proof, and for court-side failures no fax fallback is needed at all.
Then there is the acknowledgment trap. For when a deadline starts, what counts is the date the lawyer enters in the electronic acknowledgment of service, not when the message arrived and not when the acknowledgment is returned (BGH, VII ZB 22/23). Whoever returns it conspicuously late carries a secondary burden of explanation, and courts now order production of the beA message journal (OLG Celle, 20 U 8/24). Sitting on service is not a tactic anymore; it is an evidentiary risk.
And after sending comes checking: the transmission protocol alone is insufficient, someone must verify the court's automated confirmation of receipt (BGH, VIII ZB 9/20). An automation that only logs dispatch is therefore not a relief but a liability trap with a nicer interface.
What can be delegated and automated
beA's permission system is built for exactly this. With their own staff cards and software certificates, non-lawyers may retrieve, read, sort, export and file messages; practice software polls the inbox automatically through the official interface. On that foundation, a great deal can be automated cleanly:
- Triage: sorting incoming messages by file, court and urgency, exporting attachments together with the verification protocols and filing them. beA is not an archive; messages are deleted after expiry periods, so securing everything into your own system is mandatory anyway.
- Deadline extraction as proposals: pulling deadline candidates out of messages and preparing them for the deadline calendar. Responsibility for deadline control stays with the lawyer, but no human needs to retype dates. A person confirms every entry.
- Dispatch control: automatically reconciling that every outgoing filing has the court's confirmation of receipt, and escalating when it does not. Exactly the check the Federal Court of Justice demands, minus the paper chase.
- Drafts: preparing routine correspondence as a draft in the firm's tone, attached to the message, for human sign-off.
What stays personal
Two things do not belong in any automation, and a serious provider tells you so unprompted. First, sending form-bound pleadings without a qualified electronic signature: there, signer and sender must be identical, which makes it personal lawyer's work. Second, the acknowledgment of service itself: it embodies the lawyer's decision to accept service and is a legal act, not a workflow step. Staff cannot validly submit it, sharing cards and PINs is prohibited, and the trainee case above shows the damage lands on the lawyer regardless.
The map is clear: everything before and after the lawyer's decision, the sorting, filing, extracting, checking and pre-drafting, can be carried by a system set up properly inside the permission concept. The decision itself, signature and acknowledgment, stays with the professional, not out of caution but because professional law says so. How we build that layer, with draft plus sign-off as the default, is on our page for law firms.
As of 10 July 2026, not legal advice. Cited decisions: Federal Social Court B 3 KR 2/21 R; Federal Court of Justice XII ZB 88/23, VII ZB 22/23, VI ZB 19/24, VIII ZB 17/25, VIII ZB 9/20, V ZR 134/22; OLG Celle 20 U 8/24.