Manual One-Off Forecast Items¶
Status: Shipped¶
Domain: Cash Forecasting Linear Projects: Manual input of one-off forecasting items
What It Does¶
Palm allows users to manually add one-off forecast items that aren't captured by ERP data or ML predictions. These are payments or receipts that the treasury team knows about but that don't exist in any system yet - a large vendor payment, an expected tax refund, or a known receivable from a key customer.
This capability bridges the gap between "what systems know" and "what treasury knows" to produce more complete and accurate forecasts.
Capabilities¶
| Capability | Status | Notes |
|---|---|---|
| Manual single-item entry | Shipped | Dialog with account, category, amount, date, notes |
| Category assignment | Shipped | Dropdown to assign forecast category |
| Date/amount specification | Shipped | DatePicker + amount input with currency |
| Account assignment | Shipped | Account dropdown to select target account |
| Notes/description | Shipped | Textarea for notes on the forecast item |
| Batch forecast upload | Shipped | Upload multiple items via file |
Jobs Fulfilled¶
1. Produce a short-term cash forecast I can trust and act on¶
Desired Outcomes Addressed: - [x] Reduce the frequency of surprise payments not captured in forecast - [x] Increase the percentage of forecast based on booked/actual data vs guesses - [x] Increase confidence in inputs by understanding their source and historical accuracy
How Palm Addresses This: - Treasury team can manually add known items via dialog - Captures "what treasury knows" that systems don't - Items clearly marked with notes for context
2. Improve forecast accuracy by handling outliers¶
Desired Outcomes Addressed: - [x] Minimize the impact of one-off large payments on future forecasts - [x] Increase confidence in forecasts by excluding known anomalies
How Palm Addresses This: - One-off items tracked separately from ML predictions - Don't distort ML learning when properly categorized - Clear visibility into manual vs ML forecast sources
Pain Points Addressed¶
| Pain Point | Addressed? | Notes |
|---|---|---|
| Last-minute surprise payments | Partial | Treasury can add known items; truly surprise payments still surprise |
| Forgotten tax payments | Yes | Can be added as one-off items when remembered |
| Payments made outside system | Yes | Can capture payments not in ERP |
What's NOT Included (Yet)¶
- Recurring one-off items (annual tax that repeats each year)
- Item templates for common one-offs
- Automatic reminders for known cyclical items
- Integration with external calendars/task systems
How It Works (Technical)¶
TODO: Fill in via codebase analysis
| Component | Technology | Notes |
|---|---|---|
| Item storage | ||
| Forecast integration | ||
| API endpoints |
Key files/services: - TBD
Related¶
- Domain knowledge: docs/knowledge/cash-forecasting/
- Related feature: forecasting.md
- Roadmap: None currently planned
Last updated: 2026-02-03