---
title: "Void Statement"
method: POST
path: "/api/licensing/statements/{payout_id}/void"
tags: ["Licensing"]
---

# Void Statement

`POST /api/licensing/statements/{payout_id}/void`

## Request

- Base URL: `https://app.atlasipholdingsllc.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.atlasipholdingsllc.com/api/licensing/statements/{payout_id}/void`
- Auth: none declared

Void an issued statement and RELEASE the receipts/expenses it claimed.

Correction mechanic, not a deletion: the payout row stays, marked `void` with a reason and an
actor, and the ledger rows it consumed get `payout_id = null` so a corrected statement can
pick them up. Sec 5.5 requires an auditable ledger, so nothing is erased.

A settled statement cannot be voided. Once `record_settlement` has recorded a disbursement
that happened in the real world, voiding would put Atlas's books at odds with a bank
movement it cannot reverse — that is a correcting entry an operator must make deliberately,
not a status flip.

## Path parameters

- `payout_id` string, required

## Request body

- object

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/atlasipholdingsllc/apis/atlas-data-exchange-api.md) · [All operations](https://skmtc.dev/atlasipholdingsllc/apis/atlas-data-exchange-api/llms.txt) · [OpenAPI document](https://skmtc.dev/atlasipholdingsllc/apis/atlas-data-exchange-api/revisions/153f570efc30?raw)