2026.2.2

Adjustment Portal - Document Upload

We enhanced the Adjustment Portal functionality with the ability to attach files and URLs to submission requests and approvals. Now, you will be able to attach up to 4 files and unlimited URL links:

• when you don’t have an active approval workflow setup for the Adjustment Portal:
  • when you upload new Journals and submit them for auto-approval
• when you have an active approval workflow setup for the Adjustment Portal:
  • as a requestor to your submit for approval request when you upload new Journals
  • as an approver to your decision approving or rejecting a submitted request

This enhancement was introduced to align the Adjustment Portal with compliance requirements, as uploading adjustments frequently requires evidence, such as files or links, to provide clear justification for submitting the adjustment and a clear reasoning why the adjustment was approved or rejected.

Additionally, an Activity Timeline was added to the details screen of an adjustment, which you can view when you select View adjustment in the Actions column. The Activity Timeline shows all the details of the adjustment’s history, including initial upload, submission/approval requests and decisions, and all attached files and URLs.

For more details, refer to Adjustment Portal.

Video preview:

Data Structure Definition

We enhanced the Data Structure Definition screen to include more detailed information about the Entities in the grid and added an Entity Details screen for each Entity.

For a detailed description of the updated screen, refer to Data Structure Definition.

Video preview:

Finance Data Service

We enhanced the Finance Data Service screen. Previously, you were only able to view a list of all Defined Reference Entities. Now, you can view all Defined Reference and Transactional Entities, and additionally Protected Entity FX Rates and browse data uploaded to those Entities.

Data Retention Policy

We introduced a new parameter in the Configuration Data JSON file:

"retentionDays": <integer>, for Entities with "temporalityType": "Reference".

This parameter can be set for Reference Entities populated by the extraction process and used as lookups during Flow processing.

Since such data may be regenerated each time the process runs, periodically purging outdated records is recommended to prevent excessive storage consumption. When a retention policy is defined, records will be automatically deleted after the specified number of days from their creation date.

1
{
2
        "namespace": "fynapse",
3
        "name": "ReferenceEntity",
4
        "temporalityType": "Reference",
5
        "description": "Reference Entity",
6
        "type": "DefinedEntity",
7
        "retentionDays": 7,
8
        "primaryKeyAttributeNames": [
9
          "id"
10
        ],
11
        "attributes": [
12
          {
13
            "type": {
14
              "typeName": "PrimitiveType",
15
              "primitive": "TEXT"
16
            },
17
            "name": "id",
18
            "label": "ID",
19
            "mandatory": true,
20
            "source": "input"
21
          },
22
          {
23
            "type": {
24
              "typeName": "PrimitiveType",
25
              "primitive": "TEXT"
26
            },
27
            "name": "name",
28
            "label": "Name",
29
            "mandatory": true,
30
            "source": "input"
31
          }
32
        ]
33
      }

Extracts - Changes in Split per Posting Date

We changed the Split per Posting date functionality, which is available for extracts with Journals and Unposted Journals as data source.

Previously, when Split per Posting Date checkbox was selected, then extracted data was split into separate files according to the Posting Date attribute. One extract file contained data from one Posting Date unless there were some records that were not included in the extraction process for their Posting Date. In such a situation, the extract file contained data from more than one Posting Date. This approach was recommended when an extract configuration was defined for incremental data to avoid extracting and splitting all data available in Fynapse from the beginning up to the defined date and time.

Now, we implemented an additional checkbox, Hold late data for next Posting Date, which becomes available when Only extract incremental data and Split per Posting Date checkboxes are checked.

If you only check the Only extract incremental data and Split per Posting Date checkboxes, a new extract will be generated when new data with a Posting Date for which an extract was already generated is posted, without waiting for a new Posting Date.

If the Hold late data for next Posting Date checkbox is checked, in addition to the other two, when new data with a Posting Date for which an extract was already generated is posted, the new records will be held back and posted when data with subsequent Posting Date is in effect. So the extract will contain data with a previous Posting Date that was held back and data with a new Posting Date.

Example for case 1 ( Only extract incremental data and Split per Posting Date checkboxes are checked):

Example for case 2 ( Only extract incremental data, Split per Posting Date and Hold late data for next Posting Date checkboxes are checked):

Configuration Data JSON

The new property was also implemented in the Configuration Data JSON file:

"holdLateDataUntilNewGroupIsFound”

• if the property is set to true, the functionality is enabled
• if the property is set to false, the functionality is disabled

1
{
2
                "extractConfigurationName": "CustomExtract",
3
                "startDate": "2026-05-20T22:01:00Z",
4
                "extractType": "CSV",
5
                "uploadSpace": "CLOUD_STORAGE",
6
                "incremental": true,
7
                "holdLateDataUntilNewGroupIsFound": true,
8
                "query": {
9
                    "namespace": "fynapse",
10
                    "entity": "Journal",
11
                    "queryFilter": {}
12
                },
13
                "scheduler": {
14
                    "type": "DISABLED"
15
                },
16
                "splitBy": {
17
                    "isSplitByAttributeEnabled": true,
18
                    "attributeDescriptors": [
19
                        "customCoreDate"
20
                    ]
21
                }
22
            }