mcpField
P
Payment Reconciliation & Matching

Payment Reconciliation & Matching

Remote
saifs.aiOther4Updated today

About Payment Reconciliation & Matching

An MCP server for matching receipts, bank transactions, and GST 2B entries against invoices and ledger records. It proposes matches with confidence and reasons, flags deductions and exceptions, and leaves low-confidence cases for human review without automatically posting them.

Key features

  1. 01One-to-many and many-to-one matching
  2. 02Bank-to-ledger reconciliation
  3. 03GST 2B matching
  4. 04Deduction and exception flags
  5. 05Match explanations and reports
  6. 06Rules suggested from confirmed matches

Use cases

  1. 01Match incoming receipts to open invoices
  2. 02Reconcile a bank statement against ledger entries
  3. 03Compare GSTR-2B with a purchase register
  4. 04Review uncertain matches and outstanding exceptions

MCP support

Exposes reconciliation and matching tools to MCP clients over Streamable HTTP. OAuth 2.1 is used for client sign-in.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://payment-reconciliation-mcp-microsoft.saifs.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Payment Reconciliation & Matching

Match receipts, bank lines and GST 2B rows to open invoices and the ledger. Proposes one-to-many and many-to-one matches with confidence and reasons, flags deductions (TDS, bank charges, part payments), and returns an exceptions queue plus updated matching rules. Low-confidence matches always go to a person; nothing is auto-posted. We never connect to banks or the GST portal.

Registry nameai.saifs/payment-reconciliation
Endpointhttps://payment-reconciliation-mcp-microsoft.saifs.ai/mcp
TransportStreamable HTTP (remote, nothing to install)
AuthOAuth 2.1 — PKCE (S256) and dynamic client registration; your client opens a sign-in page on first use
PublisherSAIFS AI

Install

VS Code / GitHub Copilot

Add to .vscode/mcp.json (workspace) or your user mcp.json:

{
  "servers": {
    "saifs-payment-reconciliation": {
      "type": "http",
      "url": "https://payment-reconciliation-mcp-microsoft.saifs.ai/mcp"
    }
  }
}

Then start the server from the MCP view and sign in when prompted.

Claude (claude.ai, Desktop)

Settings → Connectors → Add custom connector, and paste:

https://payment-reconciliation-mcp-microsoft.saifs.ai/mcp
Claude Code
claude mcp add --transport http saifs-payment-reconciliation https://payment-reconciliation-mcp-microsoft.saifs.ai/mcp
Any other MCP client

Point it at https://payment-reconciliation-mcp-microsoft.saifs.ai/mcp using the Streamable HTTP transport. The server returns 401 with a WWW-Authenticate: Bearer … resource_metadata=… challenge, so OAuth-aware clients sign in automatically.

Tools

ToolWhat it does
explain_matchWhy these items match — amount combination, name score, date gap and reference.
gst_2b_matchIndia GSTR-2B vs purchase register: matched, mismatched, missing, and ITC at risk.
match_bank_to_ledgerBank reconciliation with one-to-many and many-to-one matches.
match_receiptsCash application including combinations, part payments and deductions.
reconciliation_reportMatched %, unmatched value, ageing of exceptions and ITC at risk.
suggest_rulesNew matching rules learned from confirmed matches, returned in rules_snapshot.

Example prompts

  • “Match today’s receipts to open invoices”
  • “Reconcile the bank statement”
  • “Run GSTR-2B vs purchase register”

Support

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.