One engine, standards packs on top

How a message flows through Strovia

Every message passes through the same visible steps, and you can see each one:

Received → Read → Mapped → Schema validation → Strict item validation → Platform controls → Chunked (if needed) → Approved → Sent → Feedback received → Completed

Fast jobs finish instantly and show a compact trail. Long jobs, and messages waiting for your counterparty’s feedback, show a live tracker. If anything fails, Strovia opens at the failed step, tells you why and what to do next.

The engine

• Formats: CSV, Excel, JSON and XML, in and out.
• Declarative mappings: links and rules are configuration, not code. Every mapping is versioned and comparable.
• Transformation functions: direct copy, constants, lookups, conditions, date and type conversion, arithmetic, grouping flat rows into hierarchies (for example scheme → cohort → payment) and flattening hierarchies into rows.
• Exact decimals: amounts are never processed as floating-point numbers. Nothing is silently rounded or truncated.
• Built for volume: streaming processing for large files, including messages with a million or more projected payment lines.
• Deterministic: the same input, mapping and standards version always give the same output. No AI in the data path.

Standards packs

A pack bundles everything needed to work with a standard:

• the official schemas, code lists and validation rules, for every supported release side by side;
• a data dictionary generated from the schemas, with rules held per message and position;
• ready-made templates, sample data and test fixtures;
• field help and plain-language error explanations;
• the message cycles the standard implies.

Packs work offline: no runtime dependency on external websites.

Available: VB-PUO (Releases 2026 and 2027). See the VB-PUO pack

Planned: further financial-messaging standards, prioritised with customers.

Delivery to your own systems

The SIVI exchange may carry messages of 10 MB or more, while core systems at large institutions sometimes accept only about 2 MB. Strovia bridges that gap. For each internal system you set a maximum piece size, and Strovia:

• splits incoming messages on business boundaries (scheme, cohort or portfolio), never mid-record;
• labels every piece (piece n of N) and adds control totals and a manifest;
• retries a failed piece on its own, without resending the rest;
• marks the delivery complete only when every piece is acknowledged and the totals reconcile.

Your own SIVI gateway, not a middleman

Under the VB-PUO standard, you and your counterparty exchange messages directly, through the standard’s REST API. Strovia doesn’t sit between you. It becomes your SIVI system: it sends with your own certificates and credentials, and receives on endpoints registered in your name, ideally under your own domain. Your counterparty sees you, not us.

Excel, CSV and XML stay on your side. Strovia turns them into valid SIVI messages before they leave, and turns incoming messages into the formats your systems use.

How Strovia connects

To your counterparties: through the official SIVI API, with mutual TLS, OAuth and, where agreed, signed messages. For each counterparty, Strovia prepares a registration pack with everything they need to set you up: endpoints, certificates, IP addresses and test details.

To your own systems, in the way that suits you:

• download results in the app, or fetch them through the API;
• a small connector agent in your network picks up your extracts from a folder and drops results into another. It only connects outwards, so you don’t open any inbound firewall ports;
• run Strovia in your own environment, where it reads and writes your folders directly [FOUNDER TO CONFIRM TIMING];
• SFTP, cloud storage and database connections [FOUNDER TO CONFIRM TIMING: planned for release 2].

Every connection is set up once, approved by a second person, and every transfer is recorded in the audit trail.

Kept current

When a standards body publishes a new release, Strovia detects it, compares it with the previous release and shows you which of your mappings are affected. Often this happens months before the new release takes effect. An expert reviews every update before it is published, and your production mappings never change without your own approval.

Cycle monitoring

Messages in a pension chain arrive in a sequence with deadlines. Strovia models each scheme’s message cycle (SPR, FPR accumulation, FPR with a collective payout phase) and flags any step that is missing, late, out of order, rejected or unexpected. It also explains which data is likely to be missing as a result.

Governance

• Validate & Test before anything goes live, with evidence tied to the exact versions tested.
• Independent approval (maker-checker); authors cannot approve their own changes.
• Any change invalidates earlier test evidence.
• Append-only audit trail and exportable evidence packs.

Delivery options

• Self-serve converter for occasional use.
• Operational platform, hosted in the EU.
• Dedicated environment for regulated organisations.
• Managed service: we run your SIVI exchange for you.

Book a demo