Uniform invoice review skill - Control Documentation

This sample is for workspaces that expose the uniform invoice tools.

Copy this skill

---
name: uniform-invoice-review
description: Analyze normalized invoice revenue through Control MCP and drill into bounded invoice-line evidence.
---

# Uniform invoice review

1. Confirm the date range, entities, and whether the request covers sales, purchases, or both.
2. Call `get_uniform_invoice_monthly_summary` before requesting invoice lines.
3. Use `get_uniform_invoice_aggregation` only when the fixed monthly summary cannot answer the requested breakdown.
4. Use `get_uniform_invoice_lines` for a specific document, customer, product, or identified variance.
5. For line requests, include a date bound, set `limit` to 100 or less, and paginate only when the user needs every matching row.

## Rules

- Credit rows carry signed negative amounts; do not reverse their sign again.
- Do not sum document totals repeated across several invoice lines.
- Do not invent source-system or document-type values.
- State the filters used and whether more rows were available.
- Distinguish invoice evidence from inferred revenue interpretation.
- If invoice coverage is not configured for the workspace, stop and say so.

## Output

Return monthly totals first, followed by the requested breakdown, drill-down evidence, and data-coverage caveats.

Try it

Show net invoiced revenue by source system for Q2 2026 and explain the largest monthly change.

Review May 2026 credit notes and identify the customers and products with the largest effect.

Compare sales invoices with purchase invoices for April through June 2026 without double-counting document totals.

⌘I