> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/june/sync-bank-account-to-xero-contact-for-application-payments.md).

# Sync bank account to Xero contact for application payments

When an application payment bill is synced to Xero, the applicant's bank account number is now automatically written to the corresponding Xero contact's bank account field. This extends the existing milestone bank account sync behaviour to application payments (payments without milestones), ensuring Xero's batch payment file generation includes correct bank details regardless of payment type.

The bank account is re-synced on every bill sync, so if an applicant updates their bank details, the Xero contact is always up to date.

## How it works

Application payments resolve the bank account via `payment.milestone_bank_account`, which checks the following in order:

1. **Milestone** — If the payment has an associated milestone, that milestone's bank account number is used.
2. **Application** — The bank account from the funding application form.
3. **Registration** — The bank account from the applicant's registration form.

Since application payments typically have no milestone, the bank account will usually come from the application or registration.

## Enabling the feature

This feature uses the same setting as the milestone bank account sync. Go to **Admin > Settings > Xero Integration** and tick the "Sync bank account to Xero contact" checkbox. The setting label and description have been updated to reflect that it now covers both milestones and application payments.

## Known limitations

The same limitations that apply to milestone bank account sync also apply here. See the [milestone bank account sync feature description](https://help.tahua.io/product-news/2026/june/xero-bank-account-sync.md) for details on overwrite risks and Xeroizer save behaviour.
