# reimbursements.recordPayment

Record an existing untouched outgoing bank payment to an explicitly confirmed active member as a reimbursement transfer awaiting receipt-backed claims. Never invents purchases or tax and never sends money.

`POST /api/v1/accounting/reimbursements.recordPayment`

Permissions: `accounting:read`, `accounting:write` · Roles: admin, finance · Idempotency key required

MCP tool: `accounting_reimbursements_record_payment`

## Fields

| Field | Type | Required | Notes |
| --- | --- | --- | --- |
| `transactionId` | string (ID) | Yes | The ID of a bank or card transaction, from transactions.list. |
| `expectedTransactionRevision` | integer | Yes | The bank transaction's current revision, from the last time you read it. at most 9007199254740991; greater than 0. |
| `expectedBankEntryId` | string (ID) |  | The ID of the related record. |
| `expectedBankEntryRevision` | integer |  | The related record's current revision, from the last time you read it. at most 9007199254740991; greater than 0. |
| `userId` | string | Yes | The ID of a person in your company. 1–200 characters. |
| `payeeConfirmed` | true | Yes |  |
| `reason` | string | Yes | A short note saying why, kept in the record's history. 10–1000 characters. |
| `idempotencyKey` | string | Yes | Any unique text you generate once per intended change, so a retried request only happens once. Send it as the Idempotency-Key header instead if you prefer; if you send both they must match. 8–200 characters. |

## Example request

```bash
curl https://app.getoatmilk.com/api/v1/accounting/reimbursements.recordPayment \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "expectedTransactionRevision": 3,
  "userId": "example",
  "payeeConfirmed": true,
  "reason": "Synthetic example from the docs"
}'
```

Reference page: https://app.getoatmilk.com/docs/api/reimbursements.recordPayment