I believe the foregoing are compelling justifications for choosing Excel Visual Basic over Visual Basic.
In effect what I am saying is that companies which get the most value from spreadsheet automation(including using it to avoid expenditure on less adaptable commercial off the shelf applications) will be those which empower their users to routinely generate "in house" solutions. In such companies, you will find that only when the requirement becomes considerably specialised or complex, does the IT department get called upon to develop or purchase software solutions for user departments or functions with significant data recording and analysis needs.
"Over_used/Over_spent"(Losses) and "Under_used/Under_spent"(Savings) _ on a monthly basis based on data entered, the program also automatically plotted charts showing trends over a 12 month period.
You can choose to learn how to do it yourself _ or call in someone(an Excel VB Solutions Developer for instance) who knows how. Again, this would be dependent on your purpose, how proficient you are, and/or how much time you have at your disposal. Ultimately, even if someone develops a custom application for you, it should happen with YOUR guidance at every point to ensure that it does EXACTLY what you want it to do, and that you can easily _ with your developer's support/coaching _ learn how to make modifications to it in future, without needing to call back your developer.