Get the FREE Ultimate OpenClaw Setup Guide →

Xero Automation

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-skills/xero-automation --openclaw
Files (1)
SKILL.md
6.9 KB

Xero Automation

Automate Xero accounting operations including managing invoices, contacts, payments, bank transactions, and chart of accounts for small business bookkeeping.

Toolkit docs: composio.dev/toolkits/xero


Setup

This skill requires the Rube MCP server connected at https://rube.app/mcp.

Before executing any tools, ensure an active connection exists for the xero toolkit. If no connection is active, initiate one via RUBE_MANAGE_CONNECTIONS.

Multi-tenant: If you manage multiple Xero organizations, first call XERO_GET_CONNECTIONS to list active tenants and obtain the correct tenant_id for subsequent calls.


Core Workflows

1. List and Filter Invoices

Retrieve invoices with filtering by status, contact, date range, and pagination.

Tool: XERO_LIST_INVOICES

Key Parameters:

  • Statuses -- Comma-separated status filter: "DRAFT", "SUBMITTED", "AUTHORISED", "PAID"
  • ContactIDs -- Comma-separated Contact IDs to filter by
  • InvoiceIDs -- Comma-separated Invoice IDs to filter by
  • where -- OData-style filter, e.g., "Status==\"AUTHORISED\" AND Total>100"
  • order -- Sort expression, e.g., "Date DESC", "InvoiceNumber ASC"
  • page -- Page number for pagination
  • If-Modified-Since -- UTC timestamp; returns only invoices modified since this date
  • tenant_id -- Xero organization ID (uses first tenant if omitted)

Example:

Tool: XERO_LIST_INVOICES
Arguments:
  Statuses: "AUTHORISED,PAID"
  order: "Date DESC"
  page: 1

2. Manage Contacts

Retrieve and search contacts for use in invoices and transactions.

Tool: XERO_GET_CONTACTS

Key Parameters:

  • searchTerm -- Case-insensitive search across Name, FirstName, LastName, Email, ContactNumber
  • ContactID -- Fetch a single contact by ID
  • where -- OData filter, e.g., "ContactStatus==\"ACTIVE\""
  • page, pageSize -- Pagination controls
  • order -- Sort, e.g., "UpdatedDateUTC DESC"
  • includeArchived -- Include archived contacts when true
  • summaryOnly -- Lightweight response when true

Example:

Tool: XERO_GET_CONTACTS
Arguments:
  searchTerm: "acme"
  page: 1
  pageSize: 25

Note: On high-volume accounts, some where filters (e.g., IsCustomer, IsSupplier) may be rejected by Xero. Fall back to searchTerm or pagination.


3. Create Payments

Link an invoice to a bank account by creating a payment record.

Tool: XERO_CREATE_PAYMENT

Key Parameters:

  • InvoiceID (required) -- Xero Invoice ID the payment applies to
  • AccountID (required) -- Bank account ID for the payment
  • Amount (required) -- Payment amount (number)
  • Date -- Payment date in YYYY-MM-DD format
  • Reference -- Payment reference or description
  • CurrencyRate -- Exchange rate for foreign currency payments

Example:

Tool: XERO_CREATE_PAYMENT
Arguments:
  InvoiceID: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  AccountID: "b2c3d4e5-f6a7-8901-bcde-f12345678901"
  Amount: 1500.00
  Date: "2026-02-11"
  Reference: "Payment for INV-0042"

4. Create Bank Transactions

Record spend (payments out) or receive (money in) bank transactions.

Tool: XERO_CREATE_BANK_TRANSACTION

Key Parameters:

  • Type (required) -- "SPEND" (payment out) or "RECEIVE" (money in)
  • ContactID (required) -- Xero Contact ID
  • BankAccountCode (required) -- Bank account code from chart of accounts
  • LineItems (required) -- Array of line items, each with:
    • Description (required) -- Line item description
    • UnitAmount (required) -- Unit price
    • AccountCode (required) -- Account code for categorization
    • Quantity -- Quantity (default 1)
    • TaxType -- Tax type: "OUTPUT", "INPUT", "NONE"
  • Date -- Transaction date in YYYY-MM-DD format
  • Reference -- Transaction reference
  • Status -- "AUTHORISED" or "DELETED"
  • CurrencyCode -- e.g., "USD", "EUR"

Example:

Tool: XERO_CREATE_BANK_TRANSACTION
Arguments:
  Type: "SPEND"
  ContactID: "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  BankAccountCode: "090"
  LineItems: [
    {
      "Description": "Office supplies",
      "UnitAmount": 75.00,
      "AccountCode": "429",
      "Quantity": 1,
      "TaxType": "INPUT"
    }
  ]
  Date: "2026-02-11"
  Reference: "Feb office supplies"

5. List Payments and Bank Transactions

Review existing payments and bank transaction history.

Tools:

  • XERO_LIST_PAYMENTS -- List payments linking invoices to bank transactions
  • XERO_LIST_BANK_TRANSACTIONS -- List spend/receive bank transactions

Common Parameters:

  • where -- OData filter, e.g., "Status==\"AUTHORISED\""
  • order -- Sort expression, e.g., "Date DESC"
  • page -- Page number for pagination
  • If-Modified-Since -- Incremental updates since timestamp
  • tenant_id -- Organization ID

6. View Chart of Accounts and Connections

Tools:

  • XERO_LIST_ACCOUNTS -- Retrieve all account codes for categorizing transactions
  • XERO_GET_CONNECTIONS -- List active Xero tenant connections
  • XERO_LIST_ATTACHMENTS -- List attachments on an entity (invoice, contact, etc.)

Known Pitfalls

PitfallDetail
Multi-tenant routingIf tenant_id is omitted, the first connected tenant is used. Always verify the correct tenant with XERO_GET_CONNECTIONS when managing multiple organizations.
High-volume filter rejectionOn large accounts, some where filters like IsCustomer/IsSupplier may be rejected. Fall back to searchTerm with pagination.
OData filter syntaxUse double-equals (==) in OData filters, e.g., Status==\"AUTHORISED\". Single = causes errors.
Pagination requiredMost list endpoints paginate results. Always check for additional pages and continue fetching until complete.
Date formatAll dates must be in YYYY-MM-DD format. Timestamps for If-Modified-Since must be full ISO 8601 UTC datetime.
Bank account codesBankAccountCode in bank transactions must match a valid code from the chart of accounts. Use XERO_LIST_ACCOUNTS to discover valid codes.

Quick Reference

Tool SlugDescription
XERO_LIST_INVOICESList invoices with filtering and pagination
XERO_GET_CONTACTSRetrieve and search contacts
XERO_CREATE_PAYMENTCreate a payment linking invoice to bank account
XERO_CREATE_BANK_TRANSACTIONRecord a spend or receive bank transaction
XERO_LIST_PAYMENTSList payment records
XERO_LIST_BANK_TRANSACTIONSList bank transactions
XERO_LIST_ACCOUNTSRetrieve chart of accounts
XERO_GET_CONNECTIONSList active Xero tenant connections
XERO_LIST_ATTACHMENTSList attachments on an entity

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/xero-automation/SKILL.mdView on GitHub

Overview

Xero Automation streamlines cloud based bookkeeping by automating core Xero tasks. It handles invoices, contacts, payments, bank transactions, and the chart of accounts to keep financial data accurate and up to date.

How This Skill Works

The skill connects to the Rube MCP server and uses the Xero toolkit tools to perform actions. For multi tenant setups, you should identify the correct tenant_id via XERO_GET_CONNECTIONS before proceeding. Typical flows include listing and filtering invoices, retrieving contacts, creating payments, and recording bank transactions in Xero.

When to Use It

  • Pull and filter invoices by status, date, or contact for review or export
  • Find or create customer contacts to invoice or pay
  • Add a payment to settle an invoice against a bank account
  • Record spend or money in by creating bank transactions
  • Manage multiple Xero orgs by selecting the correct tenant before actions

Quick Start

  1. Step 1: Connect to Xero via RUBE_MANAGE_CONNECTIONS and ensure the xero toolkit has an active connection
  2. Step 2: Retrieve data with XERO_LIST_INVOICES or XERO_GET_CONTACTS to verify access
  3. Step 3: Perform a transaction, e.g., XERO_CREATE_PAYMENT to apply a payment to an invoice or XERO_CREATE_BANK_TRANSACTION to record a bank entry

Best Practices

  • Ensure an active MCP connection to the Xero toolkit before any tool call
  • Use XERO_GET_CONNECTIONS first when managing multiple tenants to obtain tenant_id
  • Validate required fields for create operations: InvoiceID, AccountID, Amount for payments; Type, ContactID, BankAccountCode, LineItems for bank transactions
  • Filter with Statuses and where sparingly and prefer pagination to avoid long queries
  • Test with summaryOnly or small page sizes on initial runs and audit results after each step

Example Use Cases

  • List AUTHORISED and PAID invoices for a contact to prepare a monthly bill run
  • Search for a contact with acme and retrieve their details for invoicing
  • Create a payment to settle an invoice against a specific bank account
  • Record a bank transaction for a vendor payment using a line item with Description, UnitAmount, and AccountCode
  • Switch tenants in a multi org setup by calling XERO_GET_CONNECTIONS to identify the correct tenant_id

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers