Cash Visibility: Priorities & Context¶
Date: 2026-02-17 Domain: Cash Visibility
Priority Ranking¶
Cash visibility is largely solved — it's the foundation Palm was built on. Remaining gaps are about proactive alerting and scaling to 150+ accounts.
Top Priority (Confirmed — gaps in alerting)¶
1. Check cash positioning across all bank accounts each morning - Sources: ON (3 sessions), Sonder (Confirmed) - Current status: Mostly solved — dashboard works, but no proactive alerts - Why it matters: This is the daily ritual every treasurer performs. Solved for normal operations but breaks at scale. ON: "At some point, you become blind... you see the numbers but you don't know where to draw your attention if you have 150 accounts."
2. Confirm treasury-initiated payments went through daily - Sources: ON (2 sessions) (Confirmed) - Current status: Partial — must manually check balances, no proactive alerting - Why it matters: The $8M Canada payment failure story. ON: "A payment from Canada failed and no one noticed." This is a monitoring gap, not a visibility gap — the shift from "see it" to "be alerted when something's wrong."
Emerging — Needs Validation¶
| # | Potential Job | Source | Key Question |
|---|---|---|---|
| 3 | Review 150+ accounts daily and identify which need attention | ON | Is this ON-specific or common at scale? |
| 4 | Monitor currency exposures and cash pool positions | ON | Overlap with IC Activity domain? |
| 5 | Verify data completeness and categorization accuracy | ON | Is this a visibility job or a data quality job? |
The Shift: Visibility → Alerting¶
Palm solved the first generation of cash visibility (one dashboard, all accounts). The next generation is about:
- Attention routing — "which of my 150 accounts need me right now?"
- Proactive alerts — "a payment failed" vs "check your dashboard"
- Exception-based workflows — show what's wrong, not everything
Next Steps¶
- Proactive alerting (#2) — failed payment detection is the most compelling use case
- Validate attention routing (#3) — is the 150-account problem common beyond ON?
- Consider overlap with IC Activity — payment monitoring jobs span both domains