Update to InvoiceVista Invoice Maker

{
  "description": "Review InvoiceVista businesses, product catalogs, plan quotas, and aggregate revenue, receivables, quote-pipeline and business-overview summaries through a tenant-scoped read-only MCP connector. Use when asked how much was invoiced or paid in a period, what customers owe, unpaid or overdue invoices, how many quotes were accepted, product prices or InvoiceVista plan limits — never for individual customer records, transaction execution or financial advice.",
  "included_files": [],
  "name": "billing-operations",
  "skill_md_contents": "---\nname: billing-operations\ndescription: Review InvoiceVista businesses, product catalogs, plan quotas, and aggregate revenue, receivables, quote-pipeline and business-overview summaries through a tenant-scoped read-only MCP connector. Use when asked how much was invoiced or paid in a period, what customers owe, unpaid or overdue invoices, how many quotes were accepted, product prices or InvoiceVista plan limits — never for individual customer records, transaction execution or financial advice.\nlicense: Apache-2.0\ncompatibility: Requires the InvoiceVista MCP connector (https://mcp.invoicevista.com/mcp) and an InvoiceVista account with at least one business\nmetadata:\n  author: InvoiceVista\n  version: '1.1.0'\n  repository: https://github.com/invoicevista/skills\n---\n\n# Aggregate billing operations with InvoiceVista\n\nUse the InvoiceVista MCP connector only after the user connects InvoiceVista\nand authorizes the intended organization. If OAuth fails, ask them to connect\nInvoiceVista. Never request, embed, repeat or infer an API key, password, OAuth\ntoken, payment credential, bank detail, processor id or webhook secret.\n\n## Read-only boundary\n\nEvery tool is read-only, idempotent, tenant-scoped and closed-world. The\nconnector cannot create, edit, delete, send, charge, retry, refund, settle,\ntransfer or otherwise move money. It cannot contact customers or give an\nindividualized financial decision. Direct the authorized operator to\nInvoiceVista's first-party controls for changes and to a qualified professional\nfor advice.\n\n## Identifier and tenant handling\n\nOnly owned business ids are public chaining identifiers. Resolve one with\n`list_businesses`, then reuse that exact id for summaries, catalog and plan.\nNever guess an id or treat an opaque id as authority; the InvoiceVista API\nrechecks OAuth product, scope, live user membership and organization on every\nrequest. A cross-tenant id returns not found or an authorization error.\n\nProduct rows and subscription results deliberately have no persisted record\nids because none is needed for another connector tool.\n\n## Available tools\n\n| Tool                         | Use it when someone asks…                                                                |\n| ---------------------------- | ---------------------------------------------------------------------------------------- |\n| `list_businesses`            | which businesses they invoice from; also resolves the business ID every other tool needs |\n| `get_business`               | about one business's currency, country, language or timezone                             |\n| `get_revenue_summary`        | how much was invoiced or paid in a period (at most 366 UTC days, drafts skipped)         |\n| `get_receivables_summary`    | what customers owe, what is overdue and how old unpaid invoices are                      |\n| `get_quote_pipeline_summary` | how many quotes were sent, their value and how many were accepted (at most 366 days)     |\n| `list_products`              | what the business sells and at what price                                                |\n| `get_subscription`           | which InvoiceVista plan the business is on and its limits                                |\n| `show_business_overview`     | for a one-card overview of one business                                                  |\n\n`list_businesses` and `list_products` accept at most 100 rows and return an\nopaque cursor. Do not claim completeness when `hasMore` is true.\n`show_business_overview` caps customer/invoice/payment/quote counts at 100 and\nthe product preview at 12; report each lower-bound flag. Aggregate summary\nsources cap at 500 _after_ tenant and requested-date filtering; report\n`*IsLowerBound` and `amountMissingCount` rather than treating a partial total as\ncomplete.\n\n## Customer and financial-data boundary\n\nSafe outputs can contain:\n\n- owned business id/name, currency, country, locale and timezone;\n- aggregate customer/invoice/payment/quote/product counts and status counts;\n- bounded UTC date range and as-of calendar day;\n- signed aggregate invoice, payment, quote, outstanding and overdue amounts;\n- aggregate age buckets, source/missing/lower-bound flags and optional rates;\n- product catalog name, price and tax; and\n- subscription plan name/status/frequency and quota limits.\n\nThe connector never exposes:\n\n- customer names/ids, email, phone, address, tax/government identifiers or\n  profiles;\n- individual invoice/payment/quote ids, numbers, status, exact date/time,\n  value, customer linkage or document body;\n- notes, line item names/descriptions, arbitrary search or metadata;\n- cardholder, bank account, processor/customer, settlement, credential,\n  webhook, error/debug or secret data; or\n- any money-transfer, charge, refund, retry, settlement, record write or\n  financial-advice capability.\n\nDo not ask users to paste excluded data into chat or infer a customer from an\naggregate. Offer a safe aggregate/catalog/plan read or the first-party\nInvoiceVista dashboard.\n\n## Revenue workflow\n\n1. Use `list_businesses` unless the exact owned business id is already known.\n2. Call `get_business` for currency/timezone context.\n3. Call `get_revenue_summary` with explicit inclusive `YYYY-MM-DD` UTC dates\n   when the user names a period; the maximum is 366 days. With no range, it\n   defaults to the 90 days ending today.\n4. Distinguish non-draft invoice production from recorded payments. Do not\n   call either recognized revenue or independent bank settlement. Payment\n   totals include every payment recorded in the range, whatever its status.\n5. Collection rate is null when source rows are truncated, numeric values are\n   missing or invoice production is zero. Never calculate a definitive rate\n   from incomplete aggregates.\n6. Signed negative values may represent adjustments/refunds. Describe the\n   recorded aggregate; do not infer cause or provide advice.\n\nThe revenue summary MCP App renders the same aggregate output and invoice\nstatus mix; it receives no individual records.\n\n## Receivables workflow\n\n1. Call `get_receivables_summary` for open/overdue counts, signed amounts and\n   age buckets as of the returned UTC day.\n2. Report `sourceInvoiceCountIsLowerBound` before discussing completeness.\n3. Explain `partiallyPaidCountExcludedFromAmount`: InvoiceVista does not store\n   remaining balance, so including the full invoice would overstate debt.\n   The overdue count covers invoices whose status is `OVERDUE`; a pending\n   invoice past its due date shows up in the age buckets only.\n4. Use age buckets only as aggregate operational groupings. No customer or\n   individual invoice can be resolved.\n5. Do not recommend collection action against a person, extend/deny credit or\n   initiate a charge.\n\n## Quote, catalog and plan workflow\n\nUse `get_quote_pipeline_summary` with an explicit bounded period. Draft quotes\nare omitted. Acceptance rate uses approved versus rejected decisions and is\nnull when the source is truncated or no decision exists. Do not describe\npending value as guaranteed revenue.\n\nUse `list_products` only after resolving a business. Catalog names are\noperator-provided product labels, not line descriptions from a customer\ndocument. Prices/tax are configuration and need not equal a final charge;\n`tax` is the product's stored tax value and is null when none was set.\n\nUse `get_subscription` for InvoiceVista plan capacity. A business with no\nactive/past-due persisted plan receives documented Free defaults. It never\nreturns subscription, processor product/price or payment-method ids.\n\n## Aggregate overview\n\n`show_business_overview` is the broad first safe check. It displays business\nconfiguration, aggregate counts/status counts and product preview. It does not\ndisplay individual financial dates, amounts or identifiers. Follow with the\nspecific aggregate summary rather than trying to reconstruct records from\ncounts.\n\n## Safe fallbacks\n\n- Customer or individual document request: say the connector intentionally has\n  no such tool; offer aggregate status/value counts or the first-party app.\n- Card/bank/processor/credential request: do not call a tool; explain those\n  fields never enter connector output.\n- Charge/refund/retry/settle/transfer/write request: explain all tools are\n  read-only; do not pretend a read changed state.\n- Financial advice or customer targeting: do not use aggregates to recommend\n  an individualized decision; offer factual aggregate reporting only.\n- Unrelated task: do not invoke InvoiceVista.\n\n## Interactive workspace\n\nWhen the user wants to open InvoiceVista Invoice Maker or browse visually, call `open_invoicevista` with no arguments. It opens a read-only sidebar of up to 100 businesses with explicit truncation. Select a business for its aggregate overview, revenue, receivables and quote pipeline. Existing individual customer and document restrictions still apply.\n"
}