> 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/reporting.md).

# Reporting

Tie the holding account with the rollforward, and see recognition already posted and still ahead on the waterfall.

Revenue recognition reports are built from recognition schedules on the Accrual ledger. They show what has posted, what is still sitting in holding, and what is scheduled for future periods.

Use the rollforward to tie the holding account. Use the waterfall to see the revenue that is already scheduled ahead.

***

### Open the reports

Go to **Reporting** and open **Rollforward** or **Waterfall**.

{% hint style="info" %}
This is the reporting page. Policy setup and recognition schedules live under **Accounting** → **Revenue recognition**.
{% endhint %}

***

### Revenue rollforward

The rollforward explains movement in the holding account for the recognition schedules in the report. It is the balance-sheet view of revenue recognition.

<table><thead><tr><th width="140">Column</th><th>What it means</th></tr></thead><tbody><tr><td><strong>Beginning</strong></td><td>Holding balance at the start of the range.</td></tr><tr><td><strong>Additions</strong></td><td>Amounts that entered the holding account in the range from applied sources or accrued settlement.</td></tr><tr><td><strong>Recognized</strong></td><td>Recognition entries dated in the range, including entries posted ahead when the schedule was applied.</td></tr><tr><td><strong>Adjustments</strong></td><td>Holding movement from changes such as a stop, reversal, reclass, or source amount change.</td></tr><tr><td><strong>Ending</strong></td><td>Beginning, plus additions, minus recognized, plus adjustments.</td></tr></tbody></table>

Deferred schedules debit the holding account and credit revenue. Accrued schedules do the same, which builds the holding asset.

{% hint style="info" %}
**Holding account tie-out**. Ending is the holding-account balance for the recognition schedules in the report. When the general ledger balance differs, another journal entry posted to that account outside these schedules.
{% endhint %}

On the total rollforward, Kick also splits Ending into current and non-current. Current is the portion scheduled inside the next twelve months.

***

### Revenue waterfall

The waterfall is the forward view. It shows recognition by period, so you can see what has posted and what is still ahead.

Future periods are already on the general ledger. Kick posts them when the schedule is applied, and the waterfall includes them. A schedule from a rule with **Auto confirm** off shows those periods only after you confirm the schedule. A milestone row stays unposted until you confirm that milestone.

#### Waterfall views

<table><thead><tr><th width="180">View</th><th>What it gives you</th></tr></thead><tbody><tr><td><strong>By schedule</strong></td><td>Recognition by schedule, with the schedule's customer or source detail underneath.</td></tr><tr><td><strong>By counterparty</strong></td><td>Recognition by customer or counterparty, with the schedules underneath each one.</td></tr><tr><td><strong>By start month</strong></td><td>A cohort view grouped by the month recognition starts, useful when schedules begin across different periods.</td></tr><tr><td><strong>Start month summary</strong></td><td>A compact cohort summary with booked amount, recognized periods, recognized to date, and remaining amount.</td></tr></tbody></table>

#### Open a filtered waterfall from a row

From a schedule row, open the row menu and click **Open in Waterfall report**. **Open in Rollforward report** opens the rollforward for that schedule.

***

### Slice the report

<table><thead><tr><th width="140">Control</th><th>Options</th></tr></thead><tbody><tr><td><strong>Revenue</strong></td><td>All, Deferred, or Accrued.</td></tr><tr><td><strong>Method</strong></td><td>Straight-line, Daily pro rata, Point-in-time, or Milestones.</td></tr><tr><td><strong>View</strong></td><td>By schedule, By counterparty, By start month, or Start month summary.</td></tr></tbody></table>

Click an amount to open the journal entries behind that number. Click a schedule or counterparty name to open the schedules behind that row in one view.

***

### Review the report

Recognized should match the recognition entries dated in the range, including entries posted ahead when the schedule was applied. Ending should tie to the holding account for the schedules in the report. Payment matches should clear accounts receivable or the accrued-revenue asset, not create a second revenue credit.

***

### What these reports are not

These reports are built from Kick recognition schedules. They are not an accounts receivable aging report, an RPO disclosure, ARR, MRR, or standalone selling price allocation.


---

# 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/reporting.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.