ACA correction file Error TPE1106

We have been working on submitting a 2016 correction file (yes 2016!) and are receiving an error of:

"[TPE1106] The manifest file does not match our current schema. In particular, our system has detected a potential issue with the following element(s): p3:UniqueTransmissionID and p3:ACATransmitterManifestReqDtl..."

We validated the manifest xml schema and the error we get is:

ERROR: Element '{urn:us:gov:treasury:irs:common}ChecksumAugmentationNum': [facet 'pattern'] The value '98ea8a76efa7ee45bd853a928da41faa59bfb85a4fe9ed484608552e1798f08b' is not accepted by the pattern '[0-9A-Fa-f]{32}'.

ERROR: Element '{urn:us:gov:treasury:irs:common}ChecksumAugmentationNum': '98ea8a76efa7ee45bd853a928da41faa59bfb85a4fe9ed484608552e1798f08b' is not a valid value of the atomic type '{urn:us:gov:treasury:irs:common}MD5Type'.

Anyone have ideas on what I need to do to get this fixed? We have an open incident but aren't getting a response back on this latest error. We really want to get this submitted so we can focus solely on 2017 ACA. Thanks in advance!

Find more posts tagged with

Comments

Legacy Contributor

Your checksum string is 64 characters long, but "MD5Type" is supposed to be only 32 characters. The IRS changed from the MD5 method to the SHA-256 method which is 64 characters. I think that you're using the new version of the software which is using SHA-256, but the IRS seems to want MD5 for 2016 ACA. I'm not sure of that.

There's a KB 1958142 that explains how to manually calculate a checksum and insert it into your file.

Legacy Contributor

Thank you for the reply! I did a little digging based on your message and found we were validating our Manifest xml based on the 2016 schema but 2016 manifest files should be validated on the 2017 schema. Based on this the Checksum of 64 characters is correct. (The I.S. department is revalidating as I type this.) So now my only issue is the error message received from the IRS:

"[TPE1106] The manifest file does not match our current schema. In particular, our system has detected a potential issue with the following element(s): p3:UniqueTransmissionID and p3:ACATransmitterManifestReqDtl..."

Any ideas on how to fix this?

Legacy Contributor

We haven't transmitted a file in 2017; so, I don't know if the IRS made a change to their requirements. I've created test 2017 files and those two elements look the same in our 2016 and 2017 files, but, it's possible that Infor's software isn't creating the files correctly.

Legacy Contributor

Did a webex with Infor and they were stumped and said they say this issues in past years but not recent. We ended up going into the xml of just manifest file and changing the "TY16" on the header row to "TY17" and the IRS accepted it for processing!

Copyright © 2025 Infor. All rights reserved.