---
title: "Api Delete Bank Statement"
method: DELETE
path: "/api/bank_statements/{statement_id}"
tags: ["Bank - Admin"]
---

# Api Delete Bank Statement

`DELETE /api/bank_statements/{statement_id}`

Delete a statement and its movements (child-first).

This is what makes the file-hash idempotency safe: without a way to remove a
statement, a file imported by mistake — or under the wrong account — could never be
re-imported.

The gate is conditional rather than a blanket `admin` dependency. A statement with
no invoice links is fully recoverable by re-importing the file, so anyone who may
import may also delete one — the previous admin-only rule left ordinary users stuck
with their own mistake. A statement WITH links is bulk-destructive (deleting it
frees invoices that were matched), so it needs a company admin who passed `force`
after being shown the affected invoices.

## Path parameters

- `statement_id` integer, required

## Query parameters

- `force` boolean

## Headers

- `x-api-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/4b44eb76b3ee/schema)