Custodian files, market data, curves and calendars arrive on their own. Reports leave the moment a valuation is complete, orders travel by FIX, and any table leaves as a file. Each transfer is checked on the way in and kept on record.
31 kinds of data from four kinds of source – each with its own way in, none of them typed by hand.
The bank’s transaction files are recognised by their headers and mapped to booking types. Nobody keys in a statement.
Prices, rates and reference data come from the provider you choose – per data kind, per asset type or per instrument.
What the risk engine prices with, and what tells a valuation which days count.
Master data, history and field values arrive in bulk and are checked row by row before anything is written.
Schedules and watched folders do the collecting. People see the outcome: a valuation that ran, or a to-do that says exactly what is missing.
A folder per kind of file. What lands there is stored, recognised and imported within moments – the bank’s file as well as your own.
FX reference rates, yield curves, dividends and benchmark series are fetched every day; exchange calendars are kept current. Valuations start at the time and in the time zone you set.
When something is missing, the valuation waits and a to-do names the gap. Close it – one click fetches the value – and the valuation resumes by itself.
One morning, as the log has it
An example. Valuation times are set per fund; curve and dividend fetches stay off until an administrator switches them on.
A new source does not get a new set of rules. Whatever arrives or leaves is treated the same way.
A file is identified by its headers, not by its name. Drop it into the folder and X-FOLIO knows what it is.
Order types, fee codes and venues are mapped to booking types. A code nobody has seen yet registers itself instead of stopping the import.
Duplicates are recognised by key and by checksum. Loading the same file again changes nothing.
The original file is stored before a single row is read, and stays available for download – even when the import fails.
Missing data becomes a to-do that holds the valuation. Doubtful data becomes a finding that asks for a second look.
Every provider call with its request, response and duration. Every delivery with its outcome. Every imported row with its message.
Several market data providers are connected. Which one serves which data is your decision – and what a run will cost is known before it starts.
Every call is logged with its request, its response and its duration. More in X-INFORM
Three ways out, all from the same valuation: documents to their recipients, orders to the bank, data to wherever you need it next.
Rendered when a valuation completes and sent at once – through your own mail system or to an SFTP folder.
FIX 4.4 with the session layer done properly: sequence numbers survive a restart, and a lost connection is retried.
Data leaves as openly as it arrived – over the full result, not only the visible page.
X-FOLIO runs on your servers and uses what is already there: your sign-on, your mail system, your file transfer.
Authentication through Keycloak: connect your identity provider and keep your password policy and your MFA.
Reports leave through your own mail system, with your subject, your text and your logo.
Reports are uploaded to your SFTP server. Bank files are picked up from folders you control.
FIX sessions to your bank are set up when the module is introduced, and started and stopped while the system runs.
The assistants talk to any OpenAI-compatible endpoint, including a model inside your own network. An outbound filter stops client data before it leaves.
Container deployment on your servers or in your cloud tenancy. Database and file store stay where you put them.
Modules are unlocked by a signed licence file. No licence server, no call-out at start-up.
Is your custodian, your data provider or your delivery channel not connected yet? This is how it gets there – built against your real files, under the same six rules as every other connection.
You send a few days of real files: transactions and advices exactly as the bank delivers them.
Order types, fee codes and venues are assigned to booking types. From then on the file is recognised by its headers.
The files are imported on a test system. Every row carries a message, and you compare the result with the bank’s statement.
Files land in the watched folder. Codes the bank adds later register themselves.
53 entries. Each one leads to the place where it is explained.
Custodian connections are built per bank, against the bank’s real files. The ones in place map more than a hundred order types and 266 fee codes. Tell us your custodian and we tell you where it stands today – and what it takes if it is not connected yet.
Several providers are connected, and which one serves which data is set by rule: per data kind, per asset type, down to the single instrument. If yours is among them, your credentials go in and it runs. If it is not, it is a new connection like any other.
Only for what you would expect: public reference rates, the providers you set a rule for, a report to its recipient, an order to your bank. Curve and dividend fetches stay off until an administrator switches them on, and nothing phones home – not even the licence.
The valuation waits. A to-do names the gap, and the valuation resumes by itself once it is closed. Data that looks wrong – a jump, a stale price – becomes a finding and never blocks.
Custodian mappings and FIX sessions are set up by XILDI when a module is introduced. Provider credentials, mail and SFTP settings are yours to enter, each with a connection test.
Today data leaves as files and documents: any table as CSV or XLSX, a fund as one JSON bundle, reports as PDF by e-mail or SFTP. A public API and a client portal are planned; this page lists only what is in the product.
Name your custodian, your data provider and where your reports have to go. We tell you what is connected today and what we would build.