BSI 10 Taxable Wage Amounts

We BELIEVE our most current issue with the BSI 10 upgrade is that the taxable wage amounts are just not presenting. We BELIEVE that taxes are calculating correctly. I'm told that this is a Lawson issue to address. Is anyone else experiencing a similar issue???

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

We are experiencing the same issue. We have PA localities that have taxable amounts calculated with no taxable wage associated. We have support tickets opened with both BSI and Infor support. Infor is saying the only change they made is to point the PR140/PR80 to the reportable wage field in BSI, not the taxable wage.
When I look at the PR80 display log that shows the BSI calculations, that makes sense. BSI shows 0.00 in reportable wages and a valid # in taxable wages.
I am pushing BSI to tell me why their reportable wage value is 0. They are saying Lawson needs to recode and point back to taxable wages.
It is quite a ping pong situation. I have copied BSI's responses on my Infor tickets and my Infor responses on my BSI tickets.

Would be interested in any experiences...

unknown

BSI has also directed us to Infor. Our Infor Host provider has submitted tickets to Infor on our behalf, I will submit one as well.
Our employees traveling through multiple states on a weekly basis so we're seeing issues with PA, IN, WI, VA, etc etc....

unknown

This isn't a Lawson issue. The fix for the locals is within BSI's cyclic TF10e.1. Lawson has released 3 ctps, JT-641574, JT-657347 and JT-669375, non of which are required, but are, for obvious reasons recommended. JT-641574 does work with the change bsi made to taxable and reportable.

Within TF10e.1, you'll want to go into the configuration area and select the basic reciprocal calculations. This will put all local taxes back to what they were prior to TF10.

The states are a different issue. BSI states that the resident state not updating taxables is crrect, according to the state. If you don't agree with that, BSI has asked that you contact them to validate your results and back it up with documentation.

unknown

One other thing. There is also an issue with the exempt code of B on the PR13.1. BSI is fixing that when they release TF10e.2 .

m-nilo

We installed and tested 10.e2 yesterday hoping it would fix problems we encountered with 10.d and 10.e1 testing. All Regulatory Bulletins are up to date and the Infor CTP's are applied as the above response. Problems we have encountered: 1. Employees living in MD and working in DE, NC, or VA either generate a MD W/H tax record with NO Taxable Wages (in 9.0K, the W/H and Taxable wage were populated) or no longer generate a MD W/H record at all (in 9.0k, a MD W/H record was generated with taxable wage and no W/H). 2. Employees living in NJ and Working in DE, MD, or PA no longer generate a NJ W/H record (in 9.0k, a record was generated with 0 tax and a NJ taxable amount). 3. We have 2 employees living in WV and working in PA. Again, a WV W/H record is generated with W/H and no Taxable Wage. The records were no generated in 9.0K. We also encountered the PA scenario described above but agree with the BSI explanation on the differences (but based on that 9.0K was wrong). Any one else having these issues?

mstephens

Hi, are your Local Reciprocal Calculations on HR00 & HR01 set to "1" or "0". Just trying to figure out if we have to change those settings as well as "Use Basic Reciprocity".

m-nilo

Ours are all set to '1'. We've tested both ways and it doesn't seem to make a difference.

Copyright © 2025 Infor. All rights reserved.