Skip to content

Finance

  • Timestamps in trading and payment messages: FIX UTC timestamps at the precision their digits state, leap seconds included.

Trading and payment messages carry timestamps in their own formats, not the ISO date-time format. A FIX timestamp states its precision by how many fraction digits it has, and may name a leap second. This layer reads and writes those values as standard instants, keeping what the digits say. A SWIFT value date has a two-digit year, and SWIFT states its century by rule, so it needs no window from you.

  • A trade stamp loses its precision. parseFixUtcTimestamp reports the precision the digits state and keeps every digit sent, picoseconds included. See tool, guide, scenario.
  • A counterparty asks for a precision the clock does not match. formatFixUtcTimestamp writes the width asked for, cutting the fraction rather than rounding it, so a stamp never moves into the next second. See tool, guide, mistakes.
  • A leap second is rejected, or accepted on the wrong day. isValidFixUtcTimestamp accepts a second of sixty only for a leap second UTC really inserted. See tool, guide, scenario.
  • A two-digit value date lands in the wrong century. parseSwiftDate applies SWIFT’s own century rule, and refuses a year past the end of SWIFT’s range, as SWIFT does. See tool, guide, scenario.

Start with the guide: Finance: Message Timestamps.

format

parse

  • parseFixUtcTimestamp: Read a FIX UTCTimestamp as a UTC instant and the precision its digits state.
  • parseSwiftDate: Read the value date of a SWIFT MT message, YYMMDD, as an ISO 8601 date.

validate

  • isValidFixUtcTimestamp: Return true when value is a FIX UTCTimestamp that states a real UTC second.
  • isValidSwiftDate: Return true when value is a SWIFT MT value date, YYMMDD, that SWIFT accepts.
  • Finance: Message Timestamps: parseFixUtcTimestamp, formatFixUtcTimestamp and isValidFixUtcTimestamp read and write the FIX UTCTimestamp at the precision its digits state, with a second of sixty accepted only for a leap second UTC really inserted. parseSwiftDate, formatSwiftDate and isValidSwiftDate do the same for the SWIFT MT value date, using the century SWIFT states.
  • FIX Timestamp Reader: Paste a FIX UTCTimestamp. The tool reads it with parseFixUtcTimestamp and isValidFixUtcTimestamp: the instant, the precision its digit count states, whether a second 60 is an inserted leap second, and the picosecond digits apart from the instant. A second section writes one instant at all five precisions.
  • SWIFT Value Date Reader: Paste a SWIFT value date, YYMMDD. The tool reads it with parseSwiftDate and isValidSwiftDate, shows the century SWIFT gives the two-digit year and the T50 refusal, and writes an ISO date back with formatSwiftDate.
  • Finance: Common mistakes with FIX UTC timestamps, the precision their digits state, rounding when narrowing, the second of sixty, and SWIFT value dates and the century they state, in GMT’s Finance layer.
© 2026 NorthGuild · Licences

Code examples: MIT-0. Packages: MIT. Third-party data and components: their own licences, credited where they appear. Everything else: © 2026 NorthGuild, all rights reserved.