--- title: "How to synchronize monthly changes with Visualtime?" slug: "1730373613" tags: ["Integrations"] updated: 2026-11-10T12:24:56Z published: 2026-11-10T12:24:56Z canonical: "help.ila.cegid.com/1730373613" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.ila.cegid.com/llms.txt > Use this file to discover all available pages before exploring further. # How to synchronize monthly changes with Visualtime? - [x] PT - [ ] ES - [ ] AO - [ ] CV - [ ] MZ - [ ] ST - [ ] GW - [x] Professional - [x] Executive - [x] Public Sector - [ ] Omnia - [x] Evolution --- Integration with the [Cegid Visualtime](https://www.cegid.com/ib/pt/produtos/software-gestao-tempo-visualtime/) time management system ensures that **monthly changes** are successfully synchronized between the two applications > [!WARNING] > This integration must be [configured in both applications](/primavera/docs/en/1730372321), and only works for [synchronized employees](/primavera/docs/en/1730373006). --- ## How It Works This process assumes the typical **monthly, periodic, and continuous** synchronization, meaning that, once synchronization is started, you must ensure an **uninterrupted sequence** for the process to be as automatic and accurate as possible. The synchronization interval can **automatically be extended** whenever there are changes to periods prior to the one specified that were made after the previous synchronization, i.e., if there are monthly changes in Visualtime prior to the interval's start date, these are automatically reflected in the ERP. With the **Exclude Prior Period Settlements** option enabled, the system only considers the monthly changes that occurred during the import period when importing. If you choose to **disable** this option, the system **automatically** synchronizes changes to periods prior to the import's start date that occurred after the last import, i.e., changes to periods prior to the import's start date that have not yet been synchronized. **Synchronizing Extended Leaves and Absences** When importing **extended leaves** from Visualtime (for example: prolonged sick leave), the system imports them as **extended leaves** in the ERP, except for extended leaves lasting **one day**, which are imported as absences in the ERP. Visualtime's **daily leaves** are synchronized as **absences** in the ERP. This process assumes that **extended leaves** are synchronized in full, i.e., for the **entire period** and not just for the synchronization period. Daily leaves (absences) are synchronized only for the synchronization period. Synchronizing extended leaves assumes a **full-time leave**, and no other leaves are considered during that period. As for **daily leaves**, when these correspond to: - the **entire day's hours**, it's automatically converted to a **full day**; - **half a day**, it's automatically converted to **½ day.** For vacation, whenever the recorded duration is **less than a full day**, the system automatically considers it **½ day of vacation.** Note that it's converted to hours in any other case. So, the leave types must be **correctly configured** to allow this integration. **Note**: vacation is imported as absences. Therefore, when recording vacation in Visualtime, you must make sure the occurrence type is **Extended Leaves.** **Merging consecutive leaves** When the **same leave** is recorded in Visualtime over **consecutive periods** (with no days in between), the ERP **automatically merges these records into a single leave.** To do this, the system checks **whether there is already** a leave of the same type in the ERP whose end date is exactly the day before the new leave's start date. If there is, the previous leave's end date is updated instead of a new one being added. This update is only possible when the existing leave is in the **Entered** status. If the previous leave is in the **Finished** status, the new leave is not merged, and the situation is logged in the integration *logs*. **Synchronizing Overtime** Overtime synchronization is always performed **daily** and takes the **reference date** as the day it actually occurred. When properly configured in the parameters, it will be split into **two records** for the same day (one for the 1st hour, and the rest in the following one). **Synchronizing Compensation** Compensation synchronization is based on the **records from Visualtime** that have **the appropriate configuration in the ERP.** For the import to be possible, the compensation items must be set as **compensation items that can be entered in the monthly changes with quantity specified**, ensuring the correct association. This way, the values recorded in Visualtime will be automatically reflected in the ERP's monthly changes, allowing for correct processing. **Synchronizing Vacation Schedules** The ERP synchronizes the vacation days marked in the import period. To do this, you must configure Visualtime so that these vacation schedules contain **vacation absence codes** that properly correspond to the ERP's absence codes. You must use the **A# initial tag**, for example: A#F50. **Deducting Meal/Shiftwork Allowance during Vacation** Deducting Meal Allowance or Shiftwork Allowance absences during vacation has a **different behavior** than what happens in the ERP. During **synchronization**, the option selected in the **Deduct Meal/Shiftwork Allowance** field, under **Administrator | Parameters of the Fiscal Year | Vacation**, is taken into account, meaning that if the following option is selected: 1. **First Half Day,** the system **always applies** the Meal/Shiftwork Allowance absence; 2. **Second Half Day**, the system **never deducts** the Meal/Shiftwork Allowance absence; 3. **Proportional**, applies the Meal/Shiftwork Allowance **absences** proportionally. ## Synchronizing Monthly Changes The mapping between the justifications or leaves in Visualtime **must be configured in Visualtime** between the **equivalence code** and the ERP's **A#leave type code, A#absence, O#overtime**, or **E#compensation**. If there are **records** that you want the synchronization process to **ignore**, you must enter the expression ***#Ignore***. Otherwise, a warning will be shown in the synchronization log for unmapped occurrences. In the case of **vacation**, in addition to being recorded in the monthly changes, it's also **recorded in the vacation calendar**. To synchronize the data recorded in Visualtime with the ERP, follow these steps: 1. Go to **Human Capital | Visualtime | Monthly Changes Synchronization**; 2. Click **New** to create an import; 3. Set a **Description**, a **Start Date** (by default, this is the current period or the period following the previous synchronization), and an **End Date**; 4. Import to start the synchronization. You can interrupt an import. In that case, the import will be in the **Interrupted** status, and all data up to the point of interruption will be imported. To continue an interrupted synchronization, double-click the interrupted record and click **Import**. --- ## Viewing the Log A log with **synchronization details** is saved, attached to the synchronization record, and can be accessed for analysis. To view the log, follow these steps: 1. Go to **Human Capital | Visualtime | Monthly Changes Synchronization**; 2. In the list, go to the desired synchronization; 3. Below the main list, the **Attachments** area is available. Here, select the desired attachment; 4. Double-click the attachment to view it, or click **View**. --- ## Frequently Asked Questions The following frequently asked questions aim to clarify possible doubts about how this integration works: **1. There are records in Visualtime for the period I specified in the synchronization that don't exist in the ERP. Why?** You should check whether the **equivalence code** in Visualtime is **correctly set** for the justification that was not synchronized. If the equivalence code is filled in with ***#Ignore*,** during the synchronization process, all records with that justification **will be ignored** and, therefore, will not be in the ERP. You should also check whether this involves **absences or vacation that have not yet occurred**, i.e., the absence or vacation date is **earlier** than today. In these cases, synchronization is not performed for days that have not yet occurred. **2. There are compensation items that are not being imported because they have the wrong configuration. What is the correct configuration for import?** The correct configuration for compensation items to be imported is the same one that allows them to be entered in the **monthly changes with quantity specified**. For example: **Type: Unit Value | Formula: Fixed Value.** Only with this configuration will compensation items be able to be processed correctly during import. ## Related - [Integration with Visualtime: Features and Settings](/1730372321.md) - [How to synchronize employees in batch with Visualtime?](/1730373006.md)