Modern Treasury — What I Think
Modern Treasury picked the least glamorous problem in all of fintech, and was right to. Moving money is easy. Knowing what happened to the money is hard.
Every engineer who’s ever built a payments flow learns this the painful way. Firing an ACH or a wire is one API call. The nightmare is everything after — did it settle, did it bounce, did it get returned five business days later, does it reconcile against the order it was meant to pay, and is your internal ledger telling the truth right now. I’ve debugged exactly this class of bug. The hard part of money movement is the bookkeeping, not the movement.
What almost everyone underrates: reconciliation is the actual product. The industry obsesses over rails — faster payments, new networks, instant settlement — but the thing that breaks businesses is the gap between “money moved” and “our books agree about it.” Modern Treasury built payment operations as software. A ledger that’s correct by construction, automated reconciliation, one layer over ACH, wire, RTP, and cards so a company isn’t hand-rolling a brittle integration per bank. They treated the ledger as the source of truth and the payment as a side effect. Exactly backwards from how most people build it, and exactly right.
And as more non-fintech companies started moving money at scale — marketplaces, insurers, lenders, platforms paying out to thousands of accounts — they all hit the same wall, and none of them wanted to become a payments-engineering shop to climb it. Modern Treasury bet “payment operations” deserved to be a category the way CRM or the data warehouse is, bought instead of built. Turning an internal cost centre every company rebuilds badly into a product they can buy is a classic, durable infrastructure thesis. A correct ledger is something you only appreciate after one has betrayed you. Then you’ll pay anything for it.
The exposure: the ledger-and-reconciliation layer is supremely valuable and supremely abstract, which makes it a quiet land-grab from several directions. Banks want to offer it natively, the big payment platforms want to absorb it upward, and the original “unify the ACH/wire mess” wedge depends partly on how fragmented US rails stay — instant-payments standardisation could thin the very mess they organise. The real question is whether payment-ops-as-a-category becomes its own durable software market or gets swallowed as a feature by the rails and the ERPs on either side. I lean durable, because correctness-of-ledger is a trust good, and trust goods consolidate to whoever got it right first. But being the right abstraction is half the battle. You also have to be the one people standardise on.
Favorite & worst CEO
Founder-led, so this is on leadership. Dimitri Dadiomov built Modern Treasury around an insight only people who’ve actually shipped payments at scale tend to have — the ledger and the reconciliation, not the transfer, are where the real pain and the real value live. Choosing to productise the boring, correctness-obsessed middle of money movement instead of chasing a flashier consumer or rails story is exactly the kind of unsexy infrastructure conviction I respect most. It’s a bet that being right about plumbing compounds. The push into programmable ledgers and treating payment operations as a first-class category shows he’s playing for the abstraction layer, not a point feature. My one gripe is the standing risk for any horizontal infrastructure company — being the correct, neutral layer is necessary but not sufficient, you also have to win the standardisation fight before the banks and ERPs encircle the category. The strongest version is the default ledger of record for anyone that moves money, period. Worth building toward.
Part of “What I Think About the Top 50 Fintech Companies of All Time.” I’m Prajjwal Chittori. prajjwalchittori.com.