---
title: "Reverse a posted manual journal entry"
method: POST
path: "/entries/{id}/reverse"
tags: ["Accounting"]
---

# Reverse a posted manual journal entry

`POST /entries/{id}/reverse`

## Request

- Base URL: `https://ledgerhq.pro/api/v1`
- URL: `https://ledgerhq.pro/api/v1/entries/{id}/reverse`
- Auth: one of:
  - HTTP bearer and API key in header `x-organization-id`
  - HTTP bearer and API key in header `x-organization-id`

Creates a new posted entry with flipped debits/credits; the original stays posted and the pair nets to zero. Bank-feed journals must use a reviewed automation-assurance reversal manifest. Use when a manual entry's original period is closed or the original must remain visible. Use void OR reverse for a manual posting, never both - combining them over-corrects by the full entry amount. The reversal date must fall in an open period.

## Path parameters

- `id` string, uuid, required

## Request body

- object
  - `reason` string, required: Reason for the reversal
  - `date` string, date: Reversal entry date (YYYY-MM-DD). Defaults to today.

## Response `200`

Reversal entry created

- object
  - `originalEntryId` string
  - `reversalEntry` object

## Other responses

- `409`: The entry cannot be reversed generically: it is a bank-feed journal that must use a reviewed reversal manifest (feed_entry_requires_reversal_manifest), it already has a posted reversal (journal_entry_already_corrected), or a prior reversal used different inputs under the same idempotency key (idempotency_conflict).
- `default`: Error response

---

[API](https://skmtc.dev/ledgerhq-pro/apis/ledgerhq-bookkeeping-api.md) · [All operations](https://skmtc.dev/ledgerhq-pro/apis/ledgerhq-bookkeeping-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ledgerhq-pro/apis/ledgerhq-bookkeeping-api/revisions/9a8269f0a586?raw)