corestack_ billing_ invoices_ list
Invoices.
When to use it
Page through a billing account's invoices, newest first, optionally by status and with their lines.
Through the REST API (/api/corestack/billing/…) the account is account, as on the Billing pages; account_id, this tool's name, is accepted there too as its alias.
Ask for it
Using the Corefinity MCP server, call corestack_billing_invoices_list with overdue true, issued_from 2026-01-01. (Invoices.) Tell me what it returned.Inputs
One of your company's billing accounts (corestack_billing_account_get gives its id); omitted, the company's default account. At least 1.
next_cursor from the previous page. Up to 20 characters.
Issued on or after this day (YYYY-MM-DD). Format: date.
Issued on or before this day; a range that ends before it starts is refused. Format: date.
Defaults to 25. 1 to 100.
Only invoices past their due day with something left to pay.
An invoice number, or part of one. Up to 100 characters.
Up to 7 items.
opencollectingpaidunpaidvoidrefundedwritten_offlinesThese are the Invoices page's filters and GET /api/corestack/billing/invoices's, with the same checks. total counts the
invoices the status and filters choose, whatever the cursor (the page's "1–25 of N").
Example call
{
"name": "corestack_billing_invoices_list",
"arguments": {"overdue": true, "issued_from": "2026-01-01"}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | fields names the field with the page's message: a status you cannot see, a day that is not YYYY-MM-DD, or issued_to before issued_from. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |