In reviewing support tickets I found that administrators stated the need to be able to allocate by GL Code and I would like to offer a discussion on how we can improve the way in which payments are allocated to invoice items.

If an invoice has a membership and a dues rule should you be able to tell the system to apply all paymens to the membership first until it is paid and then apply payments to the remaining invoice items?

When I research online I find rules such as:

• By GL Code
• By Oldest item first
• By even percentage of the payment (which is what we currently do in YM)

I welcome your thoughts and expertise in this area.

I'd even love to see it more complex than this, so that both a user and an admin can go in and allocate the payment on an invoice by invoice basis (as they can now), but more specifically to individual items on an invoice. So for instance if an invoice includes an event registration + fee for a ticketed event, a member could pay for the event registration piece specifically using their employer's payment method (whether credit card or check) and the ticketed event with a personal payment method. As it stands now, the first payment is applied proportionally to all invoiced items, which means individuals whose employers are specific about what they should be paying for are technically not in compliance.

In general, though, I'm in support of payments being applied first to outstanding dues invoices, and then to other outstanding invoices

I agree with PP - I'd love to see this able to be controlled by either the admin or member/user. The current setup of even percentage point can be an accounting nightmare right now, and can cause confusion when following up with a member on outstanding balances.