Section 4 Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the…
Publication 5258 — Guide for Affordable Care Act (ACA) Information Returns (AIR) Submission Composition and Reference Guide · 2026-10-03 edition · updated 2026-10-04 · United States
The ISS-UI Channel is a Web Browser based user interface that allows transmitters to submit Form Data Files to IRS and retrieve acknowledgments. The purpose of this section is to describe the requirements for submitting an ACA Information Return Form Data File to IRS via the UI Channel.
4.1 | Transmitter Operations
As shown below, Figure 4-1: ISS-UI Channel Features, the operations available to transmitters, provided by the ISS-UI Channel are: A) Upload ACA Forms, and B) Check Transmission Status.
Figure 4-1: ISS-UI Channel Features
Guide for ACA Information Returns Submission Composition and Reference Guide 20
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
4.2 | Transmitting UI Files to IRS
Figure 4-2: ISS-UI Channel Transmission Submission Screen, shows the capability of the ISS- UI Channel that allows a transmitter to upload the Manifest file and the associated Form Data File containing either Forms 1094/1095-B or Forms 1094/1095-C submissions. The number of records that can be included in the Form Data File is only constrained by the 100 MB file size limit. The transmitter will have to provide information about the transmission, and the transmission itself, through ISS-UI channel. The transmitter provides a UTID in the transmission manifest file which will be uploaded along with transmission file. IRS recommends that external users validate their XML files against the schemas provided by IRS prior to submitting them to IRS. Taking this step will help avoid discovering errors after the XML file is submitted.
Performing this validation on the user end makes it easier and faster to identify and locate schema errors. Any tool which allows the external user to validate their XML files against the schemas, such as “Altova XMLSpy” or “SoapUI” should be suitable.
Once the transmission Manifest and transmission files are uploaded and validated by IRS, IRS generates a Receipt ID which will be displayed to the transmitter. The Receipt ID is used to retrieve the Acknowledgement after the transmission is processed. It is also used in combination with other identifiers to uniquely identify records in a transmission.
Note: It is very important that the Receipt ID be recorded and associated with the correct transmission. It will be needed to retrieve acknowledgements and may be needed for any corrections or replacements.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 21
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Figure 4-2: ISS-UI Channel Transmission Submission Screen
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 22
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Figure 4-3: ISS-UI Channel Transmission Submission Screen
The above Transmission Cancellation Pop-up shows a cancellation warning of a UI Channel Transmission Submission Screen and the option to select the “Yes” or “No” button.
4.2.1 | Sample Manifest File
To create the Request Manifest XML file, Transmitters should use IRSACAUserInterfaceHeaderMessage.xsd schema.
There is no requirement for naming the Manifest XML file. However, the suggested way is as follows:
Manifest_<Form Data File Name (without extension)>.xml For example: Manifest_1094B_Request XXXXX20140101T010102000Z.xml
Note that the resulting Manifest file will include both the Manifest Header and the ACA Business Header and should be ready for upload.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 23
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
The following is a sample of the Manifest XML file that would be uploaded via the ISS-UI channel:
<p:ACAUIBusinessHeader xmlns:p=”urn:us:gov:treasury:irs:msg:acauibusinessheader”
xmlns:p1=”urn:us:gov:treasury:irs:msg:acabusinessheader”
xmlns=”urn:us:gov:treasury:irs:ext:aca:air:tyYY 1 ”
xmlns:irs=”urn:us:gov:treasury:irs:common”
xmlns:p2=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility- 1.0.xsd”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=”urn:us:gov:treasury:irs:msg:acaui
businessheader IRS-ACAUserInterfaceHeaderMessage.xsd “>
<p1:ACABusinessHeader p2:Id=”idvalue0”>
1 Author replaced ty22 with tyYY - Use of generic namespace text to minimize need for Current Tax Year updates and continued document maintenance.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 24
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Figure 4-4: Sample Manifest File
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 25
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
4.2.2 | Sample Form Data File
To create the Form Data File: (1094/1095-[B,C]), Transmitters should use the following schema files:
–IRS-Form1094-1095BTransmitterUpstreamMessage.xsd –IRS-Form1094-1095CTransmitterUpstreamMessage.xsd
The following is a sample of the Form Data File XML file that would be uploaded via the ISS-UI channel:
<p:Form109495BTransmittalUpstream** **xmlns:p=”urn:us:gov:treasury:irs:msg:form1094-1095Btransmitterupstreammessage”** **xmlns:p1=”urn:us:gov:treasury:irs:ext:aca:air:tyYY”** **xmlns:p2=”urn:us:gov:treasury:irs:common”** **xsi:schemaLocation=”urn:us:gov:treasury:irs:msg:form1094- 1095Btransmitterupstreammessage IRS-Form1094-** **1095BTransmitterUpstreamMessage.xsd “> <p1:Form1094BUpstreamDetail lineNum=”0”** **recordType=””> p1:SubmissionId1 p1:TaxYr2021 p1:BusinessName p1:BusinessNameLine1TxtInformation Systems p1:BusinessNameLine2TxtLimited p1:BusinessNameControlTxtWORK p2:TINRequestTypeCdBUSINESS_TIN p2:EmployerEIN000001966 p1:ContactNameGrp p1:PersonFirstNmMargaret p1:PersonMiddleNmP p1:PersonLastNmCarter p1:SuffixNmMs p1:ContactPhoneNum3012223333 p1:MailingAddressGrp
<p:Form109495BTransmittalUpstream** **xmlns:p=”urn:us:gov:treasury:irs:msg:form1094-1095Btransmitterupstreammessage”** **xmlns:p1=”urn:us:gov:treasury:irs:ext:aca:air: tyYY” xmlns:p2=”urn:us:gov:treasury:irs:common”** **xmlns:p3=”http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd”** **xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”** **xsi:schemaLocation=”urn:us:gov:treasury:irs:msg:form1094-1095Btransmitterupstreammessage IRS-Form1094-** **1095BTransmitterUpstreamMessage.xsd “> <p1:Form1094BUpstreamDetail lineNum=”0”** **recordType=””> p1:SubmissionId1
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 26
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
p1:TaxYr2021 p1:BusinessName p1:BusinessNameLine1TxtBusinessNameLine1Txt p1:BusinessNameLine2TxtBusinessNameLine2Txt p1:BusinessNameControlTxtHERR p2:TINRequestTypeCdINDIVIDUAL_TIN p2:EmployerEIN000000000 p1:ContactNameGrp p1:PersonFirstNmPersonFirstNm p1:PersonMiddleNmPersonMiddleNm p1:PersonLastNmPersonLastNm p1:SuffixNmSuffixNm p1:ContactPhoneNum0000000000 p1:MailingAddressGrp p1:USAddressGrp p1:AddressLine1TxtAddressLine1Txt p1:AddressLine2TxtAddressLine2Txt p2:CityNmCityNm p1:USStateCdAL p2:USZIPCd00000 p2:USZIPExtensionCd0000 p1:Form1095BAttachedCnt1 <p1:Form1095BUpstreamDetail lineNum=”0”** **recordType=””> p1:RecordId1 p1:CorrectedInd0 p1:TaxYr2021 p1:ResponsibleIndividualGrp p1:ResponsibleIndividualName p1:PersonFirstNmPersonFirstNm p1:PersonMiddleNmPersonMiddleNm p1:PersonLastNmPersonLastNm p1:SuffixNmSuffixNm p1:PersonNameControlTxtHERR p2:TINRequestTypeCdINDIVIDUAL_TIN p1:TIN000000000 p1:MailingAddressGrp p1:USAddressGrp p1:AddressLine1TxtAddressLine1Txt p1:AddressLine2TxtAddressLine2Txt
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 27
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
p2:CityNmCityNm p1:USStateCdAL p2:USZIPCd00000 p2:USZIPExtensionCd0000 p1:HealthCoverageOriginCdA p1:SponsoringEmployerInfoGrp p1:BusinessName p1:BusinessNameLine1TxtBusinessNameLine1Txt p1:BusinessNameLine2TxtBusinessNameLine2Txt p1:BusinessNameControlTxtHERR p2:EIN000000000 p2:TINRequestTypeCdINDIVIDUAL_TIN p1:MailingAddressGrp p1:USAddressGrp p1:AddressLine1TxtAddressLine1Txt p1:AddressLine2TxtAddressLine2Txt p2:CityNmCityNm p1:USStateCdAL p2:USZIPCd00000 p2:USZIPExtensionCd0000 p1:IssuerInfoGrp p1:BusinessName p1:BusinessNameLine1TxtBusinessNameLine1Txt p1:BusinessNameLine2TxtBusinessNameLine2Txt p1:BusinessNameControlTxtHERR p2:TINRequestTypeCdINDIVIDUAL_TIN p2:EIN000000000 p1:ContactPhoneNum0000000000 p1:MailingAddressGrp p1:USAddressGrp p1:AddressLine1TxtAddressLine1Txt p1:AddressLine2TxtAddressLine2Txt p2:CityNmCityNm p1:USStateCdAL p2:USZIPCd00000 p2:USZIPExtensionCd0000
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 28
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
p1:CoveredIndividualGrp p1:CoveredIndividualName p1:PersonFirstNmPersonFirstNm p1:PersonMiddleNmPersonMiddleNm p1:PersonLastNmPersonLastNm p1:SuffixNmSuffixNm p1:PersonNameControlTxtHERR p2:TINRequestTypeCdINDIVIDUAL_TIN p2:SSN000000000 p1:CoveredIndividualAnnualInd0 p1:JuratSignaturePIN00000 p1:PersonTitleTxtPersonTitleTxt p1:SignatureDt2020-01-01
Figure 4-5: Sample 1094-1095 B Form Data File
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 29
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
4.3 | Retrieving Acknowledgment from IRS
Transmitters must submit a request to retrieve the processing status and error detail of their transmission which is known as the Acknowledgement. To retrieve the Acknowledgement, the transmitter must provide their Transmitter Control Code (TCC) and the Receipt ID or UTID from the transmission for which they are requesting the processing status. The below screen shots are ISS-UI Channel Transmission Status Retrieval Screens depicting the Transmission Retrieval features.
Figure 4-6a: Transmission Status Search Page (TCC and Receipt ID)
Figure 4-6b: Transmission Status Search Page (UTID)
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 30
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Note: The UTID can also be used to check the status of a transmission. The Schema allows either Receipt ID or the UTID to check status.
Figure 4-7: A2A Check Status using UTID Request
Figure 4-8: A2A Check Status using UTID Response to Transmitter
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 31
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
4.4 | Transmitter IRS Form Data File Specification
Please refer to Section 3 – Composing IRS ACA Information Returns Transmission for details on composing an IRS ACA Form Data File that will be submitted by a transmitter to IRS.
4.5 | Transmitting Information Returns to IRS
In order to transmit a Form Data File through the ISS-UI channel, a transmitter must have an active IRS e-Services account, an ACA Transmitter Control Code (TCC), and must be using IRS approved software to submit returns or retrieve acknowledgements. The transmitter will be required to interactively log in to IRS web site with their web browser and invoke the appropriate URL for AIR. The application will allow transmitters to submit information returns to IRS using the following browsers:
1. Microsoft Edge
2. Firefox
3. Safari 9 (or latest supported version)
4. Chrome
The transmitter must have two XML files to submit a single transmission via the ISS-UI Channel. The Manifest file will contain information in uncompressed native XML format related to the transmitter and the transmission. The Manifest file will include the Manifest Header XML as defined by the XML Schema located at Affordable Care Act Information Returns Schemas in IRS-Form1094-1095BCTransmitterReqMessage. xsd file located in the MSG folder of the schema. Many of the elements in the Transmission Data File will not change from transmission to transmission and thus can be reused. Elements such as the transmitter information (TransmitterNameGrp, TransmitterForeignEntityInd, MailingAddressGrp, SoftwareID, etc.) should not change frequently, if at all. Other elements in the Manifest file are likely to change for every transmission. Elements such as the transmission information (total payer and payee counts, checksum, file byte size, document file name, etc.) will be different for every transmission. Section 4.2.1, Sample Manifest File – Manifest Header, includes the elements that are required in the Transmission Data File.
The Form Data File will contain Forms 1094/1095-B or Forms 1094/1095-C data in uncompressed native XML format relative to the Form 1094/1095 data. Once the required files are uploaded to IRS, the transmitter will receive a Receipt ID, and other information about the transmission, as part of the interactive session.
The Receipt ID does not provide proof that the transmission was either Accepted or Rejected. The Receipt ID simply provides proof that IRS received the transmission. The transmitter must retrieve their Acknowledgement using the TCC and Receipt ID or the UTID to obtain proof of acceptance or rejection.
The web interface will only accept uncompressed native XML files. Security checking (XML Threat detection, virus scanning, etc.) is performed on each file before routing to IRS back-end systems.
Transmitters that take advantage of the ISS-UI Channel to submit their transmissions will have to log into IRS from a web browser on their local systems. The URL for AIR that facilitates interaction with the transmitter community will be provided on the Affordable Care Act Information Returns (AIR) page and other related guidance and Job Aids produced by IRS will also be available to the transmitters on the AIR page. The ISS-UI Channel will guide the transmitters through all the steps necessary to upload the required files from their local systems.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 32
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
The Form Data File that a transmitter uploads through the ISS-UI Channel must contain valid XML. Open tags
must be followed by closed tags. For example, the open tag
Empty tags should not be included in Form Data File. The Form Data File must conform to the XML Schema definitions included in the applicable xsd files. Table 4-1 maps the ACA forms to the XML Schema file names.
Table 4-1: Forms to XML Schema File Mapping
Applicable Forms XML Schema Root Element File
Form 1094-B/1095-B IRS-Form1094-1095BTransmitterUpstreamMessage.xsd
Form 1094-C/1095-C IRS-Form1094-1095CTransmitterUpstreamMessage.xsd
All of the required information for a transmission will be included in the file that is uploaded, including the transmission information, the form type, the Form 1094 form elements and the Form 1095 form elements.
4.5.1 | Validation of IRS Form Data File
IRS performs security checks on the Form Data File received from the transmitter. If no security threats are detected, IRS generates the Receipt ID and returns it along with the Timestamp to the transmitter. Each Receipt ID uniquely identifies a Form Data File submitted to IRS. The TCC and Receipt ID or the UTID is used to retrieve the status of the transmission. As such, the Receipt ID returned to the transmitter should be kept with the Form Data File submitted and protected from loss or deletion.
When IRS receives the uploaded Form Data File, the following checks are performed:
1. The file must be free of viruses 2. The file size must not exceed 100 MB 3. The file must be readable by AIR 4. The IRS application must be able to write the file to disk 5. The file must pass XML validations 6. The file must not contain comingled Forms 1094/1095-B and Forms 1094/1095-C 7. UUID is verified to be unique for the TCC 8. Metadata entered by the transmitter is checked for any discrepancies 9. Duplicate transmission check is performed using the DocumentSystemFileNm, Checksum and TCC 10. The reported checksum must match with IRS calculated checksum
4.5.2 | Processing of IRS Form Data File
Once the file is processed, the status is made available for the transmitter to retrieve through Retrieve Acknowledgement web service described below. When errors are identified during file processing (such as read/write errors, invalid XML, etc.), the transmission is rejected and appropriate error(s) and description(s) are returned to the transmitter through the user interface. When business rule errors are identified during processing the XML Form Data File, IRS will record these error codes and their descriptions and return them in an XML Error Data File attached to the Acknowledgement message which the transmitter will retrieve. The transmitter will have an opportunity to correct the errors and resubmit the Form Data File.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 33
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
4.6 | Retrieving Status of the Transmission through UI
After the transmitter successfully uploads a Form Data File and receives a Receipt ID, they will use the TCC and Receipt ID or the UTID to request the Acknowledgement for that transmission. Transmitters should wait at least 10 minutes after the Receipt ID is provided to request the Acknowledgement for a transmission. The transmitter is required to log in to IRS web site and invoke the appropriate URL provided by IRS. The transmitter shall select the option to retrieve one or more Acknowledgements from user interface. The TCC and Receipt ID or the UTID is the key information required for a transmitter to retrieve the Acknowledgement for a specific transmission. As such, when the transmitter receives the Receipt ID, it should be kept with the transmission and protected from loss or deletion.
Figure 4-9: ISS-UI Channel Transmission Status Results Screen, is showing a sample transmission status retrieved using the ISS-UI Channel Transmission Status Retrieval feature.
Figure 4-9: ISS-UI Channel Transmission Status Results Screen
The status of the transmission includes one of the outcomes identified in Table 4-2.
Table 4-2: Transmission Processing Status Included in Acknowledgement
| Transmission Status | Description |
|---|---|
| Processing | IRS has not completed processing the transmission. |
| Accepted | IRS has completed processing the transmission and found no errors. |
| Accepted with Errors | IRS has completed processing the transmission and the errors are documented in the Error Data File attached to the Acknowledgement. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 34
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
| Transmission Status | Description |
|---|---|
| Partially Accepted | IRS has completed processing the transmission and has rejected at least one (but not all) of the submissions. An Error data fle will be attached to the Acknowledgement File. |
| Rejected | IRS has rejected the transmission – depending on why the transmission was rejected, an Error Data File may or may not be attached to the Acknowledgement. |
| Not Found | IRS could not fnd a transmission corresponding to the Receipt ID provided. If the Receipt ID doesn’t match with IRS generated Receipt ID, the Receipt ID doesn’t belong to the Transmitter TCC. |
The transmission Acknowledgement includes the status of the transmission, and if applicable, details of errors such as any business rules validation errors, and TIN validation errors that were found when IRS processed the Form Data File.
The details of errors found when IRS processed the Form Data File are included in an Error Data File that can be viewed and downloaded through the ISS-UI user-interface. The Acknowledgement includes the errors found, in XML format, during Form Data File processing. If no errors are found during processing, no Error Data File will be included with the Acknowledgement and the transmission processing status will be “Accepted”. The transmission Acknowledgement may include:
• Unique Transmission ID (UTID) Transmitter Control Code (TCC)
• Shipment Number assigned to the transmission Receipt ID
• Form Type Code Timestamp
• Transmission Status Code: Processing, Partially Accepted, Accepted, Accepted with Errors, Rejected, Not Found
• Error Message Detail Errors (if applicable – included in the Error Data File)
4.7 | IRS Error Data File
IRS accumulates any errors encountered during Form Data File processing in the Error Data File. As with the Form Data File 100 MB size constraint, Error Data Files are also constrained by a 200 MB size limitation. Only one Error Data File will ever be created per transmission. It is possible that the Error Data File could contain a significantly large number of errors that the 200 MB file size limitation is exceeded. In this case, while AIR will process the entire Form Data File and record all of the errors found, the Error Data File will be truncated and a message will be placed at the end of the file indicating that it was truncated. Error Data Files that exceed the 200 MB size constraint are typical of a systemic problem within the Form Data File that when addressed will substantially reduce the number of errors found. To submit questions about electronic filing Forms 1094-B, 1094-C, 1095-B and 1095-C contact the AIR Help Desk at 866-937-4130 for domestic calls, or 470-769-5100 (not toll free) for international calls. The AIR Help Desk hours of operation are 6:30 a.m. to 6 p.m., Monday through Friday, Central Time.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 35
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Include the Receipt ID, ACA TCC, and Year of the ACA forms if known. The Error Data File is returned in ACA Assurance Testing System (AATS) and Production Environment.
The Error Data File includes the following data:
• The identifier that uniquely identifies the record with an error (Unique Submission Identifier or Unique Record Identifier)
• The error message code indicating what the error is
• The error message text explaining what the error is
• The element that was in error
•
Figure 4-10 provides an example of the information that will be displayed on-screen in the ISS- UI.
Note: the “Download” button that enables the transmitter to download the Error Data XML File.
Figure 4-10: Example of Acknowledgement via ISS-UI Channel
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 36
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Figure 4-11 provides an example of the information that will be included in the Error Data File (which contains the error codes, the error descriptions, and the XPath reference to the element found to be in error), that can be downloaded via the ISS-UI channel.
<ns3:FormBCTransmitterSubmissionDtl**
**xmlns=”urn:us:gov:treasury:irs:ext:aca:air:tyYY”**
**xmlns:ns2=”urn:us:gov:treasury:irs:common” xmlns:ns3=”urn:us:gov:treasury:irs:msg:form1094-1095BCtransmitter-**
**message”>
Figure 4-11: Error Data XML File
Note: XML structure of Error Data File and library import will always follow the TY2026 schema package.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 37
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
4.8 | UI Channel TY2017, TY2018, TY2019, TY2020, TY2021, TY2022,TY2023, TY2024, TY2025 and TY2026 Schemas
Transmitters sending returns through UI Channel (AATS and Production):
- AIR will accept Tax Years 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026 for processing
year 2027
- Transmitters should use latest the TY2026 schema version to generate Forms 1094/1095-B or
Forms 1094/1095-C Form Data (payload) for TY2026 returns
For prior year returns TY2017, TY2018, TY2019, TY2020, TY2022, TY2023, 2024, TY2025, use the latest year schema for that tax year for the Form Data (payload).
Example: Transmitters should use latest TY2019 schema version to generate Forms 1094/1095-B or Forms 1094/1095-C Form Data (payload) for TY2019 returns
Forms 1094/1095-B and Forms 1094/1095-C: Manifest element:
Transmitter should use Manifest schema from TY2026 schema package to generate TY2017, TY2018, TY2019, TY2020, TY2021, TY2022, TY2023, TY2024, TY2025 and TY2026 Manifest file.
Example:
2015 Manifest will be checked and validated against TY2025 manifest schema and business rules.
4.9 | 4.9 Calculate AttachmentByteSizeNum for TY2017, TY2018, TY2019, TY2020, TY2021, TY2022, TY2023, TY2024, TY2025 and TY2026
Right click on Form Data File, click on “Properties” copy the size in bytes (not “Size of Disk”) and paste on Manifest element:
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 38
Transmitting IRS ACA Form Data File and Retrieving Acknowledgment via the ISS-UI Channel
Get a plain-English answer with a citation back to this text.
Ask AI about this code