> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/syntax/timing-syntax/timing-modal-overview.md).

# Timing Modal Overview

This article explains the **Timing modal** in Model Reef.

You will learn:

* Where the Timing modal is used.
* Which fields live inside it.
* How it connects to accrual, payment timing and schedules.

The Timing modal is the main UI surface for configuring when things happen in the model.

{% stepper %}
{% step %}

### Where the Timing modal appears

You will see the Timing modal when you:

* Open a variable in the **Variable Editor** and click the **Timing** section.
* Use presets that include timing or payment term settings.
* Review imported variables where payment terms were inferred.

The modal opens as a focused panel so you can adjust timing without losing context.
{% endstep %}

{% step %}

### What the Timing modal controls

The Timing modal controls three core aspects:

* **Accrual timing**
  * When revenue or expense is recognised in P\&L.
  * Driven by start date, end date, frequency and schedules.
* **Cash timing**
  * When cash is actually paid or received.
  * Driven by payment terms and delays.
* **Patterning across periods**
  * Whether values are spread evenly or follow a schedule or seasonal pattern.

Together, these settings determine the link between P\&L, Cashflow and working capital.
{% endstep %}

{% step %}

### Main sections inside the modal

The Timing modal usually contains sections such as:

* **Start and end dates**\
  The first and last dates that accrual can occur.
* **Frequency and schedule**\
  Whether the variable occurs daily, weekly, monthly or on a custom schedule.
* **Payment terms and delays**\
  How long after accrual cash is paid or received.
* **Seasonality inputs**\
  Optional seasonal patterning on top of the base frequency.
* **Preview**\
  A small chart or grid showing how accrual and cash timing play out over the model horizon.

Each section contributes to the final timing behaviour.
{% endstep %}

{% step %}

### Relationship with the timing engine

The modal is a user interface for the underlying timing engine. When you save changes:

* The engine recalculates accruals per period.
* It recalculates receivables and payables.
* It updates cashflows, working capital and statement outputs.

You do not need to write timing formulas. You just configure the fields in the modal.
{% endstep %}

{% step %}

### Best practice for using the Timing modal

{% hint style="info" %}
To use the Timing modal effectively:

* Start by confirming the correct start and end dates.
* Choose a frequency that matches the real world pattern.
* Set payment terms that reflect contract reality.
* Add seasonality only where it matters, to avoid unnecessary complexity.
* Use the preview to confirm that the pattern matches your expectations.

Small changes in timing can have large impacts on cash, so treat this modal as a core modelling control.
{% endhint %}
{% endstep %}
{% endstepper %}

***

## Related articles

* [Viewing Scenario Differences](/syntax/scenario-syntax/viewing-scenario-differences.md)
* [Timing Preview](/syntax/timing-syntax/timing-preview.md)
* [CSV Import](/help/importing-and-data-inputs/csv-import.md)
* [Build an Investor Update Pack](/how-tos/dashboards-and-reporting/build-an-investor-update-pack.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.modelreef.io/syntax/timing-syntax/timing-modal-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.