It would be helpful if you could add a Payor column to the check register for deposits, etc., instead of putting the payor in the Payee column. Thanks
[Edited - Readability]
@rayrozema Maybe there's something I'm not understand with this request. Why isn't a single column fine for both Payee and Payor in the case of a deposit? When I have a deposit — whether it's a paycheck, a pension payment, a refund, etc. — I don't see what problem is created by identifying who sent the payment in the Payee column. (In some cases, like a refund or reimbursement, I find it actually helpful so that a report on that Payee includes the refund payment transaction as well.) And I wouldn't be keen on having to have the width of an extra column in my registers.
It would help me and others if you could give some examples who where or why you'd find a separate Payor column useful.
(Almost everything in Quicken is built around transactions which have a Payee, so I suspect removing that would entail some major changes in the code, but it's fine to have a feature suggestion without concern for how complex it would be to implement. 😀)
I wouldn't mind separate Payor and Payee columns as long as there was still a combined column that works the way the current column does. Kind of like how credit card accounts have separate Charge and Payment columns as well as an Amount column that works with either type of transaction. I would not want to be forced into having two different columns in the register for Payor and Payee.
I would also like to hear why there would be a need for both columns. Note that unless there is a case where both are needed at the same time, then we are simply talking about not liking the term "Payee". And if that is the case, I don't think not liking the term is justifies the work involved. Note that a column in the database doesn't just affect the register, it will affect other things like reports and other views.
Quicken Mac has a column named Memo/Notes to combines two historically separate but similar data fields, so maybe the idea would be to rename the "Payee" column to "Payee/Payor". But there are probably thousands of places in documentation that refer to "Payee" which might need to be changed, and most people have very few Payors, so I'm skeptical about the need.
As @Jon mentioned, one can have separate Charge and Payment columns — which I use instead of the signed Amount column — for easy visual separation of payment versus deposit transactions, so that's another reason I'm not sure I'd want a separate Payor column taking up more space in the register.
But maybe I'm overlooking some worthy need for this, which is why I hope the original poster will chime in and respond.
