Treasury Data: Priorities & Context¶
Date: 2026-02-17 Domain: Data
Priority Ranking¶
Data infrastructure is largely shipped. Both confirmed jobs are solved. The remaining emerging signal is about upstream data reliability.
Confirmed — Shipped¶
1. Get bank data into a usable format without massive integration projects - Sources: Feature file, ON (2 sessions) (Confirmed) - Current status: Shipped — S3/GCS/Azure Blob, SFTP, HTTPS APIs; ISO 20022, MT940/MT942, BAI2, CSV all supported - Why it matters: Palm's data layer eliminates the months-long integration projects that plague TMS deployments. ON had no consolidation tool and was logging into each bank portal manually.
2. Trust the data powering forecasts and reports - Sources: Feature file, ON (Confirmed) - Current status: Shipped — schema validation, freshness monitoring, audit trails - Why it matters: Every downstream feature (forecasting, variance analysis, reporting) depends on data quality. If treasurers can't trust the data, they won't trust the outputs.
Emerging — Needs Validation¶
| # | Potential Job | Source | Key Question |
|---|---|---|---|
| 3 | Maintain reliable forecast data despite upstream system limitations | ON | How common is the Kyriba daily-delete problem? |
Next Steps¶
- Monitor data quality issues across customers — as more customers onboard, new data format and quality challenges will emerge
- Validate upstream reliability signal (#3) — ON's Kyriba deletes data daily, causing training gaps for regional teams