Source: https://docs.debitura.com/collection-partners/integration-guides/update-claim-amount

# Update Claim Amount

Adjust the principal and fees on an active case to reflect the current state of the debt.

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

## When to Use This

The claim amount changes when:

-   Additional evidence reveals the debt is higher or lower than originally stated
-   Partial payments have already been made and the creditor wants to reflect the reduced principal
-   Legal costs or enforcement fees need to be added to the fees
-   Errors in the original claim amount need to be corrected

Use `PUT /cases/{id}/fees` with a `grossAmount` field to update the principal, fees, or both in a single call.

<a id="what-changes"></a>

## What Changes

When you update the claim amount:

1.  **Principal and fees are updated** — all values you supply replace the current values
2.  **Success fee is re-evaluated** — if you changed the principal and a collection partner is assigned, the pre-legal success fee (your commission percentage applied to the new amount) is re-evaluated. If the new principal crosses a fee bracket, the endpoint does **not** apply the change silently — it returns `409` asking you to confirm (see [Price-Change Confirmation](https://docs.debitura.com/collection-partners/integration-guides/update-claim-amount.md#price-change-confirmation) below). When the fee does not move (or moves by ≤0.1 percentage points) the new value is applied directly and returned as `recalculatedSuccessFee`
3.  **Remainder is recalculated** — the outstanding balance (`grossAmount + interestFees + collectionFees + reminderFees − payments`) is updated automatically
4.  **Audit event is written** — a timeline entry recording the old and new values is created and is visible to the creditor

<a id="price-change-confirmation"></a>

## Price-Change Confirmation

When a principal edit would move the success-fee percentage by **more than 0.1 percentage points**, the edit is **not applied**. The endpoint returns `409 Conflict` with a confirmation body so you can review the change before committing to it:

```json
{
  "caseId": "a1b2c3d4-...",
  "confirmationRequired": true,
  "currentSuccessFee": 8.00,
  "proposedSuccessFee": 9.50,
  "isIntentionalRate": false,
  "message": "...",
  "warning": null
}
```

Resubmit the **same** request with one resolution flag to apply it:

| Flag | Effect | When allowed |
| --- | --- | --- |
| `confirmPriceChange: true` | Re-prices to the new standard (bracket) rate and applies the edit | Only on a **standard, tier-based** rate (`isIntentionalRate: false`) |
| `keepIntentionalRate: true` | Applies the amount edit but **keeps** the existing rate | Effective on a **special agreement** (`isIntentionalRate: true`); ignored on a standard-rate case |

<a id="special-agreements-are-preserve-only"></a>

### Special Agreements Are Preserve-Only

If the case carries a deliberately-set rate — an **accepted quote** or a **manual override** (`isIntentionalRate: true`) — the rate is **preserve-only on this API**. You can apply the amount edit and keep the rate with `keepIntentionalRate: true`, but you can never re-price it. Sending `confirmPriceChange: true` on such a case is **rejected with `400`** directing you to `keepIntentionalRate: true` — nothing is applied.

Business context

The special rate was negotiated for this case and cannot be overridden from a partner integration — only a Debitura administrator can change it to the standard rate. See [Success Fees](https://support.debitura.com/en/articles/13429835-success-fees-how-pricing-is-calculated-claim-size-region-age) for how pricing is determined.

<a id="status-gate"></a>

## Status Gate

| Case Status | Principal (`grossAmount`) | Fees only |
| --- | --- | --- |
| Active | Allowed | Allowed |
| PendingVerification | Allowed | Allowed |
| Paused | Allowed | Allowed |
| NeedsAdditionalDetails | Allowed | Allowed |
| **Closed** | **Rejected (400)** | **Rejected (400)** |
| **Merged** | **Rejected (400)** | **Rejected (400)** |

Asymmetry with file upload

File uploads are allowed on Closed cases. Principal and fee edits are not — they are rejected on both Closed and Merged cases. This matches the partner portal behavior.

<a id="backward-compatibility"></a>

## Backward Compatibility

The `grossAmount` field is optional. Omitting it leaves the principal unchanged — the endpoint behaves exactly as before (fees-only update). Existing integrations that call `PUT /cases/{id}/fees` without `grossAmount` are unaffected.

<a id="decrease-is-allowed"></a>

## Decrease Is Allowed

Both increases and decreases to the principal are accepted down to a minimum of `0.00`; negative values are rejected. The UI shows an informational warning when payments exist — the API does not enforce this either.

Zero (`0.00`) is accepted as a valid principal.

<a id="request-example"></a>

## Request Example

```http
PUT /cases/{id}/fees
Content-Type: application/json

{
  "grossAmount": 850.00,
  "interestFees": 35.00,
  "reminderFees": 0.00,
  "collectionFees": 120.00
}
```

<a id="response-example"></a>

## Response Example

```json
{
  "caseId": "a1b2c3d4-...",
  "grossAmount": 850.00,
  "interestFees": 35.00,
  "reminderFees": 0.00,
  "collectionFees": 120.00,
  "totalAddedFees": 155.00,
  "recalculatedSuccessFee": 170.00,
  "remainder": 1005.00
}
```

`recalculatedSuccessFee` is null when the principal was not changed, or when no collection partner is assigned.

<a id="fees-only-update-backward-compatible"></a>

## Fees-Only Update (Backward-Compatible)

To update fees without touching the principal, omit `grossAmount`:

```http
PUT /cases/{id}/fees
Content-Type: application/json

{
  "interestFees": 35.00,
  "reminderFees": 0.00,
  "collectionFees": 120.00
}
```

For full endpoint details, see [Update Case Fees](https://docs.debitura.com/api/collection-partner-api/cases.md#update-case-fees-and-or-principal).