Common IRS ACA UI AIR Error Codes

Interfacing with the IRS is difficult, but it doesn’t have to be. You can file your ACA, 1099, and W-2 tax forms with BoomTax and we will handle the entire filing process from start to finish. Want to learn more?

TPE1001 / Error Code 6052

This error code is used to indicate an error on the IRS end of things. This is typically a transient error that will pop up from time to time. The best action to take here is to wait until off peak hours to attempt to re-transmit your information.

TPE1104 / Error Code 6064

This error code is used to indicate an error on the IRS end of things. This is typically a transient error that will pop up from time to time. The best action to take here is to wait until off peak hours to attempt to re-transmit your information.

TPE1105 – XML Is Not Well Formed

This error code is used to indicate an XML file that runs afoul of IRS rules. It’s typically best to check for illegal characters in your input that could cause a SQL injection attack like:

  • ‘–‘
  • ‘#’
  • ‘&’
  • ”’
  • ‘>’
  • ‘<‘

More information on this can be found in Section 3 of the Pub 5258, AIR Submission Composition and Reference Guide.

TPE1106 – SOAP Message Does Not Conform to WSDL

This error code is used to indicate that your XML file doesn’t follow the most up to date IRS schemas. You will want to make sure to write code against the most recent schemas for the tax year you are targetting.

TPE1107 – Message Exceeds Maximum Size Limit of 100 MB

This error code is pretty straightforward as it appears that you are sending more information than the IRS allows. In this case, we recommend breaking up your XML file into 100MB chunks then resubmitting.

TPE1108 – Potential Code Injection Threat

This error is specific to the submitted manifest.

See TPE1105.

TPE1109 – Potential Code Injection Threat

This error is specific to the submitted manifest.

See TPE1105.

TPE1110 – Potential Document Structure Threat

This error is specific to the submitted manifest. Similar to TPE1106, we recommend getting the latest IRS XSD specifications and building your solution against this.

TPE1118 – UTF-8 BOM Encoding in the Manifest File

This error is specific to the submitted manifest. The IRS requires that your submitted files do not contain what is called a byte order mark. This is a character that is typically saved with UTF-8 files to help readers understand how to interpret the encoding of the file. The IRS specifically does not allow this character to be present in your filing.

TPE1126 – Failed to Connect to Authentication Policy Server. Error Code 6064

Similar to TPE1104, this is a transient issue that should resolve itself over time.

TPE1127 – Missing Credentials in HTTP Request. Error Code 6064

Similar to TPE1104, this is a transient issue that should resolve itself over time.

TPE1128 – Failed to Authenticate with Authentication Policy Server. Error Code 6064

Similar to TPE1104, this is a transient issue that should resolve itself over time.

TPE1130 – Request Contains Invalid Test File Code Value

This error indicates that your manifest file incorrectly used a ‘T’ for the test file code on the production server or a “P” for the test file code on the AATS server. To correct, simply change the test file code to either T or P to match the environment you are filing on.

TPE1131 – Request Message UTID is Either Missing or Invalid

This error indicates that your UTID is not in the correct format or is not present. You’ll want to make sure this follows the convention:

UUID:ApplicationId:TCC::RequestType

TPE1132 – Failed Due To Checksum Validation Error

This error indicates that your checksum value is incorrect. You’ll want to make sure to use a SHA256 checksum and to use an established library to do this computation as homemade algorithms are difficult to correctly implement without running into issues.

TPE1134 – HTTP 403

This error is essentially a static HTTP 403 error page. Log out, clear your cookies, and log back in to resolve.

TPE1135 – Unauthorized Request

This error is transient error. We recommend restarting your IRS session (log out, clear cookies, log in) to correct.

TPE1136 – Unauthorized Request

This error is transient error. We recommend restarting your IRS session (log out, clear cookies, log in) to correct.

TPE1137 – Unauthorized Request

This error is transient error. We recommend restarting your IRS session (log out, clear cookies, log in) to correct.

TPE1138 – Unauthorized Request

This error is transient error. We recommend restarting your IRS session (log out, clear cookies, log in) to correct.

TPE1141 – Invalid Request

This error is transient error. We recommend restarting your IRS session (log out, clear cookies, log in) to correct.

TPE1201 – Attachment is Malformed

This is an error in the transmittal file and is caused by malformed XML. Verify you are on the latest IRS specifications and run your file through an XML validator to ensure that your file is well-formed.

TPE1203 – Potential Code Injection in Attachment

See TPE1105, but this is for the transmittal, not the manifest.

TPE1204 – Potential SQL Injection in Attachment

See TPE1105, but this is for the transmittal, not the manifest.

TPE1205 – Potential Document Structure Threat in Attachment

See TPE1110, but this is for the transmittal, not the manifest.

TPE1207 – Missing Attachments. Error Code 6064

This error code is used to indicate an error on the IRS end of things. This is typically a transient error that will pop up from time to time. The best action to take here is to wait until off peak hours to attempt to re-transmit your information.

TPE1208 – UTF-8 BOM Encoding in the Form File and Cannot be Interpreted

See TPE1118. This is specific to the transmittal file and not the manifest.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.