Release Notes

August 2026

v1.6.1

Feature Updates

Adds DuckDB as a supported destination.

July 2026

v1.4.1

Feature Update

Adds the xero__using_invoice and xero__using_invoice_line_item variables (both default true) so you can run the package without invoice or invoice_line_item data. See Disabling and Enabling Models for details.

v1.5.0

Schema/Data Change

7 total changes • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
`xero__cash_general_ledger`	New model	N/A	New end model	Cash-basis general ledger; one row per cash journal line. Mirrors the structure of `xero__general_ledger` with an `accounting_basis` column set to `'cash'`. Enabled by default; disable by setting `xero__using_journal_cash: false`. See README for details.
`xero__general_ledger`	New column	N/A	`accounting_basis`	Always `'accrual'`. Mirrors the `accounting_basis` column in `xero__cash_general_ledger` to support unioning both models.
`xero__general_ledger`	Bug fix	`payment_id` excluded `ARPREPAYMENT`, `AROVERPAYMENT`	Now includes all prepayment and overpayment source types	Aligns AR prepayment/overpayment handling with AP counterparts already present. Possible breaking change: Rows with `ARPREPAYMENT` or `AROVERPAYMENT` source types previously had a `NULL` `payment_id` and will now be populated.
`stg_xero__journal_cash` `stg_xero__journal_cash_tmp`	New staging models	N/A		Cash-basis journal header data from the `journal_cash` source table. Enabled by default; disable by setting `xero__using_journal_cash: false`. See README for details.
`stg_xero__journal_cash_line` `stg_xero__journal_cash_line_tmp`	New staging models	N/A		Cash-basis journal line data from the `journal_cash_line` source table. Enabled by default; disable by setting `xero__using_journal_cash: false`. See README for details.
`stg_xero__journal_cash_line_has_tracking_category` `stg_xero__journal_cash_line_has_tracking_category_tmp`	New staging models	N/A		Tracking category associations for cash journal lines. Enabled when `xero__using_journal_cash_line_tracking_category` is `true`. See README for details.
`int_xero__journal_cash_line_pivoted_tracking_categories`	New intermediate model	N/A		Pivots tracking categories across cash journal lines. Enabled by default; disable by setting `xero__using_journal_cash_line_tracking_category`/`xero__using_tracking_categories` to `false`. See README for details.

v1.6.0

Schema/Data Change

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
`xero__balance_sheet_report` (possible breaking change)	Data Change	`Retained Earnings` vs. `Current Year Earnings` split anchored to the runtime `current_date`.	Split anchored to each report month's (`date_month`) fiscal year.	Historical months now reconcile with the native Xero balance sheet and are stable across runs.

June 2026

v1.4.0

Schema/Data Changes (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Data Model(s)	Change type	Old	New	Notes
All models	`source_relation` column (when using a single stripe schema)	Empty string (`''`)	`<database>.<schema>`

Under the Hood

Migrates the union_connections, apply_source_relation, and partition_by_source_relation macros to the dbt_fivetran_utils package.
Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.

January 2026

v1.2.0

Documentation

Updates README with standardized Fivetran formatting.

Under the Hood

In the quickstart.yml file:
- Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
- Adds supported_vars for Quickstart UI customization.

v1.3.0

Schema Changes

2 total changes • 1 possible breaking change

Data Model	Change type	Old	New	Notes
`xero__invoice_line_items`	New Column		`contact_id`	ID of the associated `CONTACT`.
All models	Single-connection `source_relation` value	Empty string (`''`)	`<xero_database>.<xero_schema>`

Feature Update

Introduces support for the newer, more flexible unioning framework. Previously, to run the package on multiple Xero sources at once, you could only use the union_schemas variable OR union_databases (mutually exclusive). While these setups are still supported for backwards compatibility, we recommend using xero_sources instead, which can be configured as such:

### dbt_project.yml

vars:
  xero:
    xero_sources:
      - database: connection_1_destination_name # Required
        schema: connection_1_schema_name # Required
        name: connection_1_source_name # Required only if following this step: https://github.com/fivetran/dbt_xero/blob/main/README.md#recommended-incorporate-unioned-sources-into-dag

      - database: connection_2_destination_name
        schema: connection_2_schema_name
        name: connection_2_source_name

See the README for more details.

December 2025

v1.1.1

Bug Fix

Resolves naming conflicts in models with dynamically pivoted tracking category columns. When a pivoted column name matches an existing column, the model automatically adds a pivoted_ prefix. Applies to:
- xero__general_ledger
- xero__invoice_line_items
- xero__profit_and_loss_report

Under the Hood

Renames the get_prefixed_tracking_category_columns macro to get_pivoted_tracking_category_columns and simplifies it to return only base column names, improving maintainability and readability.
Updates seed data to cover a wider range of tracking category scenarios.

November 2025

v1.0.1

Feature Update

Added optional xero__calendar_start_date variable to allow users to customize the start date for the calendar spine model. The variable defaults to 2019-01-01, maintaining backward compatibility with existing implementations.

Under the Hood

Updated vertical_general_ledger_tracking validation test to filter on tracking_option_name, which was renamed for option.

Documentation

Updated README to include instructions for configuring the new xero__calendar_start_date variable.