FIX Tag 371 – RefTagID
Reject Tag
RefTagID (Reference Tag ID) appears in Reject messages (35=3) to identify the specific tag that caused the rejection. When a message is rejected, RefTagID points to the problematic tag number.
Correct Usage
RefTagID is set by the broker/exchange in reject messages. It identifies which tag caused the rejection, allowing you to pinpoint the exact field that needs correction. Always check RefTagID when receiving rejects.
Common Issues
1) RefTagID=371 indicates ClOrdID (11) was missing, 2) RefTagID=54 indicates Side was missing, 3) RefTagID points to invalid tag value, 4) RefTagID helps diagnose reject root cause, 5) Missing RefTagID in reject makes debugging harder.
Example FIX Message
8=FIX.4.4|9=120|35=3|49=EXCHANGE|56=CLIENT|371=11|372=D|373=6|58=Required tag missing|10=123|
Related Tags
Analyze Your FIX Logs
Upload or paste your FIX logs to see how tag 371 is used and detect any issues.
Analyze FIX Logs