reimbursements.matchPayment
Match a funded Wise reimbursement to its imported transfer using Wise's exact transfer reference and source amount. The bank entry becomes a transfer.
/api/v1/accounting/reimbursements.matchPaymentPermissions
Who can call it
Retries
MCP
accounting_reimbursements_match_paymentFields
paymentIdstring (ID)RequiredThe ID of the related record.
transactionIdstring (ID)RequiredThe ID of a bank or card transaction, from transactions.list.
expectedRevisionintegerRequiredThe 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
expectedBankEntryIdstring (ID)The ID of the related record.
expectedBankEntryRevisionintegerThe related record's current revision, from the last time you read it.
at most 9007199254740991 · greater than 0
idempotencyKeystringRequiredAny 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/reimbursements.matchPayment \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"paymentId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
"transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
"expectedRevision": 3
}'{
"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.
curl https://app.getoatmilk.com/api/v1/accounting/reimbursements.matchPayment \
-H "Authorization: Bearer $OATMILK_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"paymentId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
"transactionId": "7f0f6c1e-1c1f-4b5e-9c8d-2f5e8e3c1a10",
"expectedRevision": 3
}'More in Transactions.