ERP & Finance · 41 pre-built actions
Xero integration with Nexus
Keep Xero accounting aligned with billing and operations. Invoices, payments, bank transactions and reports become governed steps, so billing events reach the books with exceptions reviewed.
Pre-built actions
What you can automate
41 pre-built Xero actions, grouped by what they work on.
41
PRE-BUILT ACTIONS
- 01Invoices and Payments actions record billing outcomes in accounting.
- 02Bank Transactions actions support reconciliation.
- 03Reports actions bring financial reports into scheduled reviews.
Workflow
How it fits into a Nexus workflow
Xero steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Xero API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Stripe payment to Xero
A Stripe payment is matched to a Xero invoice and recorded as a payment.
Bank reconciliation exceptions
Unmatched bank transactions are routed to finance with both sides attached.
Month-end report pack
Reports are pulled on a schedule and shared with the finance team.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Integration patterns
Xero integration patterns
Dedicated patterns that pair Xero with another system in one governed run.
Industry use cases
Processes that use Xero
Financial services
Payment reconciliation and exception handling
Payments reconcile into accounting automatically, and mismatches become tracked exceptions.
Enterprise
Commerce to ERP and accounting
Storefront orders reach ERP and accounting with inventory checked and exceptions reviewed.
Enterprise
Procure-to-pay exception workflow
Invoice, procurement and payment exceptions are resolved with approval across four systems.
Enterprise
Marketplace sales to accounting
Marketplace activity is reflected in NetSuite and reconciled in Xero, with differences approved by finance.
Enterprise
Unified commerce operations
Storefront and marketplace activity flows into Odoo and Xero through one governed process.
Financial services
Subscription revenue reconciliation
Billing events are compared with NetSuite and Xero, and differences are approved before correction.
Financial services
PayPal payment exception to service case
PayPal payment and subscription mismatches become approved, recorded corrections.
Enterprise
CRMConnect invoicing to accounting
CRMConnect invoices are recorded and reconciled in Xero with exceptions approved.
FAQ
Xero connector questions
- Which Xero actions are pre-built?
- Nexus includes 41 pre-built Xero actions across Invoices (13), Payments (8), Bank Transactions (10) and Reports (10).
- Can Xero start a workflow?
- Runs that use Xero start from a webhook, a schedule or another trigger source. Xero steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Xero API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Stripe connector
Products, core resources and billing.
- PayPal connector
Transactions, payouts and subscriptions.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Xero fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.