The Market view
The map opens on organisations gathered around the systems they run: treasury, FP&A and EPM, ERP, banking and payments. A line means one organisation runs a system, is implementing it, is selecting one, or has replaced one, and a public page says so. Every line links to that page: a vendor's customer story, a press release, a job post, a conference talk.
You can narrow it by industry, ERP, company size, region and family of system, and the figures follow. Open an organisation and you see who on the map works or worked there. That is the point of it: a reference you found yourself, not one a vendor picked for you.
How it is counted
Every vendor is read the same way: its public customer stories, and one search for its named customers in the press and in conference talks. No vendor gets more searches than another. On top come searches that name no vendor: job posts, selection announcements, moves from spreadsheets, and one search per industry, the same for each.
Some things are never counted: a vendor, a consultancy or an integrator as a user; a job post that only asks for experience with a product; a bank using vendor software to serve its clients; paid customer databases; anything the crawler did not read itself.
Brands a vendor has bought keep their own name on the map, but count with their owner when vendors are compared: Visual Risk, Coprocess and CashAnalytics with GTreasury, Cashforce with TIS, FiREapps with Kyriba.
One rule matters more than the others. A bubble counts public evidence, not customers. Vendors that publish many customer stories look bigger, and systems with a large installed base and few published stories look smaller. Nothing is weighted or corrected to compensate. This is not market share, and the map says so on the page.
Five things the public record shows
As of 11 November the map holds 2,243 organisations: 817 with a treasury system on public record and 1,463 with an FP&A or EPM tool.
1. Treasury and FP&A never come from the same vendor. 53 organisations have both on record, and in all 53 they are two vendors, even when the brands a vendor has bought count as that vendor. The most frequent pairs are Kyriba with Pigment (Bolt, Europcar, Uber), Atlar with Abacum (Aiven, MANGOPAY, Upvest) and HighRadius with Workday Adaptive or Anaplan. Costco and Ingram Micro run Kyriba with OneStream; Microsoft runs ION and SAP treasury with Anaplan; BASF runs Kyriba and Serrala with Board.
2. Large groups run a second treasury system, mostly for payments. 21 organisations show two treasury vendors, BASF, Microsoft and Lufthansa among them. In 13 of the 21, one of the two is a payments and bank connectivity platform, TIS or Serrala. At the top end, the treasury system is a stack of its own.
3. FP&A vendors publish far more than treasury vendors. Read the same way, FP&A vendors yield 1,463 organisations and treasury vendors 817. 29 organisations even show two planning tools, often consolidation in one and planning in the other: Danone with Tagetik and Pigment, Sanofi with Jedox and Workday Adaptive. Treasury buyers go to market with far fewer peer stories to learn from.
4. Challengers win close to home. Where the country is known, 32 of Nomentia's 37 customers are in the German-speaking countries or the Nordics, 15 of Pigment's 28 are French, and Germany is Jedox's first market, with about a third of its customers in Germany, Austria and Switzerland. Kyriba, the most published treasury vendor, has about half of its customers on record in the United States.
5. No customer story names the competitor it replaced. When a story says what came before, the answer is Excel, manual processes, a legacy system, or an older version of the same product. Vendors say they beat spreadsheets, never whom they beat.
Fifty-three is a floor, not a measure. Each vendor publishes its own customers, so a company appears on both sides only when both of its vendors have written it up. What the public record does show is the shape: where both are on record, treasury and planning are two products, two projects and two contracts.
I build K-φ, which puts treasury and FP&A in one platform, so I have a stake in the first finding. That is exactly why the method is published, and why it is the same for every vendor, K-φ included.
Selections as they happen
A job post that asks someone to select or implement a treasury system shows a choice being made, often months before a request for proposal. The map marks those organisations for nine months, unless a later page shows the system running.
The people are still there
The People, Topics and Connections views remain: who appeared with whom on a public page (co-appearance, not acquaintance), who speaks about what, and who says they know whom. There is no LinkedIn crawling, no data bought from profile-scraping vendors, no photos and no contact details.
Your card, your call
Every person's card has a Suggest a change link: correct a title, point to a page the map has missed, or ask for your card to be removed. A person reads every request before anything changes. Organisation profiles (industry, size, country) come from Wikidata and link to it; when a match is wrong, tell us and it is fixed.
What comes next
The map is the first half of a selection guide for treasury and EPM software: start from the requirements of an RFP, see which systems companies like yours run, and find the people who use or implement them, to ask for a reference you chose yourself. K-φ is on the map like any other vendor, and the map does not rank systems.