I know it's been said (probably by me) but I think when you sit down and try to put the information you're requesting into a report format (rows and columns), the format breaks down as complexity increases. If it was just invoice A paid by check A, B, C, then you're all good. But imagine my company where an invoice can be paid by multiple checks, checks can pay multiple invoices, payments can be refunded, invoices can be credited, credits can be voided, balances can be present, credits can be partially applied and have balances, Overpayments can be incurred, and JE's are used as necessary. The report would need to reflect all that if it were to work all the time, but data modelling in a row and column format (which all qb reports are) does not work. 

The solution that's been provided by others: Use the Memo field in the payment window to list invoice #'s. We do that as well, and I'm literally looking at a customer transaction report with Payment #### followed by Inv###'s for each. It's super simple, (screenshot attached).

I remember when I got my Nintendo Wii. It plays game disks but not DVD's. No matter how much I wanted to watch the Matrix on my Wii, it was not going to happen.

The other issue may be: 15 people asking for something is just that. When did we start thinking we were always going to get our way?