Matching

matching.confirm

Confirm a proposed exact-amount receipt match after finance review. Requires decision, receipt and transaction revisions, proposed target revision when attaching to an existing bank entry, reason and idempotency key. Canonical provider amounts and original evidence are preserved.

POST/api/v1/accounting/matching.confirm

Permissions

accounting:readaccounting:write

Who can call it

admin, finance

Retries

Idempotency key required, with expectedRevision

MCP

accounting_confirm_matching

Fields

  • decisionIdstring (ID)Required

    The ID of the related record.

  • 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

  • entryIdstring (ID)Required

    The ID of an accounting entry, from entries.list or attention.mine.

  • entryRevisionintegerRequired

    The entry's current revision, from the last time you read it.

    at most 9007199254740991 · greater than 0

  • transactionIdstring (ID)Required

    The ID of a bank or card transaction, from transactions.list.

  • transactionRevisionintegerRequired

    The related record's current revision, from the last time you read it.

    at most 9007199254740991 · greater than 0

  • targetEntryIdstring (ID)

    The ID of the related record.

  • targetRevisioninteger

    The related record's current revision, from the last time you read it.

    at most 9007199254740991 · greater than 0

  • bankAmountMinorstring

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

    Whole number written as a string

  • exchangeRatestring

    Matches ^(?:0|[1-9]\d{0,8})(?:\.\d{1,18})?$

  • exchangeRateDatestring

    A date, as YYYY-MM-DD.

    Date as YYYY-MM-DD

  • exchangeRateSourcestring

    3–1000 characters

  • reasonstringRequired

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

    10–1000 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

Example

curl https://app.getoatmilk.com/api/v1/accounting/matching.confirm \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "decisionId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "expectedRevision": 3,
  "entryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "entryRevision": 3,
  "transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "transactionRevision": 3,
  "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/matching.confirm
curl https://app.getoatmilk.com/api/v1/accounting/matching.confirm \
  -H "Authorization: Bearer $OATMILK_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "decisionId": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
  "expectedRevision": 3,
  "entryId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "entryRevision": 3,
  "transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
  "transactionRevision": 3,
  "reason": "Synthetic example from the docs"
}'

More in Matching.