Release v0.9.0 dbt_quickbooks · fivetran/dbt_quickbooks

Bug Fixes

Added logic to the int_quickbooks__invoice_double_entry model to account for invoice discounts as they should be treated as contra revenue accounts that behavior differently from normal sale item detail invoice line items. (#85)
Updated the cash_beginning_period and cash_net_period values to coalesce to 0 in the quickbooks__cash_flow_statement in order to ensure every row has a value, especially the first row in the sequence since it will always be null. (#88)

Added department_id to the quickbooks__general_ledger and the upstream tables required for that change. (#63)
- Please note that this field was not added to the downstream quickbooks__general_ledger_by_period, quickbooks__balance_sheet, quickbooks__profit_and_loss, or quickbooks__cash_flow_statement models as this would require the grain of these models to be adjusted for the department_id. This would likely cause more confusion in the initial output. As such, the field was omitted in the aggregate models to ensure consistency of these models. If you wish this to be included, please open a Feature Request to let us know!

Included documentation within the DECISIONLOG centered around the behavior of how invoice discounts are handled within the int_quickbooks__invoice_double_entry model. (#85)

Leveraged the new detail_type field to ensure better accuracy when identifying invoice lines that should be accounted for in the general ledger calculations. (#85)
Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (#87)
Updated the pull request templates. (#87)

See the source package CHANGELOG for updates made to the staging layer in dbt_quickbooks_source v0.8.0.

Full Changelog: v0.8.1...v0.9.0