Integrations Xero
XeroPlanned

Xero invoice context, where support happens.

Plan a read-only Xero connector for selected invoice and payment context, keeping accounting records separate from public AI knowledge.

Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.

Billing

What we’re planning to connect.

  1. 01Xero
  2. 02Planned connection
  3. 03Message support
01

Investigate an invoice

The proposed staff view would show a matched invoice’s reference and payment state to support a billing conversation.

02

Respect organization boundaries

Keep each connected accounting organization tied to the intended Message workspace.

03

Leave accounting changes in accounting

Creating invoices, editing contacts or issuing credit notes is outside the initial proposed scope.

The right context

Be precise about what connects.

Define the data, permissions and destination before putting the workflow in front of customers.

Selected invoice reference

Payment state

Accounting organization

Message Inbox keeps the customer conversation together. Shown: Message’s current workspace, not a preview of the planned connector.
Prepare for the connection

Define your first workflow.

  1. 01

    Choose the first workflow

    Choose a test organization and an invoice your support staff is authorized to inspect.

  2. 02

    Agree on data and permissions

    Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.

  3. 03

    Define the acceptance test

    Test invoices from a second organization and verify they cannot appear in the first workspace.

Before you connect

Xero integration questions

Can I connect Xero to Message today?

The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.

What should we test before using it with customers?

Test invoices from a second organization and verify they cannot appear in the first workspace.