I tried the official copy listed in the reference guide for presentation and composition, with no luck (below):
<?xml version="1.0" encoding="UTF-8"?> <p:ACAUIBusinessHeader xmlns:p="urn:us:gov:treasury:irs:msg:acauibusinessheader" xmlns:acaBusHeader="urn:us:gov:treasury:irs:msg:acabusinessheader" xmlns="urn:us:gov:treasury:irs:ext:aca:air:7.0" xmlns:irs="urn:us:gov:treasury:irs:common" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurityutility-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:us:gov:treasury:irs:msg:acauibusinessheader IRSACAUserInterfaceHeaderMessage.xsd"> <acaBusHeader:ACABusinessHeader> <UniqueTransmissionId>token</UniqueTransmissionId> <irs:Timestamp>2016-12-31T12:00:00</irs:Timestamp> </acaBusHeader:ACABusinessHeader> <ACATransmitterManifestReqDtl> <PaymentYr>2015</PaymentYr> <PriorYearDataInd>0</PriorYearDataInd> <irs:EIN>EIN</irs:EIN> <TransmissionTypeCd>O</TransmissionTypeCd> <TestFileCd>TestFileCd</TestFileCd> <OriginalReceiptId>OriginalReceiptId</OriginalReceiptId> <TransmitterForeignEntityInd>0</TransmitterForeignEntityInd> <TransmitterNameGrp> <BusinessNameLine1Txt>BusinessNameLine1Txt</BusinessNameLine1Txt> <BusinessNameLine2Txt>BusinessNameLine2Txt</BusinessNameLine2Txt> </TransmitterNameGrp> <CompanyInformationGrp> <CompanyNm>CompanyNm</CompanyNm> <MailingAddressGrp> <USAddressGrp> <AddressLine1Txt>AddressLine1Txt</AddressLine1Txt> <AddressLine2Txt>AddressLine2Txt</AddressLine2Txt> <irs:CityNm>CityNm</irs:CityNm> <USStateCd>AL</USStateCd> <irs:USZIPCd>USZIPCd</irs:USZIPCd> <irs:USZIPExtensionCd>USZIPExtensionCd</irs:USZIPExtensionCd> </USAddressGrp> </MailingAddressGrp> <ContactNameGrp> <irs:PersonFirstNm>PersonFirstNm</irs:PersonFirstNm> <irs:PersonMiddleNm>PersonMiddleNm</irs:PersonMiddleNm> <irs:PersonLastNm>PersonLastNm</irs:PersonLastNm> <irs:SuffixNm>SuffixNm</irs:SuffixNm> </ContactNameGrp> <ContactPhoneNum>ContactPhoneNum</ContactPhoneNum> </CompanyInformationGrp> <VendorInformationGrp> <VendorCd>VendorCd</VendorCd> <ContactNameGrp> <irs:PersonFirstNm>PersonFirstNm</irs:PersonFirstNm> <irs:PersonMiddleNm>PersonMiddleNm</irs:PersonMiddleNm> <irs:PersonLastNm>PersonLastNm</irs:PersonLastNm> <irs:SuffixNm>SuffixNm</irs:SuffixNm> </ContactNameGrp> <ContactPhoneNum>ContactPhoneNum</ContactPhoneNum> </VendorInformationGrp> <TotalPayeeRecordCnt>0</TotalPayeeRecordCnt> <TotalPayerRecordCnt>1</TotalPayerRecordCnt> <SoftwareId>SoftwareId</SoftwareId> <FormTypeCd>1094/1095B</FormTypeCd> <irs:BinaryFormatCd>application/xml</irs:BinaryFormatCd> <irs:ChecksumAugmentationNum>ChecksumAugmentationNum</irs:ChecksumAugmentationNum> <irs:AttachmentByteSizeNum>0</irs:AttachmentByteSizeNum> <DocumentSystemFileNm>DocumentSystemFileNm</DocumentSystemFileNm> </ACATransmitterManifestReqDtl> </p:ACAUIBusinessHeader>
Of course, when you add your own information and submit it to the ISS-UI AATS 2016 website, it simply says:
1 error has occurred. See below for more information. If the problem continues, please contact us. Our system has detected a potential threat in the file you are attempting to transmit and it can not be transmitted. Please check the file and try again.
After starting the sample file with XSD, it shows that the timestamp format is incorrect (at the end it needs āZā) and the prefixes on ā irs:PersonFirstNm ā, ā irs:PersonLastNm ā, ā irs:PersonMiddleNm 'should not be.
After I changed this, the file successfully passed the XSD check, but the same error is displayed:
1 error has occurred. See below for more information. If the problem continues, please contact us. Our system has detected a potential threat in the file you are attempting to transmit and it can not be transmitted. Please check the file and try again.
Is there anyone currently working against the IRS AIR ACA system, and does anyone have an instance of the manifest file that they submitted in what they know? I pinged the IRS help desk for more information, but they take 7 business days to get back to you.
source share