Snowflake integration

Your subscriptions live in Snowflake.The payments do not.

Your subscriptions sit in Snowflake. The renewals are paid at your PSPs, some of them only on the second try.

Category
Data warehouse
Connector
Maintained by Actuals
Output
Orders matched to every PSP
Your month-end close
  • ✕✓Subscriptions in Snowflake, cash at the PSPEvery renewal matched to the payment that settled it
  • ✕✓Failed and retried paymentsEach attempt linked to the same subscription
  • ✕✓Logic in a query only one person understandsMatching logic in a maintained platform
  • ✕✓Journals rebuilt from exportsJournal entries generated, ready for your ERP
4 open issuesData warehouse · Snowflake

What you get

What you get from your Snowflake data. Four things your finance team can close on.

Live within weeks. No custom coding required.

Renewals and retries

Three attempts. One renewal.

A renewal that fails and is retried shows up as several payments. Actuals links every attempt to the subscription it belongs to. The renewal counts once, and the failed attempts never look like missing revenue.

  1. pay_88121 Oct · card declined€29.00
  2. pay_89074 Oct · retry declined€29.00
  3. pay_90157 Oct · retry paid€29.00
sub_1042October renewal3 payments, 2 failed

Three payments, and no sign that they belong together.

Illustrative renewal.

How it runs

From scoping to cutover, next to the process you run today.

SnowflakePre-built connectorMaintained by Actuals

The connectionThe technical integration with Snowflake is pre-built. No custom coding is required. When an API changes, Actuals updates it.

The workWhat takes time is configuration: defining matching logic, reconciliation rules, journal structures, and reporting to fit the business exactly.

A typical implementation ranges from a few weeks for straightforward configurations to several months for complex multi-entity, multi-currency environments.

10–20%of finance team time during the projectBook a 30-minute call
The implementationSnowflake with Actuals
  1. ScopingWhich sources feed the ledger, and what the chart of accounts expects
    ✓
  2. Technical connectionPre-built connector, no custom coding
    ✓
  3. ConfigurationMatching logic, reconciliation rules and journal structures
    ✓
  4. Parallel running, then cutoverNext to your existing reconciliation, until you switch
    ✓

Questions

What finance teams ask about Snowflake.

Still a question?Talk to Peter Engel, founder of Actuals.Book a 30-minute call
What does Actuals do with our Snowflake data?

Actuals connects to any order database or transaction platform. No matter what database or back office software you’re using; no matter if it’s about orders, subscriptions, or fees; our team doesn’t stop until Actuals is connected seamlessly. Four things: every renewal matched to the payment that settled it; each attempt linked to the same subscription; matching logic in a maintained platform; journal entries generated, ready for your ERP.

Which data warehouses can Actuals read from?

Self-built order management systems, e-commerce platforms such as Magento and commercetools, and data warehouses such as BigQuery and Amazon Redshift.

Do we need developers?

The technical integrations are pre-built. No custom coding is required. What takes time is configuration: defining matching logic, reconciliation rules, journal structures, and reporting to fit the business exactly.

What happens when a source changes?

All integrations are pre-built and centrally maintained by Actuals. When an API changes, we update it. Your team does nothing.

How long does an implementation take?

A typical implementation ranges from a few weeks for straightforward configurations to several months for complex multi-entity, multi-currency environments. Finance team time required is approximately 10 to 20 percent during the project, focused on accounting decisions rather than technical work.