> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fynapse.app/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fynapse.app/_mcp/server.

# Release Notes

## November 5, 2026

> Fynapse releases enhancements.

## File Size Limits and gzip Uploads

ingestion, file upload

We defined new size limits for upload files:

| Limit                                                                                                       | Value                                                                                                                                                                                         |
| ----------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| File uploaded via the Fynapse UI                                                                            | 100 MB. Place larger files in the dedicated cloud storage folder, see [Data Ingestion Using Backend](/documentation/data-integration/data-input-file-ingestion/data-ingestion-using-backend). |
| Uncompressed CSV file                                                                                       | 5 GB                                                                                                                                                                                          |
| File for an Entity with automatic sorting, as uploaded (for a file in the gzip format, its compressed size) | 2 GB                                                                                                                                                                                          |
| Uncompressed data in a file in the gzip format or in a file for an Entity with automatic sorting            | About 30 GB                                                                                                                                                                                   |

Additionally, we added the ability to upload gzip files via the Ingestion screen.

Read the docs

## Editable Scheduler for Extracts

extracts, scheduler

We enhanced the scheduler functionality for extracts, you can now edit an existing extract for active and inactive extracts
via the Extract Configurations screen or Configuration Data JSON file.

Read the docs

## FX Revaluation Screens Redesign

fx revaluation, ui migration

We migrated the **RX Revaluation** and nested **Show logs** screen for an improved look and feel.

The core functionalities remain unchanged.

Read the docs

## November 4, 2026

> Fynapse releases new AI skills.

## MCP Server - New AI Skills

mcp server, ai agents

We’ve added new AI skills to our Fynapse Agent:

* Flow Builder - that allows you to turn your own transaction data into Fynapse Business Events with a Flow. This skill maps your transaction entity to Business Events, adds a script or routing step only where one is needed, previews the Flow with Fynapse until it is valid, and publishes it only when you confirm
* Subledger Configuration - that allows you to set up and change the accounting rules in Fynapse: how Business Events are identified, which accounts they post to, and how their Journals are built. The skill reads your current configuration, drafts the change, checks that it balances, validates it with Fynapse, and only then writes it, after you confirm. Where your approval workflow is on, changes go through it.

Read the docs

## November 3, 2026

> Fynapse releases the ability to create configuration using the MCP server.

## MCP Server - Configuration Capability

mcp server, ai agents

We’ve added new configuration REST APIs, plus matching tools on our MCP server so your AI agent (for example, Claude) can call them directly. We’ve also released a Fynapse configuration skill. They guide the agent through building and changing your configuration properly: it reads what’s already set up, proposes changes for you to review, and validates them before anything is applied.

You can now configure Fynapse by describing what you want in a prompt, such as “add a posting for deferred revenue” or “reject events with an unknown cost centre”, and your agent makes the changes through the APIs.

Read the docs

Video preview:

## October 28, 2026

> Fynapse releases enhanced Validations screen and new extract configuration status.

## Validations Screen Redesign

validations, ui migration

We migrated the **Validations** screen for an improved look and feel.

List of changes:

* the **Download** button moved from the **Actions** column to the **Name** column, next to the name of the Entity
* the **Go to Details** button moved from the **Details** column to the **Actions** column
* the **Details** column was removed
* on the **Details** screen, if the validation includes a name of an Entity, the name is a link that will now redirect you to the Data Structure Definition Details screen for this Entity, instead of Finance Data Service

The core functionalities remain unchanged.

Read the docs

## Extraction Configuration - Invalid Status

extraction configuration

We introduced a new Invalid status for extract configurations.

The Invalid status is assigned to an extraction configuration when:

* an Entity that was used as the source for the extraction has been deleted
* attributes from an Entity were deleted that are required by the extraction

An extract configuration in Invalid status is not run and cannot be manually triggered.

If you restore the source Entity with the required parameters: the same name and attributes required by the extraction configuration,
the configuration will be automatically restored to the status it had prior to the source Entity being deleted, e.g. Active,
and will resume operations.

Read the docs

## October 27, 2026

> Fynapse releases enhancements on the Adjustment Portal screen, with new functionalities, such as error handling, and redesigns the Processing Summary screen and adds a Pipeline view that follows each ingestion through every stage of its processing, Flows included.

## Processing Summary Overhaul

processing-summary, flows, ui migration

We redesigned the **Processing Summary** screen and added a second view, **Pipeline**, that follows each ingestion through the stages it actually passes, including the Flows that read its records.

The changes are listed below.

> **Info**
>
> The classic view keeps its columns, statuses and counts.

### Changes on the Classic View:

* **Refresh** is now in the page header. The **Classic** | **Pipeline** switch, **From** date box and **Reset** are in a toolbar above the grid.
* The screen now refreshes every 30 seconds. You can no longer choose a refresh interval.
* **From** is set to midnight seven days ago by default, and **Reset** restores that value.
* The grid now shows 100 ingestions per page with a pager, instead of the **Load more** button.
* Ingestions are now sorted by start time, newest first.
* An opened ingestion now shows its counts in a **Subledger statistics** section, with **Export to Excel** beside the heading.
* A count that is too wide for its column now ends in an ellipsis. Widen the column to see the whole number.

### New Pipeline View:

* Each ingestion has a strip of the stages it passed, such as **Ingested**, **Validated**, **Flows**, **Accounting**, **Posted** and **Stored**. Each stage shows the records that passed it and the records that did not: duplicates, failures, records a Flow produced no output for, and unposted Journal Lines.
* The **Kind** column shows whether the ingestion contains Business Events, Journal input, reference data or transaction data, its Entity, and whether it came from a file, the API or an extract.
* The Pipeline view also lists the ingestions that the Classic view does not: reference data, and ingestions read by Flows that write no Business Events or Journal input.
* You can filter the grid by ingestion, kind and status.
* Click an ingestion to open its page: a diagram of its stages, a table of the Flow versions that read its records, and its Subledger statistics. **N failed records** opens the **Errors** screen filtered to the ingestion.

> **Info**
>
> The Pipeline view lists ingestions that start after your environment is upgraded to this release. Earlier ingestions remain in the Classic view, which lists the ingestions that lead to Journals.

Read the docs

Video preview:

## Adjustment Portal Enhancement

adjustment portal

We introduced a number of enhancements on the **Adjustment Portal** screen.

Previously, when uploading a file with Journals, there were two ingestion error scenarios:

* The file had invalid format or header - the file would receive **Invalid upload** status, no records were ingested and you had to download the errors in a .CSV file
* The records in the file were invalid - the file would receive **Invalid upload** status, the records were ingested but failed processing; you had to download the errors in a .CSV file

### Changes

* Error handling is now available directly on the **Adjustment Portal** screen.
* We introduced a new status: **\[number of] errors** for files with errors that can be resolved in the UI
* Additionally, the errors are available as tooltips.

So now, the two scenarios have different outcomes:

* When a file fails upon ingestion, e.g. has invalid format or header - the file still receives **Invalid upload** status and no records were ingested
  but instead of downloading the file, you view the errors on the **Details** screen for the given ingestion. These types of errors
  require changes to the file, e.g. reformatting or amending the header, and cannot be resolved on the screen.
* When a file is ingested, but the records in the file are invalid, the file receives the new status **\[number of] errors**
  in the file and you can view and resolve the errors on the **Details** screen for the given ingestion.

Read the docs

Video preview:

## October 19, 2026

> Fynapse releases enhanced Reclassification functionality.

## Reclassification Enhancement

reclassification

We enhanced the **Reclassification** functionality. You now have two reclassification methods available:

* Sweep method - this method covers how reclassification worked up to date, where adjustments of multiple Accounts are
  reclassified and posted to one offset Account based on a set of filtering condition defined for the source Accounts
* Net position method - new method for reclassification, where reclassification is based on the signage of the total sum balance for a selected asset and liability Account pair or pairs specified within the rule
  * if upon the calculation the total sum is negative, the transactions are moved from Accounts defined as asset Accounts to Accounts defined as liability Accounts
  * if upon the calculation the total sum is positive, the transactions are moved from Accounts defined as liability Accounts to Accounts defined as asset Accounts

Read the docs

## October 16, 2026

> Fynapse adds Email Notifications screen and Scheduler for reclassification and FX revaluation.

## Email Notifications Screen

email-subscriptions

We added a new **Email Notifications** screen that allows you to browse and manage the list of Approval Workflow
email notifications and cutome email notifications created for ingestion and extraction events.

Read the docs

for Approval Workflow notifications

Read the docs

for custom notifications

## Reclassification and FX Revaluation - Scheduler

reclassification, fx-revaluation, scheduler

We enhanced the **Reclassification** and **FX Revaluation** screens with the new Scheduler functionality, which allows you to schedule reclassification and revaluation runs.

Read the docs

to learn how to configure scheduler for reclassification.

Read the docs

to learn how to configure scheduler for FX revaluation.

Video preview:

## October 15, 2026

> Fynapse redesigns the Flow screens, with step details beside the diagram, a full-screen script editor and more information in the Flow grid.

## Error and Download Errors Screens Redesign

error management, ui migration

We migrated the **Errors** and **Download Errors** screen for an improved look and feel.

The core functionalities remain unchanged.

Read the docs

## October 13, 2026

> Fynapse redesigns the Flow screens, with step details beside the diagram, a full-screen script editor and more information in the Flow grid.

## Flow Screens Redesign

flows, ui migration

We redesigned the Flow screens. Please consult the sections below to see itemised lists of changes of the affected screens.

The way you build, validate and submit Flows hasn't changed.

### Changes on the Editing screen:

* A step's details, and the Flow's settings, now open in a panel to the right of the diagram instead of below it. Close the panel to see the whole diagram.
* Each panel is a column of sections, such as **General**, **Attributes mapping** and **Match keys**, instead of tabs. Each section has a description.
* You pick an Entity from a list that you can search, grouped by namespace, instead of from a drop-down list.
* After you click **Validate**, problems open in the **Validation** panel, grouped by step. **Show** opens the step that a problem belongs to.
* The status chip in the header shows the version's status, such as **Active** or **Draft**, and the **Undo** and **Redo** buttons show their names.
* A Script step's outputs use the same field grid as the **Data Structure Definition** screen.
* In a Script step, **Show full screen** gives the script the whole window. Click **Exit full screen**, or press Esc, to return.
* Edits still save automatically, 5 seconds after your last change. **Submit** now saves any pending edits and then submits the Flow, instead of staying disabled until the draft is saved.
* **Undo** now reverses one action at a time: a burst of typing in a field, or deleting a step together with its links.

### Changes on the View screen:

* The grid has new **Input Entity** and **Target Entities** columns.
* Deleting a Flow now asks you to confirm. Fynapse archives a deleted Flow and removes it from the grid.

Read the docs

## October 12, 2026

> Fynapse releases updates for the Reclassification functionality.

## Reclassification Enhancement

reclassification

We enhanced the reclassification screen with the following changes:

* Process date - allows you to set the date for which Journals created as the result of the reclassification process will be posted.

  This can be either the current business date or a specific date.

  Please note that the Process date is calculated based on the time zone of the Subledger Node/Accounting Base combination assigned to the reclassification configuration used for the reclassification run.
* Show logs - a new button that allows you to view detailed logs for reclassification runs.

Read the docs

## FX Revaluation Enhancement

fx revaluation

We enhanced the **FX Revaluation assignment** screen, you can now assign multiple FX revaluation configurations to a Subledger Node/Accounting Base combination.

Read the docs

## September 28, 2026

> Fynapse adds storage metrics to the Home screen dashboard.

## Dashboard - Stored Metrics

dashboard

We added storage metrics to the Home screen Dashboard. Storage metrics cover the usage of storage space used up by
Entities in Fynapse.

Read the docs

Video preview:

## September 25, 2026

> Fynapse adds the Zero value transactions setting, which allows Journals with a transaction amount of zero to be posted to the Subledger.

## Zero Value Transactions

journals, business-events, configuration-data

Fynapse rejects financial data with a transaction amount of zero by default. The new **Zero value transactions**
setting on the **System Settings** screen changes that behaviour: zero value transactions become valid financial
data that produces balanced Journals, posted to the Subledger and queryable alongside every other Journal.

Business Events with zero amounts generate Journals only through Posting Patterns whose Amount Signage is set to
`AUTO`, and zero value Journals contribute nothing to Balances. The setting is included in Configuration Data, so
it travels with configuration downloads and uploads.

> **Info**
>
> The setting is disabled by default, and enabling it is not retrospective. Existing instances keep rejecting zero
> value transactions until you enable it.

Read the docs

Zero Value Transactions
description: Fynapse introduces new documentation for using AI tools with Fynapse through MCP and Agent Skills.

## September 24, 2026

> New documentation for working with Fynapse using AI.

## Work with Fynapse using AI

ai, mcp, agent-skills

We added a new **For AI Agents** area to the Fynapse documentation. It brings together the resources you need to connect AI tools to Fynapse, give them access to Fynapse product knowledge, and equip them with reusable skills for finance-specific tasks.

The new area includes guidance for the **Fynapse MCP Server**, **Documentation MCP Server**, and **Agent Skills**, including skills for Flux Analysis, Journal Search, and Journal Explainer.

Explore AI Agents

## September 17, 2026

> Fynapse adds Approval Workflow integration to Period Locking.

## Period Locking - Approval Workflow

workflow, period-locking

We enhanced the Period Locking screen to be compatible with Approval Workflow functionality. Now you can
create workflow configurations, with hierarchical approval process, for actions on the Period Locking screen.

> **Info**
>
> Please note that Approval Workflow has one additional key feature on the Period Locking screen. Due to the unique
> specification of the screen's functionality, i.e. when you request an approval to open a period you specify a timeframe
> it should be open. Because the Approver may take a while to approve the request, they specify the time a period should be open.
> It can be either the timeframe specified by the requestor, e.g. 2 days, or a different timeframe selected by the approver,
> e.g. 3 days. In both instances the period is open since the time the request is approved, and NOT from the time the
> request has been submitted.

Read the docs

Period Locking

Read the docs

Approval Workflow

Video preview:

## September 7, 2026

> Fynapse adds Balance Sheet report.

## Balance Sheet

reports

We implemented a new Balance Sheet screen that allows you to generate a report that summarizes a business’s financial position at a specific point in time,
summarizing what it owns, what it owes, and the resulting equity.

Read the docs

Video preview:

## New MCP Tools

mcp-server

AI assistants and agents can now read live financial data straight from Fynapse. The Fynapse MCP server exposes four new
read-only tools that give any MCP Compatible AI Agents / Assistants real-time access to your balances, Journals
and configuration, with no exports, no stale copies, and no custom integration work.

New tools:

* Query balances — as-of account balances for any date, filtered and grouped by your own configured fields: accounts, entities and nodes, dimension attributes, transaction currency. Works in transaction or reporting currency view, resolves plain-English names such as "deferred revenue" to codes, and pages through large result sets.
* Query journals — the drill-down under balances. Find posted journals and their lines by header and line criteria: date range, journal type, account, amount, dimension values, or an exact journal ID. Returns the matching lines by default, with options to include every line, attribute and amount field.
* Browse configuration — list configuration by type, with filters and paging. Covers 32 resource types including posting components, account lookups, chart of accounts, journal types, accounting configurations, business and fiscal calendars, entities, dimension sets, node values, FX revaluation and cleardown settings, and feature flags. Summary mode for quick scans, full mode for every field.
* Get configuration — retrieve one configuration item in full by its name or code, or a whole settings object such as the journal line definition, functional and reporting currencies, or FX settings.

## Data Structure Definition - Workflow Approval

data-structure-definition, approval-workflow

We enhanced the Data Structure Definition screen to be compatible with Approval Workflow functionality. Now you can
create workflow configurations, with hierarchical approval process, for actions on the Data Structure Definition screen.

Read the docs

Data Structure Definition

Read the docs

Approval Workflow

Video preview:

## September 4, 2026

> Fynapse adds Workflow Approval integration for Webhook subscriptions, Email Subscriptions for Approval Workflow, and Custom Emails.

## Webhook Subscriptions - Approval Workflow Integration

webhooks

We integrated the Approval Workflow functionality with Webhooks.
You can now create Webhook subscriptions for your Approval Workflow events.

Read the docs

## Approval Workflow - Email Subscriptions

approval-workflow

We implemented a new feature to Approval Workflow - email subscriptions.
Now, you will recieve notifications about new approval requests or information about the status changes of your request on your email.

> **Info**
>
> Released under a feature flag.

Read the docs

## Custom Email Subscriptions

email-subscriptions

Apart from the default email notifications for Workflow Approvals, you can create custom email subscriptions for different [Event Types](/api-reference/getting-started/webhooks/event-types).

Read the docs

## August 27, 2026

> Fynapse adds Reclassification, a configurable process for moving balances between account classifications to support regulatory compliance and financial reporting accuracy.

## Reclassification

reclassification, journals

We added a new feature - reclassification.

Reclassification is an accounting process where, due to regulatory compliance requirements and financial reporting accuracy, certain accounts require balance transfers, e.g. due to initial missclassification. It adjusts where an amount is reported, i.e. how it is classified in the system, not the amount itself or the underlying transaction.

In Fynapse, the Reclassification functionality supports regulatory compliance and financial reporting accuracy by enabling systematic movement of balances between account classifications without manual intervention based on a set of specified filter criteria.

The Reclassification capability provides:

* Reclassification Configurations that specify the Journal Type for the Journal that will be posted as a result and a set of rules specifying source accounts, adjustment filters on balances, offset accounts.

* Assignment of one or more movement configurations to Accounting Base and Subledger Node combinations

* On-demand execution of the balance movement process, self-correcting against balances already moved

Read the docs

Video preview:

## August 26, 2026

## Data Structure Definition

data-structure-definition, validations

We added a new **View lookup validations** tab to the Entity details screen that allows you to view the Lookup validations
defined for the given Entity.

Read the docs

## August 10, 2026

## MCP Server

mcp-server

We added two new capabilities to the AI assistant:

1. Browse and filter configuration by type, such as Posting Components, Chart of Accounts, Journal Types, Business and Fiscal Calendars, Accounting Bases, etc.
2. Look up a specific configuration item by its exact name or code, with all of its details

Read the docs

## Data Structure Definition

data-structure-definition

To ensure better quality of data integrity, we removed the capability to delete multiple Entities on the Data Structure Definition screen.
The capability to delete a single Entity using the **Delete entity structure** action in the **Actions** column has been retained.

## August 6, 2026

## Data Structure Definition

data-structure-definition

We enhanced the **Data Structure Definition** screen to include Protected Entities, such as Journal, BusinessEvent, etc.
You can now see these Entities in the grid and view their structure on the **Details** screen.

> **Info**
>
> Please note that Protected Entities are view only, you cannot delete them.

## Retention Policy

data-structure-definition, data-retention

We enhanced the **Data Structure Definition** screen to allow you to configure Data Retention Policy for Reference Entities.

Read the docs

_Showing the 20 most recent of 29 entries. Append `/llms.txt` to the changelog URL for the complete index._