---
title: "Converge an outstanding check (Lane B)"
method: POST
path: "/vendors/outstanding-checks/{id}/converge"
tags: ["Vendors"]
---

# Converge an outstanding check (Lane B)

`POST /vendors/outstanding-checks/{id}/converge`

## Request

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

Manual convergence for a human-selected outstanding check (vendors/1099 plan, Phase 3, Section 8.3). Claims the unposted withdrawal feed row against the check's journal entry with the widened matcher, excludes the originally created register row, assigns the surviving feed row the entry's counterpart account, and marks the vendor_check cleared with cleared_via human_selected — atomically, in one transaction. The check must still be recorded, on the withdrawal's bank account, and within $1 of the withdrawal amount. Requires the post:entries role and the bank_transactions:read_write scope.

## Path parameters

- `id` string, uuid, required

## Request body

- object
  - `bankTransactionId` string, uuid, required: The unposted withdrawal feed row

## Response `200`

Converged: feed row claimed, original row excluded, check cleared

## Other responses

- `400`: Invalid check id or request body
- `409`: The check changed while converging
- `422`: Check, withdrawal, or entry no longer convergeable
- `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)