Source: https://docs.debitura.com/clients/concepts/client-divisions

# Client Divisions

Divisions allow you to segment your debt collection cases across different organizational units, brands, or legal entities.

**Business context:** See [Using Divisions for Multi-Brand Management](https://support.debitura.com/en/articles/13885732-clients-how-to-use-divisions-business-units) for setup instructions and use cases.

<a id="when-to-use-divisions"></a>

## When to Use Divisions

Divisions are the right choice when **one organization operates multiple brands or legal entities**:

| Scenario | Solution |
| --- | --- |
| Holding company with subsidiaries (Acme UK, Acme DE, Acme FR) | One client + divisions |
| Multi-brand retailer (Brand A, Brand B, Brand C) | One client + divisions |
| Company with regional offices needing separate tracking | One client + divisions |
| Completely unrelated businesses | Separate client accounts |

For Referral Partners

If your platform supports users who manage multiple brands under one organization, use divisions to separate their cases. Create **one client** per organization with **one `externalTenantId`**, then assign cases to the appropriate division.

Debitura's user system is not multi-tenant—one user cannot belong to multiple unrelated client accounts. See [Client Lifecycle](https://docs.debitura.com/referral-partners/integration-guides/client-onboarding.md#client-lifecycle) for details.

<a id="overview"></a>

## Overview

Divisions are optional organizational containers within your Debitura account. When enabled, you can:

-   Assign cases to specific divisions during creation
-   Filter case lists and analytics by division
-   Maintain separate branding or reference schemes per business unit

<a id="api-usage"></a>

## API Usage

<a id="managing-divisions-via-api"></a>

### Managing Divisions via API

The Customer API provides full CRUD management of divisions. You can create, list, update, delete, and archive divisions programmatically.

| Operation | Endpoint | Description |
| --- | --- | --- |
| Create | `POST /divisions` | Create a new division |
| List | `GET /divisions` | List divisions (paginated) |
| Get | `GET /divisions/{id}` | Get a single division |
| Update | `PUT /divisions/{id}` | Update all fields |
| Delete | `DELETE /divisions/{id}` | Delete (blocked if cases exist) |
| Archive | `POST /divisions/{id}/archive` | Archive (irreversible) |

> **Note:** The archive action uses a slash sub-route (`/divisions/{id}/archive`). An older colon form (`/divisions/{id}:archive`) still works only if you percent-encode the colon as `%3A` — a literal `:` returns `404`. Use the slash form; it is canonical.

```http
POST /divisions
Content-Type: application/json
XApiKey: YOUR_API_KEY

{
  "companyName": "Acme Nordic",
  "city": "Copenhagen",
  "countryCode": "DK",
  "registrationNumber": "12345678",
  "officeEmail": "nordic@acme.com"
}
```

Country codes use ISO 3166-1 alpha-2 format (e.g. `"US"`, `"DE"`, `"DK"`).

See the [Divisions API Reference](https://docs.debitura.com/api/customer-api/divisions.md) for full endpoint documentation.

<a id="creating-a-case-with-a-division"></a>

### Creating a Case with a Division

Include the `creditorDivisionId` field when creating a case:

```http
POST /cases
Content-Type: application/json
XApiKey: YOUR_API_KEY

{
  "creditorDivisionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "currencyCode": "EUR",
  "amountToRecover": 5000.00,
  ...
}
```

See [Create a Case](https://docs.debitura.com/clients/integration-guides/create-a-case.md) to assign a division when submitting cases.