SCD feed for IC_AA
Purpose / Description
SCD as a data source does already provide data for group clients in fee model commission calculation. For IC and AA, there will be a dedicated monthly feed
Use Case
| As a system I want to import the asset values for calculating invoice amount based on AuM or AuA under Fee Distribution model | |
| Primary Actor(s) | FSC |
| Stakeholders and Interest | Invoice reviewer, Invoice manager |
| Trigger | Import of the file with dedicated naming convention |
| Pre-condition(s) |
The file has the agreed naming convention, the file is formatted in csv. |
| Post-condition(s) | The file is processed by FSC and results are visible in the session monitor |
| Main success scenario |
FSC picks the file up from the defined storage place. After some pre-processing (see separate use case) the data is imported. Any error are visible in the session monitor. The computation is kicked off after successful import |
| Extensions |
See separate use case for cloning file to produce portfolio-counterparty links Multiple fee types (AuM and AuA) |
| Exception scenarios |
The import is done monthly. Quarterly and monthly agreements which are calculated based on 'last day of period' will be automatic. Calculations based on for example:
will not be automatic. Please contact FinSoft for these agreements as these need to be sourced via the standard template with pre-calculated values.
|
| Special requirements | |
| Open questions |
Mockup
Functional Requirements
| Business rules and functional requirements |
| The portfolio source system will be mapped to ???? |
| The file name |
Field level specification
|
FSC Usage |
SCD IC_AA column |
Rules |
Size |
Mandatory |
|
Portfolio external ref |
(G) Depot |
|
50 |
Yes |
|
Portfolio Source System |
|
Default to SCD |
|
|
|
Product external ref |
(H) SCD Security ID |
|
50 |
Yes |
|
Counterparty name |
(A) Invoice group |
|
100 |
Yes |
|
Counterparty Code |
(A) Invoice group |
|
50 |
Yes |
|
Counterparty external reference |
(A) Invoice group |
|
50 |
Yes |
|
Fee Base Amount (AUM) |
(P) Dirty Value QC |
|
N/A |
Yes |
|
Fee Base Amount (AUA) |
Q (Dirty Value PC |
|
|
Yes |
|
Effective Date |
(X) Selection date |
|
dd.mm.yyyy |
Yes |
|
Transaction external reference |
|
|
50 |
Yes |
|
Name |
(F) WP Name |
|
255 |
Yes |
| SCD Columns | Description | Finsoft internal mapping | Data type | Mandatory | Sample data |
| Fee Date (x) | Date which defines the fee period | Rebate date | Date, dd.mm.yyyy | Yes | 31.03.2026 |
| N/A | Create a unique reference for the entry by combining Fee Date_Portfolio_Product | Transaction external reference | String 50 characters, case sensitive | Yes | 31012026_PK7500D00_XS1076018305 |
| SCD Security ID (H) | Refers to which Assets/projects etc are being invoiced | Product external reference | String 50 characters, case sensitive | No | XS123456789 |
| Depot (G) | Refers to the account/portfolio etc were assets are located | Portfolio External reference | String 50 characters, case sensitive | Yes | SX7108984664 |
| Here the fixed value SCD should be used. | Portfolio source system | String, 255 characters, case sensitive | Yes | SCD | |
| Sub Service code | Refers to the sub service under which the data is invoiced | Sub Service code | String, 50 characters | Yes | AdmFee, TravelCost, PerfFee etc |
|
(P) Dirty Value |
The Amount which is the basis of the fee |
AUM (Fee Base Amount) | Real, 14,4 | No | 1.765,00 |
|
Dirty Value PC |
The Amount which is the basis of the fee calculation - here: AUA |
AUA (Fee Base Amount) | Real, 14,4 | No | 1.500,00 |
|
(K) Currency |
The currency of the fee base amount (see above) | Fee Base Amount CCY |
ISO Currency code | No | EUR |
|
|
|||||
| |||||
|
Statement start date |
Date ddd.mm.yyyy |
Yes | 01.01.2026 | |
|
Fee date |
The end date of the period for which the fees are invoiced. (example 31.03.2026) . This will appear on the invoice ! | Statement end date |
Date dd.mm.yyyy |
Yes | 31.03.2026 |
| Label | UI control |
Manda- tory |
Editable | Data Type | Value set | Default | Data sample |
Data validation failure response
| Field label | Validation/ Business reules | Error message(s) | Data dependencies | Additional information |