01
MRR you can audit
New, expansion, contraction and churn MRR, each traceable to the underlying invoices.
MRR movements
Finance
Xero + Kimo
Accounting, bank feeds and invoices. Turn invoices, charges and subscriptions into MRR, retention and margin that match your books.
- Auth
- OAuth 2.0
- Sync
- Daily
- Setup
- ≈ 2 min
Live demo workspace with fictional data · no signup, no credentials needed
kimo / connectors / xeroSyncing
Sync logdaily
- Succeeded:invoices+290 rowsnow
- Succeeded:accounts+1,909 rows2m ago
- Succeeded:transactions+1,852 rows4m ago
- Succeeded:invoices+1,071 rows6m ago
Rows synced · 30 days
56.2M
Workspaces
8%
What you can do
What teams build with Xero
Xero on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.
02
Net revenue retention
Cohort NRR by plan and segment, refreshed automatically for the board pack.
NRR by cohort
03
Failed payment alerts
Catch spikes in failed charges or overdue invoices before they become churn.
Dunning watch
Objects & tables
Exactly what gets synced
Kimo maps Xero into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.
3 tables · 14 fields
Tables
invoices
Incremental≈ 2,730,000 rows| Field | Type | Notes |
|---|---|---|
| id | id | Primary key |
| customer_id | id | References customer |
| amount_due | decimal | Measure |
| status | enum | Low-cardinality dimension |
| due_date | date | Incremental cursor |
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model
From raw Xero tables to a certified metric
A starter model Kimo suggests the moment Xero is connected. Every join is editable.
Xero · Recurring revenue
Invoices and subscriptions joined with accounts to produce MRR movements.
- Xeroinvoices
- PostgreSQLaccounts
- HubSpotdeals
Model
customer_id · account_id
Measuresmrrnew_customers
MRR · last 30 days
$215.9K+1.8% wk/wk
Fictional data · hover the chart for daily values
Setup
Connect Xero in 2 min
No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.
- 1
Click “Connect Xero”
You are redirected to Xero to sign in. Kimo never sees your password.
- 2
Approve read-only scopes
Kimo requests the narrowest scopes available. You can revoke access at any time.
- 3
Pick accounts
Choose which accounts to sync. Add more later without reconnecting.
- 4
First sync and schema mapping
Kimo backfills history, maps invoices and suggests joins with your other sources.
Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.
Connect Xero
Step 2 of 3 · Kimo demo workspace
Kimo wants read-only access to your Xero account
read-only accessread
Accounts
- Northwind · Xero
- Northwind EU · Xero
Read-only access
Illustration only · placeholder values, never real secrets
Works great with
Pair Xero with the rest of your stack
Kimo suggests these joins automatically when both sources are connected.
FAQ
Xero questions, answered
By default Kimo syncs Xero daily. You can change the schedule per table, or trigger a sync manually from the connector page.
Xero · OAuth 2.0 · Daily
See your Xero data in Kimo in 2 min.
Try it on the live demo workspace first, then connect your own account when you are ready.