io.github.sebastienrousseau/reconcile-mcp

Registre officiel Finance et paiements

Reconcile camt.053 statements vs expected pain.001 payments with explainable matching.

Que pouvez-vous faire avec io.github.sebastienrousseau/reconcile-mcp ?

  • reconcile — Match expected payments against observed entries; full explainable report.
  • explain_match — Score a single expected/observed pair with a per-signal breakdown (tuning aid).
  • normalize_pain001 — Adapt parsed pain.001 output into canonical expected records.
  • normalize_camt053 — Adapt parsed camt.053 output into canonical observed records.
  • list_sandbox_scenarios — List the built-in test-mode scenarios and magic references.
  • load_sandbox_scenario — Return one scenario's expected/observed inputs to inspect or edit.
  • run_sandbox_scenario — Load a scenario and reconcile it in one call — the fastest first run.
  • match_names_probabilistic — Score two counterparty names by Jaro-Winkler similarity and flag a match at a threshold.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package reconcile-mcp
Claude Code
claude mcp add reconcile-mcp -- uvx reconcile-mcp==0.0.7
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "reconcile-mcp": {
            "command": "uvx",
            "args": [
                "reconcile-mcp==0.0.7"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. reconcile-mcp: An MCP Server for ISO 20022 Cash Reconciliation
  2. Why this exists
  3. The ISO 20022 MCP Suite
  4. Install
  5. Quick start (zero real data)
  6. Transports
  7. Bring your own data
  8. Tools
  9. How matching works
  10. Development
  11. License

reconcile-mcp: An MCP Server for ISO 20022 Cash Reconciliation

A [Model Context Protocol][mcp] server that matches expected payments (from pain.001 credit transfers) against observed booked entries (from a camt.053 statement) and returns an explainable reconciliation — exact matches, short/over payments, split settlements (one-to-many), batch credits (many-to-one), and the residual unmatched items on each side, every match carrying a score and the reasons it was made.

Latest release: v0.0.7: 10 MCP tools over stdio, streamable HTTP or SSE, pure-Python matching engine, deterministic sandbox test-mode, for Python 3.10+. Part of the ISO 20022 MCP suite: you own both sides of the match.

Why this exists

Reconciliation is the treasury team's daily pain: did the money we expected actually arrive, and which invoice does each credit belong to? It is rarely one-to-one — customers underpay, settle an invoice in instalments, or a payout aggregator sends one lump covering a dozen receivables. reconcile-mcp does this matching as an agent tool, and — critically for finance — shows its work: every pairing comes with a numeric score and a plain list of the signals (reference, amount, date, counterparty) that drove it.

The ISO 20022 MCP Suite

reconcile-mcp is the reconciliation workflow of eight coordinated, vendor-neutral MCP servers that together cover the ISO 20022 bank-statement workflow and the November 2026 structured-address cutover, plus a high-level orchestration layer — readiness scoring, clearing-profile linting, and audit evidence — statement depth, whole-catalogue routing, reconciliation, multi-format ingestion, and address remediation. Dependency ranges are kept aligned across the suite, so the servers co-install cleanly in a single Python environment: start with one, add the rest as your workflow grows.

ServerScopeSurfaceInstallUse it when
[camt053-mcp][camt053-mcp]ISO 20022 camt.053/camt.052 bank statements: parse, validate, filter, reverse; MT940/MT942 migration; CBPR+ readiness; journal export24 MCP tools · 4 prompts · 3 resourcespip install camt053-mcpYou work with bank-to-customer statements end to end — the suite's flagship
[iso20022-mcp][iso20022-mcp]Unified gateway: search / describe / validate / generate / parse meta-tools routed across the pain · pacs · camt · acmt families7 meta-toolspip install "iso20022-mcp[all]"You want one entry point to every message family
reconcile-mcpMatches expected pain.001 payments against observed camt.053 entries — exact, partial, one-to-many, many-to-one, every match scored and explained10 MCP tools · 1 prompt · 2 resourcespip install reconcile-mcpYou need explainable statement/payment reconciliation — this package
[bankstatementparser-mcp][bsp-mcp]Multi-format statement ingestion: ISO 20022 CAMT.053 and pain.001, SWIFT MT940, OFX/QFX, CSV5 MCP tools · 1 prompt · 1 resourcepip install bankstatementparser-mcpYour statements arrive in mixed or legacy formats
[structured-address-fix-mcp][saf-mcp]ISO 20022 postal-address classification, assessment & remediation for the November 2026 structured-address cutover (pacs.008 / pain.001 debtor & creditor addresses)9 MCP toolspip install structured-address-fix-mcpYou need debtor/creditor addresses cliff-ready ahead of 14 Nov 2026
iso20022-readiness-suite-mcpOrchestration gateway: detect → structurally validate → clearing-profile lint → readiness score, plus automated remediation and pacs.002 bank-response simulation — a meta-client over the foundational servers4 MCP toolspip install iso20022-readiness-suite-mcpYou want one high-level readiness / orchestration entry point over the suite
iso20022-bank-profile-mcpManages, validates and serves bank-specific clearing profiles / rule packs (CBPR+, SEPA_Instant, FedNow, Generic); premium rule-pack entitlement gating4 MCP toolspip install iso20022-bank-profile-mcpYou lint payments against your own institution's market practice
iso20022-evidence-pack-mcpCompiles readiness findings, remediation diffs and simulated responses into a sealed, Ed25519-signable audit evidence pack6 MCP toolspip install iso20022-evidence-pack-mcpYou need tamper-evident audit / certification artifacts

In one line each: camt053-mcp is the bank-statement flagship (deepest camt.05x surface, stdio + authenticated streamable HTTP); iso20022-mcp is the generic message toolkit (a handful of verbs over the whole catalogue); reconcile-mcp is the reconciliation workflow (did the money we expected actually arrive?); bankstatementparser-mcp is the ingestion layer (many formats in, one transaction shape out); and structured-address-fix-mcp is the postal-address specialist (debtor/creditor addresses cliff-ready for the Nov 2026 cutover).

The suite also includes per-family servers — [pain001-mcp][pain001-mcp] (credit transfer initiation), [pacs008-mcp][pacs008-mcp] (FI-to-FI credit transfers), and [acmt001-mcp][acmt001-mcp] (account management) — whose parsed output feeds straight into this server's normalize_* adapters.

Install

pip install reconcile-mcp
# or run without installing:
uvx reconcile-mcp

MCP client config (e.g. Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "reconcile": {
      "command": "reconcile-mcp"
    }
  }
}

Quick start (zero real data)

The server ships a sandbox test-mode: deterministic scenarios so you can run the whole flow with no setup and no real cash data. One call gets you a full, explainable result:

run_sandbox_scenario(name="month_end")

returns a realistic mixed close — one clean match, one short payment, one split settlement, and an unexpected credit correctly left unmatched:

{
  "summary": {
    "expected_count": 3, "observed_count": 5,
    "matched_expected": 3, "unmatched_observed": 1,
    "matches_by_type": {"exact": 1, "amount_mismatch": 1, "one_to_many": 1},
    "fully_reconciled": false
  },
  "matches": [
    {"type": "amount_mismatch", "expected": ["INV-6002"], "observed": ["ENT-52"],
     "amount_delta": "-99.99", "confidence": "high",
     "reasons": ["reference exact", "amount close (delta -99.99)", "date +/-0d", "counterparty exact"]},
    {"type": "exact", "expected": ["INV-6001"], "observed": ["ENT-51"], "amount_delta": "0.00"},
    {"type": "one_to_many", "expected": ["INV-6003"], "observed": ["ENT-53", "ENT-54"],
     "reasons": ["amount sum of 2 entries"]}
  ],
  "unmatched_observed": ["ENT-55"]
}

List every scenario with list_sandbox_scenarios; load one to inspect or edit its inputs with load_sandbox_scenario.

Transports

One command line, three transports:

CommandTransportEndpointProtocol revisions
reconcile-mcpstdiothe client spawns the process2026-07-28, 2025-11-25
reconcile-mcp --transport streamable-httpStreamable HTTPhttp://127.0.0.1:8000/mcp2026-07-28 (stateless, server/discover) and 2025-11-25 (initialize, Mcp-Session-Id) on the same endpoint; responses stream as server-sent events, GET opens the server-to-client stream
reconcile-mcp --transport sseHTTP+SSE (2024-11-05)http://127.0.0.1:8000/sse and /messages/for clients that still expect the older transport

--host and --port change the bind address (defaults 127.0.0.1 and 8000). The HTTP transports carry no authentication of their own: bind loopback, or put the server behind a gateway you trust before binding a routable address. Every release is verified over streamable HTTP with passmcp in both protocol eras and over SSE with the MCP SDK client; see ADR 0001.

{
  "mcpServers": {
    "reconcile": { "url": "http://127.0.0.1:8000/mcp" }
  }
}

Bring your own data

Records are small canonical objects — id and amount required, everything else optional and used to sharpen matching:

{
  "id": "INV-1001",            // your reference / end-to-end id
  "amount": 1200.00,
  "currency": "EUR",           // ISO 4217
  "date": "2026-03-02",        // ISO-8601
  "counterparty": "Acme Ltd",
  "reference": "INV-1001"      // remittance / structured reference
}

Already using the rest of the suite? Feed parsed output straight in — the adapters map it for you:

  • normalize_pain001(document) → the expected side, from [pain001-mcp][pain001-mcp].
  • normalize_camt053(document) → the observed side, from [camt053-mcp][camt053-mcp].

Then call reconcile(expected, observed).

Tools

  • reconcile — Match expected payments against observed entries; full explainable report.
  • explain_match — Score a single expected/observed pair with a per-signal breakdown (tuning aid).
  • normalize_pain001 — Adapt parsed pain.001 output into canonical expected records.
  • normalize_camt053 — Adapt parsed camt.053 output into canonical observed records.
  • list_sandbox_scenarios — List the built-in test-mode scenarios and magic references.
  • load_sandbox_scenario — Return one scenario's expected/observed inputs to inspect or edit.
  • run_sandbox_scenario — Load a scenario and reconcile it in one call — the fastest first run.
  • match_names_probabilistic — Score two counterparty names by Jaro-Winkler similarity and flag a match at a threshold.
  • match_amounts_with_fx_drift — Compare two amounts in different currencies through a supplied FX rate, within a percentage tolerance.
  • reconcile_many_to_many — Match each deposit to a disjoint subset of invoices whose amounts sum to it (subset-sum ILP; needs the ilp extra).

Plus one prompt and two resources:

  • Prompt reconcile_workflow — Step-by-step guidance from raw pain.001/camt.053 to an explained match report.
  • Resource reconcile://sandbox-scenarios — The built-in scenario catalogue.
  • Resource reconcile://sandbox/{scenario_id} — One scenario's expected/observed inputs.

How matching works

Each candidate pair is scored on four weighted signals, then classified:

  • Reference (0.45) — exact / partial equality of references and end-to-end ids, normalised to bare alphanumerics.
  • Amount (0.35) — exact within tolerance, or a linearly-decaying closeness with the delta reported.
  • Date (0.10) — proximity within a configurable window; neutral if unknown.
  • Counterparty (0.10) — token-set overlap of names; neutral if unknown.

Assignment is greedy, highest-score-first and fully deterministic (a total tiebreak order), so the same inputs always produce the same result. Residuals are then tested for one-to-many (a bounded subset-sum: one expected settled by several entries) and many-to-one (one entry covering several expected).

Tune any of it via the options argument: abs_tol / rel_tol, date_window_days, high_threshold, review_threshold, currency_strict, enable_one_to_many, max_combination.

Development

git clone https://github.com/sebastienrousseau/reconcile-mcp
cd reconcile-mcp
python -m venv .venv && . .venv/bin/activate
pip install -e . && pip install pytest pytest-cov ruff black mypy
pytest                      # 100% branch coverage gate
ruff check reconcile_mcp tests && black --check reconcile_mcp tests && mypy reconcile_mcp

License

Licensed under the Apache License, Version 2.0 or the MIT License, at your option.


mcp-name: io.github.sebastienrousseau/reconcile-mcp

[mcp]: https://modelcontextprotocol.io [iso20022-mcp]: https://github.com/sebastienrousseau/iso20022-mcp [pain001-mcp]: https://github.com/sebastienrousseau/pain001-mcp [pacs008-mcp]: https://github.com/sebastienrousseau/pacs008-mcp [camt053-mcp]: https://github.com/sebastienrousseau/camt053-mcp [acmt001-mcp]: https://github.com/sebastienrousseau/acmt001-mcp [bsp-mcp]: https://github.com/sebastienrousseau/bankstatementparser-mcp [saf-mcp]: https://github.com/sebastienrousseau/structured-address-fix-mcp

Questions fréquentes

Qu'est-ce que io.github.sebastienrousseau/reconcile-mcp ?

Reconcile camt.053 statements vs expected pain.001 payments with explainable matching.

Comment installer io.github.sebastienrousseau/reconcile-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add reconcile-mcp -- uvx reconcile-mcp==0.0.7. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.sebastienrousseau/reconcile-mcp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.sebastienrousseau/reconcile-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence Apache-2.0.

Qui maintient io.github.sebastienrousseau/reconcile-mcp ?

Il est publié par sebastienrousseau. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.