Budgets and reserves

taxReserves.acknowledge

Reconcile a completed tax reserve whose invoice tax or receipt changed. Requires the exact fresh reviewedSnapshot, expectedRevision and an admin reason. Keeps the history and amount already moved. A remaining shortfall becomes a manual-only top-up suggestion; excess reserve remains blocked until an admin records its actual return. To record a return, supply returnedMinor, reference, transferredOn and both saved bank transaction IDs: a debit from the tax account and matching credit to the original receiving account. This checks actual same-currency bank evidence and never sends money or automatically returns funds.

POST/api/v1/accounting/taxReserves.acknowledge

Permissions

accounting:readaccounting:writeaccounting:admin

Who can call it

admin

Retries

Idempotency key required, with expectedRevision

MCP

accounting_tax_reserves_acknowledge

Fields

  • idstring (ID)Required

    The record's ID.

  • expectedRevisionintegerRequired

    The record's current revision, from the last time you read it. If someone changed the record since, the request is refused with a conflict so you can reload and check before trying again.

    at most 9007199254740991 · greater than 0

  • reviewedSnapshotstringRequired

    SHA-256 hash as 64 lowercase hex characters

  • idempotencyKeystringRequired

    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

  • reasonstringRequired

    A short note saying why, kept in the record's history.

    1–500 characters

  • returnedMinorstring

    An amount in cents (the currency's smallest unit), written as a whole-number string such as "1250" for $12.50.

    Matches ^[1-9]\d{0,14}$

  • debitTransactionIdstring (ID)

    The ID of the related record.

  • creditTransactionIdstring (ID)

    The ID of the related record.

  • referencestring

    1–300 characters

  • transferredOnstring (date)

    A date, as YYYY-MM-DD.

Example

curl https://app.getoatmilk.com/api/v1/accounting/taxReserves.acknowledge \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "expectedRevision": 3,
  "reviewedSnapshot": "9f2b5c1d7e3a4b6c8d0e2f4a6b8c0d2e4f6a8b0c2d4e6f8a0b2c4d6e8f0a2b4c",
  "reason": "Synthetic example from the docs"
}'
Response
{
  "data": { … }
}

Try it

Try it

Checks your input with this action’s real schema and answers like the API, with synthetic data. No key needed, and nothing changes.

POST/api/v1/accounting/taxReserves.acknowledge
curl https://app.getoatmilk.com/api/v1/accounting/taxReserves.acknowledge \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "expectedRevision": 3,
  "reviewedSnapshot": "9f2b5c1d7e3a4b6c8d0e2f4a6b8c0d2e4f6a8b0c2d4e6f8a0b2c4d6e8f0a2b4c",
  "reason": "Synthetic example from the docs"
}'

More in Budgets and reserves.