How do you build Xero accounting dashboards in Metabase?

{
  "mcpServers": {
    "xero": {
      "command": "npx",
      "args": ["-y", "@xeroapi/xero-mcp-server@latest"],
      "env": {
        "XERO_CLIENT_ID": "your-client-id",
        "XERO_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a scoped Xero export - creates a table and a model
mb upload csv --file xero-export.csv --collection "Finance & Accounting"

# Refresh the same table later
mb upload replace <table-id> --file xero-export.csv

Create a polished Metabase dashboard for Xero finance analytics.
Work end to end: find existing modeled data first; if none exists, load a minimal
read-only snapshot or describe the warehouse sync required.

Goal: Connect Xero to Metabase for invoices, bills, payments, bank transactions, cash flow, AR aging, budget, and management reporting.

Inspect before querying:
- Inspect actual tables, column names, currencies, status values, and timestamps.
- Do not assume the source schema matches this guide exactly.
- Reconcile source totals before publishing any finance KPI.

Important:
- Do not claim Metabase connects natively to Xero; it reads a
  supported database or CLI-uploaded tables.
- Keep native amount, native currency, and reporting-currency amount separate.
- Distinguish authorization, posting, payment, settlement, and reconciliation
  states where the source exposes them.
- Use stable business keys and apply updates/deletes during incremental syncs.
- Exclude account numbers, personal data, and secrets from broad dashboards.
- Only build cards whose required fields and history are actually present.

Dashboard sections:
1. Finance overview: Cash balance and movement; Revenue and gross margin; Open receivables; Bills due.
2. Operations: Overdue invoices; Upcoming bills; Payments by channel; Customer and vendor concentration.
3. Controls and reconciliation: Unreconciled bank transactions; Invoice-to-payment exceptions; Duplicate contacts; Tracking-category coverage.
4. Planning and trends: Budget vs. actuals; 13-week cash outlook; Expense trend; Collection forecast.

Suggested models: modeled_xero_invoices, modeled_xero_payments, modeled_xero_bank_transactions, modeled_xero_gl.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. State refresh time, reporting
currency, accounting basis, and any reconciliation caveats.

SELECT
  CASE
    WHEN CURRENT_DATE - due_date <= 0 THEN 'Current'
    WHEN CURRENT_DATE - due_date <= 30 THEN '1-30 days'
    WHEN CURRENT_DATE - due_date <= 60 THEN '31-60 days'
    WHEN CURRENT_DATE - due_date <= 90 THEN '61-90 days'
    ELSE '90+ days'
  END AS aging_bucket,
  SUM(amount_due) AS open_amount
FROM modeled_xero_invoices
WHERE invoice_type = 'ACCREC' AND amount_due > 0
GROUP BY 1
ORDER BY MIN(GREATEST(CURRENT_DATE - due_date, 0));

Keep invoice issue month separate from payment month to expose collection timing.

SELECT
  date_trunc('month', invoice_date) AS invoice_month,
  date_trunc('month', payment_date) AS payment_month,
  SUM(payment_amount) AS collected_amount
FROM modeled_xero_invoice_payments
WHERE payment_status = 'AUTHORISED'
GROUP BY 1, 2
ORDER BY 1, 2;