- Introduction
-
Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
- Subscribing to Hevo via Snowflake Marketplace
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
-
Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Best Practices to Avoid Reaching Source API Rate Limits
-
Edge
- Getting Started
- Data Ingestion
- Core Concepts
-
Pipelines
- Familiarizing with the Pipelines UI
- Creating an Edge Pipeline
- Working with Edge Pipelines
- Pipeline Job History
- Object and Schema Management
- Activity Log
-
Sources
- Connect AI: Build Your Own Connector
- PostgreSQL
- Oracle
- MySQL
- SQL Server
- CockroachDB
- Troubleshooting Database Sources
- Salesforce Bulk API V2
- Ordergroove
- BambooHR
- Stripe
- NetSuite SuiteAnalytics
- Shopify
- Slack
- ClickUp
- Monday.com
- Pipedrive
- Workable
- Fathom
- HubSpot
- Salesforce Marketing Cloud
- Google Analytics 4
- Google Ads
- Facebook Ads
- Microsoft Ads
- LinkedIn Ads
- Xero
- Naming Conventions for Source Data Entities
- Destinations
- Transformations
- Alerts
- Custom Connectors
-
Releases
- Edge Release Notes - August 2026
- Edge Release Notes - July 2026
- Edge Release Notes - June 2026
- Edge Release Notes - May 2026
- Edge Release Notes - April 2026
- Edge Release Notes - March 2026
- Edge Release Notes - February 2026
- Edge Release Notes - January 2026
- Edge Release Notes - December 2025
- Edge Release Notes - November 2025
- Edge Release Notes - October 2025
- Edge Release Notes - September 2025
- Edge Release Notes - August 2025
- Edge Release Notes - July 2025
- Edge Release Notes - November 2024
-
Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
-
Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Changing the Data Type of a Destination Table Column
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Why can't I see my Pipelines after logging in?
- Events Usage
-
Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Upgrading Pipelines with PostgreSQL Sources to Use the pgoutput Plugin
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
-
PostgreSQL FAQs
- Can I track updates to existing records in PostgreSQL?
- How can I migrate a Pipeline created with one PostgreSQL Source variant to another variant?
- How can I prevent data loss when migrating or upgrading my PostgreSQL database?
- Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery?
- Why is data not being ingested from PostgreSQL Source objects?
- Troubleshooting Database Sources
- Database Source FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Ads
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
-
Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
-
Google BigQuery
- Clustering in BigQuery
- Partitioning in BigQuery
- Structure of Data in the Google BigQuery Data Warehouse
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Modifying BigQuery Destinations to Use Service Account Authentication
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Snowflake
- Troubleshooting Data Warehouse Destinations
-
Destination FAQs
- Can I change the primary key in my Destination table?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
-
Releases- Release 2.51.1 (July 27 - August 05, 2026)
- 2026 Releases
-
2025 Releases
- Release 2.44 (Dec 01, 2025-Jan 12, 2026)
- Release 2.43 (Nov 03-Dec 01, 2025)
- Release 2.42 (Oct 06-Nov 03, 2025)
- Release 2.41 (Sep 08-Oct 06, 2025)
- Release 2.40 (Aug 11-Sep 08, 2025)
- Release 2.39 (Jul 07-Aug 11, 2025)
- Release 2.38 (Jun 09-Jul 07, 2025)
- Release 2.37 (May 12-Jun 09, 2025)
- Release 2.36 (Apr 14-May 12, 2025)
- Release 2.35 (Mar 17-Apr 14, 2025)
- Release 2.34 (Feb 17-Mar 17, 2025)
- Release 2.33 (Jan 20-Feb 17, 2025)
-
2024 Releases
- Release 2.32 (Dec 16 2024-Jan 20, 2025)
- Release 2.31 (Nov 18-Dec 16, 2024)
- Release 2.30 (Oct 21-Nov 18, 2024)
- Release 2.29 (Sep 30-Oct 22, 2024)
- Release 2.28 (Sep 02-30, 2024)
- Release 2.27 (Aug 05-Sep 02, 2024)
- Release 2.26 (Jul 08-Aug 05, 2024)
- Release 2.25 (Jun 10-Jul 08, 2024)
- Release 2.24 (May 06-Jun 10, 2024)
- Release 2.23 (Apr 08-May 06, 2024)
- Release 2.22 (Mar 11-Apr 08, 2024)
- Release 2.21 (Feb 12-Mar 11, 2024)
- Release 2.20 (Jan 15-Feb 12, 2024)
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
- Early Access New
Xero is a cloud-based accounting platform used by small and medium-sized businesses to manage their finances online. It enables you to send and track invoices, reconcile bank transactions, manage fixed assets, run payroll, and track projects, connecting your business with a network of accountants, bookkeepers, and banks.
Hevo uses the Xero Accounting, Assets, Files, Projects, Payroll AU, and Payroll NZ REST APIs to replicate data from your Xero organization to the Destination of your choice. Hevo supports the following authentication methods to connect to your Xero organization:
-
Custom Connection: Uses the client credentials of a Xero Custom Connection app you create. It is available only for Xero organizations in Australia, New Zealand, the United Kingdom, and the United States.
-
Web App: Uses your own Xero OAuth app and the Open Authorization (OAuth) 2.0, so you can choose which Xero organization the connection can access.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes |
| History mode | No |
| Custom data (user-configured tables & fields) | No |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | No |
Prerequisites
-
An active Xero organization exists from which data is to be ingested.
-
You have access to a Xero user with Administrator permissions to create the required app in the Xero Developer portal and authorize the connection.
-
The required credentials are available to provide Hevo access to your Xero organization data.
-
If you want to connect using Custom Connection, your Xero organization is based in Australia, New Zealand, the United Kingdom, or the United States, and has an active Custom Connections subscription.
Obtain the Xero Credentials
To connect Hevo to your Xero organization, you must create an app in the Xero Developer portal and obtain its Client ID and Client Secret. The steps depend on the connection method you want to use:
-
Custom Connection: Create a Custom Connection app that authenticates using the client credentials.
-
Web App: Create a Web app that authenticates using client credentials and OAuth 2.0.
Note: If the client credentials configured in the Pipeline is revoked manually from your Xero account, Hevo cannot authenticate with the Source. As a result, all active jobs for the Pipeline fail, and no data is replicated. To resume data replication, modify the Source configuration in the Pipeline with valid client credentials. Once the updated credentials are saved, Hevo re-authenticates the Source, and data ingestion resumes from the last saved offset.
Create a Custom Connection App
A Custom Connection allows Hevo to connect to Xero using the credentials of a Custom Connection app that you create in Xero. Custom Connections are available only for Xero organizations in Australia, New Zealand, the United Kingdom, and the United States, and require an active Custom Connections subscription in your Xero account.
Perform the following steps to create a Custom Connection app and obtain its credentials:
-
Log in to My Apps in the Xero Developer portal.
-
Click New app.

-
In the Add a new Xero app pop-up window, do the following:

-
App name: Specify a unique name for the custom connection app.
-
Integration type: Select Custom connection.
-
Will you use Xero data to train…: Select an option as per your requirement.
-
Do you understand and agree…: Select Yes.
-
Company or application URL: Specify the URL of your organization.
-
Select the acknowledgment check box, and then click Create app.
-
-
On the Authorisation page, do the following:

-
From the Scopes drop-down, select the following API scopes:
-
accounting.settings.read
-
accounting.contacts.read
-
accounting.invoices.read
-
accounting.banktransactions.read
-
accounting.payments.read
-
accounting.manualjournals.read
-
accounting.attachments.read
-
assets.read
-
payroll.employees.read
-
payroll.payruns.read
-
payroll.payslip.read
-
payroll.timesheets.read
-
payroll.settings.read
-
projects.read
-
files.read
Note: Custom Connections created on or after April 29, 2026 do not have access to the accounting.journals.read scope. As a result, the Journal and Journal Cash objects are not available in Custom Connection mode. Use Web App mode to sync these objects instead.
-
-
In the Authorised user section, select the Xero user who will authorize the connection. This user must have Administrator access to the organization. The selected user receives an email to complete the authorization.
-
Click Save and connect.
-
-
Once the user completes the authorization, open the app’s Configuration page to view its Client id. Click Copy to copy the Client ID and save it securely, like any other password.

-
Click Generate a secret to generate the Client Secret.

-
Click Copy to copy the Client secret 1, and save it securely like any other password.

Note: The Client Secret is displayed only once. Copy and store it securely, as it cannot be retrieved later.
Use the Client ID and Client Secret while configuring your Xero Source in Hevo.
Create a Web App
A Web app uses the standard OAuth 2.0 authorization. You create the app, provide its Client ID and Client Secret to Hevo, and then authorize the connection by signing in to Xero during Source configuration.
Perform the following steps to create a Web app and obtain its credentials:
-
Log in to My Apps in the Xero Developer portal.
-
Click New app.

-
In the Add a new Xero app pop-up window, do the following:

-
App name: Specify a unique name for the Web app.
-
Integration type: Select Web app.
-
Will you use Xero data to train…: Select an option as per your requirement.
-
Do you understand and agree…: Select Yes.
-
Company or application URL: Specify the URL of your organization.
-
OAuth 2.0 redirect URI: Specify
https://westeros.hevodata.com/edge/oauth/callbackas the redirect URI. -
Select the acknowledgment check box, and then click Create app.
-
-
Once the app is created, copy the Client id displayed on the app’s Configuration page, and save it securely like any other password.

-
Click Generate a secret to generate the Client Secret.

-
Click Copy to copy the Client secret 1, and save it securely like any other password.

Note: The Client Secret is displayed only once. Copy and store it securely, as it cannot be retrieved later.
Use the Client ID and Client Secret while configuring your Xero Source in Hevo. Once you obtain these credentials, complete the authorization for the specific Xero organization you want to sync during Source configuration.
Configure Xero as a Source in your Pipeline
Perform the following steps to configure your Xero Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select Xero.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
On the Select Pipeline Type page, click Edge, and then click Continue.

This page appears only if the selected Destination type is supported in Edge and your Team has an existing Xero Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.
-
In the Configure Source screen, specify the following:

-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, Xero Source.
-
In the Connect to your Xero account section, specify the following:
-
From the Connection Method drop-down, select how Hevo authenticates with Xero:
-
Custom Connection: Connect using a Xero Custom Connection app. This is the default option.
-
Client ID: The Client ID of your Xero Custom Connection app.
-
Client Secret: The Client Secret of your Xero Custom Connection app.
-
-
Web App: Connect using your Xero Web app and the standard OAuth 2.0 authorization.

-
Client ID: The Client ID of your Xero Web app.
-
Client Secret: The Client Secret of your Xero Web app.
-
Get Journal Objects: Enable this option to sync the Journal and Journal Cash objects. This is applicable only if your connected Xero organization is on an Advanced or Enterprise plan, and your Web app has been approved by Xero for the accounting.journals.read scope.
Note: Enabling this option for an organization or app that does not meet these requirements causes the authorization to fail.
-
Click Authorize your Xero account, sign in to Xero, and grant Hevo access to your account.
-
In the Select your organisation section, from the Organisation drop-down, select the Xero organization from which you want to sync data.

-
-
-
-
-
Click Test & Continue to test the connection to your Xero Source.
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.
You can select parent and child objects independently for replication. Selecting or deselecting a parent object does not automatically select or deselect its associated child objects.
Hevo ingests the following types of data from your Source objects:
-
Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects and loads it into the Destination.
-
Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.
For the following objects, Hevo ingests only the incremental data in subsequent Pipeline runs:
-
Account
-
Bank Account
-
Bank Linked Transaction
-
Bank Transaction
-
Credit Note
-
Invoice
-
Item
-
Journal
-
Journal Cash
-
Manual Journal
-
Overpayment
-
Payment
-
Prepayment
-
Purchase Order
-
User
-
AU Payroll Calendar
-
AU Payroll Employee
-
AU Payroll Leave Application
-
AU Payroll Pay Run
-
AU Payroll Superfund
-
AU Payroll Timesheet
Incremental changes are detected using the updated_date_utc field. For the Journal and Journal Cash objects, Hevo detects new records using the journal_number field.
For the Contact, Contact Address, Contact Phone, and Contact Group Member objects, Hevo ingests the entire data once a day, regardless of the Pipeline sync frequency.
For all other objects, Hevo ingests the entire data during each Pipeline run.
Xero currently enforces rate limits on the number of calls that can be made to its APIs in a given time period. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Schema and Primary Keys
Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
Data Model
Hevo supports the following Xero APIs for ingesting data from your Xero organization:
Accounting API
Hevo ingests the following objects using the Xero Accounting API:
| Object | Description |
|---|---|
| Currency | Contains the currencies configured in your Xero organization, including the currency code and description. |
| Account | Contains the chart of accounts configured in your Xero organization, including account codes, types, tax settings, and bank account details. |
| Bank Account | Contains the bank-type accounts configured in your Xero organization. |
| Tax Rate | Contains the tax rates configured in your Xero organization, including the rate percentage, tax type, and the accounts to which each rate applies. This object has a child object, Tax Rate Component. |
| Organization | Contains details about your Xero organization, including its legal name, base currency, financial year end, and organization type. |
| Branding Theme | Contains the invoice branding themes configured in your Xero organization, such as theme name, logo, and sort order. |
| Tracking Category | Contains the tracking categories configured in your Xero organization, used to track transactions by department, region, or other custom dimensions. This object has the following child objects: - Tracking Category Option - Tracking Category Has Option |
| Payment | Contains payments applied to invoices, credit notes, overpayments, and prepayments, including the amount, payment date, and associated bank account. |
| Item | Contains the products and services (inventory and non-inventory items) sold or purchased in your Xero organization, including pricing and account codes. |
| User | Contains the users who have access to your Xero organization, including their name, email address, and organization role. |
| Bank Transfer | Contains transfers of funds between bank accounts in your Xero organization. |
| Invoice | Contains sales and purchase invoices raised in your Xero organization, including amounts, due dates, and payment status. This object has the following child objects: - Invoice Line Item - Invoice Line Item Has Tracking Category |
| Credit Note | Contains credit notes issued in your Xero organization, including amounts and allocation status. This object has the following child objects: - Credit Note Line Item - Credit Note Line Item Has Tracking Category |
| Bank Transaction | Contains money received or spent through bank accounts in your Xero organization, such as spend money and receive money transactions. This object has the following child objects: - Bank Transaction Line Item - Bank Transaction Line Item Has Tracking Category |
| Purchase Order | Contains purchase orders raised in your Xero organization. This object has the following child objects: - Purchase Order Line Item - Purchase Order Line Item Has Tracking Category |
| Manual Journal | Contains manual journal entries posted directly to the general ledger in your Xero organization. This object has the following child objects: - Manual Journal Line - Manual Journal Line Has Tracking Category |
| Overpayment | Contains overpayments recorded against invoices in your Xero organization. This object has the following child objects: - Overpayment Line Item - Overpayment Line Item Has Tracking Category |
| Prepayment | Contains prepayments recorded against invoices in your Xero organization. This object has the following child objects: - Prepayment Line Item - Prepayment Line Item Has Tracking Category |
| Allocation | Contains the allocation of credit notes, overpayments, and prepayments against invoices in your Xero organization. This is a part of the Credit Notes, Overpayments, and Prepayments endpoints in the Xero Accounting API. |
| Contact | Contains the customers and suppliers in your Xero organization, including contact details, tax information, and outstanding balances. This object has the following child objects: - Contact Address - Contact Phone - Contact Group Member |
| Contact Group | Contains the groups used to organize contacts in your Xero organization. |
| Repeating Invoice | Contains invoice templates configured in your Xero organization to automatically generate invoices on a recurring schedule. This object has the following child objects: - Repeating Invoice Line Item - Repeating Invoice Line Item Has Tracking Category |
| Journal | Contains the accrual-basis general ledger journals generated for every transaction in your Xero organization, in the order they were created. This object has the following child objects: - Journal Line - Journal Line Has Tracking Category |
| Journal Cash | Contains the cash-basis general ledger journals generated for every transaction in your Xero organization, in the order they were created. This object has the following child objects: - Journal Cash Line - Journal Cash Line Has Tracking Category |
| Bank Linked Transaction | Contains links between billable expense transactions (such as bills) and the sales invoices to which the costs are recharged in your Xero organization. This object has a child object, Invoice Linked Transaction. |
Assets API
Hevo ingests the following objects using the Xero Assets API:
| Object | Description |
|---|---|
| Asset Type | Contains the asset types configured in your Xero organization, including the associated fixed asset, depreciation expense, and accumulated depreciation accounts. |
| Asset | Contains the fixed assets recorded in your Xero organization, including purchase details, depreciation settings, and current book value. |
| Asset Settings | Contains the fixed asset settings configured for your Xero organization, such as the asset number prefix and default disposal accounts. |
Files API
Hevo ingests the following objects using the Xero Files API:
| Object | Description |
|---|---|
| File | Contains the files uploaded to your Xero organization’s file library, including file name, type, size, and the folder to which it belongs. |
| Folder | Contains the folders used to organize files in your Xero organization’s file library. |
| Inbox | Contains the default Inbox folder used to store files uploaded to your Xero organization before they are filed into other folders. |
Projects API
Hevo ingests the following objects using the Xero Projects API:
| Object | Description |
|---|---|
| Project | Contains the projects created in your Xero organization, including the associated contact, currency, invoiced amounts, and status. |
| Project User | Contains the users assigned to projects in your Xero organization. |
Payroll AU API
Hevo ingests the following objects using the Xero Payroll AU API. These objects are available only for Xero organizations based in Australia with Xero Payroll enabled.
| Object | Description |
|---|---|
| AU Payroll Employee | Contains employee records from your Xero Payroll (AU) organization, including personal details, start date, and payroll calendar assignment. |
| AU Payroll Timesheet | Contains employee timesheets recorded in your Xero Payroll (AU) organization. This object has a child object, AU Payroll Timesheet Line. |
| AU Payroll Leave Application | Contains employee leave applications recorded in your Xero Payroll (AU) organization. This object has a child object, AU Payroll Leave Period. |
| AU Payroll Pay Run | Contains the pay runs processed in your Xero Payroll (AU) organization, including the pay period, payment date, and totals for wages, tax, and superannuation. |
| AU Payroll Calendar | Contains the payroll calendars configured in your Xero Payroll (AU) organization, defining the pay run frequency and reference dates. |
| AU Payroll Superfund | Contains the superannuation funds configured in your Xero Payroll (AU) organization. This object has a child object, AU Payroll Superfund Product. |
| AU Payroll Pay Item | Contains the pay items configured in your Xero Payroll (AU) organization, including earnings rates, deduction types, leave types, and reimbursement types. |
| AU Payroll Setting | Contains the payroll settings configured for your Xero Payroll (AU) organization, including the accounts and tracking categories used for payroll transactions. |
Payroll NZ API
Hevo ingests the following objects using the Xero Payroll NZ API. These objects are available only for Xero organizations based in New Zealand with Xero Payroll enabled.
| Object | Description |
|---|---|
| NZ Deduction | Contains the deduction types configured in your Xero Payroll (NZ) organization. |
| NZ Earning Rate | Contains the earnings rates configured in your Xero Payroll (NZ) organization. |
| NZ Reimbursement | Contains the reimbursement types configured in your Xero Payroll (NZ) organization. |
| NZ Statutory Deduction | Contains the statutory deduction types, such as student loan repayments, configured in your Xero Payroll (NZ) organization. |
| NZ Superannuation | Contains the superannuation (KiwiSaver) contribution types configured in your Xero Payroll (NZ) organization. |
| NZ Leave Type | Contains the leave types configured in your Xero Payroll (NZ) organization. |
| NZ Pay Run Calendar | Contains the payroll calendars configured in your Xero Payroll (NZ) organization, defining the pay run frequency and reference dates. |
| NZ Payroll Setting | Contains the payroll settings, such as the accounts, configured for your Xero Payroll (NZ) organization. |
| NZ Employee | Contains employee records from your Xero Payroll (NZ) organization, including personal details and payroll calendar assignment. |
| NZ Timesheet | Contains employee timesheets recorded in your Xero Payroll (NZ) organization. |
| NZ Pay Run | Contains the pay runs processed in your Xero Payroll (NZ) organization. This object has a child object, NZ Pay Slip. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
Hevo handles deleted records differently based on how data is ingested for each object. For most objects, Xero does not permanently delete records. Instead, it updates the object’s status field to a value such as DELETED, VOIDED, or ARCHIVED. Hevo captures this updated status but does not set the __hevo__marked_deleted metadata column to true. To identify deleted records in the Source, use the object’s status field.
For the Contact object, Xero does not permanently delete contact records. Instead, Xero marks an archived or GDPR-erased contact by setting the ContactStatus field to ARCHIVED or GDPRREQUEST. Hevo ingests these records and marks them as deleted in the Destination by updating the value of the metadata column __hevo__marked_deleted to True.
For the child object Contact Group Member, Hevo ingests the entire data during each sync. If a contact is removed from a group in Xero, the corresponding record is no longer present in the Destination after the next Pipeline run.
Source Considerations
-
The AU Payroll and NZ Payroll objects are available only for Xero organizations based in Australia and New Zealand, respectively, that have completed Xero’s Payroll setup process.
-
Xero does not update the updated_date_utc field on every change to a record. For example, some field-level changes do not update this timestamp. As a result, such changes may not be captured during incremental Pipeline runs. To retrieve the latest values for these fields in your Destination, you can resync the corresponding objects at regular intervals.
Limitations
-
Hevo does not support ingestion of Xero Payroll UK objects. Only the Payroll AU and Payroll NZ objects are supported.
-
Hevo supports connecting to only one Xero organization per Pipeline. To ingest data from multiple Xero organizations, create a separate Pipeline for each organization.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Aug-11-2026 | NA | New document. |