PO Prepayments in Dynamics GP

How do you handle purchase order prepayments in GP? Well, very easy: Dynamics GP allows the user to specify a prepayment amount directly in the purchase order entry screen, and then provides a simple workflow for the payment to be issued through the normal vendor check runs process. Let's see …

First of all, you need to activate and configure the prepayment functionality. This is done in the Purchase Order Processing Setup window. This setup allows to specify various options, the most important of which is the prepayment suspense account to be used to offset the bank when issuing the vendor prepayment.

Screen Shot 2017-07-12 at 11.41.52 AM

Once activated, we can begin entering prepayments when needed. When creating a purchase order, the user can now specify a prepayment amount in the designated prepayment field; the user can also open the Purchasing Prepayment Entry window to specify other options depending on the setup options chosen (for this example, we are using a check payment).

Screen Shot 2017-07-12 at 11.42.24 AM

When printing the PO, the prepayment amount appears in the document as shown here:

Screen Shot 2017-07-12 at 11.42.53 AM

The next step in the process is to actually issue the payment. Part of the beauty of the prepayment process is that it is seamlessly integrated to the normal check selection and printing from payables management, so the learning curve is non-existent. The prepayment amounts are selected in the same way any other invoice payments are selected; the user simply needs to specify that is is looking for prepayment amounts when creating the check batch as shown here:

Screen Shot 2017-07-12 at 11.45.09 AM

When building the checks batch, Dynamics GP will identify and select purchase order prepayments, as shown here:

Screen Shot 2017-07-12 at 11.45.57 AM

The rest of the check printing process is the standard one in payables. After that is done, the next step is the receiving of the purchase order, which will reflect the original prepayment automatically as shown below:

Screen Shot 2017-07-12 at 11.47.04 AM

As you can see managing purchase order prepayments is a very well integrated process, integrated seamlessly with the check printing and PO receivings in a way that it is simple to learn and use.

So, how do you handle prepayments in Dynamics GP? Well, very easily!

Awesome New All-in-One views!

All-in-One Views (AIO) are an exceptional new feature that allows the user to easily track the complete cycle for a particular transaction or group of transactions. AIOs have been introduced in Dynamics since version 2015 with the first one being the Purchasing AIO, but in GP2016 we now have new Sales and Inventory AIOs to go with it. This makes for easy review of the transaction flow for any documents selected by the user. Read More...

How to correct Vendor 1099 information in Dynamics GP

Every year there comes a time when you need to deal with 1099 reporting. And this process can be stressful for many. Along the year, some vendors may have been setup incorrectly, the some transactions entered and posted, then the vendor corrected, and so on. You get the idea. The following is a step-by-step guide that shows how to correct 1099 vendor and transaction information in Dynamics GP 2015 R2.

Dynamics GP Landed Costing

Landed costs in Dynamics GP are the additional costs that might be associated with purchasing a product. This includes all transportation fees (both inland and ocean), customs, duties, insurance, crating, handling and payment fees.

Dynamics GP has great functionality related to landed costs, allowing customers to manage the process end-to-end. This is a quick example of how Landed Costing works in Dynamics GP. Read More...

How to create a quick sales return

Sometimes it is the simpler functions that users miss. Such could be the case for sales returns. When creating a return, many users don't know a very nice sales returns feature provided by Dynamics GP. Since version 2010 Microsoft unleashed some of the functionality of the Field Service module so that users could take advantage of it in other modules, and one of them is a quick sales returns function described here.