| Description |
This issue relates to i21 Help Desk ticket. Click the link below to go to Help Desk ticket.
[HDTN-223637 - Amount Paid in New Receive Payments changes when it should not|https://helpdesk.irely.com/iRelyi21live//#/HD/Ticket/?ticket=HDTN-223637]
This issue relates to i21 Help Desk ticket. Click the link below to go to Help Desk ticket.
[HDTN-223594 - Receive payment not functioning correctly|https://helpdesk.irely.com/iRelyi21live//#/HD/Ticket/?ticket=HDTN-223594]
This issue relates to i21 Help Desk ticket. Click the link below to go to Help Desk ticket.
[HDTN-221340 - Payment Entry > Amount Paid is changing |https://helpdesk.irely.com/iRelyi21live//#/HD/Ticket/?ticket=HDTN-221340]
This issue relates to i21 Help Desk ticket. Click the link below to go to Help Desk ticket.
[HDTN-219940 - Receive Payment Efficiency Changes|https://helpdesk.irely.com/iRelyi21live//#/HD/Ticket/?ticket=HDTN-219940]
In going with our conversation, I'm just adding this back in as it also speaks to payment efficiency .
Today's topic however was the time it will take to apply to specific invoices, rather than just oldest first. The vast majority of our customer base now pays by invoice, not by statement, and they do not always pay invoices in order - some also make rounded payments that don't match anything. My understanding of the i21 payment receipts process is to select Apply to Account if you want the payment to go to oldest outstanding invoices in order.
!pastedImage_d107101_0.png!
{color:#0f0f0f}And if they want the payment applied to specific invoices that are not in order, you have to manually enter the $$ you want applied to each invoice, rather than selecting it. In this example, all of SI-4964 is being paid, so it is just clicked in the check box, but SI-4955 gets the remainder of the payment - so you have to go and manually calculate 20,000-16,875 to find what is left, then enter that amount in the Payment box to get the payment to balance.{color}
!pastedImage_d107101_1.png!
{color:#0f0f0f}if you just select the invoice (by the check boxes), it will select as though the entire invoice were being paid, which is clearly not correct as it is more than the payment, and will not save.{color}
{color:#0f0f0f}{color} !pastedImage_d107101_2.png!
This is EXTREMELY inefficient. The system should never even look at SI-4955 and think it would be paid in full as there is not enough money to pay it. You should only be able to allocate the payment amount. There are also gaps for human error in either calculating the difference (which still will not save, but will cause more time spent recalculating once it is clearly not correct) and/or input of that amount to be paid.
Again, not trying to copy what is in Gman, but their ROA system is amazing and fast. Not only are there the low number of keystrokes discussed below, but when you are not "applying to oldest" (like Apply on Account), you just select the invoices you want to pay, in the order you want them paid - the last invoice selected gets what's left (short paid if that is how the payment is). You cannot over apply the payment - you have to either change the payment amount if it is incorrect, select a credit include in the payment (but the credit has to be selected prior to the invoice that would overapply), or short pay an invoice.
This is a big one. We run hundreds of payments a day. Having to stop and calculate the amount remaining to apply to an invoice is going to be a big problem. This is a common occurrence in our customer base.
|