The little time you spend entering notes and comments will pay generous dividends when you need to refer to these notes
I spent many years in the software industry. I was not a programmer or software architect but was very close to many of the technical aspects of the business and got to observe some of the good and bad practices used.
One of the worst practices I recall was not entering comments next to program code lines, or not writing clear and sufficient notes to allow both the original developers and other people to fully understand the original code.
This became evident when we lost one of our best programmers, who left for another opportunity. Although we owned the copyright to the code, every programmer who looked at it could not make sense out of it and although the code was near completion with initial testing of functionality underway, we had to scrap it and start from scratch. We learned a very expensive lesson: Enforce the practice of documenting all programming work and minimize the risk of losing your own intellectual property due to negligence and bad work habits.
Computer programming, design and engineering are good examples why notes must be kept, however, many other activities, both business and personal, can use this discipline.
As I gained experience in corporate accounting and finance I started to adopt this concept in my work and introduced a policy that all accounting transactions (e.g., journal entries into the GL) must be accompanied by notes or comments explaining the rationale behind them and anything that would help a reader understand the underlying events that required the entry. Automated entries from sub-systems are pre-defined and repetitive with built-in comment codes and other data that explain the transactions, but manually entered transactions such as journal entries are not.
I often see journal entries made by clients without any explanations; not even the journal header notes or the one-line text per GL line, let alone the memo field where one can enter a free form text memo, add simple tables explaining the entry, etc. This feature is available in all ERP and accounting software nowadays and the excuse that they only give you eight characters to record a comment (or file name) does not work anymore.
When you make such journal entries or other financial related data entry such as in putting together a corporate budget you have to ask yourself: Will I be able to remember what I just did six months from now? Will I be able to explain my work to managers, co-workers, or auditors? Will I look at the transaction in a totally different way and maybe even suspect there are flaws in it? Simple documentation, right next to the transaction will solve all that. The common excuse that documenting your work will add extra work with no real benefits is not valid.
The real benefits are significant: For a little extra work you gain confidence that the logic used during the transaction entry will still hold at any time in the future; that other employees and managers will be able to understand your work; that any internal or external auditor will have complete information on the audited transaction; and that your financial statements and internal control over financial reporting will be more robust due to this practice.
In Budget Maestro by Centage Corporation, every area of the software has a notes section, accessible through the Notes Tab on the upper right side of the screen. Users can enter an unlimited number of individual notes for every budget line in every module (Revenue, OpExp, Personnel, Debt, etc.). These notes can be filtered by user, date entered or description.
The notes can even contain copied and pasted simple Excel or Word tables. Files that back up the logic or data used in establishing budget lines can be attached to each note within each budget line. These files (e.g., Excel, Word) can be directly opened from the notes’ associated files area. With very little effort you can reveal the data and logic used to create the budget line.
Since Budget Maestro allows users to create complex models using built in business logic, Business logic and accounting rules built into the budget, it is imperative, in my opinion, that these budget lines, many dependent on other data sources, with increases or decreases during the budget year plus other logic applied (e.g., Drivers, Based Upon) be clearly documented. It will make your work easier and more productive. You will be able to clearly explain the rationale behind choosing the various logic elements that Budget Maestro offers. It will make the budget review a lot easier and you won’t get caught trying to figure out what you were thinking at the time these particular budget lines were created.
While it may seem an extra amount of time and effort to enter notes (in Budget Maestro or in any other software application), the benefits are going to be evident the first time you need to refer to one or more of these notes. Budget Maestro makes it easy to enter notes and associated files everywhere in the application, so use this feature liberally.