Why all the disdain for "tag clouds"?
I understand that you don't want to double-count transactions for the purposes of taxes or budgeting, but certainly having the ability to "tag" or put a transaction in multiple categories has reporting and planning benefits.
For example, if I vacation in San Francisco and buy a shirt as a gift for my daughter, what category do I put it in?
It could be "vacation", "San Francisco", "clothing", "gifts", or "Lauren".
Actually, I'd like to "tag" it with all 5.
I can now ask questions/reports like:
How much did I spend on vacations?
How much did I spend in San Francisco?
How much did I spend on clothing?
How much did I spend on gifts?
How much did I spend on Lauren?
How much did I spend on clothing for Lauren?
How much did I spend on gifts while on vacations?
etc...
You get the idea...there are many different ways to cut this up and the "tag cloud" allows you to do this.
One way to to handle the tax issue, so something isn't double counted, the program could make it so that only one "tax-related" tag could be assigned to a transaction.
If you can neatly fit all your transactions into one category, that's great, but why place that limitation on others who might find multiple categories beneficial?
-Tom