RFI Browser

Back  RFI # 261: 837 Duplicate Transaction Ack

Formal vs. Informal Help Informal Formal


Dennis Zanetti


we do not process 837 transactions sent by submitters when those transactions are duplicates of previously submitted transactions. is there a way within the standard to send a notice to the submitter that their transaction is not being processed because it is a duplicate?

Submitter Assigned Keywords

duplicate transaction acknowledgement


This issue is explicitly addressed in guide 004010X098A1 on pages B12 and B13. For a truely duplicate submission (a retransmission of an entire interchange) TA1 element 05 code 025 (Duplicate Interchange Control Number) identifies the duplication and allows for rejection of the entire duplicate interchange.

Identification of a duplicate group or transaction based upon control information is not supported. Identification of a duplicate submission on a claim by claim basis is reported in other ASC X12 transactions at a business unit level. Possible ASC X12 solutions are the 824 Application Acknowledgement or (specifically for an 837) a 277 Claim Status transaction used as a Claim Acknwledgement.
Submission 6/3/2005
Status Date 8/15/2005
Status F - Final
Primary References
Document 004010X098A1
Set IDn/a