Payroll

Client has banded PTO based on years of service, however EE PTO  time is to be used during the caldendar year and should reset on Jan 1.  The accrual rate should not change until the EE reaches their anniversary date.Currently you cannot accomodate this scenario:  What you are asking is not how the system works.  You can't have the PTO Bank set to Specific Date, and have the Banding Rule based off Anniversary Date. The banding rule is going to follow the setting on the PTO Bank for Transfer Date. It will look for the Years of Service to know how many Hours they are eligible for in a given year,  but it will transfer based on the setting on the PTO Bank. If it is set to Specific Date, then it will transfer that amount on the specific date.  If it is set to Anniversary Date then it will transfer that amount on the Anniversary Date. The Hours per year is a setting so the system knows how many hours they can have in the year.Does anyone have a workaround or solution to this other than havi

We are implementing the Canadian Payroll and the customer wants to manage the Banked time in the system. We have created a new earning type BK that is used to track that, but we have noticed that the system won’t deduct the Banked time from the gross pay. In our situation the employee  has been paid for 84.91 hours at regular rate and 33.22 hours on overtime for a total of 6,871.74$You will see in the screenshot that the gross pay is 9254.99$, but it should be 6,871.74$ because banked hours should not affect gross pay.It does the following: Regular hours paid+ Overtime hours paid and Banked time that aren’t paid. Any solutions ?

Hey, gang - Running into an error and it isn’t clear where it’s coming from.  I’ve got 3 separate deductions that produce this error when I attempt to process liability bills. The corresponding account is NOT associated with an account group, so it’s not obvious why I’d be getting a project error. To make things a bit muddier, I’ve got a similar deduction that affects the tax calculation, uses the same account but DOES NOT result in an error.This is 25R1, so the Require Single Project per Document field is no longer available in AP Preferences. FWIW, the deductions in question are only used for one employee.  Any ideas on where the error is coming from?  Thanks in advance!

Hello - I’m having some issues with the Global Tax Settings tab of the Tax Maintenance form. Our client has recently updated to 25R2 and the modern UI, and when we update taxes, the Global Tax Settings tab seems to be missing all sorts of entries that used to be visible to us. For example, we used to be able to maintain the basic personal amounts for each province tied to our work locations, and those fields are now missing. They would be the Total Claim Amount fields for each province.I’ve searched the update notes and don't see anything related to this. I also thought that perhaps this was missing because I was setting up a tenant for production with no employees loaded yet, but our UAT tenant that has prior payroll data is also missing all of the field that we previously were using.I also went in and looked at the individual Employee Payroll Settings, and all prior values we had updated are still there, however the ‘Use Default’ checkbox that used to exist for some values (like the

I have a customer who needs to add Shareholder Insurance (SHI) to every payroll. It needs to go in as an Earning and out as a Deduction (Gross up/Net zero).Is there a "recurring" feature in Payroll that I’m missing? I cannot add the SHI Earning Code to the Compensation tab on the Employee Payroll Settings (PR301000) screen because of the Earning Type restrictions.How are you guys automating this so the client doesn't have to manually add these lines to the paycheck every month?

My client had to run the Tax Maintenance this week and there are now blank rows, the Values don’t have dropdowns and for example the Select Filing Status was Single, Married Filing Jointly, Married Filing Separately and Head of Household, but now everyone updated to an “S” with no options:Is anyone else experiencing this issue? 

Good day, has anyone perhaps ons successfully integrated with Deep Local Payroll (Payspace)  Th y are one of Acumatica’s API partners however I am struggling to post my ledgers from Payspace to Acumatica, the error I keep on getting is Your Acumatica login has expired. Please login and try againThis error pops up even directly signing in. I did setup a API user for payspace and I did send them the Client ID and Secret which they used to establish the connection, but I think I might be missing something. 

We gave a pay advance to an employee and set the deduction limit to $160. He had 2 paychecks of $80 each but then it didn't stop it still pulled another $80 out on the next paycheck. Can anyone tell me what I am doing wrong? The deduction limit frequency is set to No maximum.

The owner is subject to the S Corp rules for the Greater than 2% shareholder rule. Therefore the company pays 100% of her premium expenses for health, dental, vision, etc.  We have tracked these amounts for the year, and now need to add these to wages as taxable income subject to FICA but not withholding. How do we do that? Is it done through an adjustment?

Hi All,Has anyone successfully created an automatic email with paystub report attached that is sent thru a business event when the regular paycheck is released?I am referring to PR641000 that you generate directly on the individual paychecks.

Looking for a report to print and remit for payroll run that includes the garnishment deduction amount + the information for the corresponding codes Garnishment Details fields in Employee Payroll Settings. If no native report, any direction on which table contains the Garnishment Details field data?

 Hello Everyone,I am trying to clean up some tax issues that arose on the last payroll paybatch we ran after a recent upgrade. Specifically there are a few taxes that have appeared on a recent payroll payrun that were not there before the upgrade. In one case I had the NV ER SUTA SC show up. We caught it on the payroll liabilities bills run. In another case I have New Mexico Workers Comp showing up as a tax on a few employees paychecks as well. We upgraded to 2021R2 21.213.0038.What is the fool-proof way to make sure they do not appear on the paychecks next time? Is it to de-select all the “required” checkboxes and set the rates to 0.00 on the right panel? Then update/assign taxes to employees?Why would New Mexico Workers Comp show up as a tax? Is there a setting in Deduction Codes or Workers Comp Codes?  

We’re in the setup phase of our implementation and working through our Safe Harbor match configuration.Our formula is: 100% match on the first 2% 50% match on the next 4% Total match not to exceed 6% of eligible compensation Some employees will elect a flat dollar contribution, and their weekly pay varies.Has anyone configured this type of Safe Harbor match where the employee deferral is a flat amount instead of a percentage? If so: How did you structure the deduction and match calculation? Did the system correctly calculate the tiered match each payroll based on that week’s eligible compensation? Any issues with caps or special scenarios we should plan for during setup? Appreciate any insight from those who’ve already been through this.

We are having an issue with the paycheck assigning separate workers’ comp codes to different work locations. As you can see, we have 2 work locations on this paycheck. We want separate workers’ comp codes for each work location. However, currently, the system uses the same code with different deduction codes because of the 2 different states involved.I understand that there are 2 separate deduction codes, but when we go to report these wages, we have to use 1 rate per WORKERS COMP code. When we report it to our insurance, they do not care about our deductions codes--just their WORKERS’ COMP code. Does anyone know how to fix this? I want to be able to pull the workers’ comp report and use the numbers in Acumatica to report to our insurance. I can’t find a way to do it currently.

Hi ,When I try to create an expense claim, it does not automatically pick up the description for the selected expense item. Do you know why this might be happening? 

Has anyone customized a GI to create an export that can be sent in Excel to LCP Tracker for Certified Payroll?

Does Acumatica still support filing 1099s through Aatrix? If so, how is the process done?

When filing our W-2’s the payroll registers earning and tax equal the 941 that were paid and filed.  However, when running the W2s. there are 47 people out of 130 that have SS/Medicare and federal wage and tax differences.  We saw one employee has $3018 of wages and taxes $214.  What report can I run to identify why the W2 is not reporting correctly? Where can we find our issues?

Hi All,Has anyone had this issue before where amounts are not reflecting on the T4s of the paycheck adjustment created with the migration turned on?I appreciate all the help.Thanks.

The new legislation signed by President Donald Trump introduces temporary federal tax deductions for tips and overtime pay. Here's a summary of how it works.No Tax on Overtime PayDeduction Amount: Workers can deduct up to $12,500 in overtime pay ($25,000 for joint filers) from their taxable income on their federal tax returns. Income Threshold: The deduction is reduced by $100 for each $1,000 earned above $150,000 ($300,000 for joint filers). Effective Period: The deduction is retroactive to January 1, 2025, and expires on December 31, 2028. Reporting: Overtime compensation must be reported on Form W-2, Wage and Tax Statement.No Tax on Voluntary TipsDeduction Amount: Workers can deduct up to $25,000 in reported tips from their taxable income. Income Threshold: The deduction is reduced by $100 for each $1,000 earned above $150,000 ($300,000 for joint filers). Effective Period: The deduction is retroactive to January 1, 2025, and expires on December 31, 2028.Key Points to NoteImmediate P

HelloWe’re having an issue with Canadian payroll and I’d like to know if anyone else has seen this, or if there is something we’re missing.We have a test employee who has maxed out on EI and CPP (tax reports confirm this), and when I process a subsequent regular pay run and compare the Federal Withholding Tax (FWT) and the Provincial Withholding Tax (PWT) to the Payroll Deductions Online Calculator, the amounts don’t line up. In Acumatica PWT is lower while FWT is higher. If I run the Online Calculator again and do not select the option for max EI and CPP having been reached, then the PWT matches what Acumatica calculates, but FWT is still out. In all standard pay runs I can get an exact match. We’re only seeing this now with maximums having been reached. I’ve gone through all setup and can’t see anything that seems like it would impact this.Appreciate any feedback anyone has on this! 

I am working on our annual 401K census data and have run into a bit of a snag in the reports I am using.I used the Earnings by Employee report and then the Deductions and Benefits by Employee report (for 401K, 401k Match, and Roth) to get the information to include on my reporting.  These reports however don’t provide a total figure to use as a double check to what I entered to make sure I keyed everything properly.  I am using the parameter of the 2025 year as that is all it asks for.I thought I would just run a Payroll Summary report in order to get a quick view at my totals as a double-check, but the totals don’t match? I am running it for a transaction date of 1/1/2025-12/31/2025.My total wages, hours, and even the deductions don’t match. The payroll summary has more somehow?  The only one that matched exactly was the Deductions and Benefits by Employee for the 401K. Why would this be? 

Can someone provide instructions for entering Taxable Fringe Benefits? I need to enter personal use of a company vehicle for our owners for 2023.

Weekly, Thursday payroll has 53 pay periods in 2025.Thursday 1/1/2026 will be paid on Wed 12/31/2025 due to calendar exceptions/holidays.This results in an extra pay period in 2025.Employees with “Annual” unit of pay compensation receive a smaller check each pay period due to 53 periods. A simple example - $52,000 annual salary normally results in $1,000 gross per period. With the 53rd period, $52,000 annual salary results in $981.13 gross per period.Is this expected behavior?  I thought Acumatica would use the Employees Working Weeks per Year for this calculation, not the number of pay periods.  I guess both methods are reasonable.I found the following work-arounds for salary employees:Change salary rates and employee type to Hourly - defeats the purpose of Salary type Enter a manual salary rate every pay period - also defeats the purpose of Salary typeAre these the only/best options?Perhaps I’m missing something.

With the recent Acumatica 2025 R2 update, our employees lost access within their “Internal User” role to see any payroll documents (this is basically the sole reason most of our employees are logging and we had this role modified for them for this purpose only).  I have been troubleshooting with Acumatica for a month now without success on either removing the restriction from the Internal User role or just having a simple solution on how to have our employees be able to access all of their payroll documents in one place.  They say that this is a known update for security purposes and only the admin role can access pay stubs and the last email from them suggested we either remove the restriction or create a new user role that has that access.  I had not yet tried to create a new role so I tried that route and will put the steps below in detail.  Basically this ended with the same issue as trying to remove the restriction from the current role (note that I had a 45 min meeting with Acuma