Fiduciary – Module Set-up

Posted by
Print Friendly, PDF & Email

This document describes different tables used to setup the Fiduciaires within T24/Globus.

Commissions Calculations

 

Conditions applicable for commissions, fees, etc…

 

CONDITION.PRIORITY

Definition of criterion to group clients for wich « profiles » of  commission conditions, fees, etc… may be applicable for fiduciaries.

 

FD.GEN.CONDITION

Declaration of the various groups identified . Groups are based on criterion defined in CONDITION.PRIORITY.

 

FD.GROUP.CONDITION

Allocation of commissions conditions (definied in FD.COMMISSION.TYPE) to the various clients groups (declared in FD.GEN.CONDITION).

 

FD.COMMISSION.TYPE

Definition of « commissions profiles » (applicable rates by level or band) group of clients or types of fiduciaries (usually fixed or notice, defined in FD.CHARGE.PARAMETER).

 

FD.CHARGE.PARAMETER

 

Usually 2 records (fixed and notice) allow to define the computation mode for commissions : in advance or at maturity, and also the basis (on principal, interest or net amount).

NB : A new functionnality in G9.2 allows to calculate commissions amounts depending on the fiduciary portfolio volumes of clients. This to give best conditions for greater volumes.

Fiduciary Data Model
Fiduciary Data Model

 

Operational Tables

 

1. Workflow

1 orders Input

Application FD.FID.ORDER

After authorisation, the order takes a status « OPEN » (# 30 POOLING.STATUS)

 

2 Pools Modification (optionnal)

This stage allows to modify the system pre-set groups

 

3 Pools Approval

To change the status from  « OPEN » to « APPROVED ». Globus will immediately create a record in FD.FIDUCIARY (used for placements), in FHLD => feeds FD.FIDUCIARY$NAU.

 

4 Fiduciary Placements

Browsing the exceptions « FHLD » from FD.FIDUCIARY ($NAU), dealer may pick up all awaiting pools to place them. If unit orders are containing banks preferences, they are automatically defaulted.

 

It is also possible to modify principal amounts for call notice orders :

 

1 Modify on orders the fields:

# 65 PRIN.CHANGE

# 66 CHANGE.DATE

After authorisation, Globus updates the field 67 CHANGE.STATUS from « ACTIONED » to « REQUESTED ». This is done simultaneously on the corresponding placement setting the field # 46 CHNG.STATUS with « REQUESTED ». On the order, field # 30 POOLING.STATUS is moved to « AMENDED ».

 

2 Update the Placement

Select placements with field # 46 CHNG.STATUS « REQUESTED » and move it to « ACCEPTED ». Others modifications are directly coming from orders.

 

 

 

2. Tables Used

 

FD.FID.ORDER

Fiduciary Orders (fixed or Notice)

 

FD.FIDUCIARY

Fiduciary Placements (fixed or Notice)

FD.FID.CURRENCY

Minimum amounts by currency and min. quotities.

 

FD.CUST.DETAILS

Client’s preferences in terms of privileged banks for placement by currency; excluded banks, and maximum total outstanding (total or per bank).

 

FD.GROUP.PAYMENT

For each key as: banking counterparty -currency-notice no of days, possibility to define placement rates, to avoid individual updates.

 

FD.POOL.GROUP

For each order or group of orders (if pooled) this internal file (concat.file) stores details with currency, value and maturity dates, total amounts, orders and placements references with their respective status.

 

Commissions

 

  1. Commissions and unit fees to be defined

The following example is based on local swiss practices, but set in GBP (to be adapted into CHF)…

FD Commissions
FD Commissions

2. Summary of conditions applicable to a group of clients

FD Commissions
FD Commissions

 

NB : linked to fields           # 2 from FD.COMMISSION.TYPE

# 7 from FT.COMMISSION.TYPE

 

+ « automatic » allocation of these conditions depending on the client’s group; cf field 72 of FD.FID.ORDER.


 

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.