The main focus of this package is to provide users with insights into their Sage Intacct data that can be used for financial reporting and analysis. This is achieved by the following:
- Creating the general ledger, balance sheet, and profile & loss statement on a month by month grain
- Creating an enhanced AR and AP model
Please be aware that the dbt_sage_intacct and dbt_sage_intacct_source packages were developed with single-currency company data. As such, the package models will not reflect accurate totals if your account has multi-currency enabled. If multi-currency functionality is desired, we welcome discussion to support this in a future version.
This package contains transformation models, designed to work simultaneously with our Sage Intacct source package. A dependency on the source package is declared in this package’s
packages.yml file, so it will automatically download when you run
dbt deps. The primary outputs of this package are described below. Intermediate models are used to create these output models.
|sage_intacct__general_ledger||Table containing all transactions with offsetting debit and credit entries for each account, category, and classification.|
|sage_intacct__general_ledger_by_period||Table containing the beginning balance, ending balance, and net change of the dollar amount for each month and for each account, category, and classification. This table can be used to generate different financial statements for your business based on your customer accounting period. Examples include the balance sheet and income statement models.|
|sage_intacct__balance_sheet||Total amounts by period per account, category, and classification for all balance sheet transactions.|
|sage_intacct__profit_and_loss||Total amounts by period per account, category, and classification for all profit & loss transactions.|
|sage_intacct__ap_ar_enhanced||All transactions for each bill or invoice with their associated accounting period and due dates. Includes additional detail regarding the customer, location, department, vendor, and account. Lastly, contains fields like the line number and total number of items in the overall bill or invoice.|
Include in your
packages: - package: fivetran/sage_intacct version: [">=0.1.0", "<0.2.0"]
By default, this package looks for your Sage Intacct data in the
sage intacct schema of your target database.
If this is not where your Sage Intacct data is, add the below configuration to your
... config-version: 2 vars: sage_intacct_database: your_database_name sage_intacct_schema: your_schema_name
This package allows users to add additional columns to the
Columns passed through must be present in the upstream source tables. See below for an example of how the passthrough columns should be configured within your
... vars: sage_account_pass_through_columns: ['new_custom_field', 'custom_field_2'] sage_gl_pass_through_columns: ['custom_field_3', 'custom_field_4']
Custom Account Classificationlink
Accounts roll up into different accounting classes based on their category. The categories are brought in from the
gl_account table. We created a variable for each accounting class (
Expense) that can be modified to include different categories based on your business. You can modify the variables within your root
dbt_project.yml file. The default values for the respective classes are as follows:
... vars: sage_intacct_category_asset: ('Inventory','Fixed Assets','Other Current Assets','Cash and Cash Equivalents','Intercompany Receivable','Accounts Receivable','Deposits and Prepayments','Goodwill','Intangible Assets','Short-Term Investments','Inventory','Accumulated Depreciation','Other Assets','Unrealized Currency Gain/Loss','Patents','Investment in Subsidiary','Escrows and Reserves','Long Term Investments') sage_intacct_category_equity: ('Partners Equity','Retained Earnings','Dividend Paid') sage_intacct_category_expense: ('Advertising and Promotion Expense','Other Operating Expense','Cost of Sales Revenue', 'Professional Services Expense','Cost of Services Revenue','Payroll Expense','Payroll Taxes','Travel Expense','Cost of Goods Sold','Other Expenses','Compensation Expense','Federal Tax','Depreciation Expense') sage_intacct_category_liability: ('Accounts Payable','Other Current Liabilities','Accrued Liabilities','Note Payable - Current','Deferred Taxes Liabilities - Long Term','Note Payable - Long Term','Other Liabilities','Deferred Revenue - Current') sage_intacct_category_revenue: ('Revenue','Revenue - Sales','Dividend Income','Revenue - Other','Other Income','Revenue - Services','Revenue - Products')
Disabling and Enabling Modelslink
When setting up your Sage Intacct (Sage) connection in Fivetran, it is possible that not every table this package expects will be synced. This can occur because you either don’t use that functionality in Sage or have actively decided to not sync some tables. In order to disable the relevant functionality in the package, you will need to add the relevant variables.
By default, all variables are assumed to be
true. You only need to add variables for the tables you would like to disable:
config-version: 2 vars: sage_intacct__using_invoices: false # default is true sage_intacct__using_bills: false # default is true
Changing the Build Schemalink
By default this package will build the Sage Intacct staging models within a schema titled (<target_schema> +
_stg_sage_intacct) and the Sage Intacct final models with a schema titled (<target_schema> +
_sage_intacct) in your target database. If this is not where you would like your modeled Sage Intacct data to be written to, add the following configuration to your
... models: sage_intacct: +schema: my_new_schema_name # leave blank for just the target_schema sage_intacct_source: +schema: my_new_schema_name # leave blank for just the target_schema
Don’t see a model or specific metric you would have liked to be included? Notice any bugs when installing and running the package? If so, we highly encourage and welcome contributions to this package!
Please create issues or open PRs against
main. Check out this post on the best workflow for contributing to a package.
This package has been tested on Spark, BigQuery, Snowflake, Redshift, Databricks, and Postgres.
Databricks Dispatch Configurationlink
v0.20.0 introduced a new project-level dispatch configuration that enables an “override” setting for all dispatched macros. If you are using a Databricks destination with this package you will need to add the below (or a variation of the below) dispatch configuration within your
dbt_project.yml. This is required in order for the package to accurately search for macros within the
dbt-labs/spark_utils then the
dbt-labs/dbt_utils packages respectively.
dispatch: - macro_namespace: dbt_utils search_order: ['spark_utils', 'dbt_utils']
- Provide feedback on our existing dbt packages or what you’d like to see next
- Have questions or feedback, or need help? Book a time during our office hours here or shoot us an email at firstname.lastname@example.org.
- Find all of Fivetran’s pre-built dbt packages in our dbt hub
- Learn how to orchestrate your models with Fivetran Transformations for dbt Core™
- Learn more about Fivetran overall in our docs
- Check out Fivetran’s blog
- Learn more about dbt in the dbt docs
- Check out Discourse for commonly asked questions and answers
- Join the chat on Slack for live discussions and support
- Find dbt events near you
- Check out the dbt blog for the latest news on dbt’s development and best practices