AVAILABLE

Reconciliation

Reconciliation Match

Match exact amount and currency plus optional date and counterparty within a configured tolerance. It never posts a reconciliation.

CONTRACT

Predictable for agents. Legible for reviewers.

REST
POST /v1/reconciliations/match
MCP tool
match_reconciliation
Inputs
One to 500 source records, one to 500 target records, and an optional date tolerance.
Returns
CLEAR or REVIEW_REQUIRED with explainable one-to-one candidate matches.
Latency
Synchronous
Usage unit
Control check

AGENT-READABLE EXCEPTIONS

RECONCILIATION_NO_MATCHRECONCILIATION_AMBIGUOUS_MATCH

EXAMPLE REQUEST

POST /v1/reconciliations/match
Authorization: Bearer apc_...
Content-Type: application/json

{
  "source_records": [
    {
      "record_reference": "A",
      "amount": "25.00",
      "posted_on": "2026-08-01",
      "counterparty": "Acme"
    }
  ],
  "target_records": [
    {
      "record_reference": "B",
      "amount": "25.00",
      "posted_on": "2026-08-02",
      "counterparty": "Acme"
    }
  ]
}

REPRESENTATIVE RESPONSE

{
  "product": "Reconciliation Match",
  "status": "COMPLETED",
  "decision": "CLEAR",
  "exceptions": [],
  "evidence": {
    "matches": [
      {
        "source_record_reference": "A",
        "target_record_reference": "B",
        "basis": "exact amount, currency, date, and counterparty"
      }
    ],
    "matched_count": 1
  },
  "next_action": "Post only through the customer's authorized reconciliation process."
}
Structured outputStatus, decision, exceptions, evidence, confidence, and next action where relevant.
Tenant-scopedOnly the caller's organization records are searched or returned.
Read-onlyNo accounting record, vendor bank account, or payment is changed.

Use Reconciliation Match through RapidAPI.

Choose a capped marketplace plan, copy the generated request, and route the structured result through your own authorized workflow.