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, and SFTP/cloud pipelines.

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 and reconciliation.

Key challenges include managing multiple bank portals, integrating TMS platforms (Kyriba, Integrity), ERP connectivity gaps, 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)

2. Consolidate bank account visibility without logging into multiple portals ⚡

Desired Outcomes: - Minimize the time spent logging into multiple bank portals daily - Reduce manual effort gathering balances from disparate sources - Increase speed of daily cash positioning process

Source: On (Emerging - needs corroboration from other company)

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?

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