Submit Your Suggestions for Vista

volume info... 2021 = 43,255 AP invoices processed currently APUI contains almost 2,000 invoices - 400 of which are 2022

Not sure what kind of volume you have, but we are talking about thousands of invoices for us... we want to keep the rejection info from the APUI rejection - vs. manually writing this up - it is just not feasible with our volume. If you change the line item, you lose the Approver/Rejection info.

We change the amount of the invoice to $0 and post it with notes. If the vendor tries to resubmit an invoice it flags as DUPLICATE and if we need to see what happened, all the notes and correspondence is attached without paying out.

really need this! We have years worth of invoices sitting in AP Unapproved and it stops us from being able to close jobs, etc. BUT we really need the history, the invoice number for duplicate validation and notes on rejections. We have not come up with a way to book these at $0 and keep necessary info.

If you are not going to pay it, tell the vendor to issue a credit memo, in APUI, then approve both and apply them to each other. Otherwise, make up a credit memo and apply it to the open invoice. This sounds more like you can change the process and keep your APUI clean and have the APRef in history to avoid duplication.

BTW - totally agree a HOLD code is not adequate and leaving years worth of AP invoices in APUI is just BAD PRACTICE.

This is a huge issue for us too. We have APUI records back in to 2013 because we do not want to lose the record of the invoice AP Ref so the system can see it is already in the system, but we are NEVER going to pay it. It is not unusual to have multi-year jobs where this history with your sub is needed!

An entry has to be made to correct PO, JC and GL.  Enter a credit memo, put a note on it and clear it with existing functionality.  Or create a stored procedure that does that for you, reversing the dollars of course.  There is also the timing difference, if the PM marks it as DNP after the month is closed, the entry will be 'floating', with no AP detail to match.

Putting the invoice on hold still applies cost to the project/job number. This is unnecessary. A DNP function would be great, or if the rejected invoice could remain rejected and not need to be deleted from the system with no record of its rejection.

This would be very helpful. Right now, we enter "rejected" invoices (that will never be paid) as $0 with notes on why we're not paying it. Even though we have explained this process to our Ops team, they still get confused and are afraid we're going to pay it anyway. By adding the DNP function would help when statements are being reviewed by others not close to the invoice to see that it has been reviewed, but we are not paying it (as well as seeing the reasons). Plus, gives Ops the added confidence the invoice will not be paid.

Even though you can do this today as described above using hold codes, we understand the additional work involved and will evaluate ways to improve workflow.

In this case the invoices will never be paid, they're not just put on hold for future payment. We have multiple companies, so sometimes it would be nice to have that note in the system that the invoice was sent to another company for payment (and have the system alert you that the invoice is already in there, but under DNP). There's other situations that would be nice to have this for as well of course.

You're describing putting an invoice "On hold".  When you have an invoice in your AP payment workfile that should not be paid, click "Tasks" then "Additional Pay Control Functions" then select your "Hold Code" and update.  Invoice will not be paid until you remove the hold.