Skip to content

Connectivity

Overview

Connectivity refers to how treasury teams physically connect to banks, ERPs, data lakes, and other data sources. This includes direct integrations (host-to-host, APIs), bank portals, ERP connections, TMS platforms, payment hubs, SFTP/cloud pipelines, and direct data lake integrations (e.g., BigQuery) for AP/AR forecasting data.

For treasury teams, connectivity directly impacts operational efficiency — the more fragmented the connectivity, the more time spent on manual data gathering. It also affects data timeliness (real-time vs T+1) and the ability to automate processes like cash positioning, reconciliation, and forecast data ingestion.

Key challenges include managing multiple bank portals, integrating TMS platforms (Kyriba, Integrity), ERP connectivity gaps, AP/AR data extraction for forecasting, and achieving consolidated visibility across all sources.

For detailed ICP context and terminology, see fundamentals.md

Top Jobs & Desired Outcomes

Full history: jobs.md

⚡ 1. Get real-time or same-day bank balance visibility

Desired Outcomes: - Minimize the delay between transactions and balance visibility - Reduce dependency on external reconciliation teams - Increase confidence in cash position accuracy

Sources: ON x2 (Confirmed) — "Right now until the end of the month, we don't really know how much money we have"

Key Pain Points

Full history: pain-points.md

  • ERP not real-time - Don't know actual cash position until month-end reconciliation (Sources: On x2)
  • Multiple bank portals - Must log into each bank separately (UBS, BNP, Deutsche Bank, JP Morgan) (Source: On)
  • Monthly reconciliation cadence - Would prefer daily, but everything piles up at month-end (Source: On)
  • Bank reconciliation delays - External teams (e.g., Deloitte) create lag between transactions and visibility (Source: On)

Key Opportunities

  • Unified bank view - Single dashboard showing all bank account balances
  • Real-time or near-real-time data - Reduce dependency on batch reconciliation
  • Continuous reconciliation - Enable daily reconciliation vs monthly crunch
  • Automated alerts - Notify when accounts are overdrawn or outside target balance

Open Questions

  • [ ] What's the typical number of bank portals treasury teams manage?
  • [ ] How do teams prioritize which banks to integrate first?
  • [ ] What's acceptable latency for cash position data? (real-time vs T+1)
  • [ ] How do teams handle ERP-to-TMS connectivity gaps (e.g., PeopleSoft → Kyriba)?
  • [ ] What role do payment hubs (TIS, etc.) play vs TMS-native bank connectivity?
  • [ ] What's the preferred integration pattern for AP/AR data: direct ERP API, data lake (BigQuery), or TMS passthrough?
  • [ ] How often should AP/AR data refresh for forecasting purposes? (daily, weekly, real-time)

Last updated: 2026-02-25 | Sources: 3 transcripts (view all)