As a general rule only taxes that are employee taxes should show up on hte check. I know there was an issue with the SUTA sc showing up on the W2s as local taxes which is incorrect. if you see anything different you should open a case eith Acuamtica or your partner because I think it might be a bug Thanks. I thought it may be a bug but wanted to check first.
After spending some time changing the panel and dimensions of the actual png, I think it just comes down to playing around with the aspect ratios of the picture.
I believe the solution could be to extend the vendor as a customer and create something on the AR side for $200.
Hello if you need to short pay a salaried employee for some reason, you can create a special batch , select the employee or employees that you want and then go to each employees earning details and specify the amount you want to pay. see below Thanks for the insight on other options. It’s tricky because they have about 100 salaried employees and it’s not the same each pay period for who works less than 80 hours. I think we’ll just refer to the inquiry before we calculate taxes.
I’m also having trouble with this screen but my automation schedule won’t even execute. I have the same settings as my live environment (2020R2). I even created a new import scenario to test with, still nothing. I am on version 22.209.0029 , what version are you on?
If a salary employee has not worked their total hours, should the hours be replaced by something else, such as PTO? Here is another way to change the employee’s salary pay during the payroll process. In Paychecks and Adjustments (PR302000), go to the Financial tab and enter the flat amount to pay: In our case, sometimes salary do not work 80 hours. I realize you can change it on the financial tab. The catch in our situation is to find which employees are not at 80 hours per period. It’s rare but it happens. My solution is to create a generic inquiry that shows those employees with less than 80 hours as salary for that pay period. The payroll user checks this inquiry after importing the payroll batch and before calculating taxes. It is tricky because we have over 200 employees on payroll on one tenant as you know.
@podonnell11 Yes, use Inventory Account as the purchase price variance allocation mode. The $2 per unit variance will be adjusted to the receipted goods. I like this option a lot. It seems to work the way we need it to. Thanks!
Hello, the interesting thing that I noticed is that the “last executed date” is 1/30/2024 and the “next execution date” is printed as 2/29/2024. Do you change the execution date each month (i.e. it might make more sense to change your series to execute on the last Tuesday over every month)? Unless you’ve got someone who can do a SQL update in the background to change that “next execution” date you might be stuck running them on the 29th and then editing the batches before you release them. It looks like they run it manually on a certain day instead of using the generate transactions screen. We just did an upgrade from 2021R2 which might be one of the reasons for the errors. I was thinking the same thing, change the business date, and then create a quick import scenario to change the doc date to the 27th on all of them.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.