SCENARIO/ISSUE:
Let's say, User #1 created a new vendor bank account and set to expired the existing ones.
User #2 then generates a payment proposal and tries to settle an invoice that is previously tagged with the old, expired vendor bank account.
At this point, there is no warning if the vendor bank account on the transaction is already expired. User #2 then went ahead and generate the payment, not knowing that it had the incorrect vendor bank account details.
RESOLUTION:
With the current design, users need to set the new/valid vendor bank account into the 'Alternate account' field in the payment proposal lines.
FEATURE REQUEST:
To make User #2 aware that expired vendor bank accounts are being used in the vendor payment proposal lines (before they generate and send out the payment file), it would be best to add into the Payment proposal lines form the same vendor bank account validation that now exists on the vendor transactions, where it is currently throwing the following message where applicable: 'The bank account is inactive. Select an active bank account’
The desired warning/error message is similar to it with a slight variation: 'The bank account on the line is inactive. Select an active bank account as an Alternate account’
Comments
As we have many vendors who constantly change their bank accounts this would be beneficial to Uniting account payments
Category: Cash and bank management
If the Vendor Bank is updated on an Open Invoice, then the new Vendor Bank must be the one pulled in to the Payment Journal. Currently, even though the open invoice has been correctly updated, the payment journal ignores this and pulls in the expired Vendor Bank which no longer applies to the open invoice.It seems unlikely that there would ever be a scenario where this would be the desired system behaviour.
Category: Cash and bank management
The requested feature is critical and only logical. As otherwise the vendor payment process is not seamless.
Category: Cash and bank management