2025.2.3

Journal Aggregation

We enhanced the Journal aggregation functionality. You can now aggregate Journals based on defined Dimension Sets, which will allow you to filter Journals based on certain Dimensions and export the aggregated Journals list to a General Ledger.

Journal Aggregation settings can be included in the Configuration Data JSON file.

For more details, refer to Dimension Sets and Data Extraction.

REST API Changes

The following changes to REST API were introduced:

• For Get data by extractionConfigId and Get data by extractionConfigId as JSONL file endpoints, the 200 response will include the JournalSummaryId if you enable Journal aggregation.
• Get data by extractionConfigId endpoint not work for non-incremental Journal aggregation extracts.

For more details, refer to API Changelog and Extraction section in the API Reference Guide.

Bulk Operations - Unposted Journals Feature Flag

We enhanced the bulk operations functionality. The setting for Unposted Journals will now be included in the Configuration Data JSON file, in the form of the following snippet:

1
"unpostedJournalsFeatureFlag": {
2
        "unpostedJournalsEnabled": true
3
    }

Previously, this setting could only be managed from the System Settings screen. Now, you can upload the setting in the Configuration Data JSON file. This is not a mandatory section.

If you already have an active Fynapse instance and want to download your configuration, the Unposted Journals setting snippet will be included in the Configuration Data JSON file.

FX Revaluation

We implemented the following enhancements to the the FX revaluation feature:

1. You can now choose to use Accounts grouped by tags when defining FX revaluation configuration. Tag groupings are defined in the Chart of Accounts and can be configured either in the CSV file you upload to the Chart of Account screen or in the Configuration Data JSON file.
2. If you type the Accounts by hand, the field provides real-time validation against the Chart of Accounts.
3. You can now select the Offset Account from the Chart of Accounts which is now available in the drop-down list.
4. Version History was implemented on the FX Revaluation Assignment screen and on FX Revaluation Configuration screen, where it’s visible for individual configurations. It allows you to view the changes introduced by users.
5. On the FX Revaluation screen:
6. There are new columns in the grid:
7. Last run status

• Running
• Success
• Completed with errors

2. Last run for - the date for which the given revaluation was run
3. Last run at - the timestamp for when the revaluation run was started
4. Actions - the Actions column allows you to perform the following:

• Rerun - rerun the revaluation for the date in the Last run for column
• Open journals - redirects you to the Journals screen in the Subledger, where the system automatically runs a query based on the Ingestion ID of the Journals which underwent revaluation
• View errors - if a run in unsuccessful, you can view the errors in a pane that will open on the right-hand side of the screen.

2. The Show logs button which redirect you to the FX revaluation logs screen where you can browse information about previous FX revaluation runs.
   Please note, that the Actions column doesn’t have the Rerun option.

3. Finally, now, more than one revaluation can be run at any given time.

For more details on configuring FX revaluation, refer to Multiple Currencies Configuration.

Flow - Reference Entities Can Be Used as Input/Target

We enhanced the Flow functionality. You can now use Reference Entities as source in Input and Target steps.

For more details, refer to Flow and Flow Steps.