# fixing date for NDF's

**URL:** <https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526>\
**Category:** General Q&A\
**Tags:** imported, foreign-exchange, xid\_165598\
**Created:** [May 15, 2006, 8:22pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526 "2006-05-15T20:22:30Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![terrymurtaugh\_x](https://avatars.discourse-cdn.com/v4/letter/t/e47c2d/32.png) [@terrymurtaugh\_x](https://forum.fixtrading.org/u/terrymurtaugh_x)\
**Post date:** [May 15, 2006, 8:22pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/1 "2006-05-15T20:22:30Z")

</div>

Imported from previous forum

---

<div class="post-metadata">

**Author:** ![terrymurtaugh\_x](https://avatars.discourse-cdn.com/v4/letter/t/e47c2d/32.png) [@terrymurtaugh\_x](https://forum.fixtrading.org/u/terrymurtaugh_x)\
**Post date:** [May 15, 2006, 8:22pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/2 "2006-05-15T20:22:30Z")

</div>

Is there a suggested field to use to pass the fixing date on a New Order Single for an NDF? How about the market source for the fixing price?

---

<div class="post-metadata">

**Author:** ![fplpo\_x](https://avatars.discourse-cdn.com/v4/letter/f/7ab992/32.png) [@fplpo\_x](https://forum.fixtrading.org/u/fplpo_x)\
**Post date:** [May 16, 2006, 7:48am UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/3 "2006-05-16T07:48:03Z")

</div>

[original email was from Jay Hurley - [Jay.Hurley@morganstanley.com](mailto:Jay.Hurley@morganstanley.com) ]  
\> Is there a suggested field to use to pass the fixing date on a New Order

> Single for an NDF? How about the market source for the fixing price?

The analysis of NDFs including the recomendation of which field to use for fixing date or the definition of a new field is top of the agenda for phase II of the FX gap analysis. Please contact me if you need any more information.

---

<div class="post-metadata">

**Author:** ![zpasikowski](https://avatars.discourse-cdn.com/v4/letter/z/c77e96/32.png) [@zpasikowski](https://forum.fixtrading.org/u/zpasikowski)\
**Post date:** [January 7, 2019, 3:57pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/4 "2019-01-07T15:57:39Z")

</div>

This was now 12+ years ago, was this resolved? I don’t see any FixingDate or FixingTime in the latest FIX spec.

Thanks,  
Zak

---

<div class="post-metadata">

**Author:** ![deankauffman](https://avatars.discourse-cdn.com/v4/letter/d/a8b319/32.png) [@deankauffman](https://forum.fixtrading.org/u/deankauffman)\
**Post date:** [January 7, 2019, 4:29pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/5 "2019-01-07T16:29:12Z")

</div>

Zak,  
For FX messaging including NDF in FIX:

- MaturityDate(541) expresses the fixing date
- SettlDate(64) expresses the settlement date
- RateSource component reports the rate source
- Use PricingDateTime component instead of MaturityDate(541) if you must drill down to the fixing time and business centers  
Dean

---

<div class="post-metadata">

**Author:** ![zpasikowski](https://avatars.discourse-cdn.com/v4/letter/z/c77e96/32.png) [@zpasikowski](https://forum.fixtrading.org/u/zpasikowski)\
**Post date:** [January 7, 2019, 4:32pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/6 "2019-01-07T16:32:26Z")

</div>

Thanks for your quick reply Dean.

---

<div class="post-metadata">

**Author:** ![ltaikit](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.fixtrading.org/ltaikit/32/743_2.png) [@ltaikit](https://forum.fixtrading.org/u/ltaikit)\
**Post date:** [January 7, 2019, 5:28pm UTC](https://forum.fixtrading.org/t/fixing-date-for-ndfs/13526/7 "2019-01-07T17:28:20Z")

</div>

Use of MaturityTime(1079) is another way to specify fixing time in local time as it is a UTC offset field. The combination of MaturityDate + MaturityTime has been the recommendation as a simple approach for the NDF fixing requirement since FIX 5.0 (see FX section of Vol. 7 of the FIX 5.0 or FIX 5.0SP2 pdf specification on the FIX website). Use what is fit for use in your case. PriceDateTime is an embedded component that is jore rich, but if you don’t need that detail, MaturityDate + MaturityTime works just as well.
