Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel1

Step 1: Complete the Payroll Transaction Entry window

  1. Select Transactions > Payroll > Transaction Entry. The following message displays: Did you know you can use the Payroll Mass Transaction Entry window instead, to enter several similar pay transactions at the same time?
  2. Select Transaction Entry. The Payroll Transaction Entry window opens.
  3. Complete the window. See the Microsoft Dynamics GP Payroll Manual for more information. Overtime and doubletime functionality has no effect on Job Cost transactions.

Step 2: Enter job-related information

To assign a transaction to a job, you must select a transaction type of Pay Code and a pay code with a pay type of Hourly, Overtime, Double Time, Vacation, Sick, or Holiday.

...

Note
Once a transaction is assigned to a job and saved, you cannot change the Product field. You must delete the transaction and reenter the information.

Step 3: Build checks

You can build checks to pay employees for their work. Conditions that apply to building checks include:

...

Microsoft Dynamics GP uses the employee pay rate when you build checks to print and post payroll transactions to the Microsoft Dynamics GP Payroll module. Job Cost uses the pay rate for the employee when the transaction is entered. If you enter job payroll transactions daily and change an employee's pay rate in the middle of a pay period, transactions may post to Payroll and Job Cost at different pay rates.


Note

If you post payroll transaction transactions to accounts in Job Cost, do not change employee pay rates until checks print and process for all transactions entered with the old pay rate.

  1. Select Transactions > Payroll > Build Checks.
  2. Complete the Build Payroll Checks window. See the Microsoft Dynamics GP Payroll Manual for information on completing this window.

Step 4: Post payroll transactions to Job Cost

The Job Cost posting process creates a journal entry that does the following:

...

Note
  • You cannot print or process your payroll if you do not complete the Job Cost Posting process.
  • See Distribution of payroll transactions below for information on how payroll transactions are distributed in the general ledger.
  • If you changed overhead detail codes (or created new codes and assigned them to affected overhead accounts) since the unposted transactions were entered, DO NOT proceed to post these transactions. Posting these transactions could result in unbalanced general ledger entries. Contact Key2Act WennSoft Support for assistance.
  • (rate classes) If you are posting payroll transactions on a daily, when you calculate checks, benefits/deductions will only be calculated for one day instead of five. Therefore, when using rate classes, you cannot run Job Cost Posting daily; only once a week.

...

  1. Select Transactions > Payroll > Signature Payroll Posting

    Note

    You can only post the batches marked by the user that is logged in.


    • Posting Date
      Enter a posting date.
    • Display Batches
      Select to display batches created by all users or by the current user only. The batches are marked in the Job Cost or Service column to let you know the contents of that batch. If a batch contains transactions attached to a job number or service call ID, the appropriate column(s) will be marked with an asterisk (star)*.
    • Status
      Mark the checkbox in this column to select the batches you want to post.
    • Post Job Cost, Post Service
      Mark these checkboxes, as desired. 

      Note

      If you are not using Service Management or you are, and the Service Invoicing feature is not registered, or the Post to Service Only option is not marked in invoice options, the Post Service checkbox will be disabled.

  2. Select Post.

...

Job Cost batches may not be available to post prior to building checks, depending upon Job Cost setup and validation performed in this window. However, a batch that contains both Job Cost and Service-related transactions will be available to a user who wants to post only the Service related contents of a batch. Unless posting to Job Cost is selected along with Service, all job-related transactions will remain un-posted unposted in the batch and only the Service related transaction will be posted and Microsoft Dynamics GP payroll transactions deleted. This allows for Job Cost and Service to be posted at separate times, as required by the business processes of each product.

...

  • Debit amounts
    Debit amounts distribute to the -labor or other general ledger account you defined for the cost code entered in the Payroll Transaction Entry window. The debit amount equals the total labor cost posted, including overhead.
  • Credit amounts
    The payroll and overhead offset credit amounts post to the default overhead and payroll offset credit accounts defined in the Revenue and Exp Account Setup window, based on a job's assigned division. The following example shows a typical Job Cost payroll posting entry. Overhead calculates automatically based on the overhead group code you assigned to the employee's department and position. See Setting up Overhead Group Codes for more information on how Job Cost automatically calculates overhead for payroll transactions.
AccountAccount DescriptionDebitCredit
000-1411-00Labor$1135.47
000-2135-00Accrued Payroll
$959.47
000-2125-00Benefits Allowed
$176.00


Step 5: Calculate and print checks.

...