Fund Data Converter
Free online converter for the FinDatEx Tripartite Template (Solvency II TPT V7 and V8). Upload a TPT file as Excel or CSV and get a schema-valid FundsXML 4.2.11 document: the Solvency II TPT block plus the regular fund, share class, position and asset structures. Or convert a FundsXML 4 document into a TPT file — one portfolio per share class, as XLSX or CSV.
The round trip is lossless: values FundsXML has no element for are kept as custom attributes. Every conversion comes with a report — XSD validation, missing mandatory fields, moved values. Files are processed in memory and not stored; no login, no cookies.
Reference: all TPT fields, the TPT ⇄ FundsXML field mapping, what the Tripartite Template is, TPT V7 vs V8, the conversion API and all guides.
Sister tools by the same author: Online XSD Viewer (browse the FundsXML schema), XML Online Viewer and Online OData Viewer, plus the desktop app FreeXmlToolkit.
What does the Fund Data Converter do?
It converts a FinDatEx Tripartite Template (TPT V7 or V8) file — Excel or CSV — into a FundsXML 4.2.11 document, and a FundsXML 4 document back into a TPT file. The FundsXML output contains the Solvency II TPT block and the regular fund, position and asset structures, and is validated against the FundsXML XSD.
Which TPT versions and file formats are supported?
TPT V7 and V8, as .xlsx or as CSV separated by semicolon, comma, pipe or tab. The version is taken from field
1000 or from the V8-only fields 150/151; you can also set it by hand. The header row is found automatically among
the first 50 rows, and columns may be named 12, 12_CIC_code_of_the_instrument or just the field name.
Is the conversion lossless?
Yes, for TPT → FundsXML → TPT. Values without an element in FundsXML 4.2.11 — such as the V8 fields 150/151 or
the codes e1/e2/e3 of field 56 — are kept as custom attributes named TPT_<field> and restored on the way back.
The report lists every value that was moved or could not be written.
Are my files stored?
No. Files are processed in memory and discarded after the response. There are no cookies and no third-party tracking. The anonymous usage statistics count conversions (formats, sizes, durations, message codes) and whether a result was downloaded or handed over to another site – never file content, file names or values from the file. Of the funds only the country prefix of the ISIN, the month of the valuation date and an irreversible keyed fingerprint (to count distinct funds) are kept, never the ISIN or the fund name.
Can I open the result in the XML viewer or check it with the FinDatEx validator?
Yes. Below the result, a generated FundsXML file can be opened in xml-viewer.online together with the FundsXML schema, so it is validated there right away, and a generated TPT file can be checked in findatex-validator.eu, which validates it against the TPT version it was written for. The file goes from your browser tab straight to the new tab; it is not stored on the way.
Can I automate the conversion?
Yes. One POST /api/convert request converts a file and returns the result plus a JSON report — no account, no
API key. See the API documentation for curl, PowerShell and Python examples.
Does it create one TPT per share class?
Yes. TPT is reported per share class: field 1 holds the share class ISIN. A FundsXML share class with its own portfolio uses it; otherwise the fund portfolio is repeated for each share class. See FundsXML to TPT for the details.