How do you analyze Wise balances and transfers in Metabase?

{
  "mcpServers": {
    "wise": {
      "command": "npx",
      "args": ["-y", "@aiwerk/mcp-server-wise"],
      "env": { "WISE_API_TOKEN": "your-personal-api-token" }
    }
  }
}

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

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

Create a polished Metabase dashboard for Wise 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 Wise to Metabase for multi-currency balances, transfers, fees, FX exposure, settlement speed, and cross-border cash 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 Wise; 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 currency; Base-currency cash position; Transfers in flight; FX fees this month.
2. Operations: Pending and delayed transfers; Upcoming recipient payments; Statement activity; Failed or refunded transfers.
3. Controls and reconciliation: Transfer-to-statement exceptions; Unexpected fee variance; Duplicate recipient payments; Stale balances.
4. Planning and trends: Currency exposure; FX fee trend; Cash needs by currency; Corridor volume and cost.

Suggested models: modeled_wise_balances, modeled_wise_statement_lines, modeled_wise_transfers, modeled_wise_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
  balance_date,
  currency,
  balance_amount,
  reporting_fx_rate,
  balance_amount * reporting_fx_rate AS reporting_currency_value
FROM modeled_wise_balances
WHERE balance_date = (SELECT MAX(balance_date) FROM modeled_wise_balances)
ORDER BY ABS(balance_amount * reporting_fx_rate) DESC;

Compare realized fees and completed delivery time without treating transfer creation as settlement.

SELECT
  source_currency || ' -> ' || target_currency AS corridor,
  COUNT(*) AS completed_transfers,
  SUM(fee_reporting_currency) AS fees,
  AVG(EXTRACT(EPOCH FROM (completed_at - created_at)) / 3600.0)
    AS avg_delivery_hours
FROM modeled_wise_transfers
WHERE transfer_status = 'outgoing_payment_sent'
GROUP BY 1
ORDER BY fees DESC;