Categorization: Priorities & Context¶
Date: 2026-02-17 Domain: Categorization
Priority Ranking¶
Core categorization is largely solved. Remaining jobs are about downstream value and continuous reconciliation.
Top Priority (Confirmed — solved)¶
1. Classify bank transactions into budget categories for variance analysis - Sources: Euroports, Personio (Confirmed) - Current status: Solved — auto-categorization works, reclassification available, rule-based matching active - Why it matters: The foundation for everything else. Without accurate categories, variance analysis, forecasting, and reporting all break. Personio: "Way too much of my time is spent on data validation."
High Priority (Confirmed — partially solved)¶
2. Support downstream teams (AR, AP, Accounting) with granular transaction data - Sources: Sonder, ON (Confirmed) - Current status: Partial — categorization helps but no GL integration, downstream workflows still manual - Why it matters: Sonder: "We're doing this for our other AP AR teams where it's easier for them to identify or create journal entries." Treasury data becomes valuable to accounting when it's properly categorized.
Emerging — Needs Validation¶
| # | Potential Job | Source | Key Question |
|---|---|---|---|
| 3 | Tell stories with Treasury data using categories | Sonder | Is this a categorization job or a reporting job? |
| 4 | Reconcile bank transactions to ERP continuously | ON | Is this treasury's job or accounting's? How big is the demand? |
| 5 | Identify and book unprocessed bank transactions | ON | Overlap with data domain? |
Next Steps¶
- GL integration (#2) — the natural next step for downstream team support
- Validate continuous reconciliation (#4) — ON wants daily, currently monthly. Is this common?
- Monitor categorization accuracy — ON's recategorization caused dashboard instability. Need guardrails.