Treasury Data - Jobs & Desired Outcomes¶
Confirmed Outcomes¶
Corroborated by 2+ sources
Job: Get bank data into a usable format without massive integration projects¶
| Desired Outcome | Status | Solved By |
|---|---|---|
| Minimize the time from decision to live data (weeks, not months) | ✅ Shipped | Data Layer |
| Reduce dependency on IT for new bank connections | ✅ Shipped | Data Layer |
| Increase flexibility to add new data sources without rebuilding | ✅ Shipped | Data Layer |
Sources: - Feature file — shipped capabilities (S3/GCS/Azure Blob, SFTP, HTTPS APIs; ISO 20022 CAMT, MT940/MT942, BAI2, CSV) - ON (2024-09-26) — No consolidation tool, logging into each portal manually - ON (2024-10-24) — ERP data not real-time, monthly reconciliation cadence
Job: Trust the data powering forecasts and reports¶
| Desired Outcome | Status | Solved By |
|---|---|---|
| Minimize data quality issues that pollute downstream analytics | ✅ Shipped | Data Layer |
| Increase confidence that all accounts are being captured | ✅ Shipped | Data Layer |
| Reduce time spent investigating data discrepancies | ✅ Shipped | Data Layer |
Sources: - Feature file — shipped capabilities (schema validation, freshness monitoring, audit trails) - ON (2024-10-24) — "Right now until the end of the month, we don't really know how much money we have"
Emerging Signals¶
Single source - needs corroboration
Potential Job: Maintain reliable forecast data despite upstream system limitations¶
Potential Outcomes: - Minimize data loss from Kyriba's daily delete behavior - Reduce the frequency of missing forecast data when training regional teams - Increase confidence in forecast data accuracy
Source: ON (2025-10-02) - "We're training the regions now... and the data is not there because that day because we delete... it happens so many times." - Amanda
Moved from cash-forecasting — this is a data infrastructure concern.