Add an additional name field to the vendor maintenance window that represents the DBA information for vendors that need to report their 1099's this way. Then program the 1099 report to be smart enough to format the 1099's correctly depending on whether there is a value in the DBA name field or not.
I have dealt with DBA 1099 reporting a number of ways over many years for many clients (e.g. modifying the 1099 report to pull in the Address 3 or contact, or creating a conditional report that prints one thing if one address ID is detected and another thing if another is detected. There are probably many other workarounds as well, however simply adding a field to track this scenario seems to me to be a simple fix that would save a lot of people a lot of time and effort modifying their 1099 reports and/or updating their vendor addresses in ways that otherwise don't make a ton of sense.
When you assign a vendor to be 1099 part way through the year or at the end of the year because it was forgotten, a window should pop up with all the payments for the year and let you pick the ones that should be 1099 with the appropriate amounts.
GP needs the ability to import credit card transactions into payables a la QuickBooks.
We now can pay them with a 'credit card' check run, please give us an easy way to get the invoice recorded.
We need to track our purchases that are subject to Use Tax. This is not possible and the tax features in AP add the tax to the amounts owed the vendor.
The Use Tax is an amount we owe the tax authority for our purchases, not the vendor. It would be much simpler if we could somehow flag or tag invoice amounts or POP items that are subject to use tax.
Adding the capability to drag and drop files to attach them to transactions (typically images of invoices) within the various modules of GP, specifically, the payables module rather than having to open and attach an image/file.
In GP2015 or later, a feature was added to warn a user if a PO exists for a vendor that a payables transaction has been entered for. If you click the Go To button, the transaction you were working on gets deleted and the PO Navigation window is opened to view PO's for this vendor. The message does not appear until the save button or the post button is activated. If the transaction had multiple distributions added this information will be lost and the user would have to start over again if there was no PO and the transaction should be entered in the Payables Transaction Entry window. I suggest that the Go To button minimize the window and then bring up the PO Navigation window for the vendor instead of deleting the transaction.
Ability to drill into Payables distribution history from smartlist when you post a journal per batch optionThe Payables Transactions are set to create a Journal per Batch. If you open the Journal via Enquiry -> Financial -> Journal Entry Enquiry all works ok. You can select a Distribution line, click the Source Document Link and drill down into the relevant Transaction.
This does not work correctly when you try to drill down from the Smartlist
The Voucher Number field allows the user to enter special characters in it. There are no repercussions until later when the user tries to run the HATB report. Then they will receive SQL Errors.
If GP is not designed to handle this, then I think there should be a restriction on what is allowed on the Voucher Number field when the user is entering the data.
"Unclosed quotation mark after the character string ‘ and DocumentType = 6’ Incorrect Syntax near ‘XXXXX’"
When changing a Vendor Class ID a message box pops up that states "Do you want to update the vendor with the information from class XXXX?" The default has been "Yes" since I began using GP in 2003. Unfortunately for companies like mine that use Vendor Class ID for sorting and reporting, rolling down a change can overwrite necessary information. Can it default to "No" instead? Having to re-enter a change that all vendors in that class need, is much easier than adjusting hundreds of vendors back to their original version.
Bible League International
It would be OH SO AWESOME if you could create a way to add a negative amount to a PO. For instance, when we have a PO that the invoice comes in under the amount requested, add a line item of 1 item at negative amount to reduce the PO amount with description to document the change order reasoning.
TRACKING of this for auditing would be awesome instead of just closing the PO (which may sit out there for a while until someone checks to see what's still open and needs to be closed) and having no paper trail to show why...