Uploading a folder

Send a whole morning's files at once: a folder (or a .zip of one) holding security master, positions, prices, FX and any other files, in any mix of Vestoris XML, CSV and Excel. Vestoris works out what each file is, loads them in the right order, and lets you apply or undo them together.

Three ways to send a folder

In the browser (Data › Loading center, or Data › Feeds): choose a folder, drop a folder on the page, or choose a .zip of the folder. On a phone or tablet, where a folder cannot be picked, zip it first.
Through the API: POST /api/v1/feeds/bundles?filename=sod_20261023.zip with the .zip as the body and an API token (Authorization: Bearer vst_…). Files of data sets the token may not load are left out. GET /api/v1/feeds/bundles/{id} gives the status of every file.
Through the drop box: put a .zip in inbound/, or several files at once. Files that match a feed's name are processed by that feed and count toward the start of day; the others wait on the review screen.

How each file is recognised #

In this order; the first rule that applies wins. Only the last one involves the AI, and its answer is a suggestion a person must confirm: a file Vestoris cannot recognise is never loaded silently.

XML namespace. A Vestoris XML file says what it is: <feed xmlns="urn:vestoris:feed:price:1.0"> is end-of-day prices. Its businessDate is the file's business date.
File name. The file-name patterns of your firm's feeds, e.g. a positions feed named SOD_POS_{YYYYMMDD}.csv recognises SOD_POS_20261023.csv as positions for 23 October 2026. The standard name is <FIRM>_<TYPE>_<YYYYMMDD>_<SEQ>.xml.
Columns seen before. When the header row is exactly the layout of a file you loaded before (its column mapping was remembered), the same data set is used.
AI suggestion. Otherwise the AI looks at the headers and a few rows and suggests a data set. The row is marked "Suggested by the AI" and nothing in the folder is checked until you confirm it, choose another data set, or exclude the file.

On the review screen you can change the data set of any file or exclude it. A file's business date comes from the XML header, the feed pattern, or a date in its name (20261023 or 2026-10-23); when the files are not all for the same business date, the review screen warns you.

Companions and ignored files #

<file>.done and <file>.sha256 belong to <file> in the same folder. A .sha256 that does not match refuses its file (M303).
Hidden and system files are ignored: names starting with a dot (.DS_Store), Thumbs.db, desktop.ini and anything under __MACOSX/. Files that are not data files (.pdf, .docx …) are listed as ignored.

Order, apply and undo #

"Check all files" stages the files in start-of-day order: calendars → security master → issuers and classifications → accounts → account groups → models, benchmarks and lists → positions, lots and cash → prices, FX and average volume → corporate actions. Each file becomes an ordinary batch with its checks and diff, shown on one screen.

"Apply all clean files" applies, in that order, every file with no rejected row. A file whose dependency in the folder has errors or is not applied waits (positions wait for the security master and accounts; prices, classifications and corporate actions for the security master; cash for accounts). A file with rejected rows can be applied on its own after review: its valid rows load. "Undo the folder" undoes the applied files newest first; if something now depends on one of them (for example a trade on loaded lots), the undo stops there and says why.

Limits #

Up to 200 files, 50 MB per file and 250 MB in all. In the browser each file is sent in pieces of 1 MB, so the server's upload limits do not cut a folder short. Large folders are checked in the background, one file at a time, with progress on the review screen. A .zip is checked before anything is taken from it: no paths outside the folder, no links, no zip bombs, and a .zip inside the .zip is not opened.

What is recorded #

The folder and each of its batches are in the event log (who, when, each file's SHA-256 and counts). The files are kept outside the web site until they are checked; each batch then keeps its own encrypted copy for its retention period.