Skip to content

Commit 8a0be9e

Browse files
authored
Merge pull request #9149 from MicrosoftDocs/main
Auto push to live 2025-06-18 02:33:16
2 parents 1d38088 + 547f2b5 commit 8a0be9e

File tree

8 files changed

+372
-134
lines changed

8 files changed

+372
-134
lines changed

support/azure/azure-kubernetes/security/troubleshoot-seccomp-profiles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ After you configure AKS workloads to use a seccomp profile, the workloads exit u
3737
- A tool to connect to the Kubernetes cluster, such as the `kubectl` tool. To install `kubectl` using the [Azure CLI](/cli/azure/install-azure-cli), run the [az aks install-cli](/cli/azure/aks#az-aks-install-cli) command.
3838
- The [krew](https://sigs.k8s.io/krew) package manager for installing [Inspektor Gadget](https://go.microsoft.com/fwlink/?linkid=2260072)'s plugin. You can follow the [krew quickstart guide](https://krew.sigs.k8s.io/docs/user-guide/quickstart/) to install it.
3939
- The seccomp profile that you're trying to troubleshoot.
40-
- The open source project [Inspektor Gadget](/troubleshoot/azure/azure-kubernetes/logs/capture-system-insights-from-aks#how-to-install-inspektor-gadget-in-an-aks-cluster).
40+
- The open source project [Inspektor Gadget](../logs/capture-system-insights-from-aks.md#how-to-install-inspektor-gadget-in-an-aks-cluster).
4141

4242
## Troubleshooting checklist
4343

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,45 @@
11
---
22
title: Income Tax calculations or discrepancies with the CRA in Canadian Payroll
3-
description: This article provides information on how income taxes are calculated in Canadian Payroll for Microsoft Dynamics GP, and why the tax calculations in GP may be different than other tax calculators from the Canada Revenue Agency (CRA).
3+
description: Provides information on how income taxes are calculated in Canadian Payroll for Dynamics GP, and why the tax calculations in GP might be different than other tax calculators from the CRA.
44
ms.topic: troubleshooting
55
ms.reviewer: theley, cwaswick
6-
ms.date: 04/17/2025
6+
ms.date: 06/18/2025
77
ms.custom: sap:Payroll
88
---
99
# Income Tax calculations or discrepancies with the CRA in Canadian Payroll for Microsoft Dynamics GP
1010

11-
This article provides information on how income taxes are calculated in Canadian Payroll for Microsoft Dynamics GP, and why the tax calculations in GP may be different than other tax calculators from the Canada Revenue Agency (CRA).
11+
This article provides information on how income taxes are calculated in Canadian Payroll for Microsoft Dynamics GP, and why the tax calculations in GP might be different than other tax calculators from the Canada Revenue Agency (CRA).
1212

1313
_Applies to:_   Microsoft Dynamics GP
1414
_Original KB number:_   2773319
1515

1616
## Symptoms
1717

18-
This article will address these questions:
18+
This article addresses these questions:
1919

2020
- How are taxes calculated in Microsoft Dynamics GP for Canadian Payroll?
2121
- Why would the tax calculations in Microsoft Dynamics GP differ from the online payroll calculator published by the CRA?
2222
- Is the method used for tax calculations in Microsoft Dynamics GP accepted by the CRA?
2323
- Why would the tax calculations for a new hire differ from an existing employee with the same pay?
24-
- Why would the tax calculations for the same employee differ from a payrun done earlier in the year versus a payrun done later in the year?
24+
- Why would the tax calculations for the same employee differ from a pay run done earlier in the year versus a pay run done later in the year?
2525
- If you calculated taxes for each week separately, and then again as a two-week period, why wouldn't the sum of each week equal what the tax calculations are for the two-week period?
2626
- Why doesn't a new hire with no history match the CRA calculations?
2727

2828
## Cause
2929

30-
The CRA accepts different tax calculation methods (as outlined in the link below). The CRA online payroll calculator uses a simple tax calculation method. And Wintod (which is program provided by the Canadian government to calculate taxes) does not take prior history into account and is only an 'estimate'. Microsoft Dynamics GP uses a method called Cumulative Averaging that takes prior pay periods into account, uses a 'projected' annual income established by the date entered, and the number of pay periods that have occurred are factored in. This method does comply within the ranges set by the CRA.
30+
The CRA accepts different tax calculation methods, and these are outlined in [T4127 Payroll Deductions Formulas](https://www.canada.ca/en/revenue-agency/services/forms-publications/payroll/t4127-payroll-deductions-formulas.html). The [Payroll Deductions Online Calculator (PDOC) provided by CRA](https://apps.cra-arc.gc.ca/ebci/rhpd/beta/entry) uses a simple tax calculation method and provides only an estimate, without considering prior pay history.
31+
32+
Microsoft Dynamics GP uses a method called _Cumulative Averaging_ that takes prior pay periods into account, uses a _projected_ annual income established by the date entered, and the number of pay periods that have occurred are factored in. This method does comply within the ranges set by the CRA.
3133

3234
## Resolution
3335

34-
What you are seeing is normal in Microsoft Dynamics GP. The tax calculations in Canadian Payroll are complex and take quite a few factors into account. Microsoft Dynamics GP uses a method called Cumulative Averaging that takes into account prior pay periods, the date used, a projected income and how many pay periods have occurred when finding tax amounts.
36+
The tax calculations you see in Microsoft Dynamics GP are expected and correct. The tax calculations in Canadian Payroll are complex and take quite a few factors into account. Microsoft Dynamics GP uses a method called _Cumulative Averaging_ that takes into account prior pay periods, the date used, a _projected_ income and how many pay periods have occurred when finding tax amounts.
3537

36-
For instance, the existence of prior pay runs for that employee will affect the amount of Federal Tax that is withheld in Microsoft Dynamics GP. So you will find different tax amounts calculating if you compare a payrun batch for today, versus 6 months ago for the same employee. Tax calculations in GP do use 'dates' and will vary depending on the dates of the first payrun for that employee. So that is why an existing employee would calculate differently than a new hire with the same pay. You could really only compare taxes for employees that started at the same time and have the same YTD balances, dates, benefits/deductions, etc. or else you can expect differences. You will even see the taxes for a new hire change for each payrun as you go later and later into the year.
38+
For instance, previous pay runs for an employee affects the amount of federal tax withheld in Microsoft Dynamics GP. As a result, the tax calculated for a pay run today might differ from the amount calculated six months ago for the same employee. Tax calculations in GP do use _dates_ and will vary depending on the dates of the first pay run for that employee. This is why an existing employee might have different tax amounts than a new hire with the same pay. You can only expect tax calculations to match for employees who started at the same time and have identical year-to-date balances, dates, benefits, and deductions. Otherwise, differences are expected. You'll even see the taxes for a new hire change for each pay run as the year progresses.
3739

38-
The CRA actually defines a 'range' of taxes and not a single number as the tax due. The reason they define a range is because they have more than one method to calculate taxes that is accepted. They use a simpler method that is the same for each period in their calculator, and Microsoft Dynamics GP uses a more complex method that takes past history into account. We have verified with the CRA that the numbers calculated by Microsoft Dynamics GP do comply within their acceptable range. There is a pdf published at the site below to explain Computer Tax Calculations. At the bottom of the site below, click on the link under Effective January 1, 2019 to find the pdf. The method Microsoft Dynamics GP uses is similar to [Option 2 - Tax Formula based on cumulative averaging](https://www.canada.ca/en/revenue-agency/services/forms-publications/payroll/t4127-payroll-deductions-formulas/t4127-jan/t4127-jan-payroll-deductions-formulas-computer-programs.html#toc49) in Chapter 6.
40+
The CRA actually defines a _range_ of taxes and not a single number as the tax due. The reason they define a range is because they have more than one method to calculate taxes that is accepted. They use a simpler method that is the same for each period in their calculator, and Microsoft Dynamics GP uses a more complex method that takes past pay history into account.
3941

40-
[T4127-JAN Payroll Deductions Formulas - 113th Edition - Effective January 1, 2021](https://www.canada.ca/en/revenue-agency/services/forms-publications/payroll/t4127-payroll-deductions-formulas/t4127-jan/)
42+
We have verified with the CRA that the numbers calculated by Microsoft Dynamics GP do comply within their acceptable range. For more information about computer-based tax calculations, see the PDF available at [T4127 Payroll Deductions Formulas](https://www.canada.ca/en/revenue-agency/services/forms-publications/payroll/t4127-payroll-deductions-formulas.html). To access the PDF, select the link under "Effective January 1, 2025." The method used by Microsoft Dynamics GP is similar to [Chapter 5 – Option 2 – Tax formulas based on cumulative averaging](https://www.canada.ca/en/revenue-agency/services/forms-publications/payroll/t4127-payroll-deductions-formulas/t4127-jan/t4127-jan-payroll-deductions-formulas-computer-programs.html#toc38).
4143

4244
> [!NOTE]
43-
> For a new hire with no history, you must use the date of January 1 in order to match the CRA calculations. For example, in the first payrun for a new employee, the tax calculation will vary if you enter it dated January 1 versus a date later in the year, as pay periods that have occurred are also taken into account.
45+
> For a new hire with no pay history, you must use the date of January 1 in order to match the CRA calculations. For example, in the first pay run for a new employee, the tax calculation will vary if you enter it dated January 1 versus a date later in the year, as pay periods that have occurred are also taken into account.

support/entra/entra-id/user-prov-sync/troubleshoot-pwd-sync.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ In this scenario, passwords of all users appear not to sync. It usually occurs i
8686
8787
To resolve this issue, first make sure that you enable password synchronization. To do it, start Microsoft Entra Connect configuration wizard, select **Configure** and **Customize synchronization options**, then continue through the screens until you see the option to enable password synchronization.
8888

89-
After password synchronization is enabled, you must wait for a full password sync to finish. Check the Windows [Event Viewer logs](/troubleshoot/entra/entra-id/user-prov-sync/troubleshoot-pwd-sync#event-id-messages-in-event-viewer) to monitor the password synchronization process.
89+
After password synchronization is enabled, you must wait for a full password sync to finish. Check the Windows [Event Viewer logs](troubleshoot-pwd-sync.md#event-id-messages-in-event-viewer) to monitor the password synchronization process.
9090

9191
## Troubleshoot one user whose password isn't synced
9292

support/sql/database-engine/performance/troubleshoot-high-cpu-usage-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ If your SQL Server instance experiences a high CPU scenario caused by spinlock c
205205
206206
## Step 9: Check your power plan settings at the OS level
207207

208-
SQL Server workloads may experience reduced performance and cause high CPU on the system when Windows is configured with the default **Balanced** power plan. The **Balanced** power plan setting might lower the CPU clock speed to conserve energy. For example, a processor rated at 3.00 GHz may throttle down to 1.2 GHz. As a result, workloads that typically consume around 30% CPU may reach 100% utilization due to the reduced clock speed. To maintain consistent and optimal performance for compute-intensive SQL Server workloads, we recommend that you configure the system to use the **High Performance** power plan. This setting ensures the CPU operates at its full rated speed, helping to avoid performance bottlenecks. For more information, see [Slow performance on Windows Server when using the Balanced power plan](/troubleshoot/windows-server/performance/slow-performance-when-using-power-plan).
208+
SQL Server workloads may experience reduced performance and cause high CPU on the system when Windows is configured with the default **Balanced** power plan. The **Balanced** power plan setting might lower the CPU clock speed to conserve energy. For example, a processor rated at 3.00 GHz may throttle down to 1.2 GHz. As a result, workloads that typically consume around 30% CPU may reach 100% utilization due to the reduced clock speed. To maintain consistent and optimal performance for compute-intensive SQL Server workloads, we recommend that you configure the system to use the **High Performance** power plan. This setting ensures the CPU operates at its full rated speed, helping to avoid performance bottlenecks. For more information, see [Slow performance on Windows Server when using the Balanced power plan](../../../windows-server/performance/slow-performance-when-using-power-plan.md).
209209

210210
## Step 10: Configure your virtual machine
211211

0 commit comments

Comments
 (0)