> 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/change-a-schedule.md).

# Change, pause, stop, or remove a schedule

Change the term or amount, replace the policy, or pause, stop, or remove a recognition schedule.

Change the recognition schedule when the contract changes. Edit the policy when the reusable model changes. The schedule keeps the source amount, posted periods, future periods, and remaining balance for one contract.

***

### Open the schedule

Go to **Accounting** → **Revenue recognition**, then open the **Recognition schedules** tab. Open the schedule menu to change the schedule, view journal entries, or go back to the source.

{% hint style="info" %}
**Policy edits and schedule changes are different**. Editing a policy changes the reusable model for the next schedule you apply. Changing a recognition schedule changes one applied schedule. Periods already posted stay as posted unless you choose a correction action. Schedules already applied do not pick up a later policy edit.
{% endhint %}

***

### What you can change

<table><thead><tr><th width="220">Action</th><th>Use it when</th><th>What happens next</th></tr></thead><tbody><tr><td><strong>Change this schedule</strong></td><td>The contract amount, start, end, or recognition term changed.</td><td>Unposted periods rebuild. Posted periods use the correction action you choose.</td></tr><tr><td><strong>Replace the policy</strong></td><td>The source should follow a different recognition model.</td><td>Kick replaces the schedule on that source and shows how existing entries will be handled.</td></tr><tr><td><strong>Pause recognition</strong> and <strong>Resume recognition</strong></td><td>Recognition should stop for a while, then continue later.</td><td>Posted periods stay posted. Future periods are removed while paused and rebuilt from the resume date.</td></tr><tr><td><strong>Stop schedule</strong></td><td>The contract ended, the remaining work changed, or the rest should leave the schedule.</td><td>Future recognition ends. You choose what happens to the remaining holding balance.</td></tr><tr><td><strong>Remove schedule</strong></td><td>The schedule should not exist on the source.</td><td>Future periods are removed. Posted entries are either reversed or removed, depending on the option you choose.</td></tr></tbody></table>

***

### When periods already posted

When a term or source amount change affects posted periods, Kick asks how to correct those entries. The options depend on locks and on the entries already posted.

<table><thead><tr><th width="140">Correction</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Catch up</strong></td><td>Leaves posted periods as they are and posts one adjustment in the first open period.</td></tr><tr><td><strong>Reverse</strong></td><td>Posts reversals for affected periods, then reposts the schedule. The general ledger keeps the original entries and the reversals.</td></tr><tr><td><strong>Remove</strong></td><td>Deletes affected entries and reposts the schedule. Activity is the record of what changed.</td></tr></tbody></table>

{% hint style="warning" %}
A locked period can block **Reverse** or **Remove**. Open the period in [Locks](/accountants/close-workflows/locks.md#how-to-unlock-a-period) before changing an entry that has to move.
{% endhint %}

***

### Change the source amount

Change the amount on the source: the invoice, transaction, or manual amount. Kick shows the old amount and the new amount on the schedule change. Future periods rebuild from the new amount. Posted periods follow the correction action you choose.

***

### Pause or resume

Pause recognition when future periods should stop temporarily. Entries already posted stay posted, and future periods are removed while the schedule is paused.

Resume recognition when the schedule should continue. Choose the resume date. Kick rebuilds future periods from that date, and periods before that date are not put back.

***

### Stop the schedule

Stop is for the remaining balance. Past entries stay posted. Future recognition ends, and Kick asks what to do with the amount still in holding. The menu label is **Stop schedule**.

<table><thead><tr><th width="240">Option</th><th>What happens</th></tr></thead><tbody><tr><td><strong>Accelerate recognition</strong></td><td>The remaining balance posts to the policy's revenue account now.</td></tr><tr><td><strong>Reclassify to another account</strong></td><td>The remaining balance leaves the holding account and moves to the account you choose. Kick does not credit revenue.</td></tr><tr><td><strong>Decide later</strong></td><td>The remaining balance stays in holding. Kick posts no entry.</td></tr></tbody></table>

{% hint style="warning" %}
Stop cannot be undone.
{% endhint %}

***

### Remove the schedule

Remove the schedule when the source should not have recognition at all. The menu label is **Remove schedule**. Choose whether Kick should reverse posted journal entries or remove them. In both cases, unposted future periods are deleted.

<table><thead><tr><th width="220">Option</th><th>Why use it</th><th>What happens</th></tr></thead><tbody><tr><td><strong>Reverse journal entries</strong></td><td>Use this when you want the general ledger to show the original entries and the correction.</td><td>Kick posts reversal entries for posted periods and deletes unposted future periods.</td></tr><tr><td><strong>Remove journal entries</strong></td><td>Use this when the schedule was applied in error and the entries should come out of the ledger.</td><td>Kick removes the posted entries and deletes unposted future periods. The change is visible under Activity.</td></tr></tbody></table>

{% hint style="warning" %}
Remove cannot be undone. Stop the schedule when it should stay in history. **Archive** is for the policy. On the **Policies** tab, open the policy menu and click **Archive**. It disappears from pickers, rules, and bulk **Set recognition schedule**. Schedules already applied keep recognizing. You can restore the policy later.
{% 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/change-a-schedule.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.