Articles and Announcements

This contains the most recent announcements and technical content posts.

Brand new validation library

September 1, 2026 by Jeff Ward (Beneficial Strategies)

We’re announcing a new package today: BeneficialStrategies.Iso20022.FluentValidation, the validation companion to the C# ISO 20022 library. It’s on NuGet now, and it’s up to date with the same June 26, 2026 specification snapshot as the library it validates. Up front: this is a work in progress, not a finished product. It already covers real ground — enough to fully validate two entire business areas — but large parts of the specification aren’t built out yet. We’d rather ship what’s solid and be honest about what isn’t than wait until everything is done. Below is exactly where that line sits today.

C# ISO 20022 Library updated to June 2026 snapshot

August 30, 2026 by Jeff Ward (Beneficial Strategies)

Right alongside the MCP server’s own update to the June 26, 2026 ISO 20022 snapshot, we’ve brought the C# ISO 20022 Library — our free, open, .NET implementation of the standard — up to date as well. It now covers 3,311 message types from the current specification, with full XML and JSON serialization for each one. If you’ve never run across it: this is a from-scratch .NET class library that turns the ISO 20022 specification into strongly-typed, IntelliSense-friendly C# — records and structs the compiler actually helps you use correctly, instead of a loose bag of XML you have to trust yourself to get right.

MCP Server updated to June 26, 2026 snapshot

August 26, 2026 by Jeff Ward (Beneficial Strategies)

The ISO 20022 Organization periodically republishes its official eRepository — the canonical source for every message definition, business component, code set, and validation rule in the standard. On June 26, 2026, they published a new snapshot, and our MCP server has already been updated to match it, moving up from the previous May 11, 2026 edition. If that sounds like inside baseball, here’s the short version: our AI assistant’s knowledge of ISO 20022 is only as good as the data it’s built on. Every time the standards body publishes a refresh, we pull it in so that whatever your AI tool tells you — a field name, a data type, a constraint, whether a code is still valid — reflects the current official specification, not a stale copy from months ago.

Getting Close!

June 23, 2026 by Jeff Ward (Beneficial Strategies)

After a lot of heads-down building, we are close — very close — to launching version 1.0 of the ISO 20022 AI MCP Server. The server is live on production infrastructure right now. We’re running it through its paces, validating the support workflows, and tightening the last few details before we open the doors. Here’s where things stand. What’s working today The knowledge base is current. We’ve updated to the May 2025 ISO 20022 repository snapshot — over 2,500 message definitions, 400+ business components, and all associated code sets and constraints, straight from the official specification.

What MCP now understands about bank transaction codes

June 2, 2026 by Jeff Ward (Beneficial Strategies)

Open a bank statement message — a camt.052, camt.053, or camt.054 — and every entry on it carries a BankTransactionCodeStructure: a compact classification of what kind of transaction it actually is. A SEPA credit transfer, an ACH debit, a card settlement, a standing order — each gets a specific code, not a free-text description. That classification scheme, the Bank Transaction Code (BTC) hierarchy, is maintained separately from the core ISO 20022 specification, and it’s now something our MCP server can resolve directly.

What MCP now understands about data source schemes

June 2, 2026 by Jeff Ward (Beneficial Strategies)

ISO 20022 doesn’t force every code in a message into a fixed, standard list. In a handful of specific places, it deliberately leaves the door open for a market infrastructure, a central securities depository, or an industry body to define its own proprietary codes instead. That mechanism is called a Data Source Scheme (DSS), and it’s tracked in its own registry by the ISO 20022 Registration Authority — separate from the main specification, and until now, separate from what our MCP server could tell you.

Use Case How Do I Implement the ISO 20022 Digital Signature?

March 26, 2026 by Jeff Ward, Claude (Anthropic) (Beneficial Strategies)

A C# developer implementing ISO 20022 message signing asks the MCP Server to explain SignatureEnvelope and SignatureEnvelopeReference — and walks away with working code for both origination and verification.