Yes, I'm pretty sure I've even included that use case in previous threads.
Notes: transaction-wide tag
Memo: tag just for that split
Thus, you can tag individual memos and craft a Transaction Report for
job costing no matter the nature of the original physical individual
transactions.
If you have issues with consistent spelling and capitalization of tags
(which can be fixed with a search and then manual adjustments) you can
employ regular expressions in the Filter field of the report Options.
Regards,
Adrien
On 11/14/20 8:05 PM, doncram wrote:
Gal and Adrien -- I'm curious, does "method 1", i.e. tagging, allow for
transactions having splits with varying tags? E.g., it is very common for
one entity i work with to have a purchase transaction at Home Depot with
items to be charged to different jobs, so the total expense needs to be
split out. Interfaces to allow for seeing and entering/selecting specific
jobs are needed. E.g. checkbook register needs to allow for job field on
each line. E.g. journal entry interface has to allow for a job field, so
that, for example you could make a correction moving an expense from one
job to a different job. Do you think it possible to use tagging as you do
it, to serve for coding jobs until GnuCash explicitly allowed them? --Don
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
