It there’s a field for
Payee, then I should put the payee in that field, and the program should use that field accordingly. It makes no sense to have to type the payee in the
Payee field and then to type it again in the
Description field. It makes no sense either to have to ignore the
Payee field and to put the payee as unstructured data in a different field.
The built-in invoices seem to be smart enough to know that if the
Payee fields on an invoice are all empty, don’t print that column.
How about this: Instead of a separate
Payee column, the invoice should print both fields concatenated together in the
Description column, just as it already does with dates in most places.
So instead of this:
Do this, where Description column =
Date & “-” &
Payee & “,” &
My point here is that structured data should be entered into the proper structured field: Payee into
Payee and description into
Description. But to enhance information exchange with customers, the contents of the
Payee field could be incorporated into what is printed under the Description column on invoices. This should meet @Tut’s objection while solving the issue I raised that some items are not meaningful if the contents of the
Payee field are not made visible, and it is consistent with the handling of dates, for example, in other places in Manager.