Solirion
SERVICES / DELIVERY & ENGAGEMENT

Institutional needs.
Concrete deliverables.

Research, data analysis and financial systems implementation, connected to the instruments and operating records your team uses. Derivatives are the center of our financial focus.

Request a scoped proposal See the work packages
WHAT SOLIRION DOES

Three connected workstreams.

A work package specifies the output, its inputs and the evidence used to review it. The proposal establishes what is included before work begins.

01
WORKFLOW DESIGN & PROVIDER COORDINATION

Institutional trading workflows

Connect a derivatives or spot requirement with account, order, execution-record and reconciliation processes. Start with the institution’s instruments, existing providers and reporting needs.

What the work package contains

  • An instrument and account-scope register: contract identifiers, expiry, currency, account references and responsible providers.
  • An order-lifecycle map covering instruction, approval, rejection, cancellation, fill and exception ownership.
  • A post-trade reporting specification linking fills, commissions, timestamps and unresolved differences to their source records.
  • A readiness checklist and test record for the agreed connections, access roles and recovery cases.
HOW COMPLETION IS REVIEWED

Reconcile an agreed sample of account, order and execution records; document outstanding exceptions and their owners.

Explore trading workflows Request a scoped proposal
02
READ-ONLY ANALYSIS & REPORTING

Data, risk analysis & research

Bring authorized positions and permitted market data into a consistent analytical record. Derivatives research connects exposure, contract terms, collateral references and hypothetical scenarios.

What the work package contains

  • A source and field dictionary showing units, timestamps, update frequency, permitted use and the source of record.
  • An exposure workbook or report organized by instrument, account, currency and the dimensions agreed in the brief.
  • A scenario pack with stated shocks, calculation method, assumptions, exclusions and an explanation of the results.
  • A data-quality and exception register, with review notes that identify which inputs or records need attention.
HOW COMPLETION IS REVIEWED

Trace sample calculations to their inputs, reproduce agreed scenarios and compare position totals with the designated records.

Explore data & risk Request a scoped proposal
03
FIXED-SCOPE INTEGRATION & HANDOVER

Financial systems implementation

Turn a defined financial workflow into specified interfaces, consistent fields, controlled access and an operating handover. Scope follows the systems and responsible teams involved.

What the work package contains

  • An interface specification and field-mapping document covering formats, identifiers, units, timestamps and error responses.
  • A permissions matrix and configuration record identifying source owners, user roles, environments and access approval.
  • An acceptance-test pack covering normal processing, missing data, interrupted connections, reconciliation and recovery.
  • An operating runbook, issue register and handover record with support responsibilities and an agreed change process.
HOW COMPLETION IS REVIEWED

Complete the agreed test cases, retain the evidence, resolve or record exceptions and obtain the designated owner’s sign-off.

Explore implementation Request a scoped proposal
SAMPLE WORK PRODUCTS

See the structure
of a deliverable.

Explore worked examples with synthetic inputs, calculation or review notes and downloadable tables. The samples show the format and review method for a work package.

ANALYSIS SAMPLE

Futures-overlay review

An illustrative exposure comparison, scenario table and method note for reviewing an asset position alongside a futures overlay.

Open the sample analysis
OPERATIONS SAMPLE

Reconciliation register

A sample record-matching and exception register showing source references, differences, review status and assigned follow-up.

Open the sample register
IMPLEMENTATION SAMPLE

Acceptance checklist

A sample test and handover checklist connecting expected behavior, evidence, exceptions and approval responsibility.

Open the sample checklist

Public market monitor

Explore source-attributed market observations and chart controls on the website.

Open the public market monitor
FROM BRIEF TO HANDOVER

A defined route to completion.

  1. 01

    Brief & eligibility

    Confirm the entity, business purpose, locations, decision owner, existing providers and required outputs.

  2. 02

    Scope & proposal

    Agree the deliverables, source permissions, dependencies, responsibilities, acceptance criteria and written commercial terms.

  3. 03

    Build & review

    Prepare the agreed analysis or configuration. Review sample records, assumptions, exceptions and test evidence with the designated team.

  4. 04

    Accept & hand over

    Record acceptance, transfer the outputs and runbook, and document support, renewal or change arrangements where required.

PROPOSED ENGAGEMENT TERMS

Price the scope.
Separate the costs.

Project work

Analysis and implementation are scoped through a written proposal. Deliverables, milestones, acceptance, payment timing and any change to scope are agreed together.

Institutional workspace subscription

Workspace subscriptions are quoted by modules, instrument and data coverage, user access and the agreed support level. The proposal identifies the term, review commitments and renewal arrangements.

Provider and data costs

Data licenses, cloud or integration dependencies, execution, clearing and safekeeping charges are identified separately from the Solirion work package. Their source and payment responsibility are stated.

What determines the quote?

The number and quality of sources, instrument coverage, interfaces, data permissions, review frequency, test cases and handover requirements. Commercial arrangements follow the signed scope. Any transaction-related service or charge requires its own confirmed role, provider arrangements and written terms.

CLIENT REQUIREMENTS

An institutional engagement
with named responsibilities.

The focus is professional institutions and corporate teams with a defined financial or operating need: trading firms, funds and asset managers, family-office teams, corporate treasury and institutional service providers.

Who we work with

  1. Entity and jurisdiction

    Provide the legal entity, principal business, operating locations and requested product or technical scope so eligibility can be assessed for the specific engagement.

  2. Authorized records and access

    Identify the data and systems involved, the source permissions and who can approve their use. Begin with a non-confidential brief; agree a secure exchange method before sharing sensitive records.

  3. Operating and procurement owners

    Name the business sponsor, technical owner and acceptance authority. Include procurement, security and documentation requirements that affect the work.

  4. Written scope and provider readiness

    Agree the responsibilities, deliverables and commercial terms. Where trading accounts or regulated services are involved, the responsible provider assesses account eligibility, financial requirements and product permissions.

ILLUSTRATIVE ENGAGEMENTS

What a useful engagement
can look like.

These examples show how a brief becomes a work package. Each example follows a brief, required inputs, outputs and a review point.

ILLUSTRATIVE ENGAGEMENT / 01

A fund team reviewing a futures overlay

The brief
Compare the exposure from an existing asset position with a proposed listed-futures overlay before the team decides how to proceed.
Inputs
Authorized holdings, contract specifications, reference prices, hedge assumptions and the institution’s selected scenarios.
Work package
An exposure table, contract comparison, scenario results and a method note showing how the positions were combined.
Review point
The team can trace the comparison to its inputs and distinguish price exposure from collateral and funding requirements.
Hedging & portfolio overlays
ILLUSTRATIVE ENGAGEMENT / 02

A trading firm reconciling several record sources

The brief
Explain differences between an internal trade file, provider execution records and the team’s end-of-day report.
Inputs
Sample files supplied under authorization, account references, timestamps, fee fields and source-system owners.
Work package
A field map, matching rules, reconciliation output and an exception register with a responsible owner for each unresolved category.
Review point
The agreed sample reconciles to the designated source of record, with remaining differences documented for follow-up.
Systems implementation
ILLUSTRATIVE ENGAGEMENT / 03

A treasury team organizing currency and settlement records

The brief
Bring expected cash flows, currency needs and settlement confirmations into a consistent operating report.
Inputs
An approved cash-flow schedule, bank or provider exports, operating currencies, payment dates and approval responsibilities.
Work package
A cash-flow and settlement map, a reporting specification, reference-data checks and an operating handover.
Review point
The team can follow a payment reference from instruction to the responsible provider’s confirmation and the internal reconciliation record.
Treasury & settlement
OPERATING RESPONSIBILITIES

A connected workflow.
Distinct provider roles.

Solirion work package

Research and analytical outputs, workflow specifications, field mapping, implementation tests, reporting and the agreed operating handover.

Execution and carrying

Order execution, account carrying, margin administration and clearing are assigned to the responsible execution venue, futures commission merchant or other contracted provider.

Safekeeping and source data

Assets remain with the responsible safekeeping or account provider. Market data and account records retain their source permissions, timestamps and designated system of record.

Research and technical delivery do not by themselves confer trading authority. A proposed connection identifies each provider’s role and required permissions before it becomes part of the engagement.

START WITH ONE REQUIREMENT

Bring a clear brief.

Tell us your institution, locations, instruments, current providers or systems, and the report or operating problem you need to resolve. We can use that brief to define the proposed work package and the questions to settle first.

Send your requirements sales@solirion.com