Finance
Payment Orders
DEPLAW fully automates the entire court payment order procedure – from EDA generation through mass filing to the automatic processing of every follow-up step, with no human interaction.
The court payment order procedure is one of the most standardized processes in German civil law — which makes it especially well suited to full automation. DEPLAW maps the complete process: from the automatically generated payment order application, through mass filing with the responsible payment order court, to the automatic processing of every response from the court.
An Application Built From Real Case Data
A payment order application for a damages claim of 5,100 euros, for example, is filled out automatically with all the relevant details: debtor and party data, the default date, and the interest rate — for example, 5 percentage points above the base rate — all come directly from the case file and the claims table. The result is a structured, EDA-compliant application file, ready for filing with the responsible payment order court.
Court Responses Flow Back Automatically
Every response from the payment order court — service confirmation, issuance of the payment order, objection, or failed service — also comes back as an EDA file, is read automatically, and is stored in the case history. This automatically triggers the next step in the workflow, with no manual intervention at all.
01
EDA Generation
The payment order application is filled out fully automatically — claim category, amount, default dates, and party data come directly from the case file and the claims table, with no manual entry.
Case file · claims table · parties
02
Mass Filing
Thousands of applications run through the same workflow simultaneously — sorted by the responsible payment order court and bundled into a single EDA file for filing.
Sorted by payment order court
03
Workflow Integration
Fully integrated into DEPLAW workflows: from the initial application to the enforcement order, the entire procedure runs through a single continuous pipeline.
Application to enforcement order
04
Every Follow-Up Step, Fully Automatic
Service confirmation, issuance of the payment order, objection, and failed service all arrive as EDA files, are read automatically, stored in the case history, and trigger the next workflow step.
Service · objection · failed service
Example · Case INK-0003
One payment order procedure, fully automated from application to enforcement order.
From the automated application to a possible enforcement, the case runs through the same workflow — every step is triggered or confirmed by an EDA file from the payment order court, with no human intervention at all.
Thousands of Applications at Once
One EDA file. Thousands of payment order applications.
Every application runs through the same automated workflow — sorted by the responsible payment order court and bundled into a single EDA file for mass filing.
Related Features
Pairs well with Payment Orders.
Finance
Bookkeeping & Client Funds
Incoming payments, account posting, and client funds disbursement run in a single DATEV-compliant bookkeeping process – including Konfipay import and cross-case controlling.
Finance
Transfers
Payment processing without a system break: create it in the case file, have it approved automatically, and execute it via Konfipay or CSV export.
Finance
Payment Interfaces
Clients and debtors pay by credit card, PayPal, Apple Pay, or SEPA — the payment lands automatically in the case file and triggers the next workflow step.