FinancialDates
RIXML 2.5 Element
Element providing temporal context for financial data, including the last reported period, year, and actual publication date of financial numbers. Uses ISO 8601 datetime standards with Zulu time requirements.
Usage
Used within Issuer or Security elements to provide date context for financial information. All attributes are optional but work together to establish financial reporting timeline. Can specify reporting periods (Q1, Q2, etc.) and actual publication dates.
Business Context
Essential for maintaining accuracy and relevance of financial analysis by establishing clear temporal context. Critical for comparing financial data across time periods and ensuring proper sequencing of financial updates.
Specification Guide
Overview
FinancialDates is a container element that captures temporal reference points for financial data associated with issuers and securities, including the last reported reporting period, the last reported year, and the actual publication date of the financial numbers. It exists to give consumers of RIXML research the temporal context needed to interpret the recency, relevance, and proper time-series alignment of financial metrics carried within IssuerFinancials and SecurityFinancials.
Usage
FinancialDates is an optional element used within Issuer and Security contexts (and, more broadly, the financial details structures such as IssuerDetailsType and SecurityDetailsType) to qualify the associated financial values. It has no child elements; all information is conveyed through three optional attributes:
- lastReportedPeriod — a PeriodEnum value identifying the reporting period (e.g. Q1, Q2, annual).
- lastReportedYear — an integer year corresponding to that period.
- reportingDate — an xs:dateTime (ISO 8601, Zulu time) indicating when the financial numbers were actually reported/published.
Because every attribute is optional, publishers may supply only the dimensions they have available. Typical use is to pair the element with the financial values it describes so that downstream systems can sequence updates, compare period-over-period figures, and confirm the currency of the data.
Rules
- MUSTDate/time values on reportingDate must use ISO 8601 format expressed in absolute Zulu (UTC) time.[RIXML Research Data Dictionary v2.4 p.54] [RIXML Research Data Dictionary v2.5.1 p.57] [RIXML User Guide v2.2 p.39] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.75]↗
- MAYAll attributes on FinancialDates (lastReportedPeriod, lastReportedYear, reportingDate) are optional, so the element may be populated with any subset of these dimensions.[RIXML Research Data Dictionary v2.4 p.54] [RIXML Research Data Dictionary v2.5.1 p.57] [RIXML User Guide v2.3.1 p.39] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.75]↗
- INFORMATIVEFinancialDates as a child of Issuer is not required by RIXML Level One; Level One implementations omit issuer-level financial dating metadata to focus on core issuer identification.[RIXML Level One Addendum v2.2 p.17] [RIXML Level One Addendum v2.3.1 p.12]
- INFORMATIVEFinancialDates as a child of Security is not required by RIXML Level One, alongside other complex elements such as SecurityType, SectorIndustry, and Weighting.[RIXML Level One Addendum v2.3.1 p.14] [RIXML Level One Addendum v2.5 p.14]
Relationships
- qualifiesIssuer — FinancialDates appears within Issuer (via IssuerDetailsType) to provide temporal context for issuer-level financial figures such as those in IssuerFinancials.
- qualifiesSecurity — FinancialDates appears within Security (via SecurityDetailsType) to provide temporal context for security-level financial figures such as those in SecurityFinancials.
- contextualisesIssuerFinancials — Indicates the reporting period, year, and publication date that apply to the financial values reported in IssuerFinancials.
- contextualisesSecurityFinancials — Indicates the reporting period, year, and publication date that apply to the financial values reported in SecurityFinancials.
- usesPeriodEnum — lastReportedPeriod draws its values from PeriodEnum (e.g. quarterly or annual period codes).
Where It Fits
Canonical Path
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
| Content Model | Text content (string) |
Attributes
lastReportedPeriodPeriodEnum |
Used together with lastReportedYear to indicate the period when the financials were last reported. For example, Q1 2000. optionalSince 2.1 |
lastReportedYearinteger |
Used together with lastReportedPeriod to indicate the period when the financials were last reported. For example, Q1 2000. optionalSince 2.1 |
reportingDatedateTime |
Represents the date the numbers were actually published. Expressed using ISO 8601 (as refined by the World Wide Web Consortium's note http://www.w3.org/TR/NOTE-datetime). In addition, RIXML requires the use of Zulu time or Z-time (GMT +/- n hours:minute:seconds). All times are absolute and easier to compute, rather than using a relative (i.e. 08:30 +5) time. optionalSince 2.1 |
Children
Contains text content (type: string)
This element's value is its text content. Attributes provide additional context.
Example
<FinancialDates>ABC-123</FinancialDates>Version History
Unchanged since introduction in RIXML 2.1
FinancialDates is documented consistently from RIXML 2.2 through 2.5.1 with the same three optional attributes (lastReportedPeriod, lastReportedYear, reportingDate) and the same ISO 8601 / Zulu-time requirement for the reporting date (sources: user-guide-2.2 p.39; user-guide-2.3.1 p.39; data-dictionary-2.4 p.54; data-dictionary-2.5.1 p.57). RIXML Level One profiles (2.2 through 2.5) treat the element as not required at either the Issuer or Security level, so Level One conformant documents typically omit it (sources: level-one-2.2 p.17; level-one-2.3.1 pp.12,14; level-one-2.5 p.14). The v3 draft retains the element and its attribute set unchanged, with lastReportedPeriod explicitly typed as rixmlenum:PeriodEnum and reportingDate as xs:dateTime [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.75]↗.
Business Rules
The lastReportedPeriod and lastReportedYear attributes must be used together to indicate the period when the financials were last reported
Design Decisions
Level One excludes FinancialDates, SecurityType, SectorIndustry, and Weighting elements as children of Security
To simplify Level One implementations by removing complex financial and analytical data from security descriptions
RIXML Level One Addendum v2.5, p.14
Semantic Relationships
Qualifies1 relationship
Last reported period works together with last reported year to indicate when financials were last reported
RIXML Research Data Dictionary v2.5.1, p.57— lastReportedPeriod (Optional, PeriodEnum)