Connectivity: Priorities & Context¶
Date: 2026-02-17 Domain: Connectivity
Priority Ranking¶
Connectivity is foundational infrastructure. The core job is partially solved — Palm connects to data sources but doesn't have direct bank APIs. Real-time depends on the customer's upstream data freshness.
Top Priority (Confirmed — partially solved)¶
1. Get real-time or same-day bank balance visibility - Sources: ON (2 sessions) (Confirmed) - Current status: Partial — Palm connects to TMS/data lake feeds but doesn't have direct bank APIs. Real-time depends on customer's upstream systems. - Why it matters: ON: "Right now until the end of the month, we don't really know how much money we have... from the ERP we'll have to go every day into the bank if we wanted to check." The gap isn't Palm's connectivity — it's the customer's data pipeline.
Emerging — Needs Validation¶
| # | Potential Job | Source | Key Question |
|---|---|---|---|
| 2 | Consolidate bank account visibility without logging into multiple portals | ON | Largely solved by Palm already. Is there a remaining gap? |
The Reality¶
Connectivity is a solved problem at Palm's layer. We support S3/GCS/Azure Blob, SFTP, HTTPS APIs, and standard formats (ISO 20022, MT940/MT942, BAI2, CSV). The remaining friction is:
- Customer-side data freshness — ERP reconciliation happens monthly, not daily
- Bank API availability — direct bank APIs (Open Banking, SWIFT gpi) could bypass the data freshness problem
- New bank connections — each new customer/bank combination needs configuration
Next Steps¶
- Monitor Open Banking / PSD2 developments — direct bank APIs could leapfrog the data freshness problem
- Validate if direct bank connectivity is a priority — or if customers are satisfied with TMS/data lake feeds