0

I am working on ACA forms submission project and util today everything has been in the mode "business as usual", but today everything has changed.

I've started to get following error back from IRS status service on all my submissions:

<ns3:FormBCTransmitterSubmissionDtl xmlns="urn:us:gov:treasury:irs:ext:aca:air:ty16" xmlns:ns2="urn:us:gov:treasury:irs:common" xmlns:ns3="urn:us:gov:treasury:irs:msg:form1094-1095BCtransmittermessage">
    <ACATransmitterSubmissionDetail>
        <TransmitterErrorDetailGrp>
            <ns2:ErrorMessageDetail>
                <ns2:ErrorMessageCd>MANIFEST-025</ns2:ErrorMessageCd>
                <ns2:ErrorMessageTxt>Manifest 'ChecksumAugmentationNum' must match the IRS-calculated 'ChecksumAugmentationNum' value of the transmission</ns2:ErrorMessageTxt>
            </ns2:ErrorMessageDetail>
        </TransmitterErrorDetailGrp>
    </ACATransmitterSubmissionDetail>
</ns3:FormBCTransmitterSubmissionDtl>

Which is kinda odd, because I was able to submit successfully many times before. And I did not change check sum calculating algorithm in any way. Did anyone stumble upon such issue? Had IRS changed the way they calculate data file check sum?

fatherOfWine
  • 1,191
  • 16
  • 39
  • I haven't seen anything regarding the IRS changing the way they were calculating the data file `checksum`. Their documentation in section 3.4.3 of Publication 5258, appears to be the same as it was last year. – Russ Dec 29 '16 at 23:04
  • @Russ It was working fine until today. Have you tried submit any test cases today? – fatherOfWine Dec 29 '16 at 23:35
  • I have not attempted to submit yet. I believe AATS just came up today, it could be something not-quite-right with that. – Russ Dec 30 '16 at 00:30
  • @Russ If you would be able to submit, please, let me know about results. It would be beneficial to know if it's only us or more widespread phenomenon. – fatherOfWine Dec 30 '16 at 15:02
  • I will keep you posted – Russ Dec 30 '16 at 16:12

1 Answers1

2

I had the same issue. In my situation the issue was due to the case value of the checksum. Example 214527e7bfa3c7924b871679c82e1600 vs. 214527E7BFA3C7924B871679C82E1600. Lower case was accepted. I have read articles stating that checksum values are not case sensitive so this was surprising to me.

**Update - Received this from the IRS this morning.

MANIFEST-025 is setting in error. A fix for this error will be installed during the January 8, 2017, maintenance window. Please resubmit your Transmissions on January 9, 2017.

Please let us know if you are able to successfully file on January 9, 2017.

Robert Eugene Jackson Jackson
  • 36
  • 2