> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/accountants/schedules/revenue-recognition/run-close-with-mcp.md).

# Run revenue recognition close with MCP

Review contract context outside Kick, compare it to recognition schedules, and stop before anything posts.

Revenue recognition close breaks down when the facts live outside the accounting system. Contract terms are in PDFs, amendments are in email, milestones are in project tools, billing is in Stripe, and the schedule may still be in a spreadsheet.

Kick keeps the books: policies, recognition schedules, journal entries, rollforward, and waterfall. With MCP, Claude, ChatGPT, Gemini, or Cursor can help with the work around the books: gather contract context, compare it to Kick, find missing schedules, prepare changes, and stop for your review before anything posts.

{% hint style="info" %}
**Connect Kick directly**. Kick is not currently available from the ChatGPT or Claude marketplace. Add Kick directly as a custom MCP server in Claude, ChatGPT, Gemini, Cursor, or another MCP-compatible tool using `https://use.kick.co/mcp`.

→ [Connect custom AI tools](https://docs.kick.co/ai/mcp/connectors/connect-custom-ai-tools)
{% endhint %}

***

### MRR and ARR

The rollforward and the waterfall are not an MRR or ARR report. The best way to build one is with the [Kick to Google Sheets](/accountants/setting-up/integrations/google-sheets.md) add-on, then the [MRR and ARR report](https://agentbuilder.club/agents/advisory/mrr-arr-report) skill. The add-on keeps the sheet live. The skill reads revenue from the books and builds the report on top of it.

***

### Recommended close flow

<table><thead><tr><th width="72">Step</th><th width="200">Workflow</th><th>What to ask the assistant to do</th></tr></thead><tbody><tr><td>1</td><td>Collect outside context</td><td>Contracts, amendments, CRM deals, Stripe exports, project milestones, client emails, Slack threads, and old revenue spreadsheets.</td></tr><tr><td>2</td><td>Compare to Kick</td><td>Policies, invoice lines, payments, manual sources, recognition schedules, rollforward, waterfall, and journal entries.</td></tr><tr><td>3</td><td>Find exceptions</td><td>Missing schedules, wrong policy, stale term, unconfirmed milestone, stopped schedule with balance, and duplicate recognition risk.</td></tr><tr><td>4</td><td>Prepare changes</td><td>Draft the schedule, policy application, milestone update, source split, or schedule change, then stop for review.</td></tr><tr><td>5</td><td>Close in Kick</td><td>Review the rollforward, review the waterfall, and drill into the journal entries before close is approved. Confirm any milestone that is due, and confirm rule-suggested schedules that were not auto-confirmed.</td></tr></tbody></table>

{% hint style="warning" %}
Start read-only. When a workflow prepares a change in Kick, review the preview before you confirm it.
{% endhint %}

***

### Where MCP helps most

Use MCP where revenue recognition depends on context that is not yet structured inside Kick.

<table><thead><tr><th width="280">Pain point</th><th>How Claude, ChatGPT, Gemini, or Cursor can help</th></tr></thead><tbody><tr><td>Contracts are not structured data</td><td>Ask Claude, ChatGPT, Gemini, or Cursor to read contracts, amendments, order forms, and spreadsheets, then draft the schedule structure for review.</td></tr><tr><td>Revenue schedules live in spreadsheets</td><td>Compare an existing spreadsheet schedule to Kick and identify what needs to be migrated, updated, or left alone.</td></tr><tr><td>Sales terms do not always match billing</td><td>Compare CRM deal terms, invoice lines, Stripe charges, and Kick schedules to catch mismatches before close.</td></tr><tr><td>Milestones are tracked outside accounting</td><td>Check project tools for milestone completion, then prepare the matching recognition update in Kick.</td></tr><tr><td>Contract changes are easy to miss</td><td>Scan Slack, email, CRM notes, or uploaded amendments for cancellations, pauses, renewals, and scope changes.</td></tr><tr><td>Duplicate recognition risk is real</td><td>Look for invoice-based and payment-based schedules tied to the same customer contract and flag possible double recognition.</td></tr><tr><td>Close review is fragmented</td><td>Turn policy coverage, missing schedules, pending confirmations, stopped schedules, and report tie-outs into one close checklist.</td></tr></tbody></table>

***

### Start with policy coverage

Before close, check whether annual contracts, setup fees, retainers, milestone billing, and one-time services have the right policies.

{% hint style="info" %}
**Prompt**. Review the active revenue recognition policies in Kick. Group them by use case: annual subscription, implementation fee, retainer, milestone billing, and one-time service. Flag any revenue pattern that appears in recent invoices or payments but does not have a matching policy.
{% endhint %}

***

### Find revenue sources missing schedules

Use this during close to find posted invoices, invoice lines, payments, and manual sources that look like revenue but are not yet on a recognition schedule.

{% hint style="info" %}
**Prompt**. For the current close period, find posted invoices, invoice lines, payments, and manual sources that look like revenue but do not have a recognition schedule. Group by customer, source type, amount, and likely policy. Do not apply anything yet.
{% endhint %}

***

### Draft schedules from contracts or spreadsheets

Use this when a client still manages revenue recognition in a spreadsheet, or when a new contract has multiple revenue components.

{% hint style="info" %}
**Spreadsheet prompt**. Read the attached revenue schedule spreadsheet and compare it to recognition schedules in Kick. For each contract, show what already exists, what is missing, and what schedule should be created for the remaining balance. Stop before applying changes.
{% endhint %}

{% hint style="info" %}
**Contract prompt**. Read this contract and draft the recognition schedule: separate setup fees, annual subscription, and milestone payments. Map each component to the right Kick policy and show the proposed source amount, start date, method, and remaining balance before creating anything.
{% endhint %}

***

### Review schedules before posting

Close review should catch automation output, pending confirmations, and schedules where the outside contract context changed.

* **Rule-suggested schedules**. List the source, policy, amount, start date, and reason the rule matched.
* **Periods and milestones ready to confirm**. Group by customer and policy, with source amount, amount to recognize, remaining balance, and missing support.
* **Contract changes**. Compare Kick schedules to Slack, email, CRM notes, amendments, or project management updates for cancellations, pauses, extensions, scope changes, or milestone completion.

***

### Tie reporting before close

Use the final review to explain the rollforward, read the waterfall, and identify schedules that need accountant review before the period is closed.

{% hint style="info" %}
**Prompt**. Review the revenue rollforward and waterfall for the close period. Tie the ending holding balance to the schedules in the report, identify the largest movements, and list any schedule where posted revenue, remaining balance, or source amount looks inconsistent.
{% endhint %}

***

### Full close review prompt

{% hint style="info" %}
Run revenue recognition close review for Acme LLC for January 2026. Start read-only. Pull recognition schedules, revenue policies, rollforward, waterfall, posted invoices, and payments. Then compare them to the attached contract tracker and recent CRM amendments. Flag revenue sources with no schedule, schedules using a policy that does not match contract terms, contracts in the tracker missing from Kick, schedules with remaining balance after cancellation or expiration, milestones that appear complete outside Kick but are not confirmed, possible duplicate recognition between invoice and payment sources, and rollforward or waterfall amounts that need review. Return a close checklist with source IDs and recommended next steps. Do not apply changes until I approve a preview.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/accountants/schedules/revenue-recognition/run-close-with-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.