Xero books are one source in AI training data licensing, and two programs on record name Xero. Licensing nothing is a valid result.
Fact-check note: Xero's statements come from its own pages and public API specification, read on November 17, 2026, and program terms are each program's own statements, checked November 9, 2026; how we source, date and check every figure is set out in the methodology.
What a Xero Organization Holds and What a License Can Cover
A Xero organization holds a business's books: the chart of accounts, journals and manual journals, invoices, bills and credit notes, bank transactions, contacts for customers and suppliers, items, budgets, expense claims and the files attached to them, with a history of changes on many records.
Xero's data processing terms apply to the personal data of the customer's customers, suppliers and employees (cl. 22), so the books carry other people's details.
Which finance records buyers ask for, and the finance privacy rules, are covered on the page about accounting, ERP and financial records for AI training.
Who Controls Xero Data in a License
Four parties shape what can be licensed out of Xero: the subscriber that keeps the data, Xero with its license to use it, app developers bound by the Developer Platform Terms, and the customers, suppliers, employees and clients whose details fill the books.
The Terms of Use name Xero Limited, a New Zealand company (registration number 1830488, cl. 79), and the contracting entity varies by edition.
Xero's Terms of Use: Data Use, Anonymized Statistics and the Clause 56 Resale Bar
Xero's Terms of Use, last updated October 26, 2026 and effective for current customers from December 28, 2026, state that "we don't own that data" while granting Xero a license to use, copy, transmit, store, analyse and back up the data a customer submits, to run, improve and develop its services and create new ones (cl. 20).
Clause 23 lets Xero create anonymised statistical data from customer data, including by aggregation, and use it for its own purposes such as improving services. Ownership is one layer of a rights audit of the data you want to license.
Clause 56 says a customer must not "Repackage, resell, or sublicense any leads or data accessed through our services". Whether that clause reaches a subscriber licensing its own export is not answered by the text, a question for Xero and counsel.
Xero's Developer Platform Terms: No AI Training on API Data
Xero's Developer Platform Terms, last updated December 4, 2025 and binding on developers registered before that date from March 2, 2026, state: "API Data cannot be used to train, fine tune, adapt, or enhance any AI Models." (cl. 7(b)).
The terms define API Data as information accessed, received, transmitted or generated through the public APIs, "whether in raw or processed form".
- API Data serves only the app's features under its approved use case, with no passthrough to a third party without the user's consent.
- Developers must not sell user data or aggregate and supply it to another app or third party (cl. 29).
- Developers must not scrape Xero's sites with bots or browser automation (cl. 29).
A program connecting through the Xero API is bound by these terms, and so is a company's own registered app. Screen exports fall outside the API Data definition but remain under clause 56; buyer connectors vs native exports covers the mechanics.
JAX and Xero's Own Use of AI
Xero's JAX page states that "JAX chat doesn't use your data to train the LLMs it uses", naming AWS, Microsoft Azure, GCP and OpenAI as providers that do not retain the data for training (read November 17, 2026).
Xero's privacy notice, last updated October 26, 2026, says personal data is used to deliver and improve services, each "including using AI/ML". The JAX statement covers the third-party LLMs behind JAX, Xero's own license and statistics are separate, and none is a license route for the customer.
How Xero Data Leaves the Organization
Xero data leaves an organization by three routes: exports from Xero's own screens and reports, the Accounting API, or a connection run by an app or a program. The table compares them as of November 17, 2026, and clause 47 makes the customer responsible for keeping copies of its data.
| Route | What leaves | Terms that apply | Limits on record | Source |
|---|---|---|---|---|
| Reports and in-app exports | reports and lists from Xero's own screens; formats and bulk coverage not on record here | Terms of Use, cl. 56 | not on record | xero.com/legal/terms, read 2026-11-17 |
| Accounting API | accounts, journals, manual journals, invoices, credit notes, bank transactions, contacts, items, budgets, expense claims, attachments, history | Developer Platform Terms: no AI training on API Data; no passthrough without user consent; no selling or aggregating user data | rate limits not on record | github.com/XeroAPI/Xero-OpenAPI; developer.xero.com, read 2026-11-17 |
| App or program connection | whatever the app's approved use case reads | the app's own terms (DPA 1.2(e)); Developer Platform Terms bind the developer | program terms | developer.xero.com; xero.com/legal/terms/data-processing, read 2026-11-17 |
| After termination | nothing until reactivation | Terms of Use cl. 62; DPA 1.10 | archived; copy kept 7 years | xero.com/legal/terms, read 2026-11-17 |
Reports and In-App Exports
Reports and lists exported from Xero's own screens stay outside the Developer Platform Terms, because those terms define API Data by the public APIs.
Export formats and bulk attachment export are not on record here, because Xero's help articles rendered no readable text on November 17, 2026.
The Accounting API and What It Exposes
Xero's Accounting API specification, version 20.1.0 in Xero's public repository, lists endpoints for accounts, journals, manual journals, invoices, credit notes, bank transactions, contacts, items, budgets and expense claims, with attachment and history endpoints on many of them (read November 17, 2026).
Rate limits are not on record here, because Xero's developer page rendered no text that day. The API is the bulk route and the one on which AI training is barred, so a buyer offering to "connect" Xero is asked which route it uses.
Personal and Financial Data Inside a Xero Ledger
A Xero file holds personal and financial data in fixed fields and in free text: customer and supplier contacts, bank details, employee expense claims and, where payroll runs in Xero, pay records. Each place needs PII removal and de-identification before any license.
- Contact names, emails, phone numbers and addresses.
- Bank account and tax identifiers on contacts.
- Invoice and bill line descriptions.
- Bank transaction narratives.
- Expense claims naming employees.
- Attachments such as receipts, contracts and statements.
Under clause 28 of the Terms of Use, a customer agrees not to use free-form fields to store personal data (unless a field explicitly asks for it), credit card details, tax identifiers or bank account details.
That is Xero's rule, not proof that free text is clean. The Data Processing Addendum, last updated February 11, 2025, makes the customer the controller and Xero the processor (cl. 1.2(b)) and requires the customer to hold all rights and permissions (cl. 1.3).
Margins and counterparties' terms also travel in the books. Under 18 U.S.C. 1839(5), in force since May 11, 2016, misappropriation includes disclosure by someone who acquired a secret under a duty to keep it.
Reuse of data collected for bookkeeping raises purpose compatibility under Article 6(4) of Regulation (EU) 2016/679, applying from May 25, 2018. This is information, not legal advice.
Ledgers Kept for Clients: Accountants, Bookkeepers and the Subscriber Role
An accountant or bookkeeper who keeps a client's books in Xero handles the client's data, and often the data of the client's own customers and staff, so a license by the adviser needs the client's permission before any question of Xero's terms arises.
- Terms of Use cl. 9: a partner acting as subscriber for a client can be directed to give the client read-only access.
- Partner Agreement cl. 4.1, last updated June 16, 2026 and effective for current partners from August 16, 2026: a partner that breaches its client-subscriber requirements, including during a dispute, can be directed to give read-only access.
- Data Processing Addendum 1.2(b): where the customer processes for a client, Xero is the sub-processor and the client is the controller.
Client return information is governed by 26 U.S.C. 7216, which bars disclosure or use of tax return information other than for return preparation without written taxpayer consent; the rule is set out for IRC Section 7216 for tax preparers. Engagement letters and professional rules decide for bookkeeping files.
What Programs Name When They Ask for Xero Data
Two programs on record name Xero among the tools they want data from, checked November 9, 2026. The table is alphabetical and as of November 17, 2026, and every value is the program's own statement.
| Program | Role | Xero named as | Terms that matter for Xero data | Source |
|---|---|---|---|---|
| Corpus Bridge assessment and sale | broker (intermediary, seller-side; legal name not published) | "QuickBooks/Xero/NetSuite/SAP/Shopify" | assessment, then a brokerage partner approaches labs and handles contract and delivery | corpusbridge.com |
| Mercor Accounting & Tax Firm listing | licensee (company data program) | tools QuickBooks, Xero, Sage Intacct, CCH, UltraTax, Lacerte, Drake, Bill.com | asks for tax returns with workpapers across several entity types, several filing seasons, client documents that can be anonymized; not blank forms or non-US returns | api.data.mercor.com listing feed |
No program publishes a Xero-specific price, and no seller-confirmed amount for Xero data is on record. Payout ranges and terms across programs are set out in AI data partnership payouts and program terms compared.
Corpus Bridge is a broker that acts for sellers, not a buyer, and its legal name is not published.
Licensing Xero Ledgers: Benefits, Risks, Downsides and Alternatives
Licensing Xero ledgers can earn money from years of transaction history, and it also hands other people's details and the company's own margins to a third party for good, so not licensing remains a valid result.
Benefits
- Xero states that it does not own the data (cl. 20).
- Structured, dated records span many years.
- Programs that name Xero exist.
Risks
- The clause 56 resale bar is unresolved for a subscriber's own data.
- The API route is barred for AI training.
- Client, tax and financial privacy duties can bar a license.
- Data cannot be recalled: Labelbox states that models already trained on data "cannot be unlearned" (checked November 9, 2026).
Downsides
- In-app export coverage is not on record here.
- Data is unavailable to the customer after termination.
- Free text and attachments need de-identifying.
Alternatives
- License a subset, such as closed years, one entity or aggregated figures with no counterparties.
- License other systems' records without the Xero books.
- Keep the data and use it internally.
- Do not license at all.
Xero Among the Finance Systems and the Seller Steps
Xero is one of the accounting systems whose terms decide what a company can license, and its client books bring in the rules for accounting firms. The comparison across systems is export rights and mechanics by source system.
The closest sibling is QuickBooks data export, followed by NetSuite data export and SAP data export, and firm-level decisions sit with accounting and tax firms licensing data. The seller steps run in this order:
- Take a data inventory of entities and attachments.
- Check customer consent and confidentiality clauses for customers, suppliers and clients.
- Settle employee notice and consent for expense claims and payroll.
- Write the data manifest.
- Plan delivering licensed data to an AI buyer.
- Decide whether to proceed, using should you sell or license your data.
Xero Data After a Subscription Ends
Once a Xero subscription is terminated it is archived and the data is no longer available to the customer, who can regain access only by reactivating and paying the subscription fees (Terms of Use cl. 62).
- No read-only period is stated, and Xero removes the data completely on request.
- A direct subscriber or Xero can end the subscription on one month's notice (cl. 59, 60).
- Under Data Processing Addendum 1.10, Xero keeps a copy for 7 years to allow reactivation, then deletes or returns it, sooner on request.
The steps for exporting company data before shutting down apply here, and a closed company's records are covered in selling data from a defunct company.
Buyer Programs Cited on This Page
The program terms above come from each program's own pages, checked November 9, 2026.
- Corpus Bridge (seller advisory, intermediary)
- Mercor data buyer profile
- Company data partnership programs
- Who buys AI training data
Frequently Asked Questions
Can you back up Xero data?
Xero's Terms of Use make the customer responsible for keeping copies of its data (cl. 47), and once a subscription ends the data is no longer available until it is reactivated (cl. 62).
Does Xero use customer data to train AI?
Xero states that JAX chat does not use customer data to train the LLMs behind it, while its Terms of Use license Xero to use customer data to improve its services.
Platform practice across vendors is covered in user data and platform terms.
Can a Xero API connection be used to build an AI training dataset?
Not under Xero's Developer Platform Terms, which state that "API Data cannot be used to train, fine tune, adapt, or enhance any AI Models." The terms bind the app developer, including a program's connector.
Can a bookkeeper license a client's Xero data?
Not on its own authority: the client controls the data, and Xero can direct an adviser acting as subscriber to give the client read-only access.
Tax return information adds a written-consent rule, and the limits are set out in what company data cannot be licensed.