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
| 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 |
N/A |
Here the fixed value SCD should be used. | Portfolio source system | String, 255 characters, case sensitive | Yes | SCD |
| 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 QC |
The Amount which is the basis of the fee calculation- here : AUA | AUM (Fee Base Amount) | Real, 14,4 | No | 1.765,00 |
|
(Q) 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 |
|
Period From |
Default to first day of the month from column X |
Statement start date |
Date ddd.mm.yyyy |
Yes | 01.01.2026 |
|
(X) 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 |
Data validation failure response
| Problem | Visibility | Behaviour | Data dependencies | Additional information |
| Mandatory fields missing | Alert in session monitor | Line is not imported | ||
| Fields relate to data not existing (e.g. counter party, subservice etc) | Alert in session monitor | Line is not imported | Set up of sub service and counterparty in FSC prior import | |
| Wrong naming convention | Alert in session monitor | File is not imported | ||
| Negative AUM or AUA values | None | Lines are imported. | If these are not netted off the user can cap the invoice amount at Zero via constraints functionality | |
| File with same name is imported twice | None | Existing lines are overwritten if new data is different from old data. New lines will be added | Matching is done on product/portfolio/subservice and transaction external reference is identical |