TF10 and PA School District taxes

We have loaded and tested and are not having issues.

With that said, we have our PA locals set up differently from some. We still use the Lawson PR03 functionality and only assign municipality codes so it takes off the entire amount with one deduction code.

We installed TaxFactory 10 in DEV and we are having a very similar problem with Ohio school district taxes.   BSI verified that taxes are being calculated after viewing our logs but no tax is being withheld.

 

Tom

Yes, BSI is working fine.  Seems to be a Lawson issue.  I opened a case with them and they confirmed the issue.  Working on a patch at the moment.

Here was the response from my case.

Event note emailed to jbeard@cswg.com.Incident was locked for 5 minute(s).Event Log Notes : Jason - The JT is entered for "Local taxes not working after upgrading to BSI Tax Factory 10". The difference seems to be when TF10 is installed 'on premisis' compared to the SAAS model. There are also some internal changes in in TF10 with the way BSI deals with the fields taxable wages vs reportable wages that Infor needs to deal with. There is nothing different in the setup...it's with the internal way TF10 is calculating/reporting. I do get different results if I am testing here on different servers.In regards to an ETA, our goal for P2s is to deliver a resolution within 15 business days. As I said, development is actively working on a solution, and are aware of the deadlines so I wouldn't expect it to take that long. However, there is no guarantees.

Wow.

We had the same response to the case we opened (we are in Ohio so Ohio school taxes). "We have had several of these reported and the reason is that there was a change in how BSI "reads" the results of taxable wages, so we are making a change to fix that.  The JT is JT-641574 and I will tie your case to it so that you are notified when it becomes available. "

 

Tom

Just heard that the patch is complete and should be posted for download tomorrow.  I'll post our results once we apply.

 

thank you

JT was posted today, downloaded, installed and tested via PR80.  Initial feedback is positive need to test a broader populating but first couple of test cases have passed.

 

The JT is 

...Reportable Wages are returned by BSI Primary JT-PT(s):JT-641574 Superceded JT-PT(s): Primary Program(s):PR140 2...TASK: 270347 Issue Type: Correction PT/JT - Description: JT-641574:School District withholding not being taken when Reportable...

• KB: 1544802
• Type: Cumulative/Service Pack/Patch Release

Completed a parallel payroll after applying this patch and found that school district taxes were calculated correctly, but taxable wages were not populated on the PR140 or in the PAYDEDUCTN table.   I'm continuing to work a case with Lawson on this.

Tom

We can't even get the state taxes to work accurately for employees that live in one state(PA) and works in another(MD). Is anyone experiencing this problem? I have an incident open with Lawson and BSI support but no solution yet.

I'll have to check the working in one state and living in another, certainly applies to our population.  Uncovered another one...

NY Commuter tax is not being calculated.  It is showing as a valid company deduction but the "calculated tax" is coming back from BSI as zero.  

Case open with Lawson as well.

Confirmed that we are also having the issue of taxable wages not displaying and live/work state issues.

On each of these, Lawson is telling me to work with BSI. That may be the case... that it is a BSI issue but at least on the taxable wages not displaying I can see the taxable wages on the output from BSI when you run in debug... anyone else having any luck?
Is anyone actually live on TF10?

Posted By Kelly K on 10/22/2014 2:44 PM
We can't even get the state taxes to work accurately for employees that live in one state(PA) and works in another(MD). Is anyone experiencing this problem? I have an incident open with Lawson and BSI support but no solution yet.

Ditto on this one. Reciprocity is broken, even with latest patch.

 In TaxFactory 9.0 there is a flag that allows employers to tax assuming they have a business presence in all states (In Dataset Options set flag to Yes for TF80 like Reciprocity Funcitonality) therefore reciprocity rules would always be followed.  In TaxFactory 10 that is considered custom data that customers need to control because smaller companies might not have a business presence(nexus) in all states therefore they do not need to follow reciprocity rules for taxation.  BSI support said in TaxFactory 9.0 that functionality was only there for testing purposes.  So I've started adding the custom nexus data as we have a business presence in all states and so far I am getting the desired results.  It seems like a lot of work to me but that is the solution being offered.  Would love to hear from anyone that comes up with an alternate solution. 

I still haven't quite figured out how the new options on the Cert Code field of PR13.1 fit into the upgrade.  Has anyone figured out their purpose?

We are not having the problem with reciprocity. Our problem is with the PA unemployment rates. A week ago, our parallels were matching production that was still on version 9.0.j. Now with our second parallel run, the PA unemployment rates are incorrect. The only thing that I've updated since the first parallel run is the regulatory bulletin to #37. We have a ticket opened with BSI on this one.

We have similar issue with our pension payroll earnings not picking up as taxable income. This only happens with TF10. It's not taking any Federal or State W/H taxes in PR140 since the taxable income is zero. PR80 works fine. I made a big complaint via phone call over InforXtreme and they bumped the incident up as production down. 4 days later, I got a patch (yesterday) and we are testing the patch. So far so good, PR140 is picking up all the earnings as taxable. The KB is 1548524. Try the patch and see if it fixes your problem.

 

 

KB 1548539 for those on 9.0.1 applications.

We are 9.0.1 so I applied 1548539 and we are still seeing the same issues.

Is anyone having issues with BSI 10 and the Unemployment Rate overrides for PA? It is not calculating using the override rate that is setup, and we have verified that it is indeed setup with valid start and stop dates, etc. If I switch to point back to version 9, then we do not have the issue anymore. This seems to be our hang up right now. The error message that we see in the client is:

2000 - NO COMPANY UT EXPERIENCE RATE INFORMATION FOR THE PENNSYLVANIA STATE UT TAX WAS FOUND. THIS TAX HAS BEEN CALCULATED USING THE BASE RATE. THIS RESULT MAY OR MAY NOT BE VALID FOR YOUR COMPANY

Jeff -
We are not having that issue, are you sure the dump/load of custom data from 9 to 10 was successful? Also, the notification from BSI today regarding the tac date formula override resolves the NY commuter tax not being taken issue. We are still experiencing issues with taxable wages not being returned for local taxes as well as issues where live/work state differs.

Jason-
Yes, we've dumped the custom data from 9 to 10, and we can see the actual entry in 10 when we view Unemployment Overrides for that company. I'm still working with BSI on this one. Everything else for us is calculating correctly, and taxable wages are being returned. Our payroll dept. noticed the difference after I applied bulletin #37. Not sure if that's related or not, but we had been running parallels with production that is still on version 9, and everything was balancing perfectly up until that point.

Jeff

After sending our joblogs to BSI, they determined that since we are using Formula 2 to calculate unemployment taxes, that we need to pass the YTD wages. Apparently the YTD wages aren't being sent to BSI, therefore, they are using some default rate for unemployment instead of our formula 2 override rate that we have set. I've added that bit of information to the Lawson ticket, but so far no resolution.

We have applied

KB 1548539   KB 1548524 and upgraded to 10e on our test system.  We are unable to get taxable wages for Lake County Indiana for employees who are residents of IL working in IN.

I also have the custom data for nexus setup in BSI for these two states as well.  Does anyone have any insight on getting a resolution to this?

Michelle Johnson

 

 

Here's the update from my Lawson case: For the local issues where the tax is being updated, but the taxable is not, this is most likely correct according to the state, but TF10e.1 is being created by BSI to correct this, basically giving you an option to change your local taxes reciprocal taxation back to what it was prior to this release. This is set to be released to us from BSI on 11/15 so we can certify here. Normally, it would available to you only after we certify, but BSI has agreed to release it to you before then if you chose.

This does not sound precisely like the issue we are encountering but that's what they are telling me.

Tom

Tom -
Have you received the update from BSI? I e-mailed and requested it today per the instructions from Lawson but have not received anything as of yet.