Batch Forecast Uploads¶
Status: Shipped¶
Domain: Cash Forecasting Linear Projects: Batch Forecast Uploads
What It Does¶
Palm allows users to upload forecast data from external files (Excel, CSV) directly into the system. This bridges the gap between teams that maintain forecasts in spreadsheets and the need for that data in a centralized forecasting platform.
The batch upload capability handles the complexity of mapping file columns to Palm's data model, dealing with different number formats (European vs US conventions), and validating data before import. Teams can upload forecast data for specific categories (tax payments, talent costs, etc.) that don't flow from ERP or ML.
Capabilities¶
| Capability | Status | Notes |
|---|---|---|
| Excel/CSV file upload | Shipped | Standard file formats supported |
| Column mapping UI | Shipped | Map file columns to Palm fields |
| Number format handling | Shipped | European (1.234,56) and US (1,234.56) conventions |
| Data validation | Shipped | Pre-import error checking |
| Category-specific uploads | Shipped | Upload for specific forecast categories |
| Date range handling | Shipped | Upload forecasts for specific periods |
Jobs Fulfilled¶
1. Upload forecast data from files without extensive reformatting¶
Desired Outcomes Addressed: - [x] Minimize the manual changes required to file formats before upload - [x] Reduce the time spent aligning number formats and column structures - [x] Increase the success rate of first-time file uploads
How Palm Addresses This: - Flexible column mapping handles different file structures - Number format detection handles regional conventions - Clear validation messages guide successful uploads
2. Forecast cash flows entity-by-entity across decentralized group structure¶
Desired Outcomes Addressed: - [x] Reduce errors from manual Excel manipulation (format, decimal conventions, typos) - [x] Increase visibility into forecast changes vs original figures - [ ] Minimize the time spent chasing entities for forecast submissions (not direct - still requires entity input)
How Palm Addresses This: - Standardized upload process reduces format errors - Validation catches issues before data enters the system - Centralized storage provides visibility into submitted forecasts
Pain Points Addressed¶
| Pain Point | Addressed? | Notes |
|---|---|---|
| Excel chaos across many entities | Partial | Standardized upload, but still Excel-based input |
| Different formats, decimal conventions | Yes | Number format handling |
| Column limits in mapping UI | Fixed | UI improvements implemented |
| Manual data entry is error-prone | Yes | Validation catches errors |
What's NOT Included (Yet)¶
- Automatic file detection (drag-and-drop without manual mapping)
- Template generation (export template for entity to fill in)
- Recurring/scheduled uploads
- Upload history and audit trail
- Rollback capabilities
How It Works (Technical)¶
TODO: Fill in via codebase analysis
| Component | Technology | Notes |
|---|---|---|
| File parsing | ||
| Column mapping | ||
| Validation engine | ||
| API endpoints |
Key files/services: - TBD
Related¶
- Domain knowledge: docs/knowledge/cash-forecasting/
- Related feature: forecasting.md
- Roadmap: Upload forecast data from files (Delivered)
Last updated: 2026-02-17