Finance Data Services Overview

Overview

Finance Data Service is a database that stores transaction and reference data uploaded into Fynapse.

In Fynapse you can enrich your transaction data with reference data, i.e. additional information which are later visible in the Journal.

The transaction and reference data uploaded into Fynapse are stored in an organized structure defined by the user.

For more details on how data structure is defined in Fynapse, refer to Data Structure.

How Is Reference Data Uploaded to Fynapse?

In order to upload reference data into Fynapse, you have to upload them in a CSV file:

• Via the File Ingestion screen
• Directly to the correct folder on the cloud storage
• Via the Uploads screen

For more details about uploading data via UI, refer to Data Input File Ingestion and Uploads Screen.

For more details about uploading data directly to cloud storage folders, refer to Data Ingestion Using Backend.

Once uploaded the data undergo validation against the defined data structure. After successful validation of the data structure.

During the enrichment process, the reference data are taken based on the references defined in the data structure. The data are again verified against any defined constraints. If all constraints are met and the data were successfully taken, they are then inserted into the relevant Entities.

Reference Data Versioning

There are two considerations in versioning of Reference Data:

• Primary Key
• Effective From date

Primary Key

Based on the Primary Key, Fynapse determines whether the data are new or a newer version of data already in the system.

If a newer version of the data already in the system is uploaded, a new version of the record will be created.

If the data are a new addition to an existing Entity, they are appended.

Effective From Date

The Effective From date is a technical field that is mapped do a dateField defined in a Reference Entity.

If you don’t define a dateField in your Reference Entity or the dateField attribute is left empty in your ingestion file, a default Effective From date will be assigned by the system. This means that the Primary Key will be the only identifier of reference data and the newest version of the data, as identified off of the Primary Key, will be used for enrichment.

If you decide to populate the dateField, then when there are multiple versions of reference data the data with Effective From date effective at the time of the Posting Date of an ingested transaction event will be used for enrichment for this transaction.

Based on the Primary Key, Fynapse determines whether the data are new or a newer version of data already in the system.

If a newer version of the data already in the system is uploaded, a new version of the record will be created.

If the data are a new addition to an existing Entity, they are appended.

The data are then stored in the system.

Finance Data Service Screen

For information how you can view the data you uploaded for Fynapse Finance Data Service, please refer to Finance Data Service Screen.

Uploads Screen

For information how you can view the data files you uploaded for a selected Entity and what you can do with them, please refer to Uploads Screen.

Process Flow Diagram

The diagram below illustrates the process flow for reference data:

Example - How Is an Entity Updated?

How Are Transaction Data Enriched in Fynapse?

Transaction data undergo the process of enrichment in two stages.

First, the incoming Business Event is enriched during processing in the Accounting Engine, as illustrated by the diagram below:

A Journal generated by the Accounting Engine undergoes the second stage of enrichment, as illustrated by the diagram below: