A description of how Fees and Invoices might work.
I have evolved in my thinking about basic fee types from eight to four, and now to just two basic fee types. Those two are hourly rate fees and lump sum fees. The four that I thought were the truly unique types are in bold in the following list. I now see hourly rate fees and lump sum fees as the two fundamental types that bookkeeping needs to address. The other types are primarily contractural ways of describing how the fee is determined. But I am building a bookkeeping app, not a contract management app.
HOURLY RATE FEES
Estimated hourly rate fee without a maximum ::bold::
Estimated hourly rate fee with a maximum ::bold::
Hourly rate for type of work
Hourly rate for role performed
LUMP SUM FEES
Lump sum fee with lump sum phases ::bold::
Lump sum fee with percentage phases ::bold::
Simple lump sum
Fee as a percentage of construction cost
Unit cost fee
Lump sum fee with percentage phases and the fee as a percentage of construction cost are basically the same thing. The latter ties the fee directly to construction cost for contractual reasons, and so the ‘lump sum’ may change.
The unit cost fee is very similar to the fee as a percentage of construction cost because you tie the fee to a calculated number (say, dollars per square foot).
From the standpoint of contracts you have at least eight different ways to determine the fee. From the standpoint of bookkeeping there are just two types of fee, hourly rate fees and lump sum fees. This realization came to me while trying to devise ways of storing the key data of what I thought were the four fundamental fee types.
Here are two previous posts where I was feeling my way into this subject.
As I continue to feel my way into the topic of ‘Fees Bookkeeping’ there seems to be four areas where there needs to be a solution. Two of them concern the fee itself and the other two concern the invoices that request payment of the fee.
If I can get these four areas to work, I think I will have a good solution for MyCorbu. These four areas actually describe the form and table views that will be needed. Let’s look at each one in more detail.
Your fee information drives the income side of your profitability, but you cannot add your fees as income transactions until they are earned. So fees tell you about potential, rather than actual, results.
Things you want to document about fees in your bookkeeping system.
When you add a new project to your backlog of work, what are the things about its fee that you want to document?
Things you want your bookkeeping system to report to you about fees.
Periodically you will want to review your status concerning fees to determine the amount that you can invoice for work that you have completed. This same report could show you the total remaining fee to bill, which would be a rough equivalent to the size of your work backlog.
The things you will want your bookkeeping system to report to you about fees.
Determining your profitability is possible as a result of the invoice process because each invoice that you create also creates an income transaction in bookkeeping to compare to the expenses incurred.
Things you want to document about invoices in your bookkeeping system.
When you create a new invoice, what are the things that you want to document?
From a client relationship viewpoint there may be other things that you feel should be included in the invoice. From a bookkeeping viewpoint this is what matters.
Things you want your bookkeeping system to report about invoices.
When you review past invoices for a project, what are the things that you want to be shown?
I had been planning to have a single Fees/Invoices database, but it has become clear that Invoices contain a different kind of data and will need their own database.
Now the fun part begins - translating this concept into databases, forms and tables to actually implement the plan.
You can follow along by logging into the MyCorbu Test Drive account periodically and visiting the Bookkeeping >> Fees and Bookkeeping >> Invoices pages to see what it looks like and try it out for yourself.
© 2012-2020 Architekwiki