Release Noteslink
July 2023link
Our Xero connector now uses webhooks to capture all updates for the INVOICE
table. Previously, we did not capture updates for some columns, such as the sent_to_contact
column of the INVOICE
table. We have added a new toggle, Use Webhook, to the connector setup form. The toggle provides you the option to use a webhook for your connector. We have rolled out this feature for all new and existing Xero connectors. For more information, see our setup instructions.
March 2023link
We have changed the new connector creation process for Xero connectors. We now use a different authentication method for Xero connectors created after March 24, 2023. We use Client ID and Client Secret for authentication. For more information, see our Xero Setup Guide.
We will continue to support the existing Xero connectors. You can also opt to migrate your existing connector to the new authentication method.
March 2022link
We have added a new column, add_to_watch_list
, to the ACCOUNT
table.
April 2021link
We now support the Employees
, Leave Applications
and Timesheets
endpoints of the Xero-Payroll API. To use these endpoints, you must re-authorize your connector in your Fivetran dashboard. On the Connector Details page, go to the Setup tab, click Edit connection details, and then click Re-authorize connection. See Xero's API documentation to learn more about the Employees, Leave Applications, and Timesheets endpoints.
We have released pre-built, dbt Core-compatible data models for Xero. Find the models in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation*.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
We have added three new tables to support Xero's Payroll API:
AUS_PAYROLL_EMPLOYEE
AUS_PAYROLL_LEAVE_APPLICATION
AUS_PAYROLL_TIMESHEET
See Xero's API documentation to learn more about Employees, Leave Applications, and Timesheets.
We have added three new tables to support Xero's Assets API:
ASSET
ASSET_TYPE
SETTINGS
See Xero's API documentation to learn more about Assets, Asset Types, and Settings.
We have added the following new columns to the BANK_TRANSACTION
and PAYMENT
tables:
batch_payment_id
batch_payment_date
batch_payment_is_reconciled
batch_payment_status
batch_payment_total_amount
batch_payment_type
batch_payment_updated_date_utc
December 2020link
We now support values with six decimal places in the following columns of the tables below:
amount
column of theALLOCATION
tablesub_total
,total_tax
,total
, andcurrency_rate
columns of theBANK_TRANSACTION
tableunit_amount
,tax_amount
, andline_amount
columns of theBANK_TRANSACTION_LINE_ITEM
tableamount
,unit_amount
,tax_amount
,line_amount
, andcurrency_rate
columns of theBANK_TRANSFER
tableoutstanding
andoverdue
columns of theCONTACT
tablecurrency_rate
,remaining_credit
,applied_amount
,sub_total
,total_tax
, andtotal
columns of theCREDIT_NOTE
tableamount_due
,amount_paid
, andtotal
columns of theEXPENSE_CLAIM
tablecurrency_rate
,amount_due
,amount_paid
,amount_credited
,cis_deduction
,sub_total
,total_tax
, andtotal
columns of theINVOICE
tabletotal_cost_pool
,purchase_details_unit_price
, andsales_details_unit_price
columns of theITEM
tablenet_amount
,gross_amount
, andtax_amount
columns of theJOURNAL_LINE
tabletax_amount
andline_amount
columns of theMANUAL_JOURNAL_LINE
tablesub_total
,total_tax
,total
,applied_amount
,currency_rate
, andremaining_credit
columns of theOVERPAYMENT
tablebank_ammount
,amount
, andcurrency_rate
columns of thePAYMENT
tablesub_total
,total_tax
,total
,applied_amount
,currency_rate
, andremaining_credit
columns of thePREPAYMENT
tableunit_amount
,line_amount
,tax_amount
, anddiscount_rate
columns of thePURCHASE_ORDER_LINE_ITEM
tablesub_total
,total_tax
, andtotal
columns of theRECEIPT
tableunit_amount
,line_amount
,tax_amount
, anddiscount_rate
columns of theRECEIPT_LINE_ITEM
tablesub_total
,total_tax
,total_discount
, andtotal
columns of theREPEATING_INVOICE
tablediscount_rate
column of theREPEATING_INVOICE_LINE_ITEM
tabledisplay_tax_rate
andeffective_rate
columns of theTAX_RATE
tablerate
column of theTAX_RATE_COMPONENET
table
Previously, we used to round the column values to two decimal places.
September 2020link
We have added a new column, manual_journal_id
, to the MANUAL_JOURNAL_LINE_HAS_TRACKING_CATEGORY
table.
August 2020link
We have added a new column, contact_id
, to the INVOICE_LINKED_TRANSACTION
table.
We have removed the _fivetran_deleted
column from the CREDIT_NOTE
table.
May 2020link
When setting up your connector, you can now select the organizations you'd like to sync.
We have fixed an issue where the connector setup test was failing because of timeout errors.
We have added a new column, _fivetran_deleted
, to the SUBSCRIPTION
table.
April 2020link
We have added a new field, item_code
, to the PURCHASE_ORDER_LINE_ITEM
table.
We have added support to authenticate the connector using OAuth 2.0. We will be migrating the active users to the new standard of authentication.
You can now configure your Xero connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
We have added a new primary key column, index
, to the ALLOCATION
table.
February 2020link
We have updated the data type of the inventory_asset_account_code
column in the ITEM
table from Integer to String to match the type in the Xero API.
We now sync archived records from the TRACKING_CATEGORY
table.
January 2020link
We have added a new column, option
, to the following tables:
BANK_TRANSACTION_LINE_ITEM_HAS_TRACKING_CATEGORY
MANUAL_JOURNAL_LINE_ITEM_HAS_TRACKING_CATEGORY
INVOICE_LINE_ITEM_HAS_TRACKING_CATEGORY
OVERPAYMENT_LINE_ITEM_HAS_TRACKING_CATEGORY
PREPAYMENT_LINE_ITEM_HAS_TRACKING_CATEGORY
REPEATING_INVOICE_LINE_ITEM_HAS_TRACKING_CATEGORY
CREDIT_NOTE_LINE_ITEM_HAS_TRACKING_CATEGORY
JOURNAL_LINE_ITEM_HAS_TRACKING_CATEGORY
RECEIPT_LINE_ITEM_HAS_TRACKING_CATEGORY
We have added a new column, tracking_category_option_id
, to the following tables:
RECEIPT_LINE_ITEM_HAS_TRACKING_CATEGORY
CREDIT_NOTE_LINE_ITEM_HAS_TRACKING_CATEGORY
We have added the following tables:
PURCHASE_ORDER
PURCHASE_ORDER_LINE_ITEM
PURCHASE_ORDER_LINE_ITEM_HAS_TRACKING_CATEGORY
We can now delete all of the following records from the tables below:
- Bank transaction line items with no tracking from the
BANK_TRANSACTION_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Receipts with no tracking from the
RECEIPT_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Invoices with no line items from the
INVOICE_LINE_ITEM
table - Invoice line items with no tracking from the
INVOICE_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Manual journal lines with no tracking from the
MANUAL_JOURNAL_LINE_HAS_TRACKING_CATEGORY
table - Overpayment line items with no tracking from the
OVERPAYMENT_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Overpayments with no overpayment line items from the
OVERPAYMENT_LINE_ITEM
table - Pre-payments with no pre-payment line items from the
PREPAYMENT_LINE_ITEM
table - Repeating invoices with no repeating invoice line items from the
REPEATING_INVOICE_LINE_ITEM
table - Repeating invoice line items with no tracking from the
REPEATING_INVOICE_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Credit note line items with no tracking from the
CREDIT_NOTE_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Credit notes with no credit note line items from the
CREDIT_NOTE_LINE_ITEM
table - Contact addresses with no addresses from the
CONTACT_ADDRESS
table - Purchase orders with no purchase line items from the
PURCHASE_ORDER_LINE_ITEM
table - Purchase orders with no tracking from the
PURCHASE_ORDER_LINE_ITEM_HAS_TRACKING_CATEGORY
table - Journals with no tracking or tracking categories from the
JOURNAL_LINE_HAS_TRACKING_CATEGORY
table
Previously, we were not able to remove these records because of the way we set up the primary key.
September 2019link
We have added two new tables, INVOICE_LINKED_TRANSACTIONS
and BANK_LINKED_TRANSACTIONS
, to support the linked transactions endpoint.
February 2019link
- Made the field
invoice_id
the Primary Key in the table_INVOICE_LINE_ITEM
. - Made the field
overpayment_id
the Primary Key in the table_OVERPAYMENT_LINE_ITEM
. - Made the field
prepayment_id
the Primary Key in the table_PREPAYMENT_LINE_ITEM
. - Made the field
repeating_invoice_id
the Primary Key in the table_REPEATING_INVOICE_LINE_ITEM
.
Fivetran will not store the deleted line_item records
for the above tables.
October 2018link
We have added two new fields, edition
and class
, to the ORGANIZATION
table.
June 2018link
We have added the tax_number_name
field to the ORGANISATION
table, if the field is present in the API response.
We have added the account_id
field to MANUAL_JOURNAL_LINE
table, if the field is present in the API response.