Snowflake integration

Bring curated Snowflake data into the same business context as your ERP, CRM and operational systems. Connect warehouse measures to the customers, invoices, suppliers and assets they describe.

How it connects
From warehouse data to business decisions
Snowflake
Approved tables and views

Curated financial, customer and operational data.

Uplyst
A shared business model

Source records linked to customers, contracts, invoices and suppliers.

Business teams
Decisions with context

Receivables, supplier performance and customer exposure across systems.

Connect Snowflake to Uplyst

Snowflake tables and views can supply financial, customer and operational data to Uplyst through controlled SQL access. Selected records are mapped to shared business entities, so a warehouse measure can be understood alongside the transactions and activity held in other systems.

Snowflake provides SQL clients and a REST SQL API for running statements and retrieving results. The connection uses the approved database, schema, warehouse and role for the organisation's data. Query scope and refresh frequency follow the needs of the business process.

Controlled access to warehouse data

Snowflake roles restrict access to the tables, views and compute resources used by the integration. A dedicated workload identity keeps automated access separate from individual analyst accounts.

Authentication follows the methods supported by the selected Snowflake client. Key pair authentication supports key rotation, while account network policies can restrict where SQL API requests originate.

Connect measures to business entities

Invoice numbers, customer identifiers and supplier codes connect warehouse records to their operational sources. Uplyst's business model relates those source identities across systems, with currency, reporting period and calculation meaning attached to each measure.

The Snowflake account and table or view identify where a result came from. Source timestamps show how current it is, while exact decimal values preserve financial amounts.

Snowflake dataBusiness context
Invoice and source ERP identifiersInvoice identity across financial systems
Amount and currencyReceivables and financial exposure
Customer or supplier keyRelationships to CRM and procurement records
View, query and source timestampCalculation origin and freshness

Invoice balance

Warehouse result and business identity

Snowflake record

Source view
FINANCE.CURATED.INVOICE_BALANCES
Source identity
ERP-UK / UK01 / INV-88
Accounting period
September 2026
Invoice principal
36,000.00 GBP

Uplyst business context

Customer account

Northfield ComponentsAC-14
Invoice
INV-88
Order
ORD-42
Open receivable
14,000.00 GBP
Last query completed
The ERP source, company and invoice key connect a warehouse balance to the right customer. Query completion is separate from the accounting period.

Keep business context current

Scheduled queries suit recurring reporting and reconciliation. Where incremental processing is required, Snowflake Streams can expose row changes and change metadata for supported source objects. A stream tracks an offset in source history; its retention limits affect how far processing can resume after an interruption.

The selected refresh method accounts for updates, deletions and late corrections. Query duration and warehouse consumption help determine an appropriate cadence alongside existing reporting workloads.

Finance and supplier decisions

A receivables team can relate warehouse balances to customer relationships, open disputes and recent payment activity. Procurement can connect historical spend to current supplier commitments and delivery performance.

Each use case combines the warehouse's analytical depth with operational context. Source references and refresh times help teams understand the information behind a decision.

Connect your systems
with Uplyst.

Talk with our team about the systems you use and the decisions they need to support.

Discuss an integration