Use cases

Corporate treasury

How Siemens Automated Treasury Cash Sweeps With J.P. Morgan Kinexys

Siemens and J.P. Morgan tested programmable payments for treasury. Later bank materials describe Siemens using rules to automate cash allocation, intercompany funding and liquidity concentration.

Proof of concept followed by bank-documented treasury workflowsReviewed by FluidRWA Research TeamVerified through November 9, 2026
Illustrative treasury team reviewing financial records

Verified use case

What happened?

Siemens and J.P. Morgan tested programmable payments for treasury. Later bank materials describe Siemens using rules to automate cash allocation, intercompany funding and liquidity concentration.

CompanySiemens and J.P. Morgan
StatusProof of concept followed by bank-documented treasury workflows
Research cut-offNovember 9, 2026

Context before technology

Background

A treasury team can schedule transfers, but the schedule does not know when an outgoing payment arrives early or an expected receipt is late. A balance rule can make the funding decision when the account actually needs it.

The first public account described a proof of concept. Later J.P. Morgan material describes a broader Siemens treasury workflow. The two records support different conclusions: one documents a test; the other describes reported operational use.

Roles and records

How does the operating model work?

Set the balance rule

Treasury defines what the account should hold and which accounts may supply funds. The bank-side workflow can execute preconfigured transfers when the relevant condition is met.

Move funds and capture the result

J.P. Morgan describes API access to account or payment information. An implementation should match the sending and receiving records before treating a sweep as reconciled.

Keep a manual path for exceptions

For a procurement test, try stale balances, a duplicate trigger and an unavailable funding account. Ask who sees the exception, who can stop retries and what the audit record contains.

Core infrastructure

  • Bank payment accounts
  • Balance and payment data
  • Rules-based transfers
  • Treasury reconciliation

Confirmed milestones

How did the use case develop?

  1. 01

    2021

    Proof of concept reported

    J.P. Morgan described a programmable treasury payment test with Siemens.

  2. 02

    2024

    Treasury example documented in joint research

    J.P. Morgan and MIT DCI discussed programmable payments and maintaining target balances in a bank environment.

Evidence of adoption

What outcomes are publicly confirmed?

Target balance

Treasury objective documented in the case

The published materials describe the workflow, not an independently audited savings figure.

Metrics are attributed to their reporting organization and date. They are not forecasts, endorsements or guarantees of equivalent results.

Current position

What are the latest confirmed updates?

  • J.P. Morgan's Siemens treasury case describes cross-border sweeping and EUR/USD foreign exchange in the broader treasury setup. Scope should be checked by entity, currency and account.

What buyers can learn

Why did this use case progress?

  • Start with one account and a clear funding rule. Track manual interventions and unexplained balance movements before expanding.
  • Keep rule approval separate from rule execution, and make it possible to pause automation without losing the audit history.

Limits of the evidence

  • The materials do not quantify Siemens-wide savings or disclose a complete list of production accounts.
  • The reported capabilities do not establish that every bank, currency or legal entity can participate.

Questions to take into procurement

  • What happens when an account needs funding but the source account is also below target?
  • Who can pause or change a rule, and can we retrieve the history of those changes?
  • How will the treasury system reconcile both sides of a sweep and escalate a missing confirmation?

Relevant FluidRWA directories

Common questions

What is a cash sweep?

A cash sweep moves money between accounts under a defined rule, for example to concentrate surplus balances or fund an account that has fallen below its target.

Is this the same as a public stablecoin payout?

No. The cited case concerns programmable payments in a bank environment and movements between treasury accounts.

Research record

FluidRWA reviewed the following public records. Company names are presented as plain text and are not outbound promotional links.

  • J.P. Morgan, programmable payments proof of concept with Siemens: https://www.jpmorgan.com/insights/payments/blockchain-digital-assets/programmable-payments-automation-becomes-reality
  • J.P. Morgan and MIT Digital Currency Initiative, Application of Programmability to Commercial Banking and Payments, 2024: https://www.jpmorgan.com/kinexys/documents/Application-of-Programmability-to-Commercial-Banking-and-Payments.pdf
  • J.P. Morgan, Siemens Treasury's Digital Transformation: https://cws-main-ndc.jpmorgan.com/insights/payments/blockchain-digital-assets/siemens-treasury-transformation

Independent research summary, not legal, investment or regulatory advice. Public statements may be updated after the research cut-off.

Last updated

Questions about your project? contact@fluidrwa.com

Your next step

Turn the use case into a plan.

Define your needs before you shortlist providers.