Pillar 03 · Integration & Data

Straight-through to the systems you already run.

Validated instructions flow through straight-through orchestration, then out through either our native integration engine or your own integration layer — across a shared bus and an optional mapped data layer — writing into registry, CRM, comms and ECM. Data reads back, read-only, into the member portal. Custom fields can be added without a registry change project.

Orchestration

Two ways in — you choose the path

Straight-through orchestration takes the validated instruction and moves it downstream. From there, integration is a choice: run it natively within StreamlineID, or route through your existing enterprise integration layer. Both meet at the same shared bus.

Straight-Through Orchestration

Turns approved cases into downstream actions with no re-keying.

Data orchestration

Native Integration

Option A · native. Run integration inside StreamlineID — no separate platform to license or operate.

Native

Integration Layer

Option B · optional. Bring your own bus — e.g. WebMethods or another 3rd-party API layer.

WebMethodsOptional
The data path

One bus, an optional ETL layer, and a two-way flow

1

Integration Bus

Whichever option you pick, everything converges on one shared bus — a single, observable seam between StreamlineID and your systems of record.

2

Mapped ETL Data Layer Optional

Field mapping, transforms and validation — so StreamlineID's model and your registry's model reconcile without brittle point-to-point code.

3

Write out → systems of record

Clean writes into registry, CRM, comms and customer workflow via API.

4

Read back → member portal

Balances, statuses and documents pull back read-only and surface in the member portal — one source of truth, no shadow copy.

Systems of record

We write to what you already have

StreamlineID is deliberately not a system of record. It orchestrates into the registry, CRM, communications and content stores you already operate.

Registry

Bravura Garradin, GBST and equivalents — the book of record.

CRM

Salesforce, Dynamics, HubSpot — relationship and pipeline data.

Customer Comms

Letters and statements generation.

ECM / Doc Store

Digital document storage and retrieval.

Customer Workflow

Appian, Jira and BPM tools — tasks and cases.

Custom Fields

Add fields to your registry data without a registry change project — mapped and validated through the same integration layer.

Extensible without a core change project

When a journey needs a data point your registry doesn't have a field for, StreamlineID can capture and map it without waiting on a core registry change — so new requirements don't stall the rest of the stack.

Sovereignty by default

The entire StreamlineID platform is built, hosted and operated on GeoLocked Australian AWS, aligned to APRA expectations. Your data path stays in-country by design, not by exception.