Platform · module 05 · Asset management infrastructure

Operations built for small contributions.

Systems grown over decades time their operations around overnight batches and clear exceptions by hand, and that eats the margin of a contract worth €100 a month. Here allowance operations, rebalancing and lifecycle control run automatically, on an API-first backend with no legacy.

End frame: a blue circle “your portfolio” surrounded by ten fund houses whose funds are used in Xaver portfolios, as of 10/2026; on the left the line that the right funds are chosen per asset class independently of the provider, combinable with the partner's own funds or fully open, and three points: fund selection per asset class by Xaver Asset Management, no product-provider lock-in for partners and customers, ETFs and actively managed funds in one portfolio.
Why this module exists

The expensive processes run automatically, not by hand.

01The partner's problem

Systems grown over decades time their operations around overnight batches and clear exceptions by hand. In subsidised provision that is exactly what eats the margin of a contract worth €100 a month, and it gets expensive faster as the book grows, not cheaper.

02The Xaver mechanism

Allowance operations, rebalancing and lifecycle control run automatically on a backend built in 2025/26, API-first: no overnight batch windows, no mainframe-bound interfaces, and no processes that are manual out of habit.

03The proof

Portfolios from 0.05% TER, complete AVD portfolios from 0.09% TER including active ETFs. (Source: Xaver product conditions, 2026.) Structure, ways to connect and the authentication concept are in the documentation.

API documentation
Benefits

What your operations get out of it.

What it looks like

What the customer gets to see of the backend.

A tour of the glidepath from the customer's view: the first year's subsidy breakdown by contribution, allowances and tax relief, the four equity-quota stages down to the payout phase, a retirement date moved from 67 to 70 that rebuilds the curve and the stages, the comparison against the alternatives, and how the final capital is composed.
Illustrative, shows the customer's view of the subsidy and the glidepath, not the investment backend
  1. 01Subsidy breakdown, year one
  2. 02Glidepath in four stages
  3. 03Retirement moved 67 → 70
  4. 04Against the alternatives
  5. 05What the final capital is made of
How operations run

From the product rule to the operating status

Schematic, not a product screen
  1. 01

    Product rules

    Investment concept, cost model, target-market definition and the lifecycle glidepath sit in the backend as a rule set, per product and per partner.

    • Target quotas per life stage
    • Cost and allowance logic
  2. 02

    Allocation

    The individual account's target allocation is derived from those rules, not from a distribution agreement in the background.

    • Open architecture, no lock-in
    • Building blocks per investment concept
  3. 03

    Lifecycle / rebalancing event

    A contribution, an allowance, a drift from the target quota or a step change in the glidepath triggers the run. It runs automatically, not as an overnight job everything else has to be timed around.

    • Allowance operations
    • Rebalancing
    • Lifecycle control
  4. 04

    Operating status

    The result and status of every run are available through the same open interfaces everything else is connected by.

    • API-first, not retrofitted
    • Structure in the documentation

A schematic of the processing chain, drawn from the module description and the API documentation. A recording of the investment backend will replace it as soon as one exists.

At a glance

An API-first investment backend with no legacy: allowance operations, rebalancing and lifecycle control run automatically. Portfolios from 0.05% TER, complete AVD portfolios from 0.09%.

What the module does
  • Portfolios from 0.05% TER, complete AVD portfolios from 0.09% TER incl. active ETFs
  • Built API-first, not fitted with an API afterwards
  • Allowance operations, rebalancing and lifecycle control automated
  • Xaver Asset Management GmbH, an investment firm supervised by BaFin (WpIG); Xaver Group certified to ISO 27001
Questions

What partners ask at this point

What do the TER figures refer to?+

To the TER, that is the ongoing cost of the investment building blocks in the portfolio: portfolios from 0.05% TER in the AVD standard, complete AVD portfolios from 0.09% including active ETFs. Platform and distribution terms are separate from that and depend on the cut of the partnership. (Source: Xaver product conditions, 2026)

Can I use the backend on its own?+

Yes. If you run distribution and portals yourself and need only the investment backend, that is a regular cut. The reverse works just as well: if you have a backend of your own, the other modules build on it.

How is it integrated?+

Through open interfaces, the architecture is built API-first, not fitted with an API afterwards. Structure, ways to connect and the authentication concept are described in the documentation; we provide the full reference as part of demo or integration access.

A slowly turning, desaturated globe with relief coastlines, a few marked nodes and fine connecting lines.

Walk through your use case with us.

  • We show you the modules that matter for your case
  • With Max Bachem, founder & CEO
  • No obligation, no preparation needed
Would you rather ask something first?