Mapping VVG feed for Institutional clients (Fee distribution)
Purpose / Description
The Feed for the values held in VVG file will provide assets held per end of month. They are invoiced quarterly by summing up the monthly entitlements. The invoicing is based on the asset volumes held.
Use Case
|
As a system I can import the asset valuations from VVG's by product and portfolio. Based on these values I can calculate multiple fee types |
|
| Primary Actor(s) | Corporate accounting team, Institutional clients team |
| Stakeholders and Interest | MEAG Asset Management |
| Trigger | File saved on GMFT for pickup |
| Pre-condition(s) |
File has the agreed naming convention. |
| Post-condition(s) | Positions are imported, errors are thrown where applicable, Computation is kicked off |
| Main success scenario |
The file needs to be picked up from GMFT: During the import process the file is mapped for 'Fee Distribution' import The import will only load the Asset valuation (= total fund volume) from the file and ignore any fees or fee rates Where there are multiple lines refering to the same portfolio/product and date, only the latest line in the file is imported. If import is flagged as successful in the session monitor, no errors were found and all lines imported, If there are any issues, the session monitor will through errors and reject the full file or individual lines |
| Extensions | |
| Exception scenarios | |
| Special requirements | The reason why only the asset value is imported is that it is not possible to link fee amounts and fee rates calculated to a type of fee. Therefore the fee types and rate will be set up in the FSC software and the fee amounts are calculated there, This is based on the assumption that ALL fees are based on the asset valuation. |
| Open questions |
File Sample
Functional Requirements
| Business rules and functional requirements |
| The file name should be KVG_LiquidAssets_YYYYMMDD where the date relates to the date of the upload or extract of data. |
| Positions are loaded monthly with end of month data only. Should there be more dates then end of period in the file these will be imported and ignored when 'end of period' calculation is selected for the agreement. |
| The Date column within the file defines for which period the fees do apply. |
|
The file needs to be cloned so that 3 versions are available to calculate 3 different fee types ( e.g. Fees on AUM, Fees on AuA, Performance fees) each of the copies will need to align to one of these sub services. |
|
|
Field level specification
| Column headers | Description | Finsoft internal mapping | Data type | Mandatory | Sample data |
| F- Stichtag | 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 - Combine columns A_B_F | Transaction external reference | String 50 characters, case sensitive | Yes | 50101_HLECore1_20260630 |
| B-Fondsbezeichnung | Refers to which Assets/projects etc are being invoiced | Product external reference | String 50 characters, case sensitive | No | HLE Core 1 |
| A- interne Nr. | Refers to the portfolio were assets are located | Portfolio External reference | String 50 characters, case sensitive | Yes | 50101 |
| N/A | Refers to the data source. Here the fixed value IC_AA should be used. | Portfolio source system | String, 255 characters, case sensitive | Yes | IC_AA |
| N/A |
3 different fee types to be setup. (check with Michael/Judith what is required) outcome: Either clone or use same subservice in 3 different calc sets |
Sub Service code | String, 50 characters | Yes | AdmFee, PerfFee etc |
|
C-Fondsvermögen |
The Amount which is the basis of the fee calculation (e.g. Assets under management or Assets under Administration) | AUM | Real, 14,4 | Yes | 1.765,00 |
|
D-Whg |
The currency of the fee base amount (see above) | Amount CCY code | ISO Currency code | Yes | EUR |
| N/A | The amount of fees calculated (externally) | Fee Amount | Real, 14,4 | No | 98,00 |
|
N/A |
The currency of the fee amount | Fee Amount CCY code | ISO Currency code | No | USD |
|
N/A |
The fee rate applied, expressed in % | fee_rate | Real 20,9 | No | 3,5 |
|
N/A |
The start date of the period for which the fees are being invoiced ( example 01.01.2026) . This will appear on the invoice ! |
Statement start date |
Date ddd.mm.yyyy |
No | 01.01.2026 |
|
N/A |
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 |
No | 31.03.2026 |
Data validation failure response
| Field label | Validation/ Business reules | Error message(s) | Data dependencies | Additional information |