Xero Integration — Limitations & best practice

Integrate invoices with Xero while managing limits and best‑practice mappings

ID:

280

Keep these constraints and recommendations in mind when working with the Xero Integration.

Limitations

Integration is irreversible per invoice. Once an invoice has been integrated with Xero, this action cannot be undone. (Edits can still be made afterwards in either system.)
Tracking categories are capped at two. Xero supports a maximum of two tracking categories (for example State and Job code).
Prerequisite data must exist in Xero first. Items, accounts and tax rates must already exist in Xero. Use the Sync actions in SwiftFox to bring them in for mapping — SwiftFox does not create them in Xero for you.
Standard-form mappings are applied on the back end. For non-event Forms, the account/item/tax/tracking mappings are configured by your account manager — this is not self-serve.
Voided/Deleted invoices are hidden by default. They are excluded from the Invoices table by default filters; clear the filters to view them.
Xero default branding is used. Invoices are sent by Xero using your default Xero invoice branding (company details, address, contact info).

Confirm before you integrate. Because integrating an invoice cannot be undone, review the line items, account, tax and tracking before clicking Integrate with Xero.
Get your mappings right first. Configure tax rates, accounts, items and tracking categories before raising invoices, so lines post to the correct accounts with the correct tax.
Keep contact details clean. Maintain accurate first name, last name and email on SwiftFox contacts so contact matching links to the right Xero contact and avoids duplicates.
Sync after Xero changes. Whenever you add or change items, accounts, tax rates or tracking categories in Xero, run the relevant Sync action in SwiftFox.
Plan standard-form invoicing with your account manager. Enable invoicing in the form, then hand the account/item/tax/tracking details to your account manager early so the back-end mappings are ready before the form goes live.
Use tracking categories deliberately. With only two available, choose the dimensions that matter most for your reporting (for example State and Job code).

Payment gateways vs. invoicing: credit-card payments happen via the Payment method block (when a gateway is integrated), but invoice generation can be offered as an alternative payment method.
Status sync: payment processed in Xero updates the SwiftFox invoice status to Paid.