• This article is for centers using Xero accounting software and using the Detail Sync option.

  • Before syncing data to Xero, be sure to read this entire article to understand all of the details on how the sync works. There are certain transactions that will not sync to Xero and will require manual intervention so you will want to be familiar with those. If the required manual intervention is not performed in Xero, your financial records will not be complete and will not match to CoreBridge.

  • When manual intervention in Xero is required, the topic below will be highlighted with a grey background.

  • When using Detail Sync, your customer-related data will be re-created in Xero. Once you've gone through your 1st Sync, you should not edit/update/modify/delete any records that sync from CoreBridge to Xero. Xero effectively becomes "look but don't touch" for anything that has synced from CoreBridge. If you change a record in Xero that is synced from CoreBridge, that may cause sync errors or cause your financial data in Xero to not match CoreBridge resulting in erroneous financials.

  • The Detail Sync option is not available to all CoreBridge subscription packages. If you have any questions about availability and pricing, please reach out to support@corebridge.net for more information.

Table of Contents

Records That Sync

The following record types sync from CoreBridge to Xero. Once a record syncs, the record in Xero will be managed by CoreBridge.

No record of the types listed below should ever be changed in Xero if the record was synced with CoreBridge. Once a record has been synced, any changes must occur in CoreBridge.

If you need to make a change: (A) change the record in CoreBridge, (B) run a sync, (C) the sync will update Xero.

  • Customers

    Customers sync only when in Client status. A customer in the Lead or Prospect status will not sync.

    When adding a new customer to CoreBridge that already exists in Xero, the name should match exactly. If the name in CoreBridge is different than the name in Xero, the sync will create a new customer in Xero giving you duplicate customers. If the name is the same, the sync will map the existing Xero customer and will not create a duplicate.

  • Orders

    Orders sync once they have been moved to Completed status. Completed status is when revenue is recognized.

    Orders in WIP or BUILT status do not sync.

    When setting up your system, be sure that your CoreBridge order numbers will not be the same as any existing invoice numbers in Xero. If there are overlapping numbers between CoreBridge and Xero, Xero will block the CoreBridge invoice and the sync will fail.

  • Payments

    Payments will sync only after they are reconciled in CoreBridge. Each individual payment is synced and posts to the Xero bank account that is mapped within CoreBridge.

    All payments are recorded in Xero as type Prepayment.

  • Tax Groups

    Tax Groups sync as Tax Rates

    When tax rates change in CoreBridge, the old rates are managed as archived rates. When you perform a sync after a rate change, the archived records will sync to Xero with names like "old_20_State Tax" and "old_15_County Tax".

    The archived rates need to exist in both CoreBridge and Xero in order to match old invoices with old rates.

    New records with the same naming convention noted above will also be created and synced if you change the name of an agency or group. Just like any other record that syncs from CoreBridge, changing or deleting Tax Rates in Xero will cause sync errors. It can also cause invoices in Xero to have different rates than the matching invoice in CoreBridge.

  • Income Accounts

    When mapping Xero general ledger accounts to CoreBridge income accounts, you can map Revenue accounts or Sales accounts.

    If you want the sync to create an income account for you in Xero, the account type will be Revenue.

    When mapping accounts between CoreBridge and Xero, be sure the account name and number match exactly. If there isn't an exact match, the sync will create a duplicate account in Xero. If your CoreBridge system has child accounts, the sync will ignore the hierarchy and treat all accounts as parent accounts. This happens because Xero doesn't have a parent/child structure.

Multiple Locations/Centers

If your CoreBridge system has more than one location, the sync does not provide a way to distinguish financial activity separately in Xero for each CoreBridge location.

Customers – Master Accounts

Master Accounts do not sync. If you are using Master Accounts in CoreBridge, the sync will ignore those.

Customers – Merging

If you merge a customer in CoreBridge, the merge must be handled manually in Xero.

  • When a sync is performed, the sync window will display the number of customers that were merged in CoreBridge when it reaches the Merged Customer process.

  • When you click the Failed Item link for the Merged Customers process, the item displayed will be the From customer. (The losing customer)

  • The To customer will be displayed as a Successful Item for the Customers process and will show that the record was updated. (The winning customer)

  • Once the customer is manually merged in Xero, the From customer will show as a Successful Item during a sync.

  • If you need a list of Customer merges please open a support ticket.


  • Line items on an invoice in Xero will contain the item or modifier description only. The actual part and modifier records from CoreBridge do not create products and services in Xero.

  • When you give a customer a manual In-Store Credit, the sync will create a credit note in Xero.

  • If you need a support agent to trigger an invoice to sync again, all payments must be manually unapplied from the invoice in Xero first.

Invoices and Voiding

Invoices that sync to Xero should never be voided in Xero. 

  • When an invoice is voided in CoreBridge, the sync does not actually void the related invoice in Xero. The void is simply noted with a "-V" appended to the number.

  • If a CoreBridge order has been voided, and a payment has already been applied to the invoice in Xero, Xero will block the sync from touching the voided order.  The CoreBridge payment that synced to Xero will need to be moved from the voided transaction to the new transaction manually.

  • If payment has been applied to an invoice in Xero, and the payment has been reconciled, the sync will not be able to move the payment to a different invoice.  The payment must be un-reconciled for the sync to move it. The only other way past the sync error would be for CoreBridge support to stop the transaction from syncing and Xero would then need to be updated manually to match CoreBridge.

  • Invoices cannot be triggered to sync again if the invoice has been voided in Xero and the CoreBridge invoice number is retained on the voided invoice. In order for an invoice to be triggered to sync again, the reference number in Xero should be changed prior to voiding. When changing the reference number, the new reference number should not be in the same format as a CoreBridge invoice. If an invoice is voided with the existing CoreBridge number and needs to be created again in Xero, the invoice must be created manually and won't be able to have the same number as the CoreBridge invoice.

  • Credit Memos can't be voided through the sync.


  • Payments post directly to the Default Bank Account mapped in the CoreBridge accounting module.

  • Payments will sync only after they have been reconciled in CoreBridge.

  • Voided payments in CoreBridge will not sync and need to be voided manually in Xero.

  • All payments sync as type: Prepayment

  • Do not apply a Bank Feed payment to the CoreBridge invoice. If the bank feed payment is applied to the invoice, the sync will not be able to update the invoice which will cause a sync error. Bank Feed payments will then need to be manually removed from the invoice in Xero so that the sync can properly update the invoice with the CoreBridge payment.

Payments that are considered deposits on an order

  • Payments that are considered order deposits will sync to Xero before the order does. When the related order has been Completed it will then sync. Since the deposit payment synced before the order did, the sync will not apply the payment to the order. Those types of payments will need to be applied manually in Xero to the related CoreBridge invoice(s). If the payment is not applied, the related invoice(s) will remain open in Xero.

Payments - best practices when using Bank Feeds

  • Do not apply a Bank Feed payment to a CoreBridge invoice. If a Bank Feed payment is applied in Xero, then the CoreBridge payments syncs, the same payment may be applied twice to the invoice in Xero.

  • Perform a CoreBridge Reconciliation daily to capture payments.

  • Run the sync daily after a Reconciliation has been performed in order to sync payments to Xero.

  • Once the CoreBridge payment is applied to the CoreBridge invoice, the Bank Feed payment can be reconciled to the CoreBridge payment.
  • If a Bank Feed payment is applied to a CoreBridge invoice, a few things may happen:
    • Xero may block the invoice from being updated when the sync tries to apply the CoreBridge payment to the invoice.
    • You may end up with duplicate payments in Xero.

Payments - applying a payment in Xero

  • When a deposit payment is entered in CoreBridge on a WIP or BUILT order, the payment will sync to Xero before the invoice once it has been reconciled in CoreBridge.  When a payment syncs before the invoice syncs, the payment will not be applied automatically to the invoice in Xero when the invoice finally syncs. The payment will need to be applied manually.

  • To apply a payment manually, use one of these methods.
    • Open the payment then use Allocate Credit.
    • Open the invoice then use Credit this invoice.

Refunds, Bad Debt, and NSF Payments

Refunds, Bad Debt, and NSF payments will not sync and will need to be manually created in Xero.

  • When a sync is performed, these payment types will display as Successful Items for the Payments task. However, they will not sync to Xero. They are displayed for your reference as a reminder to process the transaction manually in Xero.

  • When the Successful Item link is clicked, the message will display the payment number along with a reminder. This message is only displayed once. To find the transactions later you will need to run a Payments Report so that you can manually update Xero.

Tax Groups and Tax Agencies

Tax Groups will sync only one time and Tax Agencies do not sync.

  • If Tax Groups are archived or deleted in Xero, they cannot be synced again. They will need to be created manually in Xero.

  • To create a tax group manually, the Tax Group name in CoreBridge will need to be entered as both the Display Name and Tax Component name in Xero.

  • When tax amounts are calculated differently between CoreBridge and Xero, the sync will add the difference as an invoice line item. The adjustment is usually 1 cent.

  • When you change the name or the rate in Corebridge of a Tax Group, CoreBridge creates a new record that will sync. The new record will contain the name of the group that was changed and the name of the new record will start with "old_". Although the name may be unfamiliar, do not change the name or delete the record in Xero. 

Manual Entry Needed in Xero

Refer to this support article for a summary of manual entries that may need to happen in Xero.

Sync Errors

If you get a sync error, all of your financial data from CoreBridge will not sync to Xero. To ensure that all data has synced, the sync must complete successfully with no Failed Items. If you have failed items, click the Failed Item link to view the error.

  • If you are able to fix the error, run a sync again to complete the sync.
  • If you are not able to fix the error, the error will need to be reported to CoreBridge support for assistance.

  • This support articles provide the different methods of reporting sync errors: LINK

  • For a list of common errors and possible fixes, please refer to this article:  Xero Detail Sync - Sync Errors

Sync Limits

Xero imposes 3 limits on the API that CoreBridge uses to sync data. If an error message appears during syncing that contains the text "oauth", one of the limits was reached.

  • 60 calls in a rolling 60-second window – you should not reach this limit because we set your system to sync at a set rate
  • 5000 calls in a rolling 24-hour window – unless you have an extraordinary amount of transactions to sync, you should not reach this limit. The only times that it would be possible to hit this limit is during a 1st sync when your customers, invoices and payments sync for the first time or if you have many transactions and sync once a month. If you reach this limit you will need to wait for 24 hours to sync again. We recommend syncing daily to prevent hitting this limit.
  • 30-minute window – if this limit is triggered, just Authorize CoreBridge again using the Connect to Xero button.


Since the Detail Sync re-creates transactions in Xero, you can run financial reports as well as other customer-related reports. However, because the data in Xero isn't live, you should always use CoreBridge reports to manage your customers and A/R. You should always use the CoreBridge sales tax reports when remitting sales tax.