UNIFINplatform

Solution

Unifin Corporate Actions

A corporate event is judged by the payout date and the receipt.
The service takes the announcement, fixes the register and computes the entitlement.
Tax is withheld per account and the trail runs to the statement.

  • Event register
  • Entitlement
  • Tax and payouts
All solutions

Live screens from the product terminals

Event terms entry form with checks and the processing route Event terms entry form with checks and the processing route Entitlement calculation screen with runs and per-account results Entitlement calculation screen with runs and per-account results Message flow screen with corporate action messages and the action journal
Demo Unifin Corporate Actions Theme Open separately
Event register
Event register

This is an interface demonstration: the real solution will differ in colours and content for a specific project.

Functions at a glance

Business functions at a glance

From an announcement to a receipt.

Event register
Keeps events with type, dates and status from the announcement to the closure
One register of the year, with an owner per event
Event terms
Holds rates, dates, formulas, rounding and tax rules, checked before the run
The calculation starts on confirmed terms
Entitlement
Computes the entitlement on the record date for every account
Every holder sees a number that can be explained
Tax and payouts
Withholds tax by domicile and pays the cash and asset leg
Payouts land on their dates without manual nets
Elections
Opens the election window and records the option per account
A tender or rights decision is captured with its volume
Message flow
Sends and receives corporate action messages in ISO 20022 and SWIFT
Participants and downstream systems stay in step
Reporting
Builds payout statements, receipts and the journal from the live positions
The audit walks along a ready trail

What runs today

The event life cycle, already running

Register, calculation and payouts: the live parts.

Event register

Events and terms live in one register with statuses.

Calculation

Entitlement runs per account and sub-account.

Tax

Withholding follows the domicile and the profile.

Payouts

Cash and asset legs leave with receipts.

Elections

Voluntary events carry their election window.

Messages

ISO 20022 and SWIFT formats are exchanged.

Solution description

Capabilities and overview

Key features

  • Event intake from a source system, the desk, ISO 20022 sese.023 or SWIFT files
  • Event register with types, dates, terms and statuses
  • Configurable types, formulas, rounding rules and tax rules
  • Event chains with dependencies, ordered automatically
  • Entitlement per account and sub-account on the record date
  • Simulation on theoretical positions over a chain
  • Tax withholding per account by investor type and domicile
  • Cash and asset payouts in USD with a payout calendar
  • Elections and the election window for voluntary events
  • Message flow: ISO 20022 sese.023 and SWIFT MT564, MT565, MT566
  • Receipts, statements and the immutable action journal
  • Standalone deployment or as a module of the UNIFIN platform

Product overview

Unifin Corporate Actions is the corporate action service of the UniFin platform. It serves depositories, CSDs, registrars and custodian banks that keep securities on their own register.

The service runs the whole event. The run covers intake, checks, the announcement and register fixation. Then come entitlement by account, tax withholding, payouts and receipts.

Behind the event logic stand ISO 20022 messages, SWIFT files and the platform bus. Reconciliation, supervisor reporting and the journal follow the same trail.

The service deploys standalone next to an existing depository or CSD. It also runs as a module of the platform and connects to registrars and custodians over their own interfaces.

Inside the platform it shares the register with Unifin Depository. The settlement and payment path is shared with Unifin Collateral and Unifin Payment Bank.

What it delivers

What the solution delivers

From the announcement to the receipt.

Event register

Events arrive from a source system, the desk or a file, and each one opens its own folder. The service keeps the type, the dates and the statuses in one register and shows what waits for confirmation. With the solution the year of events is visible in one place, and every event has an owner. In setup the event types and the calendars come as reference data.

Event terms

A term that is entered late or typed twice puts the payout behind schedule. The service holds rates, dates, formulas, rounding and tax rules, and checks them before the run starts. With the solution the calculation starts on confirmed terms, and a change of terms is journaled with its basis. In setup the formula and the rounding come per event type.

Entitlement

An entitlement is disputed when nobody can retrace the number. The service computes the entitlement from the frozen positions and keeps the record of the run. With the solution every holder sees a figure that can be explained step by step. In setup the official run and the simulation use the same rules.

Tax and payouts

Withholding by hand loses money and time at every payout. The service computes tax per account from the investor profile and runs the payout on the cash and asset leg. With the solution payouts leave on their dates and every event closes with receipts. In setup rates, exceptions and domiciles are configuration.

Elections

A voluntary event lives or dies by the election window. The service opens the window at the announcement, records the option and the volume per account, and closes it at the deadline. With the solution a tender or rights decision is captured with its reason, and reminders go to silent holders. In setup the available options are defined per event type.

Message flow

Participants and downstream systems expect the event in a format they already read. The service exchanges ISO 20022 sese.023 and SWIFT MT564, MT565 and MT566 messages next to the API and files. With the solution the market and the platforms stay in step, and every message leaves a receipt. In setup the addresses and the schedules are configuration.

Reporting

Statements are assembled by hand while the audit waits for the trail. The service builds payout statements, receipts and the journal from the live positions. With the solution the supervisor and the holder get an answer on time, and the audit walks along a ready trail. In setup the form scope and the dispatch schedule stay visible.

Coverage

What it covers

A route: announcement, register, calculation, tax, payout, receipt.

Event intake

Source systems, the desk, ISO 20022 sese.023, SWIFT files and the API.

Terms and checks

Rates, dates, formulas, rounding, tax rules and the confirmation gate.

Event chains

Dependencies between events and their automatic order of processing.

Entitlement

Positions on the record date, accounts and sub-accounts, the official run.

Simulation

Theoretical positions over a chain for a selected set of accounts.

Tax withholding

Investor profiles, domiciles, exceptions and payout nets.

Payouts

Cash and asset legs in USD, the payout calendar and confirmations.

Documents and journal

Receipts, statements, notifications and the immutable action journal.

Stand

Screens of the solution

The event register, the terms form, the entitlement run, tax and payouts, elections and the message flow.

Event register screen with corporate events of the year
The event register: types, dates, terms and statuses of the year
Event terms entry form with checks and the processing route
Event terms: rates, dates, rounding and tax rules before the calculation
Entitlement calculation screen with runs and per-account results
Entitlement calculation: positions on the record date, gross, tax and net
Tax and payouts screen with the withholding table and the payout calendar
Tax and payouts: withholding by domicile and the payout calendar
Elections screen for a voluntary event with the election window
Elections: the window, the option and the volume per account
Message flow screen with corporate action messages and the action journal
Message flow: ISO 20022 sese.023 and SWIFT MT564/565/566 with receipts

How it works

From an announcement to a receipt in five steps

The path of an event: intake, terms, register, calculation, payout.

  1. 1

    The event arrives

    An announcement enters from the source system or the desk.

  2. 2

    Terms are confirmed

    Rates, dates, rounding and tax rules pass their checks.

  3. 3

    The register is fixed

    Positions are fixed on the record date per account.

  4. 4

    The calculation runs

    Entitlement and tax produce a net amount per holder.

  5. 5

    The payout closes

    The cash and asset leg leaves with receipts and statements.

Industries

Industries it serves

The service serves central securities depositories and depositories, registrars and issuers, custodian banks, brokers and asset managers, and the supervisor.

Corporate / issuer

Market access for producers and issuers: auctions, deliveries, tokenised assets and data.

Architecture

Architecture and access

The architecture rests on the corporate action core and the register. Events, terms, entitlement, tax, payouts and the journal.

Service core

The event register, terms, entitlement, tax withholding, payouts, messages and the journal.

Register as the base

Positions come from the depository register, so the entitlement base is the accounts record.

Event bus

Events move with a transactional outbox: announcement, calculation and payout stay in step.

Capacity on the peak

The calculation module runs separately: more than 1,000,000 messages in less than an hour.

AI layer

The AI layer drafts the payout digest and answers questions on event terms; people decide.

Architecture scheme The same architecture as a standalone page. Open the diagram separately

Readiness

Ready today, next in line

The base is in place; next: analytics on payouts and chain modelling.

Ready today

  • The event register with types, terms, dates and statuses
  • Entitlement on the record date across accounts and sub-accounts
  • Tax withholding by profile and domicile, payouts in USD
  • Message flow in ISO 20022 sese.023 and SWIFT MT564/565/566

Next in line

  • Analytics on the payout calendar for issuer services
  • Chain modelling with scenario comparison for issuers (roadmap)
  • Additional registrar routes and local market formats (roadmap)

Releases

Release history

Quarterly releases from the foundation of the platform (2020); the corporate action service launched in 2026.

2026 Q2

  • The event register with types, terms, dates and statuses.

2026 Q3

  • Entitlement per account, tax withholding and payouts in USD.

2026 Q4

  • Elections on voluntary events and the message flow in ISO 20022 and SWIFT (plan).

Detailed description

Detailed description

The event life cycle, the tax frame and the payout calendar.

How the suite is assembled

Channels and clients
FIX 4.2 / 4.4 / 5.0, REST with mTLS, SFTP files, web portals
Edge and access
API gateway with 126 routes, Keycloak single sign-on, WAF and CSP
Platform core services
ca-ms depository-ms settlement-ms payment-bank-ms AI agentic layer Services of the suite on the shared platform core
Data and events
PostgreSQL 17 per service, Redis 7, RabbitMQ 3.13 quorum queues, transactional outbox
Results and reporting
Portals, reports, regulator and partner channels

Event intake and terms

  • The announcement arrives over ISO 20022 sese.023 or as an MT564 file; the desk can also enter it by hand.
  • The terms carry the rate, the dates, the rounding rule and the tax rules; the formula is checked before the run.
  • A chain holds the events that depend on each other; the service orders the chain and reports per event.
  • The first delivery carries dividends, coupons, redemptions, splits, rights, conversions, buybacks and meetings.

Entitlement and the tax frame

  • The official run takes the actual positions on the record date and produces a line per account and sub-account.
  • Simulation takes theoretical positions over a chain for a selected set of accounts.
  • Tax is computed per account from the investor profile, built on asset type, event type, investor type and domicile.
  • The run record is stored: a calculation can be replayed and explained step by step.

Payouts and receipts

  • Payouts run on the cash and the asset leg in USD, through the payment circuit of the platform.
  • The register is fixed before the payout; a divergence opens a case and holds the payout.
  • Every event closes with receipts and statements per holder.
  • Elections on voluntary events are recorded with the option, the volume and the reason.

Messages and the journal

  • Corporate action messages run over ISO 20022 sese.023 and SWIFT MT564, MT565 and MT566.
  • Throughput is more than 1,000,000 messages in less than an hour; capacity grows by adding nodes.
  • Downstream systems read the outcome from the bus with a transactional outbox.
  • The journal is immutable: it keeps the actor, the time and the basis of every action.

AI layer

  • The AI layer drafts the payout digest and the holder notice from the live positions.
  • Questions on the event terms are answered from the register and the journal.
  • A chain simulation shows the effect of an event on a selected set of accounts.
  • People approve: the agent prepares, the officer decides.
Detailed description

Leave your contacts to open the detailed description and download the PDF with architecture, cases and delivery details.

Ask about corporate actions

Bring one event type or one payout date. We will show the path from the announcement to the register, the calculation and the receipt.