Foreign Address Group in Form File

Has anyone else experienced the address block in the form file coded as Foreign?

Our file was rejected for that, and I am now editing the form file because I cannot figure out what is causing the BN299 to treat our address as foreign,

the manifest is correct. I know that as soon as I change the address block that probably invalidates the checksum and here we go again!

Wichtige Lösungen in der Wissensdatenbank Februar 2012.pdf

Find more posts tagged with

Comments

rkhafaji

We have a similar problem. Ours appears to be due to the address truly being foreign, but we get a schema error:

The element 'ForeignAddressGrp' in namespace 'urn:us:gov:treasury:irs:ext:aca:air:7.0' has invalid child element 'CountryName' in namespace 'urn:us:gov:treasury:irs:common'. List of possible elements expected: 'ForeignProvinceNm, ForeignPostalCd' in namespace 'urn:us:gov:treasury:irs:common'.

Legacy Contributor

We are also getting errors on our two foreign addresses. Does anyone have foreign addresses that were accepted in your XML IRS filing without errors? We would like to understand what the IRS is expecting to see for foreign addresses. I also opened an incident with Infor.

rkhafaji

I have an incident open with support regarding this and just posted the following ---

After more investigation, I've found the following:

Here is the block of schema in question within the foreign address group.

<xsd:choice>

<xsd:element ref="CountryCd"/>

<xsd:element ref="irs:CountryNm"/>

</xsd:choice>

Notice it is clearly a choice of EITHER CountryCd or CountryNm, notice also that the tag is *CountryNm*

Now here is a block of XML with a foreign address:

<ForeignAddressGrp>

<AddressLine1Txt>Rua da Vila do Seixal</AddressLine1Txt>

<AddressLine2Txt>No 17 2 dto</AddressLine2Txt>

<irs:CityNm>Almada</irs:CityNm>

<CountryCd>PO</CountryCd>

<irs:CountryName>Portugal</irs:CountryName>

<irs:ForeignProvinceNm></irs:ForeignProvinceNm>

<irs:ForeignPostalCd> </irs:ForeignPostalCd>

</ForeignAddressGrp>

Notice that it clearly has both country code and country name and that the tag is incorrect as well! This is obviously a problem in the BN299 or the associated library routine. How is this going to be addressed?

---

Legacy Contributor

Thank you! Infor has responded to my incident about this, but has not supplied a solution. I will repeat what you said in your post and ask when BN299 will be fixed.

Legacy Contributor

I also found this on the IRS site as we had the same issues. It looks like it does have to be either the country code or country name. It only worked when we removed the country name.

rkhafaji

The latest update from Infor was a workaround to modify the XML output and remove the Country Name line. We did this today and then updated the Manifest with the new byte count and checksum. The file was accepted after we did this.

Legacy Contributor

We also received a response from our Infor incident as follows:

The IRS changed how it wanted foreign address and no longer accepts the tag for </irs:CountryName> in the ForeignAddressGrp. Are able you to fix in the .xml files? You would need to run BN299 to create new files and edit the .xml to remove the countryname. In the <ForeignAddressGrp> the following tag (with data) should be removed:

<irs:CountryName></irs:CountryName>

After changing the file, the byte size and checksum will need to be corrected - this is in the Manifest.xml. This is documented in Step 7 of the following: KB 1836992 How do I submit an ACA Replacement XML File?

Copyright © 2025 Infor. All rights reserved.