Data
Every morning's files, in order, checked, and undoable.
Load the security master, accounts, holdings, prices, FX and corporate actions from files or standard XML feeds. Operations sees the start-of-day chain on one screen: what arrived, what is late, what is held, and what the data is as of. AI suggests mappings and explains rejections; deterministic rules decide what loads.
A loading center with a diff
- Upload CSV, Excel or Vestoris XML; columns are matched by name and the AI suggests the rest, remembered per file layout.
- Check digits (ISIN, CUSIP, SEDOL, FIGI), references, duplicates and dates are verified; every rejected row has a code and an error file.
- Before anything changes you see what is new, changed, unchanged and rejected. An applied batch can be undone as a whole, unless later trades depend on it (and you are told which).
History you can ask
- Every record is kept with the dates it was valid: ask what a security or position looked like on any day.
- Each batch is in the hash-chained event log with who, when, the file's SHA-256 and the counts; the original file is stored encrypted for its retention period.
- Splits adjust positions and lots deterministically; dividends credit (simulated) cash; both undo cleanly.
Feeds and the start-of-day chain
- Calendars, security master, accounts, holdings, prices and FX, corporate actions, data quality, pre-open compliance: in that order, each step waiting for the one before.
- Late and missed files, held files and failed runs raise alerts and email Operations; a banner on every page says what the data is as of until the day is complete.
- Operations can override the start of day with a reason, which is logged.
Managed file transfer and HTTPS
- A drop box per firm over explicit FTPS (port 21), outside the web site and never reachable over the web.
- HTTPS push with scoped, revocable, rate-limited API tokens shown once; HTTPS pull only from an allow-list, never from private addresses.
- A built-in scheduler runs on New York time with business calendars, retries and run history.
User-defined fields
- Ten fields of your own on every reference table - securities, issuers, accounts, groups, brokers, models, benchmarks, desks and list entries - typed (text, number, date, yes/no, list) and validated.
- They load from files and XML feeds, travel through the API, appear as blotter columns and filters, and can be used in compliance and workflow rules. Type changes that would lose data are refused; every change is versioned in the event log.
Standard XML formats
- One versioned namespace and published XSD per data set; full and delta files; streaming for 50,000+ records; gzip and zip.
- A public Data Feed Reference generated from the schemas, with every element, error code and an annotated sample, and a validator that stores nothing.
AI
Where the AI helps
- Suggests the column mapping for a new file layout; a person confirms it.
- Explains rejected rows and failed or held feed runs in plain English, from the codes.
- Writes the start-of-day and data quality briefs, and the story of a price jump.
Deterministic
What decides
- What loads is decided by validation code: schemas, check digits, references, thresholds.
- Nothing is applied from a held file until an Operations user reviews it.
- Paper trading only: loaded prices and holdings feed the simulation and compliance checks; Vestoris connects to no broker.
See it with your own eyes, in ten minutes.
Open a private sandbox firm with sample accounts, rules and orders. No sign-up, no email. Switch roles and follow the guided tour.