# Impact of time zones on MRR calculation

### Why time zones can influence the MRR calculation

In Fincome, invoice line items are interpreted based on their **start and end date and time**. To ensure calculation consistency, the platform automatically applies the **configured time zone** on the account (by default: **UTC +1** for France).

This means that when an invoice line for example starts on **01/31/2025 at 11pm UTC**, it is converted to **02/01/2025 at 00:00 (UTC +1)** in the MRR calculation.\
➡️ As a result, this line will be accounted for starting from **February** and not from **January**.

### Concrete example

* **Actual start date on the invoice** : 01/31/2025 at 11pm UTC
* **Applied time zone (UTC +1)** : offset of +1 hour
* **Start date interpreted in Fincome** : 02/01/2025 at 00:00
* **Result** : the MRR only appears starting in February.

### How to avoid a “gap” in MRR

If you notice a one-day shift due to the time zone:\
➡️ Simply **enter the end of the previous period as the 1st of the following month** to ensure continuity without a “gap” in MRR.

Example:

* If your previous period ends on **31/01/2025**, instead indicate **01/02/2025** as the end of the period.\
  This way, the MRR will be smooth from month to month.

### Best practices

* Check that your **invoice dates** are consistent with your **local time zone**.
* If you import data from an external tool (Stripe, Pennylane, etc.), make sure the exported dates are aligned to the same time zone.
* If in doubt, always prefer **full hours** (e.g. 00:00) to avoid one-day shifts.

***


---

# Agent Instructions: 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://fincome.gitbook.io/help-center/en/understanding-the-numbers/impact-of-time-zones-on-mrr-calculation.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.