Operator
Search…
Transactions Overview
Transactions is a data consolidation feature that collects every type of transaction from multiple sources and unifies them under one data model.
Transactions form the core atomic unit of finance operations, planning, and reporting.
There has been an explosion of software tools that capture or create key elements of transactions, from expense management to billing applications. As a result, key details about transactions are split across countless systems and can be difficult to consolidate.
With Transactions, you can unify and link all the data relevant to individual transaction in one platform, improving operational efficiency and lower switching costs for any tools.

Designing one transaction model

Similar to creating destinations, creating a model of transactions means defining a set of required and optional fields. Under Operator's default transaction model, a transaction consists of these required fields:
    ID
    Date
    Amount
    Source
    Source type
Not required, but highly recommended fields:
    Description
    Transaction type
    Payer
    Recipient
    Debit account
    Debit amount
    Credit account
    Credit amount
Extra fields that can be attached to a transaction are:
    Contract number
    Invoice number
    Customer ID
    Purchase order
    Receipt
    and 100's more

Creating the transaction model

To create the transaction model, there must first be a query that defines the data sources and applies the necessary transformations.
We can help modify this template query for your company if you need to apply custom logic or tweak the sources that need to be included.
Once you apply the query, you will see that the output transactions are of the defined model. All of the required and optional fields will be shown in the columns.

Syncing transactions to a data warehouse

Now that your query can create one unified model of a transaction, you can send these transactions to a table in a data warehouse destination.
You can choose any of your connected data warehouses as a destination for your transaction data, upon which that warehouse can now serve as a source that you can select data from.
For instance, once your unified transaction table is created, you can add relevant fields like customer name sourced from a tool like Stripe and add that a

Using your new transactions data

With a unified data model that holds all your transactions, the possibilities are unlimited.
Instead of integrating with each tool and working with their API to get specific data related to your transaction, you can simply work with all of your transactions using a single select, allowing you to build detailed reports, operationalize new systems, and more.
Operator Transactions and the associated API are in beta. If you'd like to learn more about using Transactions and the Transactions API feature in production, please reach out to us at [email protected]
Last modified 7mo ago