Micro Force -Velosio Newsletter Feb 2020 - Microsoft Dynamics GP Business Software System
As we slowly inch our way towards Spring, we look forward to continuing to provide you with various offerings to help you and your team get the most from your Microsoft Dynamics GP business software system. Read below for information on free webinar opportunities, helpful Dynamics GP features and more. And as always, feel free to reach out to us to schedule your annual business review if you have not done so already in 2020!
What Is the GP Process Monitor?
The GP Process Monitor is a GP function that permits you to see what processes are running. Dynamics GP will run various tasks in the background and sometimes it seems that nothing is happening, especially when printing large reports. Check the Process Monitor (Microsoft Dynamics GP>Process Monitor) to see what tasks are running or waiting to run. Tasks with a (>) sign in front of them can be deleted (useful if you have run a report several times while waiting for it to print). You can highlight the process and click Remove.
AR Statement Automation in Great Plains We have a Great Plains client who has to email AR statements to their clients each month. Their clients also requested that they forward a copy of each of the open invoices that were listed on their AR statement, along with any worksheets for those respective invoices. We were able to provide them with a fully automated solution for this requirement. We accomplished this by introducing them to a third-party enhancement product from a vendor named Liaison Messenger. So as opposed to spending a good part of a full day to complete this task, they can now do so in less than 30 minutes using this solution! No longer do they need to print each open invoice to a PDF. Scan each worksheet and save that in a folder for each of their clients each month. Then generate the email for each customer one at a time and, before sending out that correspondence, go to that client’s folder and attach each open invoice and worksheet, one at a time. Compare that to selecting an emailing of statement process that can be run for all or a subset of their customers in one step. Start the process and this solution then automates this entire process by going to the appropriate folder on their system to accomplish the same. This is because PDFs of invoices are automatically being saved each day, along with any printed copies from Great Plains in such a manner to automate this process. For further info including pricing for this solution, please email email@example.com.
Using Credit Cards to Pay Vendors in Dynamics GP Does anyone in your organization have a corporate credit card that they use to purchase services or merchandise? Do you currently process these in your Great Plains system in the payables module so that you can get vendor reporting visibility? If not, please read that following article, which was written by one of our extended team members, as noted in the article.
And if you would like to automate the effort of downloading the credit card information into an Excel worksheet that could then be used to electronically create Great Plains payable vouchers for each material vendor, please email firstname.lastname@example.org to schedule this service. There are typically three important goals that companies have when paying their vendors with credit cards:
Most of the purchases need to be recorded against the actual vendors. Especially for inventory purchases.
Monthly credit card statements need to be reconciled quickly so there is no delay in paying the bills and no huge unapplied payments sitting in GP because it takes so long to reconcile and enter the statements.
There are many ‘one time’ or ‘miscellaneous’ vendors that are paid with credit cards. While it is not important to track these purchases under individual vendors (as in # 1 above), it is still important to keep track of who the vendor was and to make it easy and fast to reconcile these purchases on the statement (as per # 2 above).
Keeping these goals in mind, let’s walk through a few examples. I will be using an older version of Dynamics GP for the navigation and screen shots, but this process is the same in any version of GP. First, we need to create a payables vendor for each credit card. The important step here is to create a different vendor for each distinct account that you get billed for or pay. If you have three American Express accounts that get billed and paid separately, create three vendors. For our example I will create one AMEX vendor (Cards > Purchasing > Vendor):
Next step is to set up a Credit Card (Microsoft Dynamics GP > Tools > Setup > Company > Credit Cards). I typically use the Vendor ID for the Card Name (unless your vendor ID is something like 12345). To set up a credit card to pay vendors select Used by Company, choose Credit Card and enter the Vendor ID associated with the credit card vendor:
That is all the setup required. Now you are ready to enter transactions. There are a number of typical scenarios: Scenario 1: You purchased non-inventory items from a vendor want to track and pay them with a credit card. You have not posted the invoice yet. This can be handled in one transaction (Transactions > Purchasing > Transaction Entry). Enter the transaction like you would normally enter a non-inventory payables invoice, then enter the amount you paid with the credit card on the bottom right:
When you tab off the Credit Card amount, the Payables Credit Card Entry window will pop up. Choose the credit card and date. Important: to accomplish our goal # 2, we need to change the Receipt Number to include whatever will help us match this purchase with the line item on the credit card statement. This Receipt Number will become the invoice number under the credit card vendor. Typically the date and the ID (or name) of the vendor you are paying is enough:
Note that I put the date in a little strangely: 081219 for December 19, 2008. This is by no means a requirement, but a ‘trick’ that I have gotten used to as a nice additional sorting mechanism for my transactions. I will remind you of this a little later on in the example. If there are multiple charges from the same vendor on the same date, you will need to come up with unique Receipt Numbers, so either use the last few digits of the Document Number (081219 STAPLES 462), add a letter to the end (081219 STAPLES A) or something similar. While you may not be able to fit the entire vendor ID or name in here, usually you can get enough in to allow easy reconciliation. The GL distributions on this may be surprising if you have not entered similar transactions before:
It is crediting the Accounts Payable account because you still owe that money to the credit card vendor. However, the type of that distribution is CASH because you are entering a ‘payment’. If you have a different Accounts Payable account set up for the credit card vendor, you will see that account here, not the Accounts Payable account for the vendor you are entering this transaction under (STAPLES in this case). Once posted, what this will accomplish:
Creates an invoice under the STAPLES vendor.
Creates a payment under the STAPLES vendor and applies it to the invoice in # 1 above.
Creates an invoice under the AMEX vendor. This invoice is open (unpaid) at this point.
Scenario 2: You have already posted the payables invoice under the correct vendor or you have purchased inventory items and have posted the invoice in POP. Since the invoice is already posted, we just need to enter the payment side, which is done as a Manual Payment (Transactions > Purchasing > Manual Payments). The Vendor ID will be who you are paying, the Payment Method is Credit Card, once you choose that you will see a lookup for the Credit Card Name. For the Document No. enter the date and the vendor you are paying as this will become the invoice number under the credit card vendor. In this example, we have already posted an invoice for DELL, now we are recording that we paid them with a credit card:
Enter the amount paid by credit card and Apply just like you would any other payment. Again the GL distributions may not be exactly what you are expecting:
The CASH type distribution is recording the payment, but since it was made with a credit card and not cash, it is crediting Accounts Payable (this will be the Accounts Payable account from the credit card vendor). The PAY distribution is recording the payment to the original vendor (DELL in this case). Basically, this transaction moves the liability from one vendor to another. Once posted, this will add a payment to the DELL vendor and an open invoice to the AMEX vendor:
Note the order of the transactions for the AMEX vendor – they are sorted in correct date order, even though they are in different years. This is because of how I entered the date with the year first and using 6 digits. Again, not a requirement, but it makes your credit card vendor invoices sort automatically with the default sorting GP uses. Scenario 3: You purchased something from a ‘one time’ or ‘miscellaneous’ vendor using a credit card. You do not really want to clutter up your Vendor list, as you might only buy from this vendor once or twice. This should be entered as a payables invoice directly under the credit card vendor (Transactions > Purchasing > Transaction Entry). The vendor ID will be AMEX in my example and the Document Number will have the date and the name of the vendor. I also put the full name of the vendor in the Description, as there any many times with this scenario where the full name will not fit into the Document Number:
Having the full name in the Description will make it much easier to search for this vendor in SmartList. Once posted, this will show as another open invoice under the AMEX vendor. When you receive your credit card statement, open the Payables Transaction Inquiry window (Inquiry > Purchasing > Transaction by Vendor), uncheck History and Work, and you will have a list of all open (unpaid) transactions to reconcile to the statement. And if you have used my date ‘trick’ they will even be sorted very closely to what should be on the statement:
Of course, you can get this list of transactions in SmartList as well and export it to Excel if that is preferable. Typically I find that with this method I just check off the transactions I already have in GP on the credit card bill and circle the ones I still need to record. This method is certainly not for every company out there paying vendors with credit cards. However, it may provide some solutions for many. My goal is simply to offer options. I have gotten feedback in the past that this method is very time consuming because you have to enter all the individual transactions instead of one transaction for the entire credit card statement. As noted at the top of this article, if you would like to learn about the various options to automate this task, please request so by emailing email@example.com. Original Source: Yudin, Victoria. “Using credit cards to pay vendors in Dynamics GP” Ramblings and musings of a Dynamics GP MVP (blog), January 4, 2009.
Lunch'n'Learn: SmartList Tips & Tricks Thursday, February 27, 2020 - SmartList Tips & Tricks We would guess that you are currently using SmartList on a regular basis to complete your daily activities in Great Plains. Maybe you are using the out-of-the-box reports. Or maybe you have learned many of the advanced features to create your own. In either case, we believe that you could benefit from this free class, which will cover some basic but also some very advanced features that have been added to SmartList over the past decade. To sign up for this free Lunch'n'Learn, which will be held on Thursday, February 27th from 12:00 pm to 1:00 pm EST, please click here to register.
How to Change Your GP Password Here are the steps to change your GP user password:
Click on the Microsoft Dynamics GP icon on the top toolbar and select 'User Preferences'.
Next, click on the password button located on the right-hand side of the screen.
Type in your old password, then type in your new password twice. Click OK to save your changes.
For more info about your GP system and business software in general, visit our blog site at https://www.micro-force.com/blog
Thank you once again for choosing Micro Force, we truly value our partnership together and the opportunity to serve your business solution needs! Sincerely, Jim McCann Jim McCann Partner, Senior Sales Analyst and Software Consultant Micro Force, A Velosio Affilate Phone: (631) 421-1030 x 302 / (212) 777-7029 x 302 Email: firstname.lastname@example.org