Using Integration Manager to Import Payroll Manual Checks into Dynamic GP

Using Integration Manager to Import Payroll Manual Checks into Dynamic GP

Written By: John Earle of Business Ready Solutions

from September 10, 2012

The manual payroll check is not a high volume transaction in GP and can usually be done as one-offs when necessary. However, when the need arises to import these checks in bulk the integration can be very intricate.  In this article I hope to provide some useful information and screenshots for anyone in the future that may find themselves in the same situation.  This article assumes that you are familiar with the basic functions and operation of IM and will not spend time going over the basics, for information related to basic use of IM there are ample video walkthroughs that can be accessed via YouTube.

The Import File

This is a screenshot of a sample integration file in excel view.  All the columns here are required for importing a manual check except for Transaction Type which is purely for me to know what each line meant for troubleshooting reasons and BATCHID which can be used as a constant or have the user enter an ID upon import.  You could also add other columns such as Checkbook ID if you were going to be integrating checks using multiple checkbooks.

The Integration:
Sources – Grouping
It is vital that the grouping be correct on the import of manual checks.  Incorrect grouping can cause multiple weeks of data to be imported into one check batch, or duplication of data across multiple batches. I suggest grouping by Employee ID, Payroll Run Date throughout the integration in order to pull the data in correctly for each check.

Header Mapping

As you can see in the mapping I am allowing IM to use default values for several of the fields. In this instance I am using a constant for Checkbook ID but this can also come from the source file as mentioned previously.
Transaction Mapping

Under the transaction mapping I am allowing GP to choose the transaction number for each transaction that I am bringing in, I found this to work much better than attempting to use my own number due to duplication.  Most of the unmapped information in the transaction mapping screen will default from the employee cards based on the ID that is used in the integration.  I found this mapping to work the best for the data set I was working with and I was able to integrate hundreds of manual checks without issue.

Hopefully the tips and screenshots mentioned can save you some time if you are ever in need of integrating manual payroll checks using Integration Manager in Dynamics GP.