BigQuery integration

Your orders already live in BigQuery.Actuals matches them to every payment.

Your orders sit in a BigQuery table. Your payments sit at several PSPs. Every month, someone joins the two by hand.

Category
Data warehouse
Connector
Maintained by Actuals
Output
Orders matched to every PSP
Your month-end close
  • ✕✓Orders in BigQuery, payments at the PSPOrders matched to PSP settlements every day
  • ✕✓A join that breaks on every new PSPOne matching logic across all PSPs
  • ✕✓Unmatched orders found at month endOpen items listed with their reason, daily
  • ✕✓Journals built from a query exportJournal entries generated, ready for your ERP
4 open issuesData warehouse · BigQuery

What you get

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

Live within weeks. No custom coding required.

Your table, every PSP

Four orders, three payment providers.

Actuals reads the orders where they already live and matches each one to the payment, settlement and bank line it belongs to. What does not match is listed the next morning, with its reason.

shop.ordersBigQuery
order_idamountmatched to
NL-284731€84.95
NL-284732€129.00
NL-284733€42.10
NL-284734€64.90

Four orders from your table. Three PSPs on the other side.

Illustrative rows.

How it runs

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

BigQueryPre-built connectorMaintained by Actuals

The connectionThe technical integration with BigQuery 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 implementationBigQuery 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 BigQuery.

Still a question?Talk to Peter Engel, founder of Actuals.Book a 30-minute call
What does Actuals do with our BigQuery 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: orders matched to PSP settlements every day; one matching logic across all PSPs; open items listed with their reason, daily; 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.