> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paywise.de/llms.txt
> Use this file to discover all available pages before exploring further.
# Single Mandate Statements Overview
> High-level guide to the Single Mandate Statements endpoints (Aktenabrechnungen)
An **Aktenabrechnung** (per-case statement) settles exactly one case. It is created by a case
event in our collection system and becomes available through the API once we have released it.
Use these endpoints to list and retrieve per-case settlements, to reconcile them in your
accounting system, and to download the corresponding PDF.
## Not the same as a Statement
A **statement** (Sammelabrechnung, `/v1/statements/`) settles every case of one clearing run at
once and carries a `mandate_details` sub-resource. An **Aktenabrechnung**
(`/v1/single-mandate-statements/`) settles a single case and carries that case directly in
`mandate`.
Both resources draw their `clearing_no` from the same number range, so the same clearing number
never appears in both. If you look a clearing number up in one resource and get a 404, try the
other.
| | [Statements](/api-docs/case-management-api/statements/overview) | Single Mandate Statements |
| -------------- | --------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Scope | All cases of one clearing run | Exactly one case |
| Case data | `mandate_details` sub-resource | `mandate` on the object itself |
| Files | PDF and Excel exports | One PDF |
| Webhook events | `statement.created` / `statement.updated` | `single_mandate_statement.created` / `single_mandate_statement.updated` |
## Types
| `statement_type` | Meaning |
| ----------------------------------- | ----------------------------------------------------------------- |
| `interim` | Zwischenabrechnung — interim settlement while the case continues |
| `final` | Endabrechnung — final settlement of the case |
| `expenses_invoice` | Auslagenrechnung — invoice for expenses we advanced |
| `transition_to_longtime_monitoring` | Übergabe Überwachungsverfahren — handover to long-term monitoring |
| `negative_closing` | Negativabschluss — the case is closed without success |
## Which way the money flows
`total_balance` is the authority: a **positive** value is a payout to you, a **negative** value is
an amount you owe us. A negative balance is itemised in `cost_burden`, a payout in `vat_entries`.
Do not infer the direction of the money from `statement_type` — an `interim` settlement can end up
negative.
`payout_method` tells you how the balance is settled: `transfer` (Überweisung) or `direct_debit`
(Lastschrift).
## References
`reference_number` is our case reference (Aktenzeichen). `your_reference` is your own customer
number **for the debtor**, as it was stored on the case — note that this differs from
`your_reference` on a claim, which is your reference for the claim itself.
Both corresponding filters match exactly (case-insensitive); they are not substring searches.
`reference_number` is a snapshot taken when the settlement was booked and is always present.
`mandate` may be `null` if the case is no longer linked — reconcile on `reference_number` when
you need a value that never disappears.
## VAT rates
`vat_rate` is a decimal fraction: `0.19` means 19%. This is the same convention as
`overview_vat_specific` on `/v1/statements/`.
The VAT breakdown of an Aktenabrechnung is called `vat_entries`, with one entry per VAT rate.
Each entry carries the debtor's payments for that rate and how they were allocated (main claim,
default interest, expenses, fee, success commission, and the VAT on each).
## Example
```json theme={null}
{
"href": "https://api.paywise.de/v1/single-mandate-statements/9f1c2d3e-4a5b-4c6d-8e9f-0a1b2c3d4e5f/",
"id": "9f1c2d3e-4a5b-4c6d-8e9f-0a1b2c3d4e5f",
"clearing_no": "A2026/000123",
"invoice_no": "R2026/000456",
"statement_type": "interim",
"booking_date": "2026-08-18",
"period_start": "2026-07-01",
"period_end": "2026-08-18",
"canceled": false,
"comment": "Zwischenabrechnung nach Teilzahlung",
"reference_number": "K26-757P3",
"your_reference": "W00150540",
"mandate": {
"href": "https://api.paywise.de/v1/mandates/5600672e-2bfa-488c-b23a-460c1dd1f833/",
"id": "5600672e-2bfa-488c-b23a-460c1dd1f833",
"reference_number": "K26-757P3"
},
"pre_tax_deductible": true,
"payout_method": "transfer",
"principal_claims_total": { "value": "200.00", "currency": "EUR" },
"open_principal_claim": { "value": "0.00", "currency": "EUR" },
"total_balance": { "value": "180.00", "currency": "EUR" },
"principal_claims": [
{ "voucher_no": "RE-1", "voucher_date": "2026-05-03", "amount": { "value": "123.45", "currency": "EUR" } },
{ "voucher_no": "RE-2", "voucher_date": "2026-05-04", "amount": { "value": "76.55", "currency": "EUR" } }
],
"vat_entries": [
{
"vat_rate": "0.19",
"total_payments": { "value": "200.00", "currency": "EUR" },
"allocation_to_main_claim": { "value": "180.00", "currency": "EUR" },
"allocation_to_fee": { "value": "16.81", "currency": "EUR" },
"allocation_to_fee_vat": { "value": "3.19", "currency": "EUR" },
"payout": { "value": "180.00", "currency": "EUR" }
}
],
"cost_burden": null,
"downloads": [
{
"id": "1d1eb5ba-2a3c-5f78-9c11-6b3f0d5a7e42",
"type": "full_pdf",
"filename": "aktenabrechnung_A2026-000123.pdf",
"mime_type": "application/pdf",
"file_size": 42317,
"download_url": "https://api.paywise.de/v1/single-mandate-statements/9f1c2d3e-4a5b-4c6d-8e9f-0a1b2c3d4e5f/download/full-pdf/"
}
],
"created": "2026-08-18T09:12:44.512300Z"
}
```
The `vat_entries` entry is abbreviated here; see
[Retrieve an Aktenabrechnung](/api-docs/case-management-api/single-mandate-statements/retrieve-an-aktenabrechnung)
for every field.
## Filtering
| Filter | Description |
| --------------------- | ---------------------------------------------------------------------- |
| `id` | The ID of the Aktenabrechnung |
| `reference_number` | Our case reference number (exact match) |
| `your_reference` | Your customer number of the debtor as stored on the case (exact match) |
| `clearing_no` | The clearing number (Abrechnungsnummer) |
| `invoice_no` | The invoice number (Rechnungsnummer) |
| `statement_type` | The type of settlement |
| `booking_date` | An exact booking date |
| `booking_date_after` | Booked on or after this date |
| `booking_date_before` | Booked on or before this date |
| `canceled` | Whether the statement was reversed (Storno) |
| `mandate` | The ID of the settled case |
```bash theme={null}
curl -H "Authorization: Bearer $PAYWISE_TOKEN" \
"https://api.paywise.de/v1/single-mandate-statements/?statement_type=final&booking_date_after=2026-08-01"
```
Results are paginated with `limit` and `offset` and are ordered newest first.
## Downloading the PDF
Each released Aktenabrechnung carries at most one file, described in `downloads[]`:
```
GET /v1/single-mandate-statements/{id}/download/full-pdf/
Authorization: Bearer
```
The response is the PDF itself, served through the API; there is no direct storage URL. The
`download_url` in `downloads[]` points at exactly this endpoint and needs the same Bearer token as
every other call.
`downloads[].id` is stable across requests and across deployments, so you can store it. `full_pdf`
is the only file type.
`downloads[]` is empty until the PDF has been transferred — the JSON arrives first, the document
follows. Treat an empty array as "not yet", not as an error.
## Reversals
A reversed settlement (Storno) is not deleted: `canceled` becomes `true` on the original, and the
reversal itself is booked as its own Aktenabrechnung. Both stay retrievable. Filter with
`?canceled=false` if you only want settlements that still stand.
## Staying up to date
Subscribe to
[`single_mandate_statement.created` and `single_mandate_statement.updated`](/api-docs/case-management-api/webhooks/event-types)
instead of polling. You receive `.created` when we release an Aktenabrechnung to you — not when it
is first booked internally — and `.updated` for later changes such as a reversal.