Connect Claude to Xero

Return the organisation this connection is pointed at: its name, legal name, country, base currency, financial year end, tax settings and edition. Xero's route is singular, /Organisation, and the payload comes back under a plural Organisations key - that is Xero's shape, not a mistake here. This is the connection test: it needs nothing, costs nothing, names no person, and it is the one call that proves the tenant id in the credential actually resolves to a set of books this sign-in can read.

Return the chart of accounts: every account with its code, name, type, tax type, class and status. This is the organisation's accounting structure rather than anybody's data, so it is the map to read before interpreting an invoice line or a report row. Its response is kept in the audit log for that reason - an agent that has to reason about where a figure came from needs the account list in front of it. Narrow with `where`, e.g. Type=="BANK", or Status=="ACTIVE".

List invoices and bills - Xero keeps both in this one resource and separates them by Type, ACCREC for what you have billed a customer and ACCPAY for what a supplier has billed you. Narrow before you fetch: `statuses` takes a comma-separated list such as AUTHORISED,PAID, `where` filters on any field, and `search_term` matches the invoice number and reference. Set summary_only for a much lighter response without line items, which is what you want when counting or listing. Xero pages this 100 at a time by default; ask for a page with `page`. Its response is kept out of the audit log because an invoice names a real customer or supplier and what they were charged.

Fetch one invoice by its InvoiceID, with its full line items, the contact it belongs to, its payments, credit notes and prepayments, and its running amounts due and paid. Ids come from list_invoices. Its response is kept out of the audit log - it names a counterparty and the amounts between you.

List the customers and suppliers on the organisation, with their names, contact people, email addresses, addresses, tax numbers and outstanding balances. `search_term` matches name, first name, last name, contact number and email address, which is the fastest way from a person's name to a ContactID. Set summary_only for a lighter response. Its output is kept out of the audit log and `where` and `search_term` are masked before the call is logged, because both the answer and the question name real people.

Fetch one customer or supplier by ContactID, with their full record: addresses, phone numbers, email, tax number, default account codes, payment terms and outstanding balances. Ids come from list_contacts. Xero accepts no query parameters at all on this route. Its response is kept out of the audit log - it is one named person or company and their details.

List money in and out of the organisation's bank accounts - spend and receive transactions - with the contact, the bank account, the line items and the reconciliation state. This is the cash view, as opposed to the invoice view: an invoice is what was billed, a bank transaction is what actually moved. Narrow with `where`, e.g. Status=="AUTHORISED", or by bank account. Kept out of the audit log because each row names a counterparty and an amount.

List payments applied against invoices and credit notes, with the invoice each one settles, the account it went through, the amount and the date. Use it to answer "has this been paid, and when" without pulling whole invoices. Narrow with `where`, e.g. Status=="AUTHORISED", or Date>=DateTime(2026,08,01). Kept out of the audit log because a payment names the counterparty it settles with.

Run the Profit and Loss report and return it as Xero's row-and-cell report structure. Every parameter is optional: with none, Xero reports the current month. Pass from_date and to_date for an explicit range, both as YYYY-MM-DD, or use periods together with timeframe to compare several periods side by side - periods 1 to 11, timeframe MONTH, QUARTER or YEAR. The response is aggregate figures with no customer or supplier named in it, which is why, unlike the invoice and contact reads here, it is kept in the audit log: a number an agent reported should be checkable afterwards.

Run the Balance Sheet report and return it as Xero's row-and-cell report structure. Note the difference from the Profit and Loss: a balance sheet is a position at a single moment, so it takes `date` rather than a range, and Xero defaults to the end of the current month. Add periods and timeframe to show prior positions beside it. Note too that Xero's tracking parameters are named differently on this report - trackingOptionID1 and trackingOptionID2, with no category parameter - which is Xero's own asymmetry and not a typo here. Aggregate figures, no counterparties, so the response is kept in the audit log.