well_get_period_ledger_export_status

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

Show which of a fiscal period's journal entries are already on the connected accounting tool and which are not, grouped by journal type, checked against the tool's own records. It sends nothing and needs no close run. Use it for a closed month: entries leave draft only when the month closes. Each tile carries `journal_type`, `entry_count`, `exported_count` and `missing_on_connector`. `missing_on_connector: null` means the tool's records were not read, so the state is unknown: never say the entries are there. `already_sent: true` means every entry is confirmed on the tool. `write_scope` says whether Well can post to the tool: `available`; `ungranted` (the connection is missing the scope to post: tell the user to reconnect); `absent` (no accounting tool is connected, or Well cannot send entries to the one connected yet). This read never sends the entries: the push stays behind the export card of the month's close. Take `fiscal_year` and `fiscal_period` from a `well_list_period_unmatched_invoices` or `well_list_periods` entry; never derive them from a calendar month yourself. **`success: false` means the status is UNKNOWN.** Never say the entries were sent on a failed read. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.