Running BN299 thru IRS Schema

unknown

Hello,

Does anyone have steps to follow when running the 1095C XML File and Manifest created by the BN299 thru the IRS Schema?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

sriman-shivakoti

I did find a document on Xtreme showing how to do it. Try searching on How to Validate ACA XML Schema. I would attach it here but don't know how to do that.

unknown

I used KB1836688 from the Infor site.

unknown

I just figured out how to attach something so I am attaching the word doc from the KB. To attach a document: when you click the reply button, underneath the box where you type, on the right, the text "Use rich formatting" appears. If you click on the text, your reply window will get fancier and you will see the Insert option, which you can use[View:/cfs-file/__key/communityserver-discussions-components-files/18/KB1836688-How-do-I-validate-my-ACA-XML-Files-Schema-_2800_1_2900_.docx:320:240] to attach a file.

0712131256598360.doc

unknown

Thank you so much! It really helped however, I keep getting the error-"Error loading schema 'IRS-ACAUserinterfaceHeaderMessage.xsd' Could not find file (specific file folder)

unknown

I used the software Altova XMLSpy2018. Are you using the same software? When I downloaded the IRS file, it was in a compressed zip file format. I had to unzip the file. I also had to copy the XML files created by PR299 to the MSG folder of the IRS File. (See Screenshot)

unknown

I need some help. I've downloaded the Altova XMLSpy2018 and I've read through the KB 1836688, but I cannot figure out how to "process to validate" the Manifest and Forms XML files. Can anyone guide me through this?

sriman-shivakoti

Did you download the IRS schema? Did you place your xml files in the MSG folder that is in the IRS download?

unknown

Yes, I did that. But I can't figure out what to do next?

unknown

Our analyst transmitted our files and had the p3:ContactPhoneNum flagged, then asked if I would look at the xml files. Phone number has hyphens, which I assume are not allowed (I checked last years files and they hyphenless). Can I just edit the file, and tell him to resubmit?

sriman-shivakoti

Mike,

If you do that, I would recommend you check the byte size of the file to see if you need to adjust the size in the manifest file and create a new CHECKSUM.... number.

Sometimes, it is easier to correct in Lawson and rerun. I am surprised that isn't one of the items Lawson automatically removed from the xml file. They do remove a lot characters that aren't allowed.

sriman-shivakoti

Cyndie,

I think this is what I did. I am by now means and xml editor so techie people can laugh if they want to do so.

I put my xml files in the MSG folder, started up the xml editor program, took the irs file and put it in the spot where you load the files in the xml editor, then I put our associated output file in the editor.

If there were errors, they showed up.

Our manifest file did not have errors but our detail xml file did (double spaces in places between the number in an addresses and the street name for example.

I hope this helps you.

I wanted to pull my hair out until our folks were successful.

It was more stressful than the very fist year.

The IRS site could be more user friendly. Uploading W-2 info to SSA is much easier. Hope I retire before they mess that up.

unknown

Hi,

I am going to do screenshots.

1:Open of the BN299 XML files sitting in the MSG folder. I am using the Manifest XML as an example.

2: Click on the DTD/Schema Menu Item

3: Select the appropriate xsd file. (for instance: IRS-ACAUserInterfaceHeaderMessage.xsd for the Manifest XML file)

4: Press F8 (validate) or Click the page icon with the Check Mark.

Once done, I exit without saving. repeat same steps for AXA Forms XML Schema.

unknown

Our analyst tried submitting our BN299 files and the 1094-C was rejected, so I was given an "opportunity". Loaded the XML tool suggested and IRS guidelines. The XML reader pointed out 4 errors.

The easy one was a zipcode had a leading space.

Two errors were for former employees that have since relocated internationally and it balked at the line <ForeignProvinceNm> </ForeignProvinceNm> in the <ForeignAddressGrp>. My guess is that the State or Province field that used to contain 'MN' is now blank or not null. Has anyone else encountered this? Is there a way to fix the field in HR11? The quick & dirty fix would seem to be to just delete the line from XML file and recalculate the checkesum.

The fourth error was at the line <Section4980HReliefInd>1</Section4980HReliefInd> imbedded in <Form1094CUpstreamDetail. Anyone have any ideas? This section looks the same as what was transmitted and accepted last year, but of course I admit that i suffer from "male blindness" and that I am more concerned with my major software upgrade on our Student Information System that starts tonight at 5pm (start of someone elses Spring Break).

thanks for any assistance

unknown

Mike, on the 4th error - assuming it is currently populated with 0 or 1, try overtyping the value. Also, it's optional, so you could try removing it and see if the error goes away or moves to the next line.

unknown

We also have issues with foreign addresses. We have found over the years that it is best to identify these as early in your process as possible and test thoroughly.

In previous years we “fixed” foreign addresses in the BN299 IRS xml file but that was not my first preference so this year we took a different approach.

Depending on your HR11 rules you may or may not be able to "fix" on HR11. You will want to be looking at both the State and Country fields. If you cannot fix on HR11 you may need to “fix” in the database itself (EMPLOYEE table).

Be aware that the Lawson Country codes do not always match up with the IRS Country codes. Obtain the IRS Country Codes and be sure you use those for HR11/xml file.

By fixing our foreign addresses this way we did not have to adjust the IRS xml file this year and our files have been Accepted.

Another thing to watch for is making sure your foreign addresses are correct in the BN297 forms file, especially if you actually mail the forms.

unknown

I *think* the 1094C files are good (Altova verified them), I tossed them back 'over the wall' to the business analyst for resubmission. Thanks to the group for volunteering their expertise. Special thanks to Patti, Margie, & Jeano for sharing links and screenshots they were invaluable!

Copyright © 2025 Infor. All rights reserved.