[Feature] Dual-use categories

[cajeiri]

📝 Feature Description

Allow for categories to be selected not just as Income or Expense, but as Income & Expense too.

🛑 Problem Statement

Having to manually recreate every category that can be both a type of income and expense.

🎁 Benefits

Yes to both.

🖥️ OS

Both

✍️ Additional Context

Example:

Category Birthday Gift could be an income, as in - receiving cash as a birthday gift AND it can be an expense when you pay for a birthday gift for someone else.

📜 Code of Conduct

• ✅ I agree to the Code of Conduct

[mikev-cw]

Hello! This is honestly the first time I’ve heard of a requirement like this. I think it would be a feature that would be rarely used and fairly complex to implement from a logical standpoint. How would you calculate the category total? How would you clearly distinguish between the total amount received as gifts and the amount actually spent on gifts?

Moreover, this would violate a fundamental accounting principle: clearly separating inflows from outflows. Let’s see what other users think about this.

[cajeiri]

Up to you Mike, I'm just sharing my usecase.

Simply put, it annoys me to have to recreate some categories, where logically it's the same thing. How you go about it, if you deem this an acceptable addition, doesn't really matter to me - it doesn't have to be dual-use, it could even an option to "duplicate as expense" as a checkbox when creating a new category..

In my mind, the transaction is what should be marked as an inflow or outflow, the category is just a definition under which it falls, regardless of whether it's coming or going.

[mikev-cw]

it could even an option to "duplicate as expense" as a checkbox when creating a new category..

Good catch. Let's see if this could work for other users.

In my mind, the transaction is what should be marked as an inflow or outflow, the category is just a definition under which it falls, regardless of whether it's coming or going.

I understand what you mean, and yes, it makes sense. Unfortunately it's not how Sossoldi works at its roots: our transaction is tagged IN/OUT itself, and only then an inbound or outbound category is assigned. This is what i meant when i said that is complex to implement from a logical standpoint.
But if turns out that this is a popular feature, we could surely find a way i guess.
Thanks for the input!