GTreasury

Name: GTreasury
Brand: GTreasury
Rating: 4.2 (46 reviews)

GTreasury is a treasury management system that centralizes and automates cash visibility, payments execution, forecasting, bank connectivity, and risk/hedge accounting within a modular platform.

Est 1986|Valuation $1B|Raised $28.6M|67 Ref Customers

LinkedIn 20K|Website|FTEs 147|HQ Buffalo Grove, Illinois, US

MarketsERP Treasury Management Systems (TMS)

01Competitive Landscape

Narrative analysis

GTreasury vs Kyriba - Vendor positioning contrasts shorter implementation timelines and lower TCO for GTreasury against longer implementations for some legacy TMS vendors; these are vendor claims and should be validated with multiple customer references. - Third-party review summaries suggest Kyriba scores higher in overall satisfaction in some comparisons and highlight responsive support; GTreasury is described as configurable and potentially easier to set up, but with areas for improvement in forecasting. - Some review snapshots show Kyriba with higher support and implementation sentiment in specific samples, though sample sizes are small. GTreasury vs Serrala - Serrala emphasizes SAP-centric treasury and payments automation and publishes automation metrics as vendor claims; buyers should request definitions, prerequisites, and reference customers. - Serrala may be a stronger fit for organizations standardized on SAP wanting treasury tooling tightly aligned with SAP processes. GTreasury vs Coupa Treasury - Coupa positions treasury capabilities as part of a broader finance/spend control suite. Public materials often reference supplier portal plans; enterprise treasury pricing and scope are typically quote-based.

Market share and adoption (caution)

Some market intelligence sites estimate Kyriba as a leading vendor with a larger share and GTreasury as a smaller share. These estimates are not audited and depend heavily on web-detection methodology; treat as directional.

	GTreasury	Kyriba	Coupa Treasury
Starting Price	Not publicly listed (quote-based likely); third-party estimates vary	Often quote-based (some directories publish estimates, but vendor pricing is commonly custom)	Quote-based for buyers; publicly visible pricing pages often relate to supplier portal plans, not treasury buyer licensing
Best For	Enterprises needing centralized cash visibility + payments + risk modules in one platform; teams valuing configurability	Large global enterprises prioritizing maturity, connectivity, and scale	Organizations aligning treasury with a broader Coupa finance/spend ecosystem
Key Strength	Centralization across banks/entities; reported integration experiences; modular platform	Broad market adoption; higher satisfaction in some comparisons; perceived strong support in some sources	Integration with a broader business spend management approach; mobile approvals and supplier integration
Key Weakness	Some UI areas described as less modern; workflow rigidity; implementation/data-load friction reported; support/documentation mixed in small samples	Implementations can be lengthy and complex per multiple narratives	Pricing transparency for treasury buyers can be low; depth of treasury features depends on buyer needs

01Competitive Landscape

Narrative analysis

GTreasury vs Kyriba

Vendor positioning contrasts shorter implementation timelines and lower TCO for GTreasury against longer implementations for some legacy TMS vendors; these are vendor claims and should be validated with multiple customer references.
Third-party review summaries suggest Kyriba scores higher in overall satisfaction in some comparisons and highlight responsive support; GTreasury is described as configurable and potentially easier to set up, but with areas for improvement in forecasting.
Some review snapshots show Kyriba with higher support and implementation sentiment in specific samples, though sample sizes are small.

GTreasury vs Serrala

Serrala emphasizes SAP-centric treasury and payments automation and publishes automation metrics as vendor claims; buyers should request definitions, prerequisites, and reference customers.
Serrala may be a stronger fit for organizations standardized on SAP wanting treasury tooling tightly aligned with SAP processes.

GTreasury vs Coupa Treasury

Coupa positions treasury capabilities as part of a broader finance/spend control suite. Public materials often reference supplier portal plans; enterprise treasury pricing and scope are typically quote-based.

Market share and adoption (caution)

Some market intelligence sites estimate Kyriba as a leading vendor with a larger share and GTreasury as a smaller share. These estimates are not audited and depend heavily on web-detection methodology; treat as directional.

	GTreasury	Kyriba	Coupa Treasury
Starting Price	Not publicly listed (quote-based likely); third-party estimates vary	Often quote-based (some directories publish estimates, but vendor pricing is commonly custom)	Quote-based for buyers; publicly visible pricing pages often relate to supplier portal plans, not treasury buyer licensing
Best For	Enterprises needing centralized cash visibility + payments + risk modules in one platform; teams valuing configurability	Large global enterprises prioritizing maturity, connectivity, and scale	Organizations aligning treasury with a broader Coupa finance/spend ecosystem
Key Strength	Centralization across banks/entities; reported integration experiences; modular platform	Broad market adoption; higher satisfaction in some comparisons; perceived strong support in some sources	Integration with a broader business spend management approach; mobile approvals and supplier integration
Key Weakness	Some UI areas described as less modern; workflow rigidity; implementation/data-load friction reported; support/documentation mixed in small samples	Implementations can be lengthy and complex per multiple narratives	Pricing transparency for treasury buyers can be low; depth of treasury features depends on buyer needs