Commerce & Finance integration
Reconcile Stripe billing into Xero accounting.
Stripe payment, subscription and invoice events start a governed run that looks up the customer and invoice, records the accounting entry in Xero and routes exceptions to finance.
The problem
Why Stripe + Xero needs a governed process
Billing happens in Stripe and the books close in Xero. Matching payments, refunds and subscription changes by hand delays month end and hides mistakes.
Responsibility
How the systems divide responsibility
Billing engine
Stripe
Products, customers, payments, subscriptions and billing invoices.
Accounting record
Xero
Invoices, payments, bank transactions and financial reports.
Capabilities
What Nexus orchestrates
Pre-built action groups used in this pattern. Anything else runs through an API, protocol or database step, or Rules + Code, in the same workflow.
Stripe
43 ACTIONS
- Billing19
- Core Resources16
- Products8
Xero
41 ACTIONS
- Invoices13
- Payments8
- Bank Transactions10
- Reports10
Architecture
One governed run across both systems
How work starts
Stripe
Stripe is a trigger source, so a billing event can start the run directly. Xero steps run as pre-built actions.
When a pre-built action does not cover it
Workflow patterns
What teams run across Stripe + Xero
01
Payment to Xero payment
A Stripe payment event is matched to the Xero invoice and a payment is recorded against it.
02
Subscription invoice to accounting
A Stripe billing invoice creates or updates the matching Xero invoice.
03
Bank transaction reconciliation
Xero bank transactions are compared with Stripe payouts and differences raised for review.
04
Refund and dispute handling
Refunds and disputes outside policy pause for finance before any accounting entry changes.
Direction and ownership
Which way each change moves
Billing events flow from Stripe to Xero. Xero remains the accounting record, and Stripe remains the billing record.
Stripe Xero
Payment, invoice and subscription context for the accounting entry.
Xero Stripe
Rarely needed. Reconciliation status is kept in the run record.
Control
Approvals and exception handling
Human approval
Finance approves entries that would change revenue outside policy, unmatched payments and refunds above a threshold.
Exceptions
- Unmatched customers or invoices route to a finance queue.
- Currency or amount mismatches stop the write and record both values.
- Xero API errors are retried and surfaced.
Security, audit and deployment
Every run leaves a reviewable record
- The Stripe event payload.
- Lookup and matching results.
- Finance decisions on exceptions.
- The Xero entry created and its response.
Credentials for Stripe and Xero are held in the vault and used only by the steps that need them. Role-based permissions decide who can edit, approve and run the workflow. Nexus runs on premises, in private cloud or air-gapped, so the execution record stays inside your deployment boundary. Governance and audit
Participating connectors
The connectors behind this pattern
Related
Continue from here
- Payment and subscription events into CRM and ERP
Billing events reflected in downstream systems under one record.
- Compliance evidence
Evidence produced by the work itself.
- Enterprise integration
Connectors, interfaces and code in one platform.
- Integration explorer
Add more systems to this combination.
FAQ
Stripe + Xero questions
- Can a Stripe event start the run?
- Yes. Stripe is a trigger source in Nexus.
- Does Nexus replace our reconciliation process?
- It runs the matching you define and routes what does not match to people. Your accounting policy stays in charge.
- What about PayPal?
- PayPal transactions, payouts and subscriptions have their own pre-built actions and can join the same workflow.
Integration review
Discuss this integration
Bring your Stripe and Xero process. We will map ownership, approval and the steps each system needs.