Nobody should be keying bank transactions into an accounting system in 2026. The Xace integrations send them across for you, with the review step you actually want before anything lands in the ledger.
What connects
- Xero and QuickBooks: pre-built integrations under the Connections tab. Ask support to enable them.
- NetSuite and anything else: through the API, or through Zapier for no-code automation.
Supported transaction types include incoming payments, outgoing payments, fees, FX movements and card transactions.
Step one: map the accounts
After connecting, map each Xace account to the matching account in your chart of accounts. This is the step that decides whether the integration is a help or a mess.
- One Xace account maps to one ledger bank account. Do not map several Xace accounts to one ledger account; you lose the ability to reconcile each one.
- In a group, map per entity. The Xace account for the Malta entity maps to the Malta entity's ledger, not the group's.
- Name the ledger accounts the same as the Xace accounts.
MT-EUR-OPSin both places saves a lot of explaining.
Step two: review, then sync
Before transactions are sent you can review each one and add what the ledger needs:
- Supplier or vendor details
- GL codes and cost centres
- Descriptions and references
- Spend categories
Card transactions arrive already tagged by user, brand or entity if you set the tags when you issued the card, so this step is mostly confirming.
Step three: let it run
Once mapping is done, transactions flow into the ledger. Month-end becomes reconciling, not re-keying, and reports are current rather than a week behind.
A month-end routine
- Sync and review the last few days' transactions.
- Reconcile each ledger bank account against the Xace account balance. Xace statements for the month are available from the first of the following month; the API also provides a daily statement in CAMT.053 format if you reconcile daily.
- Check FX movements posted to the right accounts, with the rate visible.
- Check fees posted as fees, not lost in payment amounts.
- Close.
If you need more than the pre-built integrations
The API gives read access to accounts, balances, transactions, payees and statements, and with the right access, payment creation and approval. Webhooks notify your system when a payment is requested, approved, declined or received, so you never have to poll. Zapier can sit in front of both if you would rather not write code.
