<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Semantic Ontologies and Financial Reporting: An Application of the FIBO</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Oliver BROWNE</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Nenad KRDZAVAC</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Philip O'REILLY</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mark HUTCHINSON</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Accounting, Finance and Information Systems, University College Cork</institution>
          ,
          <country country="IE">Ireland</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper illustrates the application of a developed global fund reporting ontology (GFRO) for efficient financial reporting. The GFRO extends Financial Industry Business Ontology (FIBO). Existing reporting financial information systems lack the ability to integrate data from heterogenic sources and provide unified and consistent financial reports that will comply with regulations. This study reveals that by integrating the power of XSLT and Semantic Web technologies, operationalised through the development of a scalable working prototype, allows financial services industry experts to build more flexible and consistent reports. Our research shows that the consistency of financial reports can be dramatically improved by using an appropriate inference engine.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>Ontologies</kwd>
        <kwd>FIBO</kwd>
        <kwd>financial reporting</kwd>
        <kwd>information systems</kwd>
        <kwd>reasoning</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Introduction
Data required for reporting to regulatory bodies is open to interpretation, from teams of
legal experts to data analysts and senior management, interpretation of legal documents
can leave experts arguing ad infinitum about minor nuances of language and
terminology. These challenges have spurred the need for the development of a
standardised language across financial instruments and institutions, a terms sets such that
there is little room for interpretation and the regulator receives transparent and
comparable data from all institutions for aggregation, and to be able to prove that the
report is consistent with regulations which are constantly changing and developing [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>Towards addressing this shortcoming, we have developed GFRO and implemented
a framework that uses GFRO to provide consistent and unified financial reporting across
heterogenic data from different sources. Our research aims to advance research on
ontologies by illustrating their application for improved reporting capabilities over a
broad subset of financial instruments; specifically, bonds and equities, and to perform
reasoning over source data to infer new observations.</p>
      <p>
        Bonds are a debt investment instrument in which an investor loans money to an
entity, the entity borrows the money for a fixed period of time and repays moneys to the
investor as incremental interest payments with a bullet payment of the principle at a set
date. Many variations of bonds coupon and principle payments also exist. Equities are a
piece of ownership and generally control of an entity, generally referred to as shares or
stocks.
1. Main Ontology-based Features of the Framework for Financial Reporting
The most important task in adapting the FIBO [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] standard to serve as a core in financial
reporting, is to bridge the gap between domain specific databases and FIBO ontologies.
Table 1 contains a list of extensions that were made to FIBO in this research study to
support GFRO.
      </p>
      <p>We generate three types of rdf graphs. The first one covers point in time
representations of the financial instruments i.e. month end data. The second
transformation covers transactional data of financial instruments i.e. buying and selling
of positions. The last one covers accrued interest to certain financial instruments such as
bonds.</p>
      <p>
        The second component of the implementation establishes communication between
the end user and the triple store. It uses parametrized SPARQL queries to deliver data
needed to generate financial reports, or conversely, return exceptions in case of
inconsistencies. On top of this, is the GUI layer, which implements a graphical user
interface that allows subject matter experts to create custom intelligent reports over
financial data including regulatory reports, automatically populating regulatory reporting
templates. The end user can produce reports across many funds or fund types over
features of that fund. We use the JavaFX [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] library to generate different type of charts.
      </p>
      <p>Figure 2 illustrates a UML class diagram of the implementation of all layers. The
central class is GenerateReport. Method getTransformation runs the XSLT
transformation of financial data stored in a folder and generates appropriate RDF file,
and exports that file into the triple store, also loading GFRO into the triple store. The
system runs SPARQL queries necessary for reporting of financial instruments. Some of
these queries are parametrized, and some of them are not. For example, parametrized
queries for bond reporting are reusable for any type of bond. All queries are stored in one
folder.</p>
      <p>
        When an end user submits a request for generating a report, then method
runQueries() in Query class runs all queries over Stardog [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] triple store, and generates
results that are stored in the output folder as a csv file as well as remembered results as
properties in bean classes such as FinancialInstrumentBean class. The Query class
allows a user to query more than one graph in the triple store. Methods in
GenerateReport class such as getPieChart() uses csv files and methods in bean classes to
generate and visualize report to end user.
2. POC Output: Illustrative Example
      </p>
      <p>Clockwise from bottom left; we represent the equity holdings of the fund, by
country, and next by sectoral allocation of the equities as pie charts. The bar charts are
used to represent currency allocation of the equities within the fund and the physical cash
holding of the fund. Data in the tables’ represent overall summary data. The
representation of the data is standard in its presentation; however, the method of retrieval
and querying is unique in its flexibility.</p>
      <p>
        Databases find it difficult to query from a data end point and must be queried more
generally and data collated and validated [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], this approach allows us to be flexible over
querying by using shared characteristic over reasoning, removing the need for collation
of spreadsheets and manual processes.
3. Conclusions and Future Work
The paper demonstrates a framework for consistent financial reporting that complies
with regulations by adapting and extending FIBO to meet the requirements of the data.
This a flexible approach to extending current reporting over legacy database systems
rather than design new databases.
      </p>
      <p>Although we tested the process described in the paper over a large amount of
complex and varied data representative of fund level data, a limitation of our research is
that we did not test beyond the scope of bonds and equities. The next stage of our research
is to explore the utility of our framework in a bid data setting.</p>
      <p>
        This application of regulatory and risk reporting over a complex set of data and the
ability to automatically verify results over reasoning should allow further research into
the benefits of ontologies. The adoption of a shared ontology could potentially
dramatically reduce the timeframe for transaction processing. The financial ontology
standards (FIBO) are at early stages of development, these standards are conceptually
strong but lack the testing to allow for robust implementation. All findings were reported
to the EDM Council and Object Management Group to help to improve the FIBO
standard wherever possible [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
4. Acknowledgements
The proof of concept outlined in this paper was funded by the State Street Corporation.
In particular we would like to attribute the ongoing success and funding of this project
to David Saul, Dáire Lawlor, Daragh McGetrick
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Bennett</surname>
          </string-name>
          ,
          <article-title>The financial industry business ontology: Best practice for big data</article-title>
          ,
          <source>J. Bank. Regul</source>
          .
          <volume>14</volume>
          (
          <year>2013</year>
          )
          <fpage>255</fpage>
          -
          <lpage>268</lpage>
          . doi:
          <volume>10</volume>
          .1057/jbr.
          <year>2013</year>
          .
          <volume>13</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Java</surname>
            <given-names>FX</given-names>
          </string-name>
          , http://docs.oracle.com/javase/8/javase-clienttechnologies.htm, Accessed on September,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Stardog</surname>
          </string-name>
          ,
          <year>2017</year>
          , http://stardog.com/ Accessed on September,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>G.W.</given-names>
            <surname>Dickson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.L.</given-names>
            <surname>Leitheser</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.C.</given-names>
            <surname>Wetherbe</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Nechis</surname>
          </string-name>
          ,
          <article-title>Key Information Systems Issues for the 1980's, MIS Q</article-title>
          .
          <volume>8</volume>
          (
          <year>1984</year>
          )
          <fpage>135</fpage>
          -
          <lpage>159</lpage>
          . https://doi.org/10.2307/248662
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>[5] FIBO, https://www.edmcouncil.org/financialbusiness</mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>