A debt collection process looks simple on a slide: remind, call, escalate, go to court. In software it is a long-running process with waiting times, promises, partial payments, and legal steps that differ by country. Modelling the debt collection process in BPMN 2.0 gives operations and IT one picture they can both read, and a model that an engine can run as it is drawn.

This article walks through such a model, element by element. It describes public procedures as an overview, not legal advice: check the current rules, or ask a lawyer, before you build a legal step into a process.

Why one collection process is never enough

Collection teams rarely run a single process. A consumer loan with a small balance, a business invoice, and a debt that is already in court follow different paths. The amicable stage has its own rhythm per portfolio, and the court stage depends on the country of the debtor.

Hard-coding these paths into application code makes every change a release. A process model keeps the paths visible, makes the differences explicit, and lets a team compare the process as designed with the process as run.

BPMN 2.0 for a debt collection process: events, tasks, gateways

BPMN (Business Process Model and Notation) is a specification of the Object Management Group (OMG). The current version, 2.0.1, is also the international standard ISO/IEC 19510:2013. A collection model needs only a small part of it:

ElementWhat it means in collections
Message start eventA new case arrives, for example from a lender's system
Service taskThe system does something: sends a reminder, calculates interest
User taskA person does something: calls the debtor, reviews a dispute
Timer intermediate eventWait a number of days, for example after a reminder
Exclusive gatewayExactly one path is taken: paid in full? promise to pay?
Event-based gatewayWait for whichever comes first: a payment or a deadline
Call activityRun a separate, reusable process, such as the court path for one country
Interrupting message boundary eventLeave the normal path when a message from outside ends it, such as notice of the debtor's insolvency

That is enough to describe most collection logic. Keep the rest of the specification for when you need it.

The amicable stage as a model

The amicable (pre-court) stage is where most of the waiting happens. A typical model for one portfolio looks like this:

  1. Message start event: the case is received with debtor, claim, and contract data.
  2. Service task: check the data and register the case.
  3. Service task: send the first reminder through the debtor's preferred channel.
  4. Event-based gateway: wait for a payment message or a timer of N days, whichever comes first.
  5. If the payment arrives, an exclusive gateway checks whether it covers the whole claim. If yes, the case closes. If not, it returns to the reminder loop with the new balance.
  6. If the timer fires first, a user task asks an agent to contact the debtor.
  7. An exclusive gateway records the outcome: paid, promise to pay, dispute, or no contact.

A promise to pay deserves its own path. It starts a timer for the promised date, and the same event-based gateway pattern decides whether the promise was kept. A broken promise moves the case to the next step instead of starting over.

The numbers in this model, such as the days between reminders, the channels, and the number of attempts, belong in configuration, not in the diagram. The diagram says "wait the reminder interval"; the value can differ by portfolio.

XML
<bpmn:intermediateCatchEvent id="WaitAfterReminder" name="Wait reminder interval">
  <bpmn:timerEventDefinition>
    <bpmn:timeDuration>${reminderInterval}</bpmn:timeDuration>
  </bpmn:timerEventDefinition>
</bpmn:intermediateCatchEvent>

The expression syntax for ${reminderInterval} depends on the engine you use. The element itself is standard BPMN 2.0.

From amicable to court: the decision gateway

At some point, the amicable stage ends without payment. The decision to go to court is a business decision, not a timer: it weighs the size of the claim, the cost of the procedure, the evidence available, and the chance of recovery.

Model it as an exclusive gateway after a user task or a business rule task. The outgoing paths are typically:

  • Go to court, with the country of the debtor as a variable.
  • Sell or return the case to the creditor.
  • Write off, with a reason.
  • Back to amicable, for example when new contact data arrives.

Keep the decision and its reason as data on the case. Reporting on why cases go to court, or why they do not, is one of the things a process model makes easy.

Court and enforcement paths by country

Each country's court procedure is a call activity: a separate process the main model calls with the case data. The main model does not need to know the steps inside; it only waits for the result. Two examples show why a separate sub-process per country makes sense.

Germany: the Mahnverfahren

The German court payment-order procedure (gerichtliches Mahnverfahren) is governed by §§ 688 ff. of the Code of Civil Procedure (ZPO). According to an IHK Köln overview:

  • The court issues a Mahnbescheid on a correct application without checking whether the claim exists.
  • The debtor can object (Widerspruch) within two weeks.
  • Without an objection, the creditor can apply for a Vollstreckungsbescheid; this has to happen within six months.
  • The debtor can file an Einspruch against the Vollstreckungsbescheid within two weeks of service. Otherwise it becomes enforceable.
  • Applications can be prepared online at online-mahnantrag.de (Justiz NRW). Lawyers and registered collection companies may not use the paper form.

In BPMN, this sub-process is a chain of event-based gateways: after each step, wait for the debtor's response or for the deadline. Each deadline is a timer event, and each response is a message event that leads to the contested court procedure instead.

Romania: ordonanța de plată and small claims

The Romanian Civil Procedure Code offers two fast procedures, according to an overview on e-juridic.manager.ro:

  • The ordonanța de plată (payment order) applies to certain, liquid and due monetary claims that arise from a contract or are established by a document (a statute, a regulation, or another document), and has no value limit. The creditor must first formally notify the debtor (somație) before going to court.
  • The cerere de valoare redusă (small claim) has a value limit and no mandatory prior step. The European e-Justice portal gives the limit as 10,000 lei in the Code and mentions a temporarily higher limit introduced in 2022; check the threshold that applies today.

The overview also notes that the current Code repealed the earlier fast-recovery rules, OG 5/2001 and OUG 119/2007.

For the model, this means the Romanian payment-order sub-process starts with a service task that sends the formal notice and a timer event for the response period, before any court step. The small-claims path has no such step. An exclusive gateway at the start of the Romanian sub-process chooses between them.

Enforcement and the exceptions

Enforcement after a title is yet another call activity per country. Across all paths, attach interrupting message boundary events for the messages from outside that end the normal flow: notice of the debtor's insolvency, a successful objection, or a settlement. Each leads to its own handling instead of letting the case wait for a timer that no longer makes sense.

Changing a process without a release

The main reason to put collections in BPMN is change. Portfolios change their reminder intervals, legal deadlines change, and new countries are added. With a process engine:

  • Configuration (intervals, channels, thresholds) changes without touching the model.
  • A new model version is deployed while running cases continue on the version they started with. New cases use the new version.
  • A new country is a new call activity, added to the court gateway without changing the amicable stage.
  • Tests run against the model: given a case and a sequence of events, the process must reach the expected end state.

The model is also documentation. A new team member, an auditor, or the creditor can read the diagram and see what happens to a case, without reading code.

How we can help

We build debt collection software with BPMN processes: case and debtor management, configurable collection workflows, reminders, payment plans, and the court and enforcement stages as separate, versioned processes.