ACA XML Production file Rejected - Duplicate

Our production file has been rejected with the following errors:

AIRMF3006: Rejected transmission - Duplicate UUID

AIRMG3014: Rejected transmission - File is a duplicate

I have read other posts about how the Transmission ID needs to be unique which should be fine in our file because it is the only BN299 run as Final Update only 1 time. Our Benefits Analyst uploaded it once. I confirmed she used the Production URL and had called to move our status from Test to Production. I also confirmed the ID is different than the ID in our test file. Trying to go through any possibility of why this would have occurred. Has anyone else experienced this? Debating on whether to have our Benefits Analyst call the IRS or running the BN299 to create a new file/ID.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

ccburt - Last week, I submitted a set of two files (file and manifest) in production. Early this morning, I checked the status of the transmission and I had exactly the same message you got for my first file. Immediately, I call IRS and they told me that I had submitted the exactly same file twice with couple of minutes of difference. For sure, I didn't submitted it twice. I asked for the other missing Receipt ID and the agent gave it to me. I searched the status of that transmission (receipt id) and it was Accepted. That's why the other file that was sent by the system (I assumed) went into duplicate error. So, I think their transmission system is submitting the file twice, even you submitted only once. I'm so glad that you brought it up, because this is confirming my fear.

unknown

Thank you Luis Acevedo - That is exactly what happened to us as well! After being on hold almost 2 hours were found out we had files were submitted 2 minutes apart. They told us the Receipt ID # of the "first" file and that was Accepted with Errors so now onto working through that.

rod-roller

We are having the same issue. I had a file that I submitted the first time and it said it was a duplicate. I will have to call the IRS to see if they have the file as accepted.

com_2010feb_proactive.pdf

unknown

Has anyone had this error been able to determine the duplicate receipt id of the first file WITHOUT the IRS telling them what it was?

I have 3 files with this error, which I am certain are the result of a session timeout during the submission process. However, as everyone is aware, now I am unable to get through to the IRS phone number.

Any ideas would be greatly appreciated. Thanks.

unknown

I don't think there is a way to obtain it without calling...unless you feel like guessing the number by starting at the number you obtained and working backwards. Ours was a diff of 25, but that was on Monday and I imagine the site is getting hit a lot more today.

unknown

Thanks MaryBeth.

That's what I was afraid of. The difference on one was 650 +/-.

So, if the AIRMF3006 was only one of the errors with a particular file, and the other error was AIRMF3002 (the one with the attachment byte size number issue)...Since in order to correct the byte size issue, I need to create a new file anyway, does the duplicate file error even matter? (My thought is, proceed with addressing the byte size issue, generate the new file and submit it as a replacement file to the original...but, my fear is the true original is the one submitted prior to receiving the AIRMF3006 error on.)

rod-roller

We have sent replacement files that have been accepted. You need to run the BN299 again, change the transaction code to "R", insert the OriginalReceiptId and if you did any changes check the number of bytes of the detail file. If it is different you need to correct the manifest and then run a check sum utility and change the check sum at the bottom of the manifest.

We have not gotten all our entities back yet - some were accepted and some were rejected for various reasons.

unknown

Thanks lcardaccio. The problem is that we do not know the original receipt id, only the rejected receipt id. Since the page timed out when we were submitting our files, the receipt id we have is the one that was rejected as a duplicate.

By the way, I assume there are freeware check sum programs, but does anyone recommend one product over any of the others? Thanks.

deanna-plant

We too are in the same boat. Timed out so we don't have the original receipt id. Tried getting through to IRS and was on hold for 6 1/2 hours before we got disconnected.

juergen-erbe

I've been using the portable version of Checksum Control, not via recommendation but due to it being on hand when I started the project. Its fairly straightforward to use and the source code is published on Github in case it's ever necessary to audit it.

rod-roller

I was on the phone with the IRS from 7:30 this morning and they picked up at 9:20. If you are receiving a AIRMF3014 error that does not mean that you file was necessarily accepted with an earlier transmission. I have a file with that error only AIrmf3014 and the IRS said that the file was not accepted but had a check sum error.

unknown

We got this error and don't know how to resolve.

AIRMF3014 MANIFEST-019

Manifest 'ChecksumAugmentationNum' must not match a

'ChecksumAugmentationNum' of any AIR transmission from the same

'TCC' previously accepted.

We've not had one submission go through and be accepted so not sure how to resolve. Any others have same error?

unknown

From the ACA AIR workgroup meeting on June 14:

IRS Response #3: Transmissions for the same TCC with an identical Checksum Augmentation Number (which were Accepted, Accepted with Errors, or Rejected with an AIR error code) will be rejected as duplicates. Therefore, you must alter your submission. For example you could add a hyphen to the contact person suffix name or add a trailing space to an address field. The AIR Help Desk can look up your UTIDs and tell you which ones have a Receipt ID.

•Contact the ACA Information Return (AIR) Help Desk toll free at 1-866-937-4130. The AIR Help Desk hours of operation are 6:30 a.m. to 6:00 p.m., Monday through Friday, Central Time.

unknown

Got the AIRMF3014 error "Rejected transmission - File is a duplicate". I had sent once and it was rejected because of the byte error, so I reran BN299 and resent and am now getting this error. Help please! What am I missing now...

0712131256598360.doc

unknown

Where do you find the transaction code and the place for the OriginalReceiptId on BN299? I am unable to locate those areas.

unknown

refer to this KB article:

KB1836992 How do I submit an ACA Replacement XML File?

unknown

MaryBeth - this post was VERY helpful, thank you. On my small COBRA file, I was getting the AIRMF3014 - File is a duplicate error message. Initially, I thought it was the issue some others ran into, that their system was submitting it twice. But, when I called IRS to find the missing second receipt ID that was accepted, I learned that's not what happened in my case. In my case it really was a duplicate because when I reran my BN299 to generate a new unique ID# for a replacement file, it did not generate a new checksum augment number at the bottom of the manifest file. After speaking with IRS, he gave me 2 ideas to try - 1- rerun the BN299 again, if the checksum number was still the same, submit it as a O, not R. I reran the BN299, checksum number was the same, so I submitted as a O not a R, but still got the duplicate file error. 2 - if I could get the checksum number to change, then resubmit as R with the true original receipt ID it was replacing, not the duplicate file error receipt ID #'s. So then I was faced with how do I get the checksum number to change to try his second suggestion? And that's when I saw your post here. I decided to modify my contact information on the contact tab of the BN299 and rerun, rather than trying to manipulate the manifest xml file after the fact. So, I added a middle initial to our contact's name and changed his first name to his legal first name, changed the job, resubmitted the BN299 and bingo!! Got a new checksum number, corrected my byte size, changed my file type from O to R and inserted my original receipt ID# and my file finally got accepted without any errors! Thanks again!

Copyright © 2025 Infor. All rights reserved.