@Yaser, your recommendation and related discussion was moved to a new topic. It has nothing to do with the topic on receipts where you posted it. Please do not divert topics with unrelated issues.
Your suggestion is not possible for a simple accounting reason. You are suggesting that a single payment transaction include payments from multiple sources. But a payment can only be from one source. Every movement of funds into or out of the business involves a single counterparty.
@Ealfardan is correct that what you describe is more appropriately recorded via expense claims. Even then, an expense claim can have only one expense claim payer.
That’s true, but the ultimate payment can include as many expense claims as needed.
Aside from the fact that it better to maintain a 1 to 1 correspondence between your records and actual transactions, adding such a field in payment lines wouldn’t do you anymore good that using a custom field since this field will fail to fit into the design of the software since the contacts (i.e. employees, customers, etc) are children of control accounts that were not used in the example you provided.
So either you:
Go through the normal process of recording individual expense claims which can be later paid in a bulk payment.
Skip the expense claim and create separate payments each addressed to a contact
Create a single payment and use a custom field to hold the payee per line.
The problem with that, @Ealfardan, is that @Yaser wants to record multiple payers per transaction, not multiple payees (which would also be illogical). He overlooks the fact that the only payer for any payment transaction is the business itself. What he wants is an impossible situation
Why should I make 10 transactions for 10 payments that have been done by 10 employees?
while I can make 1 payment with 10 lines and save time and effort,
forget about Paid by … just to add the ability to add a custom field to the line of payments … that would help big time
As @Tut already explained this is not possible nor is it correct. Each payment is a financial transaction from a single payer to a single recipient. So if you have multiple transactions by multiple payers then each of them is a separate payment. If you want to speed up such process then use batch create payments.
What started out as a feature request for line item custom fields veered into @Yaser’s real desire, the ability to enter multiple, separate payments by multiple parties on a single payment form. Adding the capability for line-item custom fields on payment forms, despite being what was originally requested, would not satisfy @Yaser’s goal.
I thought my response was clear, @Yaser wanted to use a single payment entry where each line would represent another source. There was no dispute about using custom fields for line items in payments and receipts.
All I’m asking is to have a custom field in Payment’s lines, Using it after that for any purpose it is up to the user of the system according to his business nature or goal
but I got a strong rejection and the subject was closed permanently
so all I can do is to wait till you make it someday in the future, which will be needed for sure