Skip to main content
Skip table of contents

Manage Transactions

Introduction

Your transactions form the backbone of your investment records. From the moment they're created to the time they’re confirmed or matched, each transaction goes through a defined lifecycle. This guide helps you understand that lifecycle, especially how statuses and status reasons work and shows you what actions are available to you along the way.

What This Guide Covers

  • How to determine a transaction’s status and status reason

  • What transactional Actions are available (and where)

  • The list of transaction statuses, along with actions available to you

  • Updates to the Transaction Dialog: Related Records and Logs tabs

  • The matching flow triggered when you allocate a transaction

Permission Requirements

Permission IDs

Needed for?

transaction_modify

All actions are available under this permission.

  • Match

  • Activate

  • Approve

  • Allocate

  • Rollback

  • Reprocess

  • Deactivate

transaction_modify + order_create

Allocate action is available under the set of these 2 permissions.

transaction_modify + mifir_modify + transaction_modifyAll

For Sync to Mifir action.

Transaction Actions & Where to Find Them

As you manage your transactions, you’ll have access to various actions depending on the transaction's type, status and status reason. Here’s a breakdown of each action, what it does and where you can perform it.

Where You Can Perform These Actions

You’ll find transaction actions in three key places:

  1. Bulk Panel on the Transaction Table
    When you select one or more transactions using checkboxes, a panel appears at the top of the table showing all actions that are applicable to the selected items.

  1. Actions Menu on Each Transaction Row
    Click the ⋮ icon on the right side of any transaction row to access individual actions specific to that transaction.

  1. Inside the Transaction Dialog
    When you open a transaction > click Edit, you’ll see all available Actions based on its current status and reason.

Transaction Statuses

Here’s a breakdown of each status, status reason, what it means and what you can do:

Full Reference Table:

Status

Status Reason

Description

Available Actions

ACTIVE

Included in position calculation.

Confirmed

Approved or matched.

Rollback, Deactivate, Sync to MIFIR

Order

Based on order execution.

Approve, Match, Deactivate, Sync to MIFIR

PENDING

Not included in calculation.

Not_matched

From bank; not yet matched.

Match, Approve, Allocate, Reprocess, Deactivate, Sync to MIFIR

Pending_confirmation

Manual/imported transaction.

Approve, Reprocess, Deactivate, Sync to MIFIR

Not_allocated

Instrument exists on same date in strategy position.

Allocate, Match, Approve, Reprocess, Deactivate, Sync to MIFIR

ERROR

Not included in calculation.

Processing_error

Creation failed due to missing/invalid data.

Reprocess, Deactivate

Matching_error

Matching failed (technical issue).

Reprocess, Deactivate

DEACTIVATED

Not in calculation.

Error

Manually deactivated.

Activate

Duplicate

Marked as duplicate.

Activate

Amalgamate

Deactivated via amalgamation.

Activate

Available Actions & What They Do

Full Reference Table:

Action

What It Does

Rollback

Undo the transaction’s confirmation and return it to a pending state.

Deactivate

Mark the transaction as deactivated. It won’t affect positions anymore.

Sync to MIFIR

Sends the transaction data to the MIFIR reporting system. (See conditions here).

Match

Pairs the transaction with another one (typically an order or bank record) to confirm it.

Approve

Confirms the transaction without matching or further processing.

Allocate

Distributes the transaction amount across related strategy positions or portfolios.

Reprocess

Retriggers extraction and processing of the raw transaction data (usually helpful for fixing technical issues).

Activate

Restores a previously deactivated transaction.

Edit

Lets you manually update transaction form/fields.

Create Order

Generates a new order object from this transaction.

Conditions to Use Specific Actions

Some actions are only available under certain circumstances.

Here's what to keep in mind:
  1. Sync to MIFIR — When It’s Available

You’ll only see the Sync to MIFIR option if all the following are true:

  • You are not a client user.

  • You have permission flags enabled:transaction_modify, mifir_modify, and transaction_modifyAll.

  1. Link Transaction with Private Asset — When It’s Enabled

You can only link a transaction to a Private Asset if:

  • The transaction type is either Withdrawal or Investment.

  • The transaction status is Active.

  • The status reason is Confirmed.

  • The associated Portfolio type is not Virtual.

How to Manage Transactions

We’ve improved the transaction dialog to give you more clarity.

transaction form.gif

Main: Dynamic Action Menu

No more jumping back to the transaction table. The Action dropdown is now right inside the transaction dialog. It dynamically updates based on each transaction’s status and status reason, showing only the actions that matter.

Related Records

This tab gives you a clear view of how a transaction connects across the platform. Here’s what you get across the three sub-tabs:

Parent & Child Structure

See how partial executions or order splits are grouped under one parent. No more hunting across multiple screens.

TTCA & Virtual Structure

Shows related transactions within a TTCA (Omnibus) or Virtual account structure that appears here when the transaction is either a parent omnibus transaction or is linked to one.

Related Orders

Shows all orders linked to the selected transaction, helping you trace its origin and execution path.

Logs

Stay informed with complete visibility into what’s changed:

Updates History

Review field-level changes over time.

Fields Reference:

Platform Field

Description

Date & Author

A unique code used for grouping purposes internally.

Action

Describes the type of change performed (e.g., Object linked, Value changed, etc).

Date

The timestamp when the change occurred.

Author

The user who performed the action.

Field Name

The specific field that was changed (e.g., accrued, grossAmount, qty, price, etc).

Before

The value of the field before the update. May be blank depending on the action type.

After

The value of the field after the update. May vary based on field type and action.

Change Requests

Track submitted and approved changes, all in one place.

Fields Reference:

Platform Field

Description

Approver

The user responsible for reviewing and approving or rejecting the change request.

Creator

The user who submitted or initiated the change request.

Created

The date and time when the change request was originally created.

Updated

The most recent date and time when the request was modified.

Status

The current state of the change request (e.g., Pending, Approved, Rejected).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.