> ## Documentation Index
> Fetch the complete documentation index at: https://docs.commander.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing recurring transactions

> Create a schedule in Commander Finance, confirm or dismiss detected candidates, and pause, edit, or delete a schedule as your commitments change.

Schedules record your standing commitments in Commander Finance. Open them from **Recurring** under Transactions in the sidebar. See [Recurring transactions](/core-concepts/recurring-transactions) for what a schedule holds.

## Creating a schedule

<Steps>
  <Step title="Open the schedule form">Tap **New schedule**.</Step>
  <Step title="Describe the commitment">Fill in **Name**.</Step>

  <Step title="Set the amount and direction">
    Enter an **Expected amount**, then pick **Spending** or **Income**. A
    signed readout below the field previews the result, so you can confirm
    the direction before saving.
  </Step>

  <Step title="Choose how often it recurs">
    Pick a cadence in **Repeats**.
  </Step>

  <Step title="Say when it starts">Set **First expected date**.</Step>

  <Step title="Set an end, if it has one">
    Leave the end condition empty for an open-ended commitment, or set an
    **End date** or a **Number of occurrences**.
  </Step>

  <Step title="Link it, if you want">
    Under the optional disclosures, connect the schedule to a merchant, an
    account, or a budget line so its activity rolls up with the rest.
  </Step>
</Steps>

The schedule joins the list under **Active**, grouped by when it's next due.

## Reviewing detected schedules

When Commander spots a repeating charge, it proposes a candidate in the review queue above the list. Each candidate row shows its cadence, expected amount, next expected date, and a confidence rating of High, Medium, or Low. Open the candidate to see the rest of the evidence, including how many times it has been seen.

* **Confirm** turns the candidate into an active schedule.
* **Dismiss** rejects it.

To work through several at once, select them with the per-row checkboxes and use the bulk confirm or bulk dismiss action. Bulk dismiss asks for confirmation first, since the only way back is re-running detection.

To reconsider a dismissed candidate, choose **Reset suggestions** from the overflow menu. It clears every dismissed candidate and detects again, so rejected suggestions can reappear.

## Changing a schedule

Open a schedule from its row, or use the row's overflow menu:

* **Edit**—change the name, amounts, cadence, end condition, and links. The start date is fixed once the schedule exists and shows as read-only.
* **Pause**—stop tracking without losing history. **Resume** starts it again, and also works on a schedule that has ended.
* **Delete**—remove the schedule after a confirmation dialog. The dialog offers **Also remove upcoming pending transactions created by this schedule**, checked by default. Transactions that already happened are always kept.

## Related

* [Recurring transactions](/core-concepts/recurring-transactions)
* [Creating a new transaction](/how-to/create-transaction)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.