Kyriba is attempting to break down the functional silos that isolate treasury data from broader enterprise intelligence. By launching Data-as-a-Service (DaaS), the company aims to provide finance and IT teams with governed, analytics-ready access to liquidity and payment information. This move targets the friction caused when critical cash and risk data remains trapped within treasury departments, inaccessible to the ERP and forecasting tools used by the wider organization.
Kyriba DaaS Technical Architecture and Data Scope
The new DaaS offering is designed to feed structured treasury data directly into existing business intelligence (BI) and data platforms. Kyriba is positioning this as a method to bypass manual file downloads and reformatting by utilizing standard connectivity protocols, including JDBC, OAuth2, and SQL. The service includes more than 165 tables and 4,400 fields, covering domains such as cash, payments, risk, and supply chain finance. According to the company, customers can access up to three years of historical data from the first day of implementation, depending on data availability. This technical framework is intended to support high-volume analysis and incremental data refreshes, allowing for more seamless integration with enterprise-wide data environments and existing reporting infrastructures.
Strategic Integration of Treasury and Enterprise Data
Kyriba is framing DaaS as a bridge between specialized treasury functions and general corporate finance. The company suggests that by combining Kyriba’s cash, payments, and foreign-exchange data with external inputs like sales forecasts, operating expenses, and workforce plans, finance leaders can better assess how business activity shifts impact working capital and liquidity. For IT departments, the service is presented as a governed alternative to creating bespoke, departmental data processes. By enabling the use of existing BI tools, Kyriba aims to reduce the administrative burden on IT teams while providing a more connected view of financial performance. This integration is intended to support faster, data-driven decision-making regarding liquidity and risk management across the entire enterprise.
Key Takeaways
- Kyriba's DaaS provides access to over 165 tables and 4,400 fields across cash, payments, risk, and supply chain finance.
- The service utilizes JDBC, OAuth2, and SQL connectivity to integrate with existing enterprise BI and data platforms.
- Customers can access up to three years of historical data, subject to availability, to support high-volume analysis.
FinanceInsyte's Take
In our view, Kyriba is moving to capture more value within the enterprise data stack by addressing the "data silo" problem inherent in specialized treasury management. By offering DaaS, Kyriba is not just providing a treasury tool, but is positioning itself as a critical data provider for the entire finance function. This signals a shift toward deeper integration with ERP and BI ecosystems, testing whether treasury-specific data can become a primary driver for broader corporate liquidity forecasting and strategic capital allocation.
Questions & Answers
How does DaaS facilitate integration with existing enterprise BI tools?
DaaS utilizes standard connectivity protocols, specifically JDBC, OAuth2, and SQL, to allow treasury data to flow into the business intelligence and reporting platforms that organizations already employ.
What specific data categories are included in the DaaS offering?
The service encompasses more than 165 tables and 4,400 fields, which include data related to cash, payments, risk, and supply chain finance.
What is the intended impact of DaaS on IT department workloads?
Kyriba suggests that DaaS provides a governed way to support data use cases through existing platforms, which could reduce the necessity for IT teams to build and maintain separate, manual data processes for different departments.
How much historical data can be accessed through this new service?
Subject to data availability, the company states that customers can access up to three years of historical data from the start of using the service.
Source: Kyriba
