TwinDocs
Develop with your Twin

Xero

Connect a Xero organisation to your Twin, how Twin uses its data, and how to disconnect it.

Your Twin reads your organisation's Xero records so its members can ask about invoices, bills, payments, bank transactions and reports in plain English, with answers that cite the Xero records they came from. When a member asks, Twin can also create or update records in Xero. In Xero, the app is called MLX Twin.

Each Twin organisation connects one Xero organisation. Your Xero password is never entered into Twin: you sign in on Xero's own page.

How data flows

 Xero organisation                    Your Twin (your MLX deployment)
 ─────────────────                    ───────────────────────────────
 Xero sign-in and consent  ───1───▶  Connection: tokens kept server-side,
                                      in your deployment's secret store
 Accounting API, reports   ───2───▶  Hourly sync of your organisation's records
                           ───3───▶  Live reads when a question needs them
                           ◀──4────  Writes a member asks for (logged)
                                             │
                                             5  the records a task needs
                                             ▼
                                      AI model providers listed at
                                      mlx.systems/subprocessors
  1. An organisation admin agrees to how Twin uses Xero data, then connects Xero through Xero's sign-in. The connection's tokens stay on the server.
  2. Twin syncs the organisation's records from Xero about every hour.
  3. When a question needs current figures, Twin reads them from Xero, including Xero's own reports.
  4. When a member asks, Twin creates or updates records in Xero. Each write is recorded with its result.
  5. To answer a question or run work, Twin sends the Xero records that task needs to the AI model providers listed at mlx.systems/subprocessors, only to complete that task. Mercury Labs does not use Xero data to train or tune AI models.

Getting started

  1. Sign in to your organisation's Twin, at the address your organisation was given (such as yourcompany.mlx.systems).
  2. Open Marketplace and choose Xero.
  3. An organisation admin reads Before you connect Xero, ticks I agree on behalf of your organisation, and selects Connect Xero.
  4. Sign in to Xero, choose the Xero organisation and allow access.
  5. Xero returns you to your Twin, which shows Xero organisation: and its name, and starts the first sync. It usually takes a few minutes.
  6. Ask your first question, such as "Which invoices are more than 30 days overdue?"

What Twin reads and writes

Reads: accounts, contacts, invoices and bills, credit notes, payments, bank transactions, manual journals, purchase orders, quotes, repeating invoices, tax rates, tracking categories, budgets, attachments and organisation settings, and Xero's reports: profit and loss, balance sheet, trial balance, aged receivables and payables, bank summary, budget summary, executive summary and tax reports.

Writes, only when a member asks: invoices and bills (such as draft bills), contacts and attachments, using your organisation's own Xero account codes and tax rates. Xero calculates the tax and totals.

How Twin uses Xero data

An organisation admin agrees to this wording once, on the organisation's behalf, before Xero can be connected:

To answer your organisation's questions and run the work it sets up, Twin sends the Xero records each task needs to the AI model providers listed at mlx.systems/subprocessors, only to complete that task. Mercury Labs does not use Xero data to train or tune AI models.

Twin records who agreed, when, and to which wording. The Xero page shows it as Agreed on behalf of your organisation, with the admin's name and the date. If the wording changes, an admin is asked to agree again.

Status and errors

The Xero page in Marketplace shows:

  • the connected Xero organisation's name;
  • each sync's status, record counts and last error, with Xero's reason;
  • when Xero needs you to sign in again, a Reconnect button;
  • when the connection was ended from Xero, "This organisation's Xero connection was ended in Xero on" the date, with Connect Xero to resume.

FAQ

How do I disconnect from Xero?

In your Twin, open Marketplace, choose Xero and select Disconnect. Twin ends its connection in Xero and removes your organisation's saved Xero credentials. If Xero does not confirm, nothing is removed and Twin tells you.

You can also disconnect in Xero: go to Settings → Connected apps, choose MLX Twin and disconnect it. At its next check Twin shows the connection as ended in Xero and stops syncing until an admin connects again.

Who can connect or disconnect Xero?

An organisation admin in your Twin. Every member your organisation lets use Twin can ask questions about the connected data.

Can I connect more than one Xero organisation?

Each Twin organisation connects one Xero organisation. To connect another, ask us for another Twin organisation.

Does Twin train AI models on my Xero data?

No. Mercury Labs does not use Xero data to train or tune AI models. Twin sends the records a task needs to the model providers we list publicly, only to complete that task.

Does Twin change anything in Xero by itself?

No. Twin writes to Xero only when a member asks it to, and each write is recorded with its result.

Why does Twin say my connection was ended in Xero?

Someone disconnected MLX Twin in Xero, under Connected apps. Select Connect Xero to connect again.

How do I have Xero data removed from Twin?

Disconnect Xero first, then email team@mercurylabs.io.

Support and privacy

For help connecting, syncing or disconnecting, email team@mercurylabs.io. We aim to reply within one business day.

On this page