Match to a payment
rec_matchTie a statement row to the payments or refunds recorded here that it is. They must add up to the row exactly. The row then posts nothing itself: the payment already did. A deposit on the statement is often a payment already recorded against an invoice. Read rec_candidates: per row, what fits by amount, date and name. Show the person, then match with a reason ("the Northwind ACH is their payment NW-ACH-2210"). One row can be several payments (a deposit of three checks); the items must add up to the row exactly, never "close enough". A row already booked as income or spending cannot be matched: that would count the money twice; say what it is booked as and let the person decide. Never record a payment just to have something to match. Effects: statement row matched; it posts nothing itself; the payments it is are now on the statement.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"transaction_id": "<transaction_id>",
"items": "<items>",
"reason": "<reason>"
},
"name": "rec_match"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | The payments or refunds it is; they add up to the row exactly. | |
| reason | Yes | Why they are the same money. | |
| transaction_id | Yes | The statement row. An existing purch_transaction id. |