Contact us today: (866) 4-WEBSAN (932726)

Sunday, 11 August 2013 06:30

Using Checklists in Dynamics GP

Written by

Learn more about Dynamics GPView Dynamics GP PricingFree Dynamics GP Training

In October 2009 I wrote a blog about using Checklists in GP.  I find this blog is still useful today as I have clients wherein turnover has forced the need to document processes within the system.  Checklist are the perfect tool to allow these processes to be documented.  See my blog below:

 Lots of us make checklists for a variety of tasks from grocery shopping to complex projects.  Microsoft Dynamics GP offers built in checklists in the Routines section of every module that can help walk users through a diverse range of topics.

Once you have accessed the appropriate Checklists window, ensure the frequency is appropriate for the checklist you are about to create.  Click Add to create a link to a Microsoft Dynamics GP window.  Name the checklist item & select the appropriate in the Command (Dynamics GP window).  Once your list is complete, order the items appropriately by using the Up & Down buttons.  Now every time a user performs this particular task, all they are required to do is click the checklist item in order & populate the fields with new data.

Checklists are particularily beneficial when turnover is an issue or roles require extensive training.  Two tasks I recommend clients create checklists for are performing payroll & completing year-end.  Mistakes made performing either of these functions can have wide-reaching effects.  In my next blog, I will cover a few tasks that should be on your year-end checklist.

Payroll Checklist

 

Adam MacIntosh is a Senior Account & Project Manager with WebSan Solutions Inc, a Microsoft Dynamics GP Partner and 2013 Canadian Channel Elite Awards Finalist.  Adam can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it. or 416-499-1235 ext 213.

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.