What's new: Payroll features

Article
11/29/2021

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2

Payroll processing was redesigned in Microsoft Dynamics AX 2012 R2 and now provides a more consistent user interface. Additionally, setup and data entry have been simplified.

What’s new in AX 2012 R2

Overview

Item	Description
Required	Optional. You might not use these features, depending on how you run your business.
Feature areas affected	Accounts payable Human resources General ledger Project management and accounting
Stakeholders	Business decision makers Technical decision makers Implementation team members Independent software vendors (ISVs)/developers Partners

Required

Optional. You might not use these features, depending on how you run your business.

Feature areas affected

Accounts payable

Human resources

General ledger

Project management and accounting

Stakeholders

Business decision makers

Technical decision makers

Implementation team members

Independent software vendors (ISVs)/developers

Partners

New functionality

Payroll now handles mandatory deductions for garnishments (such as child support orders) and tax levies. When there is more than one garnishment order for a worker, the calculation sequences make sure that each garnishment is handled correctly, and that the combined deductions are not more than the amount that is legally allowed.

Before you can generate pay by using Payroll, positions must be assigned to workers. Position settings are used to control how earnings are generated. These settings are also used for workers’ compensation, general liability insurance, and unions.

Many payroll settings are now date effective. The date-effective settings make it easier to maintain data for which changes must be tracked at different times. For example, if a worker notifies you that her residence will change in a month, you can enter the future-dated change immediately. The current residency information is used until the effective date that you set up for the new information, and then the new information is automatically used.

Special considerations

Payroll data and settings from Microsoft Dynamics AX 2009 can be migrated to Payroll for Microsoft Dynamics AX 2012. Due to the wide range of enhancements, many new settings must be configured before you can run payroll for the first time after migration.

Benefits and deductions have changed extensively from AX 2009. Benefit setup and the determination of eligibility for benefits are both handled in Human resources. Setup for deductions and contributions is performed in Payroll. Workers can be enrolled in benefits from either Human resources or Payroll.

The processes for posting payroll and issuing worker payments are now separate. Additionally, some terms that were used in AX 2009 have changed in AX 2012 so that they better match standard usage in the payroll industry.

Term used inAX 2009	New term for AX 2012	Comments
Benefit	Benefit accrual	Benefit accrual plans for sick leave and paid time off can be set up in forms that you open from the Setupgroup on the Payroll area page.
Fringe benefit	Benefit	Fringe benefits have been merged with all other benefits in AX 2012. What was known as a fringe benefit in AX 2009 is now a benefit that has an employer contribution but does not have a worker deduction.
Imputed earning	Fringe benefit	An imputed earning is now a fringe benefit that workers are taxed on, such as life insurance, even though the workers do not receive an increase in pay.
Pay elements	Earning codes	Pay elements that were previously combined, such as deductions, contributions, and union fringe benefits, are now separate and are referred to as earning codes.

Comparison with AX 2009

Payroll has changed considerably since AX 2009. AX 2012 includes the following new functionality:

Handling for garnishments (such as child support orders) and tax levies
Position settings for payroll

The following Payroll functionality has changed for AX 2012:

Payroll taxes
Benefit accrual plans, such as paid time off and sick leave
Generation of earnings statements
Generation of pay statements
Earning codes to identify the type of earnings that workers receive for their services
Worker settings for payroll
Benefits and deductions
Posting and issuing pay

Handling for garnishments (such as child support orders) and tax levies

What can you do?	AX 2009	AX 2012	Why is this important?
Set up deductions to process garnishments (such as child support orders) and tax levies.	Not available.	Set up garnishments and tax levies by using the same forms and controls that you use to set up benefits.	Data entry is simplified.
Enter and store the state and federal requirements that are used to determine disposable income.	Not available.	Specify percentage-based limits and other data that is required to make sure that a garnishment or levy does not reduce a worker’s net pay below the minimum that is set by federal, state, or local governments.	Your payroll process complies with applicable legal requirements.
Correctly calculate deductions for one or more garnishments or tax levies.	Not available.	Specify the amount or percentage of wages to deduct, and the lifetime limit for the garnishment, if applicable. You can also specify the order in which deductions are calculated and the maximum percentage of the base wages that can be deducted.	Net pay is calculated correctly.

Position settings for payroll

What can you do?	AX 2009	AX 2012	Why is this important?
Use position settings to control how earnings are generated.	Not available.	Specify the legal entity that the position is paid from, and set the typical hours that are worked per year and per pay cycle for the position. You can also select whether to generate pay based on salary or a schedule.	The amount of data entry that is required when workers change positions is reduced, and the risk of payroll errors is minimized.
Set up workers’ compensation, general liability insurance, and union settings for the position.	Not available.	Assign default values to positions, so that you can control the standard worker settings.	The amount of data entry that is required when workers change positions is reduced, and the risk of errors is minimized.
Set up accounting details, such as financial dimensions and template support, for the position.	Accounting details were set up for the worker.	Assign default values to positions, so that you can control the standard worker settings.	The amount of data entry that is required when workers change positions is reduced, and the risk of errors is minimized.

Payroll taxes

What can you do?	AX 2009	AX 2012	Why is this important?
Use position settings to control how earnings are generated.	Not available.	Specify the legal entity that the position is paid from, and set the typical hours that are worked per year and per pay cycle for the position. You can also select whether to generate pay based on salary or a schedule.	The amount of data entry that is required when workers change positions is reduced, and the risk of payroll errors is minimized.
Set up workers’ compensation, general liability insurance, and union settings for the position.	Not available.	Automatically assign default values to workers’ positions, so that you can control the standard worker settings.	The amount of data entry that is required when workers change positions is reduced, and the risk of errors is minimized.
Set up accounting details, such as financial dimensions and template support, for the position.	Accounting details were set up for the worker.	Automatically assign default values to workers’ positions, so that you can control the standard worker settings.	The amount of data entry that is required when workers change positions is reduced, and the risk of errors is minimized.

Benefit accrual plans

What can you do?	AX 2009	AX 2012	Why is this important?
Keep a detailed audit history of all changes that are made to workers’ benefit accrual balances.	Balances could be updated, but no records were kept of when changes were made and who made them.	Audit records are created for every change in the balance of an accrual plan, regardless of whether the changes are made manually or as part of an automated process.	The integrity of benefit accrual data is better protected.
Accrue balances based on either the worker’s hire date or the seniority date.	Accrued balances were based on the hire date only.	You can specify the basis that is used to accrue benefits under a benefit accrual plan.	You have more flexibility when you design benefit accrual plans.
Configure multiple earning codes to deduct the balances of a plan.	A single earning code was used for each benefit accrual plan.	You can set up as many earning codes as you require for each benefit accrual plan. For example, you could use separate earning codes for positions in different legal entities.	You have more flexibility when you account for benefit accrual plans.

Generation of earnings statements

What can you do?	AX 2009	AX 2012	Why is this important?
Automatically generate earnings.	Earnings were generated based on a set of working days in a week.	Generate earnings based on either salary or a schedule.	Most manual entry is eliminated, and the risk of errors is reduced.
Manually generate earnings. You can manually generate earnings that are not related to worked time or to leave.	Earning information was entered through employee attendance.	Enter the earning information on an earnings statement.	You have more flexibility when you enter earnings that are not generated as salary or from a schedule.
Release earnings for payment processing.	Not available.	Releasing earnings is a stand-alone procedure that designates the earnings as ready to be processed in a worker payment.	The release procedure validates that the accounting distributions for the earnings are completed.

Generation of pay statements

What can you do?	AX 2009	AX 2012	Why is this important?
Track pay statements that are generated as part of a group in a single payroll run.	Not available.	Batch numbers are automatically assigned when you generate pay statements.	Reports and other downstream processes can be run on the same set of pay statements.
Provide a combined pay statement for workers who hold multiple positions that are paid in the same pay cycle and by the same legal entity.	A separate pay statement was created for each position that a worker holds.	Include independent benefits and earnings on a single pay statement.	The potential for employee confusion is reduced, because employees receive a consolidated pay statement for a given time period.

Earning codes

What can you do?	AX 2009	AX 2012	Why is this important?
Specify accounting templates and dimension values for earning codes.	Not available.	Accounting templates and dimensions are linked to earning codes. Therefore, different earnings can be accounted for differently.	The cost of earnings is distributed to accounting dimensions by using the accounting rules that are specified in the earning code.
Integrate Payroll with fixed compensation plans in Human resources.	Not available.	When earnings are generated, the earning codes (which are provided for rates calculated per pay period or on an hourly, monthly, or annual basis) reference the fixed compensation plan for the worker’s position.	Setup of worker earnings is simplified. Additionally, this feature takes advantage of the HCM fixed compensation structure. This means you can specify earnings by position, multiple compensation plans can be active at the same time, and compensation rates can be derived for each worker and position instead of just for each worker.
Create and assign gross-up earning codes.	Gross-up earnings could be generated, but they were difficult to set up.	Create earning codes that are used to correctly calculate gross-up earnings. The gross-up amount is the amount that is added to the net take-home pay, so that an employee always receives a specified amount.	This process automatically “backs out” tax changes that might be missed if they are performed manually. For example, if a tax bracket changes, and a worker receives a 500.00 car allowance, the worker’s pay is automatically adjusted so that 500.00 is still received after the new tax amount is deducted.

Worker settings for payroll

What can you do?	AX 2009	AX 2012	Why is this important?
Set up worker bank accounts.	An employee bank account in Payroll was used.	Payroll is integrated with the worker bank account in Human resources, and also with the bank account distributions in Cash and bank management.	The information is set up and maintained in one area, which means there are fewer chances for discrepancies.
Set up bank account disbursements by legal entity.	Workers were paid through a Payroll bank account.	Workers are paid through the worker bank account in Human resources.	The amount of setup that is required is reduced, and integration is improved.
Use date-effective settings to maintain worker information that affects payroll status, such as residency and marital status.	Changes to tax-related settings were effective as soon as they were entered. There was no record of previous values for those settings.	You can enter worker information for tax regions and tax codes, and specify the date that the changes take effect.	Data management is simplified, and payroll taxes are calculated correctly.

Benefits and deductions

What can you do?	AX 2009	AX 2012	Why is this important?
Enroll workers in the benefits they are eligible for by using the new eligibility policy function in Human resources.	Any worker could be enrolled in any benefit.	Workers can be enrolled in only the benefits that they meet the eligibility requirements for.	The policies that your organization sets for benefit eligibility are enforced fairly, and there is less risk of error.
Set up benefits in different categories, such as healthcare, retirement, and workers’ compensation.	Each category of benefits was set up and processed individually.	Use the same forms and controls to set up all benefit categories.	Data entry is simplified.

Posting and issuing pay

What can you do?	AX 2009	AX 2012	Why is this important?
Submit pay statements to Accounts payable for payment.	A single process was used to submit pay statements to Accounts payable and to post the payments.	Submit pay statements to the payment journal for payment.	Users have more flexibility to submit pay statements and post payments in any order, so that workers can be paid in a timely manner.
Post pay statements.	A single process was used to submit pay statements to Accounts payable and to post the payments.	Post the pay statements.	Users have more flexibility to submit and post pay statements in any order, so that workers can be paid in a timely manner.

More information

For more information, see Payroll.

What’s new in cumulative update 7 for Microsoft Dynamics AX 2012 R2

What’s new	Description
Update benefit rates for workers.	You can now mass-update the rates for worker deductions and employer contributions for all workers who are enrolled in a benefit. Workers who have custom rates are flagged and excluded from the mass-update process. For more information, see ”Update benefit rates” in Benefit setup tasks.
Tiered contribution calculation rates for retirement benefit plans.	You can now create a retirement benefit plan that calculates the employer contribution. This is based on a cumulative tiered calculation of the rows in the contribution calculation rates table. For more information, see Benefit setup tasks and Contribution calculation rates (form) 6.2 CU7 and prior.
Create and update payroll tax groups.	You can now create and update groups of payroll taxes. Each tax group contains a set of payroll tax codes. You can update all the tax codes in a tax group at the same time. For example, you can change the vendor and main account for every tax code in a tax group at the same time. Tax groups can also be used in transaction posting definitions. Each tax code can be included in multiple tax groups, but a tax code can be in only one tax group that is enabled for posting definitions. For more information, see Tax groups (form) 6.2 CU7 and prior and Tax information tasks.
(USA) Preparation of regulatory compliance reports for payroll.	The following preparation reports are now provided, to make it easier for employers to complete mandatory reports for payroll: Form 940 preparation report Form 941 preparation report State and quarterly wage and tax preparation report These reports provide some or all of the information that is required to complete the mandatory reports. This information lets employers prepare the actual reports in whatever format is required. For more information, see the following topics: Form 940 preparation report (PayrollUnemplTaxRtnPrepReport) Form 941 preparation report (PayrollEmplQuarterFedTax) State quarterly wage and tax preparation report (PayrollStateWageTaxPrepReport) These topics are also available in the Report catalog for Microsoft Dynamics AX on TechNet.
Separate positive pay statements for Payroll bank accounts.	You can now generate a positive pay statement file for your Payroll bank account. You can also configure positive pay for bank accounts that are not Payroll bank accounts, so that you can exclude payroll payments. This change helps make sure that only a Payroll user can generate a positive pay statement for the Payroll bank account.

What’s new in Microsoft Dynamics AX 2012 R3 Cumulative Update 8

What’s New	Description
Automatically calculate regular rate of pay earnings.	The Fair Labor Standards Act (FLSA) provides the framework for U.S. organizations to pay overtime to workers. One part of FLSA defines the way that the premium portion of overtime pay must be calculated. Failure to calculate the overtime payment correctly can open up the organization and its management team to significant fines and penalties. By using earning codes that have a rate basis of regular rate of pay to calculate and pay overtime premiums (instead of a standard 1.5x or 2.0x overtime code), the premium calculation will be made according to FLSA rules. For more information, see Premium earning setup tasks and Generate earnings.
Generate premium earnings based on characteristics of the worker or position, or on other earnings.	You can now use the Dynamics AX policy framework to automatically determine when workers qualify for premium earnings such as shift differentials or certifications held by workers. The premium generation process then calculates the amount of the earnings and adds the appropriate lines to worker pay statements. For more information, see Premium earning setup tasks and Generate earnings.
Generate retroactive earnings.	You can now automatically generate retroactive earnings statement lines when a worker receives earnings for past services at a new rate. An example might be an increase in compensation that was agreed on after the worker was already paid. For more information, see Earning code examples and Generate earnings.
Additional flexibility for benefit accrual plans.	New options allow you more flexibility to define when accrual plan benefits are accrued and used. For more information, see Benefit accrual plan tasks.
Pay statements with zero earnings	You can now manually generate a pay statement without earnings included. You might do this to update only benefit or tax deductions and contributions. For more information, see Pay statements and the payment generation process.

Share via