Kyriba to Holistics Integration

How Datrise loads Kyriba into Holistics

Datrise syncs Kyriba's bank accounts, cash positions, payments, transactions, forecasts, and bank statements into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Kyriba: Treasury, cash, and liquidity management.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Kyriba entities map to Holistics

Kyriba entity	Holistics object	Notes
bank accounts	`kyriba_bank_accounts`	id PK · custom fields → flattened columns for the modeling layer
cash positions	`kyriba_cash_positions`	id PK · linked to kyriba_bank_accounts
payments	`kyriba_payments`	id PK · linked to kyriba_bank_accounts
transactions	`kyriba_transactions`	id PK · linked to kyriba_bank_accounts

FAQ

How does Datrise handle Kyriba's custom fields in Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the Kyriba to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect Kyriba to Holistics the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.