Hash Key
0926 Publ 5165 (PDF) · 2026-10-03 edition · updated 2026-10-04 · United States
IRS will reject a transmission that contains any of the special characters identified in Table 4-2, either in the SOAP Message or in the XML file, upon receipt.
Example 1: If a record has a last name data field containing MyCorp #10, then the transmission must not include the hash key/pound sign, so that the data field instead contains MyCorp 10 .
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 26
Transmitting Information Returns
Example 2: If a record has an address data field containing NoPlaceWay--Suite 4, then the transmission must not include the double dash, so that the data field instead contains NoPlaceWay-Suite 4 .
The following special characters must be escaped before they are included in the data fields that allow escaped characters of either Forms 1094/1095-B or Forms 1094/1095-C transmissions:
Table 4-3: Allowable Characters
| Character | Character Description | Character Allowed? | Escape Characters | Escape Character Allowed |
|---|---|---|---|---|
| & | Ampersand | Rejected | & | Allowed |
| ‘ | Apostrophe | Rejected | ' | Allowed |
| < | Less Than | Rejected | < | Allowed |
| “ | Quotation Mark | Rejected | " | Allowed |
| > | Greater Than | Allowed | > | Allowed |
*Caution: “ PersonFirstNm ”, “ PersonMiddleNm ”, and “ PersonLastNm ” cannot contain any special characters. For example, if a record has a last name data field containing an apostrophe, such as “ O’Malley ”, the transmission cannot include the apostrophe or the escaped apostrophe characters. The apostrophe must be stripped, and the last name data must be entered as “ OMalley ”. The transmission will be rejected if the apostrophe is used. As a rule, the schema definitions must be followed.
However, the escaped apostrophe will be allowed in the “BusinessNameLine1Txt” and “BusinessNameLine2Txt” schema elements. Any special characters that are not listed in the Table 4-3 or Table 4-4 will be allowed as-is. For example, a hyphen is allowed in the “ PersonFirstNm ”, “ PersonMiddleNm ”, “ PersonLastNm ”, “ BusinessNameLine1Txt ” and “ BusinessNameLine2Txt ”.
Additional elements may also be restricted by XML schema data element definitions. For example, the schema does not allow the use of escaped Less Than or escaped Quotation within “ BusinessNameLine1Txt ” and “ BusinessNameLine2Txt ”.
4.3.4 | Tag Names
Each field on the AIR Forms 1094/1095-B or Forms 1094/1095-C is identified using an XML tag name within the XML schema.
Tag names were created using the following conventions:
A meaningful phrase with the first letter of each word capitalized and using no spaces (upper Camel case)
A length of not more than 30 characters
Standard abbreviations to meet the tag name 30-character limit
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 27
Transmitting Information Returns
The Tag Names, also known as Element Names, were standardized by IRS for all ACA Information Return forms. A notional example of a simple XML element that identifies the record number in a submission would be:
<xsd:element ref= _"UniqueRecordId"_ minOccurs= _"1"_ maxOccurs= _"unbounded"_ />
A notional example of a complex XML element that identifies all the data elements required for Form 1094-B would be:
Figure 4-4: Form 1094-B Schema Structure
4.3.5 | Attributes
Attributes provide additional information or describe a constraint of a data element.
- The first letter of the first word of an attribute name is lower case; the first letter of each subsequent
word is capitalized (lower camel case).
For instance, in the example of the simple XML element Form1094BUpstreamDetail above, the attribute maxOccurs = "unbounded" identifies that there is no limit to the number of Forms 1095-B that can be included in the XML. (However, the number of Forms 1095-B included in a submission is constrained by the 100 MB file size limit.)
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 28
Transmitting Information Returns
4.3.6 | Repeating Group
Repeating groups are specified in XML schema definitions using the minOccurs and maxOccurs facets on sequence or choice definitions. An example of a repeating group is as follows:
<xsd:element ref="CoveredIndividualGrp" minOccurs="0" maxOccurs="99"/>
The element ‘CoveredIndividualGrp’ allows a maximum of 99 groups within each 1095 record that is submitted. Beginning and ending tags are necessary for each group submitted. The reference element resolves to the eFile Type EmployerCoveredIndividualType:
<xsd:element name="CoveredIndividualGrp" type="EmployerCoveredIndividualType">
EmployerCoveredIndividualType is a complex data element that includes the nodes Covered Individual Name, Social Security Number or Date of Birth, and several other indicators required for the repeating group. All the elements of the EmployerCoveredIndividualType repeat as each CoveredIndividualGrp are reported.
Figure 4-5: Example of the Covered Individual Repeating Group
The ability to repeat information within the XML Schema is the electronic equivalent of attaching additional forms when there is insufficient space on the form to include all the information that must be filed (e.g., If there are more than six covered individuals, see Form 1095-B Part IV, Continuation Sheet(s), for information about the additional covered individuals.).
4.3.7 | AIR Schema and Business Rules
A schema is an XML document that specifies the data elements, structure and rules for the transmission Manifest and each form or document. In addition to formats defined by schemas, information returns must also adhere to business rules, which provide a second level of validation for information returns processed by the AIR System.
IRS created an XML schema for each of the different types of ACA Information Returns (Form 1094-B, Form 1094-C, Form 1095-B, and Form 1095-C), Transmission File, and Acknowledgement File. Each schema also has a respective set of business rules that are used during AIR validation.
Within the XML schema, data elements are the basic building blocks of an XML document. Schemas recognize two categories of element types: simple and complex. A simple type element contains only one data type and may only have documentation attributes, such as description or line number. A complex type element is an element that has one or more attributes or is the parent to one or more child elements.
The Transmitter and Issuer have the responsibility to provide information as specified by IRS forms, instructions and regulations.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 29
Transmitting Information Returns
Note: The software used to transmit AIR documents to IRS must be capable of putting the information in the specified schema while also abiding by all applicable business rules.
The AIR schemas do not allow empty or null values within schema tags. All data elements present by virtue of an opening and a closing tag must contain a value. Empty or null tags (even for optional data elements) will result in a transmission rejection. Do not include tags for optional data elements that are empty.
Each year, new legislation and/or improvements to IRS programs impact IRS forms and processing procedures. IRS evaluates these changes to determine if updates to the XML schemas and business rules are necessary.
When the AIR schemas are posted on the Affordable Care Act Information Returns (AIR) page, IRS will identify when the schemas are available in the AATS and Production environments. Software Developers are not required to retest when new schemas (minor or major) are posted. However, IRS strongly recommends the use of AATS to retest when Software Developers update their software in response to schema changes. Links to the AIR XML Schemas and Business Rules are located on the Affordable Care Act Information Returns (AIR) page.
Note: If there are critical changes required due to late legislation changes, national disasters, or errors identified during testing or production, IRS may issue updated XML schemas and business rules after December and during the processing year.
General Information about Version Numbers follows:
Each version of the XML Schemas and the corresponding business rules has a unique version number assigned. It is important to note the following principles regarding version numbers:
- Each information return’s schema version has an associated set of business rules with the same version
number. This ensures that each updated schema version includes an updated set of business rules.
- The “ FormnnnnUpstreamDetail Type” complex element includes a documentation element and
dictionary entry name that identifies the form including the major and minor version numbers of the schema for each return type as well as the effective begin date for the XML Schema. For example, the “ Form1095BUpstreamDetailType” from IRS-Form1094-1095BTransmitterUpstreamMessage.xsd file shown below identifies the schema version as v1.0 with an effective date of 2015-01-27.
Figure 4-6: 1095-B Upstream Detail Type
- Each business rule documents version number identifies the version and effective begin date of the
business rules.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 30
Transmitting Information Returns
- The “Active Validating Schema Version” specifies the business rules and schema version that will be
used to validate an information return that has been received by IRS during a timeframe. This provides a mechanism for different versions to be accepted at the same time. It also enables an older version to be validated against a newer version’s set of schemas and business rules. IRS will publish all valid schema/ business rule versions.
The active validating schema version will be the most recent schema version posted on the Affordable Care Act Information Returns (AIR) page. IRS will provide the “Start” dates when schemas are available in Production and AATS. These “Start” dates also represent when the latest schema posted becomes the active validating schema.
4.3.8 | Validating Schema Versions
Throughout the year, multiple versions of XML Schemas and Business Rules may be posted to IRS.gov depending upon whether a change to the schema is major or minor; AIR may not require that the schema version used to submit the return data match the schema version used by AIR during validation. In general, there is one active validating schema version for each return type in a tax year. The Schema/Business Rules tables will include the Start dates and End dates, if applicable, for AATS and Production. IRS strives to limit the number of schema and/or business rule revisions, especially after production opens. A QuickAlerts message is issued when a new version of the XML Schemas and Business Rules are posted on the Affordable Care Act Information Returns (AIR) page.
Minor Schema Changes – When IRS issues revised schemas for an information return type and changes the increment for the minor number, AIR continues to accept returns composed using previous schema versions. When the minor number is changed, IRS allows Software Developers to decide for themselves whether they need to use the latest version or not based on what is included in their tax preparation software and what changes were made to the schemas.
Returns may be composed using previously published schema versions, but IRS will only validate against the “active validating schema version” when the return is processed. For example:
If the current schema version is 1.0 and the schema change is minor, IRS will assign the new number 1.1. The active validating schema version is 1.1. AIR will continue to accept returns composed using version
1.0. However, all returns (whether composed with version 1.0 or 1.1) will be validated with the latest version, 1.1.
Major Schema Change – When IRS issues revised schemas for an information return type and changes the increment for the major number, all returns must be composed by software using the latest version. If information returns are composed using previously published schema versions, they will not validate against the active validating schema version when the return is processed and will be rejected.
For example, if the current version is 1.1 and IRS determines it can no longer accept information returns composed using schema version 1.1 (or v1.0), it will assign the new major number 2.0. The active validating schema version is 2.0. Returns submitted with version 1.1 or earlier will be rejected for using an unsupported schema version.
Software Developers and Transmitters should select the applicable form type on the AIR Schemas and Business Rules page to get information about all active and prior year schemas and business rules used by the AIR Production and AATS.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 31
Transmitting Information Returns
Tax Year 2017 Forms 1094-B, 1094-C, 1095-B, and 1095-C
Version Date Posted AATS Dates Production Dates
Updates: 05/25/2018 New posting of revised Release
Memo and business rule v1.1, v1.2,
v1.3, and v1.4
Start Date: 1/22/2018 Note: Schemas v1.0 and Business Rules v1.1, v1.2, v1.3, and v1.4 are valid for Production.
End Date: TBD
07/02/2017
Start Date: 10/30/2017
Note: Schemas v1.0 and Business Rules v1.1, v1.2, v1.3,
and v1.4 are valid for AATS. End Date: TBD
Figure 4-7: Example of AIR Schema Information
4.3.9 | Example of Schema Versioning
The Affordable Care Act Information Returns (AIR) page provides information and technical guidance for Software Developers and Transmitters who are interested in developing software for AIR for Tax Years 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025 and 2026. Included are the XML Schemas, Business Rules, Release Memorandums and specific instructions.
Note: When creating payload for prior year TY2017, TY2018, TY2019, TY2020, TY2021, TY2022, TY2023, TY2024, TY2025 and TY2026) data, please use the schemas and business rules that were in effect for that tax year. Do not use the current year schemas and rules. In addition, do not mix or combine tax years within the same submission or the same transmission. Transmitters should use the latest schema package Filing Season (FS) 2027 (TY2026) Manifest schema to generate A2A SOAP message or the UI Manifest file regardless of which tax year is being submitted.
Below is a sample of the AIR Forms XML Schema Version
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 32
Transmitting Information Returns
Figure 4-8: Samples of Schema Versioning for AIR Forms
4.4 | Threat Mitigations in AIR Transmissions
Information Submission Services (ISS) will only accept XML files and attachments. Each file, message and/ or attachment transmitted through the ISS-A2A or ISS-UI channels will be checked for threats before being routed to AIR back-end systems. In the event the system detects a threat in the Transmission File, the following steps will be taken:
ISS will perform threat mitigation and initial validation on authorized connections
The Transmission will be rejected and a fault code (TPE Error) response will be returned
The Transmitter must remove the infected data and then retransmit the file
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 33
Transmitting Information Returns
Figure 4-9: Sample of an A2A Channel Fault Message
Figure 4-10: Sample of a UI Channel Fault Message
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 34
Transmitting Information Returns
Table 4-4 below defines fault codes and messages from the ISS.
Table 4-4: List of Fault Codes (TPE Errors) for Tax Years 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2024 2025 and 2026
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1001 | Request | Message Delivery Failure |
A2A | We are experiencing a technical issue. Please try your request again later. We apologize for the inconvenience. |
| TPE1001 | Request | Message Delivery Failure |
UI | We are experiencing a technical issue [Error Code 6052]. Please try your request again later. We apologize for the inconvenience. |
| TPE1101 | Request | Invalid/ Namespace |
A2A | Our system detected invalid or outdated XML namespaces in your message. Please review the XML standards outlined in Section 3 ofPublication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1101 | Request | Invalid/ Namespace |
UI | [TPE1101] Our system detected invalid or outdated XML namespaces in the Manifest fle. Please review the XML standards outlined in Section 3 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Manifest fle, and try again. |
| TPE1102 | Request | Service Window Closed |
A2A | The requested service is not available at this time. Please resubmit during normal operation hours. |
| TPE1102 | Request | Service Window Closed |
UI | *Error not applicable to ISS-UI |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 35
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1104 | Request | Request is not compliant |
A2A | The request is not compliant with web service policy requirements. Please review the transmission instructions outlined in Section 5 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1104 | Request | Request is not compliant |
UI | We are experiencing a technical issue [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE1105 | Request | XML is not well-formed |
A2A | The message was not formatted properly and/ Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1105 | Request | XML is not well-formed |
UI | [TPE1105] Our system has detected a potential threat in the Manifest fle you are attempting to transmit, and it cannot be transmitted. This may be due to malformed XML. Please review the XML standards outlined in Section 3 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Manifest fle, and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 36
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1106 | Request | SOAP message does not conform to WSDL |
A2A | The message did not match our current WSDL and/ the Fault Details information below for the particular element(s) our system has detected a potential issue with. Please review the published WSDLs and schemas located on theAIR page, correct any issues, and try again. |
| TPE1106 | Request | SOAP message does not conform to WSDL |
UI | [TPE1106] The Manifest fle does not match our current schema. In particular, our system has detected a potential issue with the following element(s): and others. Please review the published schemas on theAIR page, correct any issues, and try again. |
| TPE1107 | Request | Message exceeds maximum size limit of 100 MB |
A2A | Request message exceeds the 100 MB maximum size limit. Please review the XML fle standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues with the request, and try again. |
| TPE1107 | Request | Message exceeds maximum size limit of 100 MB |
UI | [TPE1107] The Form fle exceeds the 100 MB size limit. Please review the XML fle standards outlined in Section 3 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues with the request, and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 37
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1108 | Request | Potential Code Injection Threat |
A2A | Our system has detected a potential threat in the transmission and it cannot be transmitted. Please review the XML standards outlined in Section 3 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1108 | Request | Potential Code Injection Threat |
UI | [TPE1108] Our system has detected a potential threat in the Manifest fle and it cannot be transmitted. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Manifest fle, and try again. |
| TPE1109 | Request | Potential SQL Injection Threat |
A2A | Our system has detected a potential threat in the transmission and it cannot be transmitted. Please review the XML standards outlined in Section 3 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1109 | Request | Potential SQL Injection Threat |
UI | [TPE1109] Our system has detected a potential threat in the Manifest fle and it cannot be transmitted. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Manifest fle, and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 38
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1110 | Request | Potential Document Structure Threat |
A2A) | Our system has detected a potential threat in the transmission, and it cannot be transmitted. Please review the XML standards outlined in Section 3 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1110 | Request | Potential Document Structure Threat |
UI | [TPE1110] Our system has detected a potential threat in the Manifest fle and it cannot be transmitted. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Manifest fle, and try again. |
| TPE1112 | Request | HTTP Compression Failure |
A2A | The request message must be sent using HTTP compression (RFC 1952 - GZIP). Please review the transmission instructions outlined in Section 5 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1112 | Request | HTTP Compression Failure |
UI | *Error not applicable to ISS-UI |
| TPE1114 | Request | Message not MTOM encoded |
A2A | The request message must be MTOM encoded. Please review the transmission instructions outlined in Section 5 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1114 | Request | Message not MTOM encoded |
UI | *Error not applicable to ISS-UI |
| TPE1115 | Request | Unable to decode MTOM encoded request message |
A2A | We are experiencing a technical issue. Please try your request again later. We apologize for the inconvenience. |
| TPE1115 | Request | Unable to decode MTOM encoded request message |
UI | *Error not applicable to ISS-UI |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 39
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1118 | Request | UTF-8 BOM encoding in the Manifest fle and cannot be interpreted |
UI only | Our system has detected UTF-8 BOM encoding in the Manifest fle and cannot be interpreted. Please review the XML standards outlined in Section 10 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1122 | Request | Invalid WS Security Signature (Keystore, Password) |
A2A | Our system identifed an issue with the WS-Security Header in your message. Please review the WS-Security instructions outlined in Section 5 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again |
| TPE1122 | Request | Invalid WS Security Signature (Keystore, Password) |
UI | *Error not applicable to ISS-UI |
| TPE1123 | Request | Invalid Digital Signature (Signed Parts) |
A2A | Our system identifed an issue with one or more signed parts in your message. Please review the WS-Security instructions outlined in Section 5 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1123 | Request | Invalid Digital Signature (Signed Parts) |
UI | *Error not applicable to ISS-UI |
| TPE1126 | Request | Failed to connect to the Authentication Policy Server |
A2A | We are experiencing a technical issue. Please try your request again later. We apologize for the inconvenience. |
| TPE1126 | Request | Failed to connect to the Authentication Policy Server |
UI | We are experiencing a technical issue [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 40
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1127 | Request | Missing credentials in HTTP request |
A2A | Message not formatted properly and is missing HTTP credentials. Please check message and try again. |
| TPE1127 | Request | Missing credentials in HTTP request |
UI | We are experiencing a technical issue [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE1128 | Request | Failed to authen- ticate with the Authentication Policy Server |
A2A | We were unable to authenticate your credentials. Please review the information about digital certifcates included in Section 5 of thePublication 5258, AIR Submission Composition and Reference Guide, ensure that the credentials are valid, and try again. |
| TPE1128 | Request | Failed to authen- ticate with the Authentication Policy Server |
UI | We are experiencing a technical issue [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE1129 | Request | Failed to authorize with the Authentication Policy Server |
A2A | We were unable to authenticate your credentials. Please review the information about digital certifcates included in Section 5 of thePublication 5258, AIR Submission Composition and Reference Guide, ensure that the credentials are valid, and try again. |
| TPE1129 | Request | Failed to authorize with the Authentication Policy Server |
UI | We are experiencing a technical issue [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 41
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1130 | Request | Request contains Invalid Test File Code value |
A2A | Our system has detected an error with the Test File Code. Please check the message and try again. Please note that the Test File Code value of 'T' is used for AATS transmissions and the Test File Code value of 'P' is used for transmissions intended for IRS compliance processing. |
| TPE1130 | Request | Request contains Invalid Test File Code value |
UI | [TPE1130] Our system has detected an error with the Test File Code of your Manifest fle. Please check the fle and try again. Please note that the Test File Code value of 'T' is used for AATS transmissions and the Test File Code value of 'P' is used for transmissions intended for IRS compliance processing. |
| TPE1131 | Request | Request message UTID is either missing or invalid |
A2A | Our system has detected an error with the Unique Transmission ID. Please review the UTID format outlined in Section 5 ofPublication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1131 | Request | Request message UTID is either missing or invalid |
UI | [TPE1131] Our system has detected an error with the Unique Transmission ID of your Manifest fle. Please review the UTID format outlined in Section 3 of the Publication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Manifest fle, and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 42
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1132 | Request | Failed due to checksum validation error |
A2A | “ChecksumAugmentationNum” value in your transmission against the calculated value of the form data fle attachment. Please reviewPublication 5258, AIR Submission Composition and Reference Guide, Section 3.4.3, Computing Checksum, correct the checksum value, and retransmit. |
| TPE1132 | Request | Failed due to checksum validation error |
UI | [TPE1132] Our system detected an error while validating the “ChecksumAugmentationNum” value in your manifest fle against the calculated value of the form data fle. Please reviewPublication 5258, AIR Submission Composition and Reference Guide, Section 3.4.3, Computing Checksum. Correct the checksum value and retransmit. |
| TPE1133 | Request | Unable to extract UserId from Manifest |
A2A | Our system has detected an error with the UserId feld of the ACASecurityHeader. Please verify that your A2A Client Application System ID (ASID) is included in the UserId feld. For more information, please review the UserId guidelines outlined in section 5 ofPublication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1133 | Request | Unable to extract UserId from Manifest |
UI | *Error not applicable to ISS-UI |
| TPE1134 | Request | Unauthorized request |
A2A | *Error not applicable to A2A |
| TPE1134 | Request | Unauthorized request |
UI | 403 Static Error Page |
| TPE1135 | Request | Unauthorized request |
A2A | *Error not applicable to A2A |
| TPE1135 | Request | Unauthorized request |
UI | [TPE1135] Our system has detected an issue with your request. Please return to the homepage and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 43
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1136 | Request | Unauthorized request |
A2A | *Error not applicable to A2A |
| TPE1136 | Request | Unauthorized request |
UI | [TPE1136] Our system has detected an issue with your request. Please return to the homepage and try again. |
| TPE1137 | Request | Unauthorized request |
A2A | *Error not applicable to A2A |
| TPE1137 | Request | Unauthorized request |
UI | [TPE1137] Our system has detected an issue with your request. Please return to the homepage and try again. |
| TPE1138 | Request | Unauthorized request |
A2A | *Error not applicable to A2A |
| TPE1138 | Request | Unauthorized request |
UI | [TPE1138] Our system has detected an issue with your request. Please return to the homepage and try again. |
| TPE1139 | Request | Unable to process provided certifcate |
A2A | Our system has detected an issue with the transmission's certifcate. Please check the request and try again. |
| TPE1139 | Request | Unable to process provided certifcate |
UI | *Error not applicable to ISS-UI |
| TPE1141 | Request | Invalid request | A2A | *Error not applicable to A2A |
| TPE1141 | Request | Invalid request | UI | [TPE1141] Our system has detected an issue with your request. Please return to the homepage and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 44
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1201 | Request | Attachment is malformed |
A2A | The attachment was not formatted properly and/ Please review the XML standards outlined in Section 3 ofPublication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1201 | Request | Attachment is malformed |
UI | [TPE1201] Our system has detected a potential threat in the Form fle, and it cannot be transmitted. This may be due to malformed XML. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Form fle, and try again. |
| TPE1203 | Request | Potential Code Injection in Attachment |
A2A | Our system has detected a potential threat in the request message attachment. Please review the XML standards outlined in Section 3 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1203 | Request | Potential Code Injection in Attachment |
UI | [TPE1203] Our system has detected a potential threat in the Form fle and it cannot be transmitted. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Form fle, and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 45
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1204 | Request | Potential SQL Injection in Attachment |
A2A | Our system has detected a potential threat in the request message attachment. Please review the XML standards outlined in Section 3 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1204 | Request | Potential SQL Injection in Attachment |
UI | [TPE1204] Our system has detected a potential threat in the Form fle and it cannot be transmitted. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Form fle and try again. |
| TPE1205 | Request | Potential Document Structure Threat in Attachment |
A2A | Our system has detected a potential threat in the request message attachment. Please review the XML standards outlined in Section 3 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE1205 | Request | Potential Document Structure Threat in Attachment |
UI | [TPE1205] Our system has detected a potential threat in the Form fle and it cannot be transmitted. Please review the XML standards outlined in Section 3 of thePublication 5258, AIR Submission Composition and Reference Guide, correct any issues on the Form fle, and try again. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 46
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE1206 | Request | Extra attachment(s) | A2A | The request message contains more than one attachment. Please review the transmission instructions outlined in Section 5 ofPublication 5258, AIR Submission Composition and Reference Guide, and resubmit with only one attachment. |
| TPE1206 | Request | Extra attachment(s) | UI | *Error not applicable to ISS-UI |
| TPE1207 | Request | Missing attachment(s) |
A2A | The request message is missing an attachment. Please review the transmission instructions outlined in Section 5 ofPublication 5258, AIR Submission Composition and Reference Guide, add an attachment to the request, and resubmit. |
| TPE1207 | Request | Missing attachment(s) |
UI | We are experiencing a technical issue [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE1208 | Request | UTF-8 BOM encoding in the Form fle and cannot be interpreted |
UI and A2A |
Our system has detected UTF-8 BOM encoding in the Form fle and cannot be interpreted. Please review the XML standards outlined in Section 10 of Publication 5258, AIR Submission Composition and Reference Guide, correct any issues, and try again. |
| TPE2001 | Response | Consumer is unreachable |
A2A | Unable to deliver response message to transmitter. |
| TPE2001 | Response | Consumer is unreachable |
UI | TPE2001 is deprecated in the A2A service policy. Can be triggered via ISS UI, but under extremely rare circumstances. Could possibly remove this entry from the table entirely as transmitters are extremely unlikely to ever see this code. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 47
Transmitting Information Returns
| Fault Code | Service Leg | Reason | Channel | ISS Fault Message |
|---|---|---|---|---|
| TPE2111 | Response | Unable to parse Receipt ID from Receipt message using XPath |
A2A | Parse Receipt ID from Response message using XPath. |
| TPE2111 | Response | Unable to parse Receipt ID from Receipt message using XPath |
UI | We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE2112 | Response | Unable to parse timestamp from Receipt message using XPath |
A2A | Parse Timestamp from Response Message using XPath. |
| TPE2112 | Response | Unable to parse timestamp from Receipt message using XPath |
UI | We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE2113 | Response | Unable to parse UTID from Receipt message using XPath |
A2A | Parse UTID from Response Message using XPath. |
| TPE2113 | Response | Unable to parse UTID from Receipt message using XPath |
UI | We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE2114 | Response | Unable to parse Error Code from Receipt message using XPath |
A2A | Parse Error Code from Response Message using XPath. |
| TPE2114 | Response | Unable to parse Error Code from Receipt message using XPath |
UI | We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
| TPE2115 | Response | Unable to parse Error Message from Receipt message using XPath |
A2A | Parse Error Message from Response Message using XPath. |
| TPE2115 | Response | Unable to parse Error Message from Receipt message using XPath |
UI | We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience. |
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 48
Fault Code
Transmitting Information Returns
Service
Reason Channel ISS Fault Message Leg
We are experiencing a technical issue. Please try your request again later. We apologize for the inconvenience.
We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience.
We are experiencing a technical issue. Please try your request again later. We apologize for the inconvenience.
We are experiencing a technical issue with the receipt [Error Code 6064]. Please try your request again later. We apologize for the inconvenience.
A2A
UI
A2A
UI
TPE2201 Response
TPE2202 Response
There is an excess number of attachments in the response
The attachment in the response exceeded maximum size limit
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 49
Transmitting Information Returns
4.4.1 | Threat Mitigation through ISS-UI:
If an error has occurred upon upload of the Manifest and Form Data File, the user will be returned to the upload page with an error marked in red. Examples of the upload page and upload error page are shown below in Figures 4-13.
Figure 4-11: Example of UI Upload Page
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 50
Transmitting Information Returns
If an error has occurred upon submission status requests, the Transmission Status Details page will display an error table depicting the error codes and corresponding error details. An example of the transmission status page is shown below in Figure 4-12.
Figure 4-12: UI Check Transmission Status Page Showing the Search Error
4.4.2 | Threat Mitigation through ISS-A2A
ISS-A2A will perform threat mitigation and initial validation on authorized connections. ISS-A2A will return a fault if a transmission contains a threat, if a transmission fails initial validation, or if a connection with the endpoint cannot be established and reject the transmission.
Faults differ from errors – a fault is an issue during transmission, whereas an error is the result of business rules processing failure. The Fault Generation process is common to each of ISS-A2A process flows. Fault messages generated to ISS-A2A are always routed to the transmitter via a SOAP message.
Guide for Electronically Filing ACA Information Returns for Software Developers and Transmitters 51
Section¶
Get a plain-English answer with a citation back to this text.
Ask AI about this code