Reverse a journal entry
well_create_journal_entry_reversalReverse ONE posted journal entry: Well writes a new entry dated today with the same lines, debit and credit swapped, so the two cancel out. The posted entry stays as it is: a posted entry is never deleted.
Call it when the person asks to delete, cancel or undo a posted (validated or locked) entry and chose to reverse it, or asks to reverse it. To delete a posted entry, first say it is posted and is not deleted, offer the reversal dated today, and call this tool only on the person's yes. Pass the journal_entry_id.
Only an owner or an admin of the workspace reverses an entry. Refused, with nothing written: a draft entry (it is not posted, so there is nothing to reverse), an entry that already reverses another, an entry a connected accounting tool synced in (reverse it in that tool), and a reversal whose period (today's) is locked. A second call on the same entry returns the reversal the first one wrote.
Returns { success: true, reversal }, the new entry with its number and date. Name both numbers in the reply ("BQ-0211 is reversed by OD-0031 of 15 Oct"). { success: false, error } means nothing was written: say why from error.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. | |
| journal_entry_id | Yes | The journal_entry_id of the posted entry to reverse. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| error | No | ||
| success | Yes | ||
| reversal | No | ||
| reply_lines | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| near_candidates | No | ||
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| near_candidates_truncated | No |