Get statement import result
well_get_statement_import_resultRead the outcome of a bank-statement upload started with well_create_statement_upload, by the document_id that tool returned.
well_create_statement_upload already renders a card from its own result — this tool does not create or redraw it. Call it once, shortly after the client has uploaded the file bytes, to learn what happened. The card refreshes itself as extraction and promotion complete, so a later call here narrates the current state in chat; it never advances or re-renders the card.
status "not_found_yet": the upload has not landed yet — a NORMAL result right after minting the slot, not an error. Poll again once the file has been uploaded.
status "processing": the file is uploaded and the statement is still being extracted / promoted.
status "imported" | "needs_account" | "duplicate" | "skipped" | "failed": the terminal outcome. On "imported", matched_count / review_count / minted_count / already_present_count report the promotion's own snapshot counts, taken once at import time and covering every promotable line of the file disjointly; null on any of them means the row predates count tracking — treat as unknown, never as 0.
recordslists the minted transactions only — matched or ambiguous lines link an existing transaction and are excluded;graphis the frozen record graph for the same snapshot;records_urlopens the workspace's transactions table.
This tool reads only — it changes nothing.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes | The document_id well_create_statement_upload returned — pre-allocated at mint, before the upload lands. | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | ||
| error | No | ||
| graph | No | The frozen record graph for this import, taken from the same snapshot as `records`. Never present on "processing" or "not_found_yet". Like `records`, its counterparty fields are null (frozen before resolution runs) — see `records_url` for the live values. | |
| status | No | ||
| records | No | Transactions this import minted as new rows — matched or ambiguous lines link an existing transaction and are excluded. Present only on a terminal "imported" result that carries a snapshot. The snapshot freezes at mint time, so `counterparty` is always null here — resolution runs asynchronously after import; open `records_url` for the live resolved value. | |
| success | Yes | ||
| document_id | No | ||
| imported_at | No | ||
| records_url | No | Login-gated deep link to the workspace's transactions table — opened on the first minted record when `records` is non-empty, otherwise the plain table. | |
| minted_count | No | Lines minted as new transactions. Absent means the row predates count tracking — treat as unknown, never as 0. | |
| review_count | No | Lines skipped as an ambiguous cross-connector match, pending review. Absent means the row predates count tracking — treat as unknown, never as 0. | |
| matched_count | No | Lines linked to an existing cross-connector transaction. Absent means the row predates count tracking — treat as unknown, never as 0. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| already_present_count | No | Lines an earlier import already carried — a partial-overlap re-export mints only the new lines, so the four counts cover the file's promotable lines. Absent means the row predates count tracking — treat as unknown, never as 0. | |
| statement_extraction_id | No |