{"id":7162,"date":"2025-08-28T22:36:25","date_gmt":"2025-08-29T03:36:25","guid":{"rendered":"https:\/\/librarytestdev.wpenginepowered.com\/?post_type=doc&p=7162"},"modified":"2025-08-28T22:36:25","modified_gmt":"2025-08-29T03:36:25","slug":"fix-recovery-reconciliation","status":"publish","type":"doc","link":"https:\/\/library-staging.tradingtechnologies.com\/tt-fix\/tt-fix-recovery\/fix-recovery-methods\/fix-recovery-reconciliation\/","title":{"rendered":"FIX Recovery – Reconciliation"},"content":{"rendered":"\n

Reconciliation Using Custom Tag 18002 (Optional)<\/h2>\n\n

If you need to reconcile missed messages, you can include CustomTag (18002=Y) on your Recovery Request\n (U2)<\/a> or Logon (A)<\/a> message. In doing so, FIX will search all messages from\n the beginning of the session (last session reset\n time) up to the most recent message and will send only those messages not previously sent. <\/p>\n\n

Note<\/span> If you include CustomTag (18002=Y) on your Recovery Request (35=2) or\n Logon (35=A) message, you should not<\/b> include the StartDate (916) and EndDate (917) tags. If CustomTag (18002=Y)\n is\n sent in addition to the 916 and 917 tags, you will receive a rejection message and no recovered messages will be sent.\n<\/p>\n\n

Example: Reconciliation Using CustomTag (18002)<\/h3>\n\n

An example of a FIX Recovery Request (35=U2) message sent to request recovery with reconciliation is shown below.<\/p>\n\n\n Recovery Request (35=U2) Message for Reconciliation<\/b>\n\n

8=FIX.4.2|9=62|35=U2<\/b>|49=XYZABC|56=TT_DC|34=6|52=20240216-02:52:52|18002=Y<\/b>|10=059|<\/p>\n\n\n

Example: FIX Reconciliation with CustomTag (18002), StartDate (916) and EndDate\n (917) Rejected\n<\/h3>\n\n

In the following example, a Recovery Request (35=U2) including CustomTag (18002), StartDate (916) and EndDate (917) is sent and a\n Business Message Reject (35=j) is sent in response.<\/p>\n\n

    \n
  1. FIX client sends Recovery Request (35=U2) message<\/b><\/li>\n\n

    \n 8=FIX.4.2|9=103|35=U2|49=XYZABC|56=TT|34=16|52=20240313-20:26:18|916=20240213-13:57:06|917=20240213-19:57:07|18002=Y<\/b>|10=208|\n <\/p>\n\n

  2. FIX client receives Business Message Reject (35=j) message<\/b><\/li>\n\n

    8=FIX.4.2|9=00180|35=j|49=TT|56=jeromedc|34=16|52=20240313-20:26:18.502|45=16|372=U2|380=0|\n 58=Provide either\n StartDate(916) and EndDate(917) or CustomMode(18002) in OutOfBandRecoveryRequest message\n <\/b>|10=020|<\/p>\n\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    Reconciliation Using Custom Tag 18002 (Optional)<\/h2>\n

    If you need to reconcile missed messages, you can include CustomTag (18002=Y) on your Recovery Request
    \n (U2)<\/a> or     Logon (A)<\/a> message. In doing so, FIX will search all messages from
    \n the beginning of the session (last session reset
    \n time) up to the most recent message and will send only those messages not previously sent. <\/p>\n

    Note<\/span> If you include CustomTag (18002=Y) on your Recovery Request (35=2) or
    \n Logon (35=A) message, you should not<\/b> include the StartDate (916) and EndDate (917) tags. If CustomTag (18002=Y)
    \n is
    \n sent in addition to the 916 and 917 tags, you will receive a rejection message and no recovered messages will be sent.\n<\/p>\n

    Example: Reconciliation Using CustomTag (18002)<\/h3>\n

    An example of a FIX Recovery Request (35=U2) message sent to request recovery with reconciliation is shown below.<\/p>\n

    Recovery Request (35=U2) Message for Reconciliation<\/b><\/p>\n

    8=FIX.4.2|9=62|35=U2<\/b>|49=XYZABC|56=TT_DC|34=6|52=20240216-02:52:52|18002=Y<\/b>|10=059|<\/p>\n

    Example: FIX Reconciliation with CustomTag (18002), StartDate (916) and EndDate
    \n (917) Rejected
    \n<\/h3>\n

    In the following example, a Recovery Request (35=U2) including CustomTag (18002), StartDate (916) and EndDate (917) is sent and a
    \n Business Message Reject (35=j) is sent in response.<\/p>\n

      \n
    1. FIX client sends Recovery Request (35=U2) message<\/b><\/li>\n

      \n 8=FIX.4.2|9=103|35=U2|49=XYZABC|56=TT|34=16|52=20240313-20:26:18|916=20240213-13:57:06|917=20240213-19:57:07|18002=Y<\/b>|10=208|\n <\/p>\n

    2. FIX client receives Business Message Reject (35=j) message<\/b><\/li>\n

      8=FIX.4.2|9=00180|35=j|49=TT|56=jeromedc|34=16|52=20240313-20:26:18.502|45=16|372=U2|380=0|
      \n 58=Provide either
      \n StartDate(916) and EndDate(917) or CustomMode(18002) in OutOfBandRecoveryRequest message
      \n <\/b>|10=020|<\/p>\n<\/ol>\n","protected":false},"author":2,"template":"","meta":{"_acf_changed":false,"footnotes":""},"docs-category":[1671],"class_list":["post-7162","doc","type-doc","status-publish","hentry","docs-category-fix-recovery-methods"],"acf":[],"_links":{"self":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7162","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc"}],"about":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/types\/doc"}],"author":[{"embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/users\/2"}],"version-history":[{"count":0,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/doc\/7162\/revisions"}],"wp:attachment":[{"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/media?parent=7162"}],"wp:term":[{"taxonomy":"docs-category","embeddable":true,"href":"https:\/\/library-staging.tradingtechnologies.com\/ja\/wp-json\/wp\/v2\/docs-category?post=7162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}