Skip to content

Release/1.9.0#213

Merged
fivetran-avinash merged 30 commits into
mainfrom
release/1.9.0
Jul 13, 2026
Merged

Release/1.9.0#213
fivetran-avinash merged 30 commits into
mainfrom
release/1.9.0

Conversation

@fivetran-avinash

@fivetran-avinash fivetran-avinash commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

PR Overview

Package version introduced in this PR:

  • 1.9.0

This PR addresses the following Issue/Feature(s):

  • QuickBooks tax lines completion

Summary of changes:

  • Merged into a final branch.

Submission Checklist

  • Alignment meeting with the reviewer (if needed)
    • Timeline and validation requirements discussed
  • Provide validation details:
    • Validation Steps: Check for unintentional effects (e.g., add/run consistency & integrity tests)
    • Testing Instructions: Confirm the change addresses the issue(s)
    • Focus Areas: Complex logic or queries that need extra attention
  • Merge any relevant open PRs into this PR

Changelog

  • Draft changelog for PR
  • Final changelog for release review

fivetran-avinash and others added 7 commits June 24, 2026 13:13
* Feature re: remaining tax lines

* Resolve outstanding issues

* Testing tax lines

* Schema

* Take out tax line variable, will bring in later

* Changelog, docs

* Generate dbt docs via GitHub Actions

* Fix compilation error

* table/table doc additions

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…ed data

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@fivetran-avinash
fivetran-avinash marked this pull request as ready for review July 7, 2026 19:23
@fivetran-avinash fivetran-avinash self-assigned this Jul 7, 2026
@fivetran-avinash fivetran-avinash added the docs:ready Triggers the docs generator workflow. label Jul 8, 2026

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few change requests and open questions before approval.

Comment thread integration_tests/tests/consistency/consistency_ap_ar_enhanced.sql Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md
Comment thread .quickstart/quickstart.yml Outdated
Comment thread integration_tests/ci/test_scenarios.yml Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed we're not looking up any tax account in this model. Whereas the other models leveraging the tax lines join in the tax payable account to use here.

This logic currently is using the same account_id as the normal double entry method. I don't presume that's what we want to use in the tax line case.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a miss from the first implementation. Updated to align with the other tax lines.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry these joins could cause fan out. This tax line section also seems to behave differently from the other tax line implementations (such as bill). Is this accurate?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed these joins.

fivetran-avinash and others added 3 commits July 8, 2026 09:20
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>

@fivetran-avinash fivetran-avinash left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-joemarkiewicz Changes applied. Redshift Buildkite is taking a long time (I'm still in the queue), but everything else passed, so this is good for re-review.

Comment thread integration_tests/tests/consistency/consistency_ap_ar_enhanced.sql Outdated
Comment thread integration_tests/tests/consistency/consistency_expenses_sales_enhanced.sql Outdated
Comment thread integration_tests/tests/consistency/consistency_expenses_sales_enhanced.sql Outdated
Comment thread integration_tests/ci/test_scenarios.yml Outdated
Comment thread CHANGELOG.md
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a miss from the first implementation. Updated to align with the other tax lines.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed these joins.

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few final change requests before approving

Comment thread integration_tests/ci/test_scenarios.yml
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes in this model need to be documented in the CHANGELOG

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Row added to schema/data changes.

Comment thread DECISIONLOG.md Outdated
Comment thread models/staging/stg_quickbooks__invoice_line.sql
Comment thread CHANGELOG.md Outdated
fivetran-avinash and others added 3 commits July 8, 2026 14:41
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>

@fivetran-avinash fivetran-avinash left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-joemarkiewicz changes applied, ready for final review

Comment thread CHANGELOG.md Outdated
Comment thread integration_tests/ci/test_scenarios.yml
Comment thread models/staging/stg_quickbooks__invoice_line.sql

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Row added to schema/data changes.

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with a few small requests

Comment thread CHANGELOG.md Outdated
| ------------- | ----------- | --- | --- | ----- |
| All tax line models | Variable configuration (opt-in) | Individual tax line variables sufficient | `quickbooks__tax_lines_enabled: true` also required | **Potential breaking change for dbt Core users** If you previously enabled any individual tax line variables, those models will now be disabled by default. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for configuration details. |
| `quickbooks__general_ledger` | Potential new rows | No tax lines | Tax lines now available (opt-in) | Tax line rows are disabled by default. Set `quickbooks__tax_lines_enabled: true` and enable individual tax line variables to post tax lines to the tax liability account. Tax lines are added only when you opt in. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for details. |
| `int_quickbooks__purchase_double_entry` | Data change | `paid_to_account_id` = purchase line expense account; `class_id` = expense class from purchase line | `paid_to_account_id` = tax liability account; `class_id` = `null` | **Potential breaking change** for users with `using_purchase_tax_line: true`. Tax lines now correctly post to the tax liability account. `class_id` is no longer populated for tax line rows. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only relevant if the individual tax line table is enabled and quickbooks__tax_lines_enabled: true. Let's add the clarification.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for calling that out, updated.

Comment thread CHANGELOG.md
[PR #213](https://github.com/fivetran/dbt_quickbooks/pull/213) includes the following updates:

## Schema/Data Change
**12 total changes • 3 possible breaking changes**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the sections below we use interchangeably "potential" and "possible" for breaking change callouts. Can you update either way to have consistent verbiage.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Standardized.

Co-authored-by: Avinash Kunnath <108772760+fivetran-avinash@users.noreply.github.com>
fivetran-avinash and others added 3 commits July 10, 2026 15:31
* feature/exchange-gain-loss

* fixes

* decisionlog

* yml

* Apply suggestion from @fivetran-catfritz

* ad some aliases

* convert to full

* Generate dbt docs via GitHub Actions

* update vars

* update docs

* Generate dbt docs via GitHub Actions

* Apply suggestions from code review

Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
Co-authored-by: fivetran-catfritz <111930712+fivetran-catfritz@users.noreply.github.com>

* fix seed ids

* fix seed dupes

* put the seeds back

* restore seeds again

* restore seeds again

* restore seeds again

* update col seed types

* Generate dbt docs via GitHub Actions

* merge conflicts

* Update CHANGELOG with tax line model changes

Updated the CHANGELOG to reflect changes in tax line models and potential breaking changes for users. Added details about enabling tax lines and configuration requirements.

* Update CHANGELOG.md

* Revise CHANGELOG for new features and updates

Updated the CHANGELOG to reflect new features and updates regarding tax lines and exchange gain/loss entries.

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
@fivetran-catfritz fivetran-catfritz added docs:ready Triggers the docs generator workflow. and removed docs:ready Triggers the docs generator workflow. labels Jul 11, 2026
@fivetran-avinash fivetran-avinash added docs:ready Triggers the docs generator workflow. and removed docs:ready Triggers the docs generator workflow. labels Jul 13, 2026

@fivetran-jamie fivetran-jamie left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved pending one item

Comment thread CHANGELOG.md Outdated
| All tax line models | Variable configuration (opt-in) | Individual tax line variables sufficient | `quickbooks__tax_lines_enabled: true` also required | **Possible breaking change for dbt Core users** If you previously enabled any individual tax line variables, those models will now be disabled by default. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for configuration details. |
| `quickbooks__general_ledger` | Potential new rows | No tax lines | Tax lines now available (opt-in) | Tax line rows are disabled by default. Set `quickbooks__tax_lines_enabled: true` and enable individual tax line variables to post tax lines to the tax liability account. Tax lines are added only when you opt in. See the [Enabling Tax Lines](https://github.com/fivetran/dbt_quickbooks/tree/main#enabling-tax-lines) section of the README for details. |
| `int_quickbooks__purchase_double_entry` | Data change | `paid_to_account_id` = purchase line expense account; `class_id` = expense class from purchase line | `paid_to_account_id` = tax liability account; `class_id` = `null` | **Possible breaking change** for users with `using_purchase_tax_line: true` and `quickbooks__tax_lines_enabled: true`. Tax lines now correctly post to the tax liability account. `class_id` is no longer populated for tax line rows. |
| `currency_id`, `exchange_rate`, `quantity`, `sales_item_quantity` in several header staging tables | Explicit type cast | Warehouse-native type | `string` / `float` | **Possible breaking change** for downstream consumers with type-sensitive logic built on staging models. |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

string / float is a lil confusing -- are some fields strings and others floats?

@fivetran-avinash fivetran-avinash Jul 13, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-jamie Yep. Updated to make it clearer.

@fivetran-avinash fivetran-avinash added docs:ready Triggers the docs generator workflow. and removed docs:ready Triggers the docs generator workflow. labels Jul 13, 2026
@fivetran-avinash
fivetran-avinash merged commit cf1867c into main Jul 13, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs:ready Triggers the docs generator workflow.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants