You’re offline. This is a read only version of the page.
Hi all
I have a fun request from the treasurer at my company. She wants to make sure that no invoices are entered in twice by accident in AP. We all know there's an option that exists for that already. But she's worried about a vendor sending the invoice twice, perhaps with one of the invoices entered in through a different GP company (database), or perhaps even to a Vendor ID that sounds an awful lot like another one. For example ABC Towing (ABC001) versus ABC Towing Services (ABC002).
I've fiddled with a few ideas, but haven't made much headway. Has anyone else had a request like this, and if so, how did you tackle it??
Thanks!
*This post is locked for comments
I have the same question (0)
Two ways jump to mind,
1. Get a customisation implemented as an add-in for GP that checks on submission of that field that it is not a duplicate in your other companies, I doubt this would be very expensive.
2. Use reporting to retrospectively monitor for duplicates. A scheduled report ran each day could check the previous day's transactions through a SQL query looking for duplicates, they could then be retrospectively dealt with, or run the report before you do payment runs if you run daily payment runs.
Tim
Share
Report
All responses (
Answers (
5,713
