well_list_missing_invoices

io.github.WellApp-ai/well-mcp · Verify this server

List the supplier invoices a past period is still missing — the settled spend whose invoice has not been collected, one row per counterparty, exactly as the Well app's expense-invoices card shows them. Use it for "which invoices am I missing for <month>?" and as the input to fetching them. Name the period ONE way: `{ calendar_year, calendar_month }` (the calendar month, e.g. June 2026 → 2026, 6), `{ fiscal_year, fiscal_period }`, or `periods: [{ calendar_year, calendar_month }, …]` for SEVERAL months in one call (1-12) — or name NO period at all to use the months the user selected on the period card this session (well_list_periods → the user clicks → well_switch_workspace records them). With no period named and no months selected, the call refuses and tells you to run the period step first. Every month must have ended — a current or future month is refused, and so is the adjustment period (13). Duplicate months are refused. COST: there is no batch endpoint, so each named month is a separate read of that month's spend. Ask for the months the user actually named, not a whole year "to be safe". Returns `rows` — one per counterparty PER MONTH, oldest month first, each tagged with `calendar_year`, `calendar_month` and `period_label` — plus `name`, `tx_count`, `base_total_amount` in `base_currency`, `mode`, `suggested_action`, `matched_provider_name`, `matched_connector_service_id`, `proof_task_id`, `acquisition_status`. `months` carries each month's totals (rows are NOT repeated there — group `rows` by their tag instead), `periods_covered` names the months in the result, and `transaction_count`, `row_count`, `group_count` and `dropped_groups` are totals across every month read. `dropped_groups` is the spend that produced no row: party-less bank operations, unresolved counterparties, unnamed companies. The single-month fields `calendar_year`, `calendar_month`, `fiscal_year`, `fiscal_period` and `period_label` appear ONLY when the call named exactly one month. `mode` is what the card offers for that row: `agent` (a browser agent can collect it from the supplier portal), `connect` (connect the named service and Well fetches it), `upload` (the user supplies the file). Present it per row so the user knows what to do for each supplier. Only CATEGORIZED expense transactions are considered — uncategorized spend is not listed, so poor categorization coverage under-reports the gaps; disclose the `hints`. This tool only reads. It does not mint tasks, start a close, connect anything, or fetch any invoice. Call this directly — no other tool call is needed first (workspace is resolved from the caller's authorized token, same as every other well_* tool).