# Xero Integration **URL:** \ **Category:** HubSpot-built Apps\ **Created:** [August 9, 2025, 2:32pm UTC](https://community.hubspot.com/t/xero-integration/137731 "2025-08-09T14:32:08Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![RubenBurdin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rubenburdin/32/75212_2.png) [@RubenBurdin](https://community.hubspot.com/u/RubenBurdin)\ **Post date:** [August 19, 2025, 5:43pm UTC](https://community.hubspot.com/t/xero-integration/137731/4 "2025-08-19T17:43:24Z")
Hi @MGilvey3 , good question This comes up often with the native HubSpot Xero connector. Right now, the integration applies the single default Account you configure during setup to every invoice that syncs. ([Connect HubSpot and Xero (Data Sync)](https://knowledge.hubspot.com/integrations/connect-hubspot-and-xero-data-sync)) There isn’t a way to pick an Account dynamically at runtime. If you need invoices to land in different Xero Accounts, the native route forces either manual edits after the sync or setting up middleware Some folks patch this with Zapier or custom API scripts, but it quickly gets brittle at scale ([2026-03 API reference - HubSpot docs](https://developers.hubspot.com/docs/reference/api/overview)) Where we’ve seen teams get relief is with a sync layer that supports conditional mappings rules like “if invoice line item = X, push to Revenue Account A, otherwise use Account B.” That avoids both manual fixes and over-engineered Zapier chains. For example, Stacksync was built to handle this exact type of scenario: a managed two-way sync where you can map fields dynamically at sync time and keep Xero and HubSpot consistent in real-time, without maintaining custom code or worrying about silent failures Hope this helps clear it up. --- _[View the full topic](https://community.hubspot.com/t/xero-integration/137731)._