Hi,
I don't thing is a bad idea.I don't know what really want sfsolution but I interesting for some king of budget.
I try to look on project what you linked, but I have same problem like you there many thing what I don't want to use.
It's complicated and orientated for sales etc.
What I interesting is simple budget. some basic overview of accounts income/outcome and summary. If it's write abstractly
it can be used in many cases.
This is not request or final solution it's vision. I trying prepare more detailed description but now i try to write it shortly.
Call it budget integration.
Entities:
Account - bank account, credit card, Property (Building/gold/License SW/HW etc)
Payment - income/outcome realized payment
Planed payment - planed income/outcome payment
Currency -
Relation:
Planed payment - with calendar for overview when is planed pay or receive payment.
Planed payment - project - for filtrate and use same logic like task's etc.
Planed payment - payment for understand is realized or not of course.
Planed payment - Account - for know where it's money
Payment - account - same
Account - payment ... - currency - currency is basic universal identification cost for us.
Account - project - I thing it's better what make global type of account.
Summary/Report/Statistic
-------------------------------------------
Situation or model:
1. Account - My Bank account with 100$
Planed payment - rent office payment 50$ per month
Summary - overview state of my bank account
2. Account - My properties for current project. For example for small project i cooperate with one guy, and want borrow
my license for special SW with prise 1000$.
Planed payment - in this case i create 2x payments when i borrow and when it's probably return SW.
Summary - overview probably date overview when this return or something more interesting.
3. Probably you can image another situation....
4. With integration hour price functionality it can be great for example this user is planed on this project and I have only 1000$ now i know i need paper, pens etc = 100$ and 500$ it's planned for user work (based on payment per hour) for example it 100 hours. This is a plan after project end I only recalculate in overview what is saved and for example pay to used bonus.
-------------------------
Comments
Account may present any properties group of everything what can be priced
Payment - transfer of properties based on price (in comment or another field can be better specification payment/borrow/etc)
Summary - some kind of graph for overview state of account, for properties maybe what is account content, summary of planed payment per month etc.
I thing we can image many types of overviews.
Major point of view is not on customer but on user (feng user) for make some notes about money over project. It's not orientated for make report make prices and send to customer. Only for user overview how many project cost, for example.
Names of entities is not good but i don't know another
