retroactively process the payroll

[former_member342752]

Hi Gurus,

We are experiencing a problem regarding W2's not being produced because prior year refunds ocurred for pre-tax benefits. We would like to explore the possibility of a barrier that prevents processing of prior year refunds for pre-tax benefits. At the very least we would like some sort of flag so we can evaluate why the refund is occurring.

We want the ability to retroactively process payroll into next year while still making sure that 401k and taxes do not retro into the prior year.

Your suggestions required for the above issue to retroactively process the payroll into next year while still making sure that 401k and other atxes do not retro the prior year.

thanks!!

[Former Member]

Hi Arbindo,

there must be something in the tax reporter log why it does not provide a w2.

It would be good to know the log information. if you want to reach out to me directly, we can discuss it.

[former_member342752]

Hi Spatz,

We are able to stop retroing by putting the E.R.date and control. The problem is client requires for the above issue to retroactively process the payroll into next year while still making sure that 401k and other atxes do not retro the prior year. The client wants prior year refunds ocurred for pre-tax benefits need not be taxed,let it go retro without effecting 401k and taxes.

I need the solution that will do retro but do not touch the prior year refunds ocurred form pre-tax benefits.

Thanks!!!

arbindo

[Former Member]

Dear Arbindo,

I would need to know a bit more. Taxes are not changed in the retro period. New income or reduced income is passed forward to the in period and taxed there. That means if you have changed income a previous year, it is passed forward and taxed in the current period.

It might look like they are calculated but the function utpri resets it to the old values.

401K needs to be restricted perhaps in a schema change and prevent 401K values to be changed.

Let me know if you need more help.

[former_member342752]

Thanks Spatz,

Yes, I hope it 401K needs to be restricted perhaps in a schema change and prevent 401K values to be changed.

It was helpful

Arbindo