TreasuryOS — Cash Visibility and Forecasting
Fintech / TreasuryTreasuryOS
Product overview
TreasuryOS aggregates balances and transactions from multiple banks and systems into one dashboard. Finance teams see real-time cash position, run forecasts, manage approvals and workflows, and export data for reporting and audit. The platform is built for security and compliance from the ground up.
Problem statement
Treasury and FP&A teams were logging into multiple bank portals and copying data into spreadsheets. Cash position was a daily manual exercise; forecasting was error-prone and hard to update. Approval workflows for payments and transfers lived in email and shared drives. Auditors and leadership had no single view of liquidity and controls.
Product vision
One place to see 'how much we have, where it is, and what we expect.' Bank data should flow in automatically; forecasts should be model-driven and scenario-based; approvals should be traceable and role-based. The product should meet the security and audit expectations of CFOs and auditors.
Key features
- Multi-bank aggregation with automatic refresh and transaction categorization
- Cash position dashboard by entity, account, and currency with drill-down
- Forecasting: baseline and scenarios with drag-and-drop adjustments
- Approval workflows for transfers and payments with audit trail
- Role-based access, SSO, and detailed activity logs
- Export to Excel and integration with ERPs and reporting tools
UX / product design approach
We prioritized trust and clarity: numbers must be clearly sourced and timestamped. We used a familiar 'spreadsheet-like' layout for tables with strong hierarchy (entity → account → period). Workflows were designed as linear steps with clear 'who approved what and when.' We avoided flashy visuals in favor of precision and consistency. Accessibility and keyboard navigation were required for power users.
Technical architecture
React SPA with a strict auth and session model. Backend: multi-tenant API with tenant isolation at DB and cache level. Bank connections via licensed aggregation provider with encrypted credentials. Event-driven pipeline for balance and transaction sync. Forecasting engine as a separate service with versioned models. Full audit logging to immutable store. SOC 2-oriented controls (encryption, access, logging).
Technology stack
- React, TypeScript
- Node.js (NestJS), PostgreSQL
- Redis, message queue
- Bank aggregation API (Plaid / Tink or equivalent)
- SSO (SAML/OIDC), encryption at rest and in transit
Challenges solved
- Keeping bank data in sync and handling varying bank API reliability and latency
- Designing multi-tenant data isolation and permission model for sensitive data
- Building forecasting models that were explainable and adjustable by finance users
- Meeting security and audit requirements without slowing product iteration
Business impact
The client has a working treasury platform with bank aggregation, cash visibility, and approval workflows. Their own finance team relies on it for daily positioning and reporting. The product is built with clear audit trails and export so it’s ready when they bring on paying customers.
Visual elements
Suggested UI highlights for this product.
- Cash position: table and optional chart by entity/account with last refresh time
- Forecast view: timeline with baseline and scenario comparison
- Workflow: approval queue with status and history
- Activity log: filterable list of actions and exports
Outcome
Core platform shipped: multi-bank view, cash position, and approval workflows. Client’s finance team uses it daily; built with security and audit in mind for future customers.
Services
- Fintech
- SaaS
- Custom Development
- Design
- Security