Guides and resources
Guides for the FinDatEx Tripartite Template (TPT), openfunds and FundsXML: what TPT and openfunds are, what changed in TPT V8, how each field maps to FundsXML 4, and how to automate the conversion.
Tripartite Template
- The TPT file format: Excel and CSV — How a Tripartite Template file is laid out: one row per position, column headers, CSV delimiters and encodings, number and date formats — and what the converter accepts.
- TPT V7 vs TPT V8 — The differences between Tripartite Template V7 and V8 field by field: new fields 150 and 151, securitisation codes e1–e3 in field 56, and how FundsXML 4 handles V8 data.
- What is the Tripartite Template (TPT)? — The FinDatEx Tripartite Template explained: why insurers need fund look-through data for Solvency II, what a TPT file contains and how it relates to FundsXML.
Conversion
- Automate TPT ⇄ FundsXML conversion — Convert Tripartite Template files to FundsXML 4 and back from scripts and pipelines: one HTTP POST with curl, PowerShell or Python, the result file plus a JSON report. No account, no API key.
- FundsXML 4 to TPT — How the converter builds a Tripartite Template (TPT V7/V8, Excel or CSV) from a FundsXML 4 document: one portfolio per share class, the order of sources, and the fields it derives.
- TPT to FundsXML 4 — How a Tripartite Template (TPT V7/V8) file becomes a FundsXML 4.2.11 document: the Solvency II TPT block, funds, share classes, positions and asset master data, and lossless custom attributes.
openfunds
- FundsXML 4 to openfunds — How a FundsXML 4 document becomes an openfunds file: one row per share class with OF-ID columns, a holdings sheet with OFPH columns, template fields from the EMT/EPT/EET/EFT blocks.
- openfunds to FundsXML 4 — How an openfunds file becomes a FundsXML 4.2.11 document: share class and fund static data, NAVs, OFPH holdings as positions, EMT/EPT/EET/EFT template blocks and lossless custom attributes.
- TPT ⇄ openfunds — How a Solvency II Tripartite Template (V7/V8) becomes an openfunds file with OFPH holdings, and back: the FundsXML step, the fields both know, and how every TPT field is kept.
- What is openfunds? — openfunds is an open standard for exchanging fund data: static data, prices, portfolio holdings and the FinDatEx templates EMT, EPT and EET, each field identified by an OF-ID such as OFST020000.
Reference
- Conversion messages explained — What the messages in a TPT ⇄ FundsXML conversion report mean — missing mandatory fields, values kept as custom attributes, V8 data in the V7 block, share classes without a portfolio — and what to do about them.
- Tripartite Template (TPT) fields — All 154 fields of the FinDatEx Tripartite Template V7 and V8 with Solvency II flag, format, allowed codes and their FundsXML 4 mapping.
- openfunds fields — All 1855 fields of openfunds 2.13.0 — static data, holdings, EMT, EPT, EET and more — with format, values and their FundsXML 4 mapping.