libra: improve expense description helper text to guide categorization (and add an "Other" account) #137

New issue

Open

opened 2026-06-25 12:26:50 +00:00 by padreug · 0 comments

padreug commented

2026-06-25 12:26:50 +00:00

Owner

Context

Client feedback on the libra expenses flow. We discussed adding categories to expenses in the future, but agreed we don't yet know which categories to add.

Clarification on terminology: in libra, the "category" the client means is the account the user selects in Step 1 (AccountSelector, e.g. Expenses:Groceries:Organic) right after clicking Add expense. That account selection is the categorization mechanism — there is no separate "category" field. So an "Other" category is just an "Other" account in that hierarchy, for cases where nothing else fits.

The near-term ask is to make the expense description field do more of the categorization work — by prompting the user to write a richer, more structured description — so that even when they fall back to "Other", we have enough detail to reconcile/recategorize later.

Near-term request (this issue)

Update the helper/description text on the expense Description field so it guides the user on what to type to help us categorize the expense.

Current (src/modules/expenses/components/AddExpense.vue:101-116):

Label: Description *
Placeholder: e.g., Biocoop, Ferme des Croquantes, Foix Market, etc
FormDescription: Describe what this expense was for

Proposed — wording is approximate, refine as needed:

Use the Other account if you don't see one that matches. Add a detailed description of the purchase / invoice / bill, and what it was used for (event / project / etc).

Future work

Add an "Other" account to the account hierarchy as the explicit fallback when no existing account matches.
Once we have a candidate taxonomy from real usage, formalize a set of expense accounts/categories. This issue is the placeholder for that conversation.

Acceptance criteria

Description-field helper text updated to prompt for a detailed description (what it was + what it was used for: event/project/etc).
Helper text points users to the Other account when nothing matches.
An Other account exists (or is confirmed to exist) in the account hierarchy as the fallback.
Final copy reviewed with the client / product.

Source: client feedback, 2026-06-25.

## Context Client feedback on the libra expenses flow. We discussed adding **categories** to expenses in the future, but agreed we don't yet know which categories to add. Clarification on terminology: in libra, the "category" the client means is the **account** the user selects in Step 1 (`AccountSelector`, e.g. `Expenses:Groceries:Organic`) right after clicking **Add expense**. That account selection *is* the categorization mechanism — there is no separate "category" field. So an **"Other"** category is just an **"Other" account** in that hierarchy, for cases where nothing else fits. The near-term ask is to make the **expense description** field do more of the categorization work — by prompting the user to write a richer, more structured description — so that even when they fall back to "Other", we have enough detail to reconcile/recategorize later. ## Near-term request (this issue) Update the helper/description text on the expense **Description** field so it guides the user on what to type to help us categorize the expense. **Current** (`src/modules/expenses/components/AddExpense.vue:101-116`): - Label: `Description *` - Placeholder: `e.g., Biocoop, Ferme des Croquantes, Foix Market, etc` - FormDescription: `Describe what this expense was for` **Proposed** — wording is approximate, refine as needed: > Use the **Other** account if you don't see one that matches. Add a detailed description of the purchase / invoice / bill, and what it was used for (event / project / etc). ## Future work - Add an **"Other"** account to the account hierarchy as the explicit fallback when no existing account matches. - Once we have a candidate taxonomy from real usage, formalize a set of expense accounts/categories. This issue is the placeholder for that conversation. ## Acceptance criteria - [ ] Description-field helper text updated to prompt for a detailed description (what it was + what it was used for: event/project/etc). - [ ] Helper text points users to the **Other** account when nothing matches. - [ ] An **Other** account exists (or is confirmed to exist) in the account hierarchy as the fallback. - [ ] Final copy reviewed with the client / product. _Source: client feedback, 2026-06-25._

padreug added the

app:libra

enhancement

labels

2026-06-25 12:26:57 +00:00

padreug changed title from ~~libra: improve expense description helper text to guide categorization (and seed future "Other" category)~~ to libra: improve expense description helper text to guide categorization (and add an "Other" account)

2026-06-25 12:30:36 +00:00

padreug referenced this issue from a commit

2026-06-25 19:44:52 +00:00

feat(libra): guide expense description toward categorization

padreug referenced this issue

2026-06-25 19:45:06 +00:00

feat(libra): guide expense description toward categorization #138

padreug referenced this issue from a commit

2026-06-25 20:10:50 +00:00

feat(libra): guide expense account choice + description copy