Financial services workflows

Four agentic workflows. One observability layer.

Regulated financial institutions ship AI agents into production faster than IAM, OAuth, MCP and workflow engines can keep up. KYE Delegated Auditability binds read-only to those stacks and answers, for every agent action: who or what acted, on whose behalf, under what authority, inside what scope, with what evidence.

Workflow 1

Agentic payments.

A supplier-payment agent prepares and confirms invoices on behalf of finance ops. KYE captures each prepare/confirm action, runs a Shadow Evaluation against the bank's Authority Graph, and flags missing_authority_grant, dual_control_missing, rate_cap_exceeded and amount_above_threshold gaps. PSD3 SCA-exemption claims become defensible because they reference signed Evidence Packs.

Workflow 2

Procurement agents.

A procurement copilot accepts vendor quotes and triggers contract drafting. KYE captures every quote acceptance, runs Shadow Evaluations against the bank's third-party-risk policy, and flags out_of_scope_action (vendor outside approved tier), jurisdiction_mismatch (sanctions exposure), and data_class_unauthorized (commercially sensitive data shared outside its grant).

Workflow 3

Open finance.

A consent-aware finance copilot reads accounts via PSD2/PSD3 open-banking APIs, classifies transactions and recommends actions. KYE captures the agent's interpretation of consent (Purpose Permission), flags purpose_unbound when the agent acts beyond the consented purpose, and emits stale_delegation alerts when consent ages past its reconfirmation window.

Workflow 4

Risk & compliance copilots.

A model-validation copilot reviews a credit-scoring model for compliance with SR 11-7. KYE captures the copilot's findings as Observed Actions, runs Shadow Evaluations to detect ambient_authority (the copilot reading production model artefacts it was never granted access to), and emits Guard Recommendations that align to SR 11-7 §IV (independent challenge).

Delegated authority gaps

Across all four workflows.

The same nine-class taxonomy applies across agentic payments, procurement, open finance and risk/compliance. The same Guard Recommendation types close them: Authority Gate, Purpose Permission, Tool Guard, MCP Guard, scope attenuation, rate cap.

Evidence Pack examples

Open the demo bundle.

A real Evidence Pack for a supplier-payment action — observed, evaluated, classified, recommended. Replayable offline.

Pilot package

30–90 day engagement, fixed scope.

  • Bind 1–4 customer stacks (read-only). Default scope: one agent class, two workflows.
  • KYE operators triage Observed Actions and classify Authority Gaps weekly.
  • Signed Audit Pilot Report at week 4, with prioritised Guard Recommendations.
  • Optional: install one Guard in shadow mode in week 6, promote at week 9.
  • Fixed price; no production stack change in scope.