Something not working with the Factorial - Sage 100 France | Congés & Absences Payés interface? Start with the two quick checks below, then look up your situation in the table. New to this interface? See Absences: Setting up the interface first.
| What you see | đź“Ť Where to fix it | Who | What to do |
| The run stops: no cancellation code is linked to one or more Sage codes | Sage 100 France | Payroll | Give each listed code a cancellation nature. See Set up the cancellation codes in Sage. |
| The run stops: the date of validity question is missing or its answer is not supported | BrynQ (Configuration tab) | BrynQ administrator | Answer Quelle est la date de validation ? with one of the three options. |
| The log says dry mode is on and nothing was sent | BrynQ (interface > Settings) | BrynQ administrator | Expected in dry mode. Turn dry mode off to send the changes to Sage. |
| The log says there is nothing to send to Sage | None | — | Sage already matches the approved absences in Factorial. Missing an absence? See the next row. |
| An absence is not sent | Factorial, then BrynQ (Scenarios tab) | HR, BrynQ administrator | Check that the absence is approved in Factorial; that its leave type is in the leave type mapping for that legal entity, spelled exactly as in Factorial; and, if you entered test matricules in the Configuration tab, that the employee is one of them. |
| A deleted or changed absence is still in Sage | Sage 100 France | Payroll | BrynQ only cancels events of the current cycle (the date of validity of the current run), and only for employees who still have at least one approved absence in Factorial. Cancel the event in Sage by hand. See How it works in Absences: Setting up the interface. |
| A change of half day is not in Sage | Sage 100 France | Payroll | BrynQ does not compare half days. Correct the half day in Sage by hand. |
| An event entered by hand in Sage was cancelled | Factorial | HR | For employees with absences in Factorial, an event of the current cycle that is not in Factorial is cancelled. Enter the absence in Factorial instead. |
| The run stops: Nombre is missing for absences that must be cancelled | BrynQ (Scenarios tab) | BrynQ administrator | The message lists the employees, codes and motifs. Add back a mapping line that gives this event code and motif a Nombre, or cancel these events in Sage by hand. |
| The run stops: the mapping gives two different values for one line, or two different Nombre for one code and motif | BrynQ (Scenarios tab) | BrynQ administrator | Keep one value, then run again. |
| The run stops: no dossier can be found for employees whose absences must be cancelled | BrynQ (Scenarios tab) | BrynQ administrator | Map the legal entities in the message to their Sage dossier. |
| The run stops: no import folder for a dossier | BrynQ (Scenarios tab) or the Agent dashboard | BrynQ administrator, Server administrator | The dossier in the mapping must match a company folder in the Sage import folder. Correct the mapping, or add the company on the SAGE 100 France page of the local admin dashboard. Nothing was sent. |
| The run stops: absence rows have no dossier | BrynQ (Scenarios tab) | BrynQ administrator | Map every Factorial legal entity to a Sage dossier. |
| The run stops: the absence file could not be uploaded to the Sage server | Windows server | Server administrator | Check that the BrynQ services are running and that the Agent can write to the import folder. See Troubleshooting the BrynQ Agent. |
| The file arrives on the server, but the absences are not in Sage | Sage and the Windows server | Payroll, Server administrator | Check that the import model BrynQ Absences exists in Sage with exactly that title (the SAGE 100 France page of the dashboard shows a missing model). Check that the employee exists in Sage with the same matricule and is hired, not under Salariés en attente. Then read connectimport-error in logs\sage. |
| 'Erreur mot de passe' on the Sage server | Sage 100 France | Payroll | Reinitialise the user or the dossier. See Factorial - Sage 100 France | Employees: Troubleshooting. |
BrynQ corrects and cancels absences in Sage with cancellation events. For that, every Sage event code you use in the mapping needs a matching cancellation nature. The run checks this first and stops with the list of codes that still need one.
Follow Step 5: Create the cancellation codes in Sage in Absences: Setting up the interface. It shows every click with screenshots.
âš If a step is skipped or done wrong, this is what you can expect:
| What went wrong | What you see | What to do |
| The original code has no Nature d'annulation, or a code from the mapping was skipped | The run stops before anything is sent, and lists the codes. | Do step 9 for each listed code, then run again. |
| The Sens was not reversed on the cancellation code | Nothing in BrynQ: the run reports that Sage is up to date. But in Sage a cancellation adds the days again instead of removing them, so balances such as congés pris are wrong. | Correct the Sens on the cancellation code. Then check and correct the balances of the employees with cancelled absences in Sage by hand. |
| Nature d'annulation is also filled in on the cancellation code (for example when you copied a code that already had one) | As soon as the first cancellation is in Sage, BrynQ mixes up the two codes and sends the same absences again on every run. | Empty Nature d'annulation on the cancellation code, then cancel the duplicate absences in Sage by hand. |
| The new code was already used by another event nature | Events of that other nature count as cancellations: absences are sent twice, or not cancelled. | Create a cancellation code with a free number, select it in Nature d'annulation of the original code, and check the absences of the affected employees in Sage. |
Help us help you faster. Include: