The Advantage of Payroll Posting Accounts in Microsoft Dynamics GP

By Kyle Rehome | July 19, 2018

The advantage of payroll posting accounts in microsoft dynamics gp

Payroll posting accounts in Microsoft Dynamics GP allows for very granular control over the General Ledger accounts that are used when processing payroll checks. Wages, taxes, deductions, and benefits all have their own setup for determining which accounts will be used, and within each of those, you can break down the posting by the department and position of the employee.

The Payroll Posting Accounts Setup window (Microsoft Dynamics GP > Tools > Setup > Posting > Payroll Accounts) is broken down based on the type of payroll transaction that is being processed. The following types are available:

  • Gross Pay (DR)
  • Federal Tax Withholding (CR)
  • State Tax Withholding (CR)
  • Local Tax Withholding (CR)
  • Deduction Withholding (CR)
  • Employer’s Tax Expense (DR)
  • Benefits Expense (DR)
  • Benefits Payable (CR)
  • Taxable Benefits Expense (DR)
  • Taxable Benefits Payable (CR)
  • SUTA Payable (CR)*
  • FUTA Payable (CR)*
  • W/Comp Tax Expense (DR)*
  • W/Comp Tax Payable (CR)*

*These accounts are used when posting the SUTA, FUTA, or Worker’s Comp taxes in the Period End Routines window, rather than during normal Payroll Computer Checks or Manual Checks.

Each transaction type will post either a debit or a credit, as noted in the transaction type options. For Benefits, we have control over both the Expense and the Payable side of the transaction – If we choose to set these as the same account, the benefit will not post to the GL at all, as GP will summarize the distributions and they will wash out to be zero.

Within each transaction type, we can add lines to allow for a more detailed segregation of payroll posting. Each line contains a potential combination of Department, Position, and Code (Pay code, Deduction, Benefit, or tax type) that could apply to a payroll transaction.

Dynamics GP uses “ALL” to represent a wildcard for that line. This means that it doesn’t matter the value of the specific dimension, it works for this line.

The default setup for most transaction types is to have a line for “ALL ALL ALL.” This line is the “catch-all” line, such that if GP is unable to match up the Department, Position, and Code to a more specific line, it will use this one. If we do not need to break down the specific transaction type based on the employee’s Department or Position or Code, then all we need is “ALL ALL ALL.”

To add a new line to the Payroll Posting Accounts Setup, just click anywhere on the next blank line. The default values will be “ALL ALL ALL,” but we can fill in the line with the desired values for Department Position and Code. Leave the value of “ALL” for any dimension that we do not need to match specifically. Then enter the Account that we want to use for this combination of values.

We can also post the values to a Unit Account, but this functionality is not commonly used with Payroll Posting Accounts.

Continue adding lines to the Payroll Posting Accounts until we have covered the possible combinations where we want to use different accounts.

The hierarchy used by Dynamics GP when determining the posting account to use can cause some confusion. Dynamics GP will always look to match specific values before using the “ALL” wildcard, and will match starting with Department, then Position, then Code.

For example, we have set up lines in the Gross Pay (DR) account type for “ADMN ALL ALL” and “ALL ALL HOUR” (where ADMN is a Department and HOUR is a Pay code). If an employee in Department 01 is paid using the HOUR pay code, GP will use the line for “ADMN ALL ALL” rather than “ALL ALL HOUR” because it prioritizes the match on the Department before the pay code.

Payroll Posting Accounts

This means if we want to have different posting accounts based on the employees Department AND Paycode, we would need to setup Payroll Posting Account lines for each possible Department and Paycode combination (using ALL as the Position value). It is still a best practice to use the Wildcard for each Department so that as new codes are added into the system if we forget to update the Payroll Posting Accounts Setup we can still easily identify which Department the posting came from.

Payroll Posting Accounts

Here are a few things to keep in mind as we are setting up Payroll Posting Accounts:

  • A specific value always matches before ALL.
  • If we are breaking down values for a specific Department or Position, be sure to include an “ALL” line for the Code so that we have something in place if GP cannot match the specified value.
  • If we add a line and use an account that has already been used in the Payroll Posting Account setup, GP will provide a warning. This is informational and will not prevent we from using that account again, but we may want to review and make sure we are not doubling up on Accounts when it is not expected.
  • Each transaction type needs to have an “ALL ALL ALL” line. This is required, and if it is not populated, we will receive errors during the Build and Calculate process of Payroll checks.

“Not all required payroll posting accounts have been assigned. Checks cannot be built”

Payroll Posting Accounts

  • To delete a line, right-click the line and choose “Delete Row.”

If you’d like to learn more about payroll and Dynamics GP, let us know!

Related Posts

Recommended Reading:

Managing Your Business Through Uncertain Times Using Dynamics 365 Finance and Operations

  Dynamics 365 Finance and Operations (F&O) can help you make informed decisions on how to move your business forward. […]

Read the Article
5.13.22 Power Platform

Using Power BI Object Level Security

  The following article will demonstrate how to use Power BI Object Level Security to disable column data based on […]

Read the Article
5.12.22 Dynamics CRM

How to Use the Stoneridge Support Portal

Stoneridge Software’s support portal is an intuitive and useful function that makes it easy for you to access resources to […]

Read the Article
5.6.22 Dynamics GP

Dynamics GP Transaction Removal: Purchase Orders

  Are you having performance issues with Purchase Orders?  Do you find that there are old Purchase Orders on your […]

Read the Article
5.5.22 Dynamics GP

The Real Story about the Long-Term Future of Dynamics GP Support

I’ve seen a number of people put forward comment that Dynamics GP is going away and you have to get […]

Read the Article

New Features in Dynamics 365 Business Central 2022 Wave 1 Release – Financial Enhancements

The Dynamics 365 Businses Central 2022 Wave 1 Release has a lot of new and exciting features to help your […]

Read the Article
4.29.22 Dynamics GP

Dynamics GP Transaction Removals: Bank Reconciliation

  This is part 2 of a 3 part series on Dynamics GP Transaction Removals. These quick tips will hopefully […]

Read the Article
4.28.22 Dynamics GP

Uncommonly Used Features – Integrate Purchasing and Payables to Fixed Assets in Dynamics GP

Being able to integrate Purchasing and Payables to Fixed Assets in Dynamics GP will help you create visibility for your […]

Read the Article

New Features in the Dynamics 365 Business Central 2022 Wave 1 Release – Ease-of-Use Features

  There are many new features in the Dynamics 365 Business Central 2022 Wave 1 Release to get excited about! […]

Read the Article

Start the Conversation

It’s our mission to help clients win. We’d love to talk to you about the right business solutions to help you achieve your goals.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!

X