The Feasibility of Using an Automated Net Asset Value Validation Tool in an International Investment Bank
Bibliographic record
Abstract
Fund administration is a relatively new service that some banks and back office offer Investment Company’s. This service was regarded as “boutique” in some countries as it was not a necessity hence not enforced by law to have independent calculation and verification of a fund price. However, this sector of business was and has been a major factor in the economic boom for many countries worldwide. In general most companies have many human resources tagged to this service. This is mainly due to the high volume of manual work that needs to be carried out to validate a Net Asset Value. If the Net Asset Value is calculated incorrectly and hence not validated correctly then there is huge repercussions for the company that calculated the Net Asset Value (monetary, reputation, losing a client). With the turn in the current climate the operational requirements that was once affordable has snowballed out of control, this is why invest company’s are finding ways to reduce costs and hence use less labour intensive methods or relocate these specific jobs to lower cost countries such as Eastern Europe and India. However, this is not without its own set of problems, some being that most companies and in our case, the company always employs a distributed service requirement. Within the scope of a collaboration project which focuses on a Net Asset Value automated validation solution to replace a labour intensive manual approach. In this paper, we research the feasibility of using such a tool in a funds business of an international investment bank where parts of this process are based in Asia and Europe. Our approach is based on surveying people that are currently working in the Net Asset Value validation process, and in turn analyse the results attained. Throughout this process, we must not only focus on the efficient method of applying a Net Asset Value validation automated solution but we must also provide an overview of the important factors in building a solutions to be used in a fund administration environment.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.007 | 0.018 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.008 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".