Finance
Claim tables
Default interest is calculated to the exact day for each item, installment payment plans are created in a few clicks — and every case file can maintain any number of claim tables, seamlessly linked to templates and dunning proceedings.
app.dep.law| Position | Gesamt | Gezahlt | Offen | Status |
| Schadensersatz | 38.000 | 38.000 | 0 | Bezahlt |
| Verzugszinsen (5 % p.a.) | 4.820 | 0 | 4.820 | Offen |
| RVG-Vergütung | 5.500 | 5.500 | 0 | Bezahlt |
| Gesamt | 48.320 | 43.500 | 4.820 |
In many debt collection and damage claim cases, claim management is the data source almost everything else is derived from — interest calculation, payment plan, dunning application, invoice. DEPLAW therefore models the claim table not as a static list, but as a living data structure that stays current automatically with every payment and every day of accrued interest.
An example: a major damage claim with three items
In the Müller vs. an insurance company case, for instance, the claim totals €48,320 across three items: damages, default interest, and statutory fee compensation. The damages and the legal fee compensation are already settled, leaving only the interest item of around €4,820 open. It is exactly this breakdown by item, rather than by total sum, that makes the table usable for templates and dunning order export — every partial claim remains individually traceable.
Interest and installments with no manual calculation
DEPLAW calculates the default interest on an outstanding principal claim of, say, €12,400, to the exact day from the date of default — at a rate of 5 percentage points under Section 288 BGB and a term of around 940 days, this automatically produces a concrete interest amount, with no manual formula required. If a claim can only be settled in installments, DEPLAW creates a structured plan spanning several monthly installments, including repayment order, which updates itself with every incoming partial payment.
Multiple tables for one matter
For claims involving multiple injured parties or other complex matters, a single claim list quickly becomes unwieldy. DEPLAW therefore allows several claim tables to be maintained in parallel within one case file — for example one for the primary damage, one for consequential damages such as loss of earnings, and one for court costs. Each table can be exported independently or referenced in a template.
Figures flow directly into documents and dunning proceedings
Through a placeholder system, total amount, amount paid, outstanding balance, interest amount, and date of default are available directly in templates and generated documents. Statutory fee compensation is also calculated automatically from the table’s amount in dispute or amount recovered. This removes a typical source of error in traditional case management: manually transferring amounts from bookkeeping into the document.
01
Default interest to the exact day
For every claim item, default interest is calculated individually from the date of default, interest rate, and outstanding amount — under Section 288 BGB, Section 247 BGB, or a freely configured rate. No manual interest formula, no calculation errors.
§ 288 BGB · § 247 BGB · freely configurable
02
Installment payment plans
An installment payment plan, including repayment order, can be created in a few clicks and sent directly to the debtor. With every partial payment, the plan updates automatically, and each payment is allocated to the correct item.
Repayment order · automatic updates
03
Multiple tables per case file
For large claims or complex matters, the claim can be split into any number of tables — for example separated by type of damage, procedural stage, or party involved, instead of one unwieldy combined list.
Any number of tables · separated by damage type
04
Directly usable in templates and dunning proceedings
Total amount, amount paid, outstanding balance, and interest are available as placeholders in templates and generated documents. The same table is dunning-order compatible for enforcement with no extra effort.
Placeholders · dunning-order compatible
Example · Case INK-2024-1847
One claim, three items, one automatically current status.
Damages and statutory fee compensation are already settled, while the default interest item remains open — each item is tracked and calculated individually, and made available for templates and dunning order export.
Every case file with its own claim table
Many case files, many tables — each calculated live.
Default interest, installment status, and outstanding balance run separately for every case file and are automatically recalculated with every partial payment — regardless of how many claim tables are active at the same time.
Related Features
Pairs well with Claim tables.
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 Orders
From the automatically generated payment order application to the enforcement order, the entire court payment order procedure runs without manual intervention.