How do you analyze Airwallex finance data in Metabase?

{
  "mcpServers": {
    "airwallex": {
      "type": "http",
      "url": "https://mcp.airwallex.com/mcp"
    }
  }
}

# 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 Airwallex export - creates a table and a model
mb upload csv --file airwallex-export.csv --collection "Finance & Accounting"

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

Create a polished Metabase dashboard for Airwallex 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 Airwallex to Metabase for global-account balances, collections, payouts, FX, card spend, and settlement dashboards.

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 Airwallex; 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: Balance by account and currency; Collections and payouts; Transfers in flight; FX and payment fees.
2. Operations: Pending payouts; Failed collections; Settlement lag; Card spend awaiting review.
3. Controls and reconciliation: Account-to-ledger exceptions; Duplicate payout candidates; Unexpected FX variance; Webhook or sync freshness.
4. Planning and trends: Liquidity by currency; Cross-border fee trend; Settlement forecast; Payment corridor mix.

Suggested models: modeled_airwallex_balances, modeled_airwallex_cash_movements, modeled_airwallex_settlements, modeled_airwallex_fx_cost.

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
  source_currency || ' -> ' || destination_currency AS corridor,
  COUNT(*) AS transfers,
  SUM(source_amount) AS source_volume,
  SUM(fee_amount_reporting_currency) AS fees,
  ROUND(100.0 * SUM(fee_amount_reporting_currency)
    / NULLIF(SUM(source_amount_reporting_currency), 0), 2) AS fee_rate_pct
FROM modeled_airwallex_cash_movements
WHERE movement_type IN ('PAYOUT', 'CONVERSION')
GROUP BY 1
ORDER BY fees DESC;

Keep native balances visible and translate them with an explicit reporting rate.

SELECT
  balance_date,
  currency,
  available_amount,
  available_amount * reporting_fx_rate AS reporting_currency_amount
FROM modeled_airwallex_balances
WHERE balance_date = (SELECT MAX(balance_date) FROM modeled_airwallex_balances)
ORDER BY ABS(available_amount * reporting_fx_rate) DESC;