Financial Markets – EduDataSci – Educating the world about data and leadership

Stop Settlement Fails Before They Start

At 9:42 a.m., an institutional equity trade executes normally. There is no break and no exception to repair.

By 2:00 p.m., the picture has changed. The client’s allocation is later than usual. The standing settlement instruction (SSI) on one record does not agree with the custodian’s current instruction. Securities expected from another account have not arrived. A routine counterparty acknowledgment is still missing.

None of those facts proves that the trade will fail. Together, they say that the trade is becoming harder to settle.

The traditional operating model waits for a definite exception, places it in a queue and asks an operations analyst to reconstruct what happened. A prevention model starts earlier. It watches the trade’s full lifecycle, recognizes a risky pattern, applies the firm’s control rules and intervenes while useful choices remain.

This is not a proposal for a better exception queue. It is a different job for operations: prevent avoidable failures, resolve safe and bounded issues automatically, bring judgment-heavy cases to the right expert, and remove recurring defects from the upstream process.

The Client Passed KYC. Why Can’t They Trade?

“Can the new fund trade on Monday?” should be an easy question.

The relationship manager knows the asset manager. The client record is active. KYC is complete. Legal has a signed agreement, and credit has approved a limit. Every team appears to have done its part.

But operations is still opening an account. A tax form is attached to the parent company rather than the fund. The agreement covers the right legal entity but not the requested product in that jurisdiction. A market permission has not reached the entitlement system. On Friday afternoon, every function can report that its task is complete—or at least within its service level—while the client still cannot place a trade.

No single system is necessarily wrong. Each system is answering a smaller question than the client asked.

This is the gap that process mining can address. The technology is often discussed in connection with claims automation, where it can identify slow routes, repeated work, and unnecessary handoffs. Those are useful applications. But the same method can be even more valuable in financial-markets onboarding, where one commercial outcome depends on several functions and systems agreeing at the same time.

The goal is not merely to complete KYC faster. It is to make the client usable—safely, lawfully, and with a clear record of how that decision was reached.

From Vibes to Specs: The New Citizen Development Financial Services Can Actually Trust

A friend of mine recently came back from a conference session on “vibe coding” with the kind of energy you only get when something fundamental has shifted. They are smart, tech-enabled, and fully comfortable around digital tools, but they are not a programmer. After a brief introduction, they sat down and built several applications. Not toys. Not abstract demos. Useful applications that solved real problems in both their daily life and their professional work. They even shared those applications with colleagues. And, as is often the case with these new tools, the apps were not only functional. They were polished, themed, and appealing to use.

That story is easy to file under amazement. It is harder, and more important, to recognize it as a signal. The computing world is going through a fundamental shift that changes the locus of invention. Before – and almost every programmer has had this experience, I suspect – non-developers would come up to you and tell you an idea, then try to get you to help them make it happen. Now they can do a lot of the hard work themselves!

The signal, though, is not that everyone should now go build production systems from a prompt window and hope for the best. The signal is that the distance between understanding a problem and expressing a solution in software has collapsed. The people closest to the work can now participate in shaping the tools they need in a much more direct way. That is the breakthrough. And in the financial services sector, where structure, security, explainability, and accountability are non-negotiable, the way to turn that breakthrough into something durable is not vibe coding. It is spec-driven development.

If we want a world where everyone can get to what they need to do, their way, even inside the highly governed world of banking, wealth management, lending, life insurance, reinsurance, property and casualty insurance, and credit card processing, then spec-driven development should become the new citizen development model.

After FabCon: What Agentic Apps on Microsoft Fabric Could Actually Look Like in Insurance and Wealth Management

The real test for agentic AI is not whether it can answer a question. It is whether it can answer the right question, with the right data, under the right controls, and then move work forward without creating new risk. That is why Microsoft’s March 12 piece on operationalizing agentic applications mattered. It shifted the conversation away from chatbot theater and toward architecture, telemetry, governance, and action. Since FabCon Atlanta in March 2026, that story has become more concrete: Microsoft used the event to frame trusted AI around OneLake, Real-Time Intelligence, Fabric IQ, and AI agents; said Fabric data agents are now generally available; introduced Fabric Remote MCP in preview; and announced Planning in Fabric IQ.

Just as important, the weeks immediately after FabCon filled in several missing pieces. Microsoft says Fabric IQ now supports Azure Private Link integration, and it also says Fabric IQ ontology will be exposed through public MCP endpoints. Microsoft added Ontology Rules with Fabric Activator, documented Business Events in Real-Time Intelligence, published source control and deployment-pipeline guidance for Fabric data agents, and, in April 2026, announced shortcut transformations as generally available. Taken together, those updates make Fabric’s agent story look less like a promising concept and more like an emerging operating model.

That matters because Fabric IQ is no longer just a semantic side note. Microsoft now describes IQ as a workload spanning ontology, plan, graph, data agents, operations agents, and semantic models. Ontology defines entity types, relationships, properties, and condition-action rules bound to real data. Graph adds relationship-centric analysis. Plan brings budgets, forecasts, and scenarios onto the same governed platform. And Fabric data agents can answer questions over lakehouses, warehouses, semantic models, KQL databases, ontologies, and Microsoft Graph in Fabric.

Pages: 12

Straight Through Processing for Documents: When “Touchless” Becomes the Cost-Saving Feature

Most organizations don’t drown in documents because they lack OCR.

They drown because every document creates work-in-the-middle: a person opens an email, downloads an attachment, checks a value, rekeys it into a system, compares it to a second system, and routes it to a third. Multiply that by thousands of invoices, claims, onboarding packets, and compliance forms, and your “document workflow” turns into a labor model.

That’s where Straight Through Processing (STP) comes in.

In this post, I’ll lay out what STP actually means, why it’s the most practical way to think about cost reduction in document-heavy operations, and what “STP-ready” AI document automation requires beyond basic extraction—without anchoring the conversation to any single vendor.

From Tables to Networks: A Deep Dive into Graph in Microsoft Fabric for Financial Services Insights

Most financial services data is already “connected.” It just isn’t modeled that way.

Fraud rings don’t show up as a single row. Money laundering doesn’t announce itself in one transaction. Counterparty exposure isn’t obvious from one booking. The meaningful signal lives in relationships: who shares an address, which accounts route funds through the same nodes, where devices and identities overlap, and how risk propagates through a network.

Graph in Microsoft Fabric is designed for exactly that: turning your OneLake data into a connected model you can explore visually, query with GQL, and enrich with built-in graph algorithms—without standing up a separate graph stack and duplicating data.

In financial services, this is the difference between “we have the data” and “we can reason over the connections.”