Setup an automated data interface between Factorial and Sage
Setup an automated data interface between Factorial and Sage
📌 This guide is for: BrynQ Agent 3.10 or newer (screenshots: 3.10.1) · Sage 100 France v9. Another version? See Start here – choose your version.
Updated for Sage 100 France v9 and BrynQ Agent 3.10.1. The installer checks your BrynQ token while you type, shows the steps for the Sage service account and the import models on its own pages, and creates the ConnectImport scenario for you. The admin page has a new look and a Troubleshooting page with a support file for BrynQ support.
* What's new with Sage v9 and Agent 3.10
New employees are sent in a separate file, <dossier>_EN_ATTENTE.xlsx, which Sage imports into Salariés en attente (import model BrynQ Salariés en attente). Payroll then hires them in Sage: Gestion > Salariés en attente, select the rows with Tout and click Embaucher. Until they are hired, BrynQ skips them on the next runs.
Embaucher only becomes available when DPAE envoyée is set (from the DPAE question in the Configuration tab) and the rows are selected with Tout.
For the DPAE, make sure the birth city and the trial period end date are filled in in Factorial.
Sage v9 requires the matricule (employee number) to be exactly 4 characters.
Error 'Code pays inexistant': the country must be the 3-letter code (for example FRA). The prefilled country mapping takes care of this.
The import reports 'Import terminé avec succès' but you don't see the employee: in v9, new employees appear under Salariés en attente first.
New installation step: create three empty import models in Sage with exactly the right titles. See Step 5.
What you will achieve
By the end of this guide, employee master data flows automatically from Factorial into Sage 100 France (v9). No manual exports and no copy-pasting.
How it works
It helps to picture the flow before you start. Every run goes through four steps:
BrynQ reads the employee data from Factorial.
BrynQ converts that data into an Excel import file that Sage understands.
The BrynQ Agent, a small program on your Sage server, receives the file.
ConnectImport imports the file into the right Sage company (PRH file).
So you set up two things: the Agent on the Sage server (Part 1) and the interface in BrynQ (Part 2).
Know where you are
This guide switches between several places. Each step starts with a 📍 Where label so you always know where to work:
📍 Label
What it is
Windows server
The computer (machine) on which Sage 100 France is installed. You install the BrynQ Agent here.
SQL Server
The database software that stores the Sage data. It usually runs on the same Windows server, but it can also run on a separate machine. In the installer you only enter its name.
Sage 100 France
The Sage application itself, opened on the Windows server.
BrynQ
The BrynQ platform in your browser (https://your-slug.app.brynq.com).
Factorial
Factorial in your browser.
The route at a glance
Part
What you do
📍 Where
Who
1.A
Download the BrynQ Agent
BrynQ, opened on the Windows server
Server administrator
1.B
Install and configure the Agent, and create the BrynQ import models in Sage
Windows server + Sage 100 France
Server and Sage administrator
1.C
Check that the Agent is running
Windows server
Server administrator
2
Create, configure and connect the interface
BrynQ (+ Factorial and Sage for look-ups)
BrynQ and Factorial administrator
Before you start
Tick off this checklist first. Each item prevents a common reason for getting stuck halfway.
☐ Access to BrynQ with permission to create or edit interfaces.
☐ A Factorial administrator account with access to all employee data (see the box below).
☐ A Sage 100 France administrator, plus a payroll user who can review import results.
☐ Administrator access to the Windows server that runs Sage, including the Sage PRH files and the programFiles and programData folders.
☐ Database access: the account the Agent uses to connect to SQL Server (your Windows account, or a SQL Server login) must have access to the Sage company databases. If you are not sure, check this with your IT administrator before you start.
☐ The Windows server runs Windows Server 2016 or newer. The installer does not start on older versions.
☐ A BrynQ API token for this customer, at hand. Create it in BrynQ under Admin Portal > API Access > Add API token and select exactly one customer, or ask BrynQ support. Why: you need it in both Part 1 and Part 2. If the token has an IP whitelist in BrynQ, it must include the public IP address of the Windows server.
⚠ Use a Factorial ADMINISTRATOR account BrynQ only syncs the employees that the connecting Factorial user can see. A non-admin account means missing employees in Sage.
Watch first: video walkthrough of Part 1
💡 Tip: watch a video to see what to do, then use the written steps below for the details of each step.
Video 1: the complete installation, explained step by step (Sage v8, BrynQ Agent 3.9.4). It does not include Step 5 (the import models).
🎬 Video 2: Sage v9 and Agent 3.10, including Step 5 The same installation as video 1, plus the explanation of Step 5 (creating the three import models in Sage), which video 1 does not have. It goes through the other steps more quickly; watch video 1 if you want those in more detail.
This video shows Agent 3.10.0. Since 3.10.1 a few installer pages look different; the steps in the text below are leading.
Part 1.A) Download the BrynQ Agent on the Windows server
📍 Where: BrynQ, opened in a browser on the Windows server where Sage runs. Goal: get the Agent installer onto that server.
Log in to BrynQ and go to Organization > Agent.
Download the latest BrynQ Agent installer (brynq-agent-installer-<version>.exe).
ℹ Security warning? The files are signed and published under 'Salure ICT BV'. Your browser or Windows may still flag them as untrusted. That is expected and you can continue.
Part 1.B) Install and configure the Agent
📍 Where: the Windows server (installer), plus Sage 100 France for steps 4 and 5. Goal: install the Agent and connect it to SQL Server and your Sage companies.
💡 Tip: the installer fills in most values for you: the PRH files, the SQL connection (read from the PRH files) and the Sage installation it finds on the server. The suggested values usually work: keep them and click Next, unless a step below says otherwise. Some pages only show when they are needed, so you may see fewer pages than described here.
⚠ Windows permissions
Install as administrator: right-click the installer and choose Run as administrator.
Signed software: the installer is digitally signed (right-click > Properties > Digital Signatures shows the publisher). Does Windows show Windows protected your PC? Click More info > Run anyway. If your organisation only allows approved publishers (AppLocker, antivirus), ask IT to allow the Agent as described in Security. File blocked after download? Right-click > Properties > tick Unblock.
While running: the BrynQ services run as LocalSystem. That account needs read and write access to the Sage folders, the PRH files and the import folder. With Windows authentication it is also the account SQL Server sees: NT AUTHORITY\SYSTEM, or the computer account DOMAIN\SERVERNAME$ when SQL Server or the Sage files are on another server.
Folder created by another user? The installation stops when one of BrynQ's folders (for example C:\ProgramData\BrynQ\Agent or its config folder) was created by another Windows user. The message names the takeown command that fixes it.
Is it a permission issue? Look for Access is denied, Permission denied or Login failed in the installer log (a copy is kept in C:\ProgramData\BrynQ\Agent\logs\installer, named setup-<date>-<time>.log) or in the Agent logs (C:\ProgramData\BrynQ\Agent\logs\agent and \sage).
Advanced checks (for IT):
Service and install logs:C:\ProgramData\BrynQ\Agent\logs\services (for example BrynQAgentService.err.log) shows why a service stopped; logs\installer\install-post.log shows the installation steps and the one that failed.
Event Viewer (eventvwr.msc): under Windows Logs > System, events from Service Control Manager show why a BrynQ service failed to start or stopped. Under Windows Logs > Application, a SQL Server Login failed (event 18456) means the Agent account has no SQL access.
Service account: in services.msc, open a BrynQ service > Log On to see which account it runs as.
Folder access: right-click a Sage folder > Properties > Security > Advanced > Effective Access, select SYSTEM (or the computer account) and click View effective access.
Step 1: Run the installer
Start the installer and select your language. The installer suggests the language of Windows. The BrynQ pages are available in English, French, German and Dutch; the license agreement is in English, and the names of Sage screens stay in French. The screenshots below are in English.
Read the license agreement carefully. If you agree to it and want to use the BrynQ Agent, accept it to continue.
Keep the default (pre-filled) installation path. It works for most setups, but you can choose another folder if you prefer. This page only shows on a first installation.
Cloud connection: paste the BrynQ API token (see "Before you start"). The installer checks the token with BrynQ while you type. Next becomes available once the page says BrynQ accepts this token. Token not accepted?
BrynQ does not accept this token (…): check that you copied the whole token. The reason is shown between brackets, for example TOKEN_NOT_FOUND or TOKEN_EXPIRED.
BrynQ only accepts this token from other IP addresses: add the public IP address of this server to the token in BrynQ, then click Check again.
…it is not an agent token: an agent token is linked to exactly one customer. Use the agent token of this customer.
BrynQ could not be reached or The BrynQ platform is not responding: wait a moment and click Check again.
Installing again on the same server? The page says the server is already connected. Keep Keep the existing API token (recommended), or choose Replace it with a new API token.
Modules: tick Sage 100 France (under Payroll integrations). This also turns on SQL Server and File Management; they stay ticked and greyed out. Tick REST Proxy too if BrynQ asked you to. You can change the modules later by running the installer again.
Step 2: Choose your Sage companies
Key idea: each PRH file is the database of one company in Sage. Selecting a PRH file means "BrynQ may import into this company".
The installer first looks for Sage 100 Paie & RH and the PRH files on the server. This can take a few minutes. On the page Sage — Select Companies, tick the PRH files of the companies you want to connect to the interface. Only if a company is missing: add its PRH file with Add PRH File.... If that company is already ticked, the installer asks whether to replace its file. Scan Again searches again and keeps the files you added.
Step 3: Connect to SQL Server
BrynQ reads the SQL connection from the PRH files you ticked. When that connection works, the installer skips this step. Tick Review SQL connection settings manually on the previous page if you want to see it anyway.
SQL Server connection:
Server: pick the suggested server, often SERVERNAME\SQLEXPRESS. Not sure? SQL Server Management Studio shows the server name when you connect, or ask your IT administrator.
Login method:Windows authentication, or SQL Server authentication if your setup uses a SQL Server login. Only the latter asks for Username and Password. That account needs access to the Sage databases.
Click Test connection. It shows Connection successful, or the reason why it failed.
Advanced... shows the ODBC Driver and the Extra connection options (default Encrypt=no;TrustServerCertificate=yes). Only change these when the test fails; take the driver with the highest number (for example ODBC Driver 18 for SQL Server).
Databases: keep Only the databases I select (recommended) and tick at least the databases of your Sage companies. A database is not in the list? Click Database not in the list? and add its name. All databases on this server also includes databases that are added later. This choice only records which databases the BrynQ interfaces use. It does not limit access: to limit access, give the SQL login rights on these databases only.
Step 4: Create a Sage service user
📍 Where: Sage 100 France. Why: the Agent needs its own Sage account so imports are not tied to a person's login.
The installer page Sage service account lists the same steps.
Open Sage 100 France, connect to a PRH file, go to Fichier > Droits d'accès > Utilisateurs and click +.
Set Mode d'authentification to Compte de service. Enter a description you will recognise (for example BrynQ) and leave the validity date empty. Tick Token actif and click Générer. Example:
📍 Back in the installer, paste the Code of the service user (for example AAA, not the login name) and the Token.
📍 In Sage, click OK. The user is only created after this step.
🔍 Sage installation Next, the installer picks the Sage 100 Paie & RH that BrynQ imports into. With one installation it does this by itself. With more than one, the page Sage installation shows each one with its version and folder: choose the one you use for payroll. You create the import models in that one in Step 5. Not listed? Click Browse... and select its pmsw32.exe or ConnectImport.exe. Older versions (v8) can only be chosen after a warning; an installation without ConnectImport or without a data folder can't be chosen.
Step 5: Create the three BrynQ import models in Sage (new in Agent 3.10)
📍 Where: Sage 100 France and the installer, both open on the Windows server.
Title (Intitulé)
Root file (Fichier racine)
BrynQ Salariés
Fiche salarié
BrynQ Salariés en attente
Salariés en attente
BrynQ Absences
Bulletin de paie > Evènements
A. Open the models screen in Sage
The installer now shows the page Sage import models. At the top it says how many of the three models it found; below that is one row per model: a green check with the Sage code (found), a red cross with the reason, or an hourglass while it checks. Select a row to see its title with a Copy button and the eight steps for that model. Leave the page open.
Open Sage 100 Paie & RH (the installation named at the top of the page). You don't need to open a company.
Go to G.A. > Format d'Importation.
B. Model 1: BrynQ Salariés
Click + at the bottom of the list.
Select Fiche salarié and click Ok.
A screen for the fields opens. Don't change anything: close it with the X at the top right.
The save window opens. In the installer, select the row BrynQ Salariés and click Copy. In Sage, paste it into Intitulé (Ctrl+V) and click Ok.
In the installer, click Check again. The row BrynQ Salariés now has a green check ✔ and its Sage code. The installer also checks by itself every few seconds.
C. Model 2: BrynQ Salariés en attente
Same steps, with another root file and title.
Click +.
Scroll down, select Salariés en attente and click Ok.
Close the fields screen with the X.
Copy BrynQ Salariés en attente in the installer, paste it into Intitulé and click Ok.
Click Check again: BrynQ Salariés en attente has a green check ✔.
D. Model 3: BrynQ Absences
Same steps again. The root file is one level deeper, under Bulletin de paie.
Click +.
Select Bulletin de paie and click Ok.
Select Evènements and click Ok.
Close the fields screen with the X.
Copy BrynQ Absences in the installer, paste it into Intitulé and click Ok.
Click Check again: BrynQ Absences has a green check ✔.
E. Close Sage and continue
While Sage is still open, the page says All 3 models found. Close Sage 100 Paie & RH on this server (all sessions) to continue.Close Sage 100 Paie & RH completely (also other sessions on this server).
The page now says All 3 models found. Click Next to continue. Click Next.
✖ A row still has a red cross?Next stays unavailable until all three models are found and Sage is closed. Select the row: the installer tells you what to do.
Not found: the title is not exactly right, or the model was not saved. Copy the title again and correct it in Sage. Letter case and spaces around the title don't matter.
Renamed: the model BrynQ used until now has another title in Sage. Give it exactly the title shown again (use the Copy button).
Duplicate: more than one model has this title. Keep the model the installer names and delete or rename the others in Sage.
Wrong Fichier racine: the model was created with another root file. Delete it in Sage and create it again with the root file from the table.
This model is in another Sage installation: create it in the Sage installation named at the top of the page.
Sage's model list was not found: create the models in Sage first, then click Check again.
ℹ Good to know
Sage gives each model a code (for example IMP00012). Your codes can differ from the screenshots; only the titles matter.
Don't rename or edit the BrynQ models later. BrynQ checks their titles every import cycle: if a title is no longer exact, nothing is imported until it is right again (the files wait in the queue). Changes to their fields are undone by BrynQ.
Updating the Agent later? You only see this page again if a model is not OK or Sage is open. A blue information sign (fields changed in Sage) or a note that the model files are missing needs no action: BrynQ restores the model itself. Automatic updates and silent installs never show this page.
OPTIONAL: after the installation you can see the three models under G.A. > Format d'Importation. Select one and click the pencil to see the fields BrynQ filled in. Don't change them.
Step 6: Finish the installation
ConnectImport scenario: keep Let BrynQ create the scenario (recommended) and click Next. Only choose Use my own ConnectImport scenario if BrynQ support asks you to. Installing again? Keep Keep the current scenario (recommended). Recreate the scenario from the BrynQ settings overwrites the current scenario.
Additional options:
Shortcuts: keep Create a desktop shortcut (recommended), and Create a Start Menu shortcut if you like. Both take you straight to the Agent's admin page later.
BrynQ support:Share advanced diagnostics (recommended) lets BrynQ support collect extra Windows details when the logs don't explain a problem. Click What does BrynQ support see? to read exactly what. You can change this later on the admin page under Troubleshooting.
OPTIONAL: skip unless needed.Use custom local network settings is only needed if another program on this server already uses port 7070 or 7071. Not sure? Leave it unticked.
Click Install. The installer shows each step. If the last step fails (for example because BrynQ does not answer for a moment), it shows the reason and offers Retry: all your choices are kept.
OPTIONAL. Keep Open the BrynQ Agent dashboard ticked and click Finish, or later use the shortcut or open http://127.0.0.1:7071/admin in a browser on the Windows server (Edge, Chrome or Firefox; Internet Explorer can't show it). The admin page is available in English, French, German and Dutch; switch the language at the top.
Part 1.C) Check that the Agent is running
📍 Where: the Windows server.
✅ Checkpoint 1: confirm this before you move on to Part 2.
Open Task Manager and go to the Services tab.
Check that all three BrynQ services have the status Running.
Or open the admin page (http://127.0.0.1:7071/admin) and go to Troubleshooting: BrynQ services shows 3 of 3 running.
✖ A service is not running?
Right-click the service and choose Start.
Wait a moment and check that the status changes to Running.
Does it not start, or does it stop again? This is often a permission issue: check Windows permissions at the start of Part 1.B and look for Access is denied in the logs. Still stuck? Contact BrynQ support and include a screenshot of the Services tab and the support file (see Find the Agent log files).
💡 Remember: whenever BrynQ cannot reach the Agent later on, check these three services first.
Part 2) Create the interface in BrynQ
📍 Where: BrynQ (any computer). You only look up values in Factorial and Sage 100 France. Goal: tell BrynQ what to sync and where to send it.
Step 1: Create the interface from the template
Open BrynQ and go to Interfaces.
Click New interface and choose Use our templates.
Search for Sage and select Factorial - Sage 100 France Employees.
Click Use template.
Step 2: Fill in the Configuration tab
Open the Configuration tab.
Set the company's payment frequency.
OPTIONAL (recommended). Enter a few employee IDs. The first runs then only process these employees, so you can test safely.
Answer the question Is the DPAE sent outside Sage? with yes or no (oui/non, ja/nee, ja/nein and 1/0 also work). This answer is required: without a valid answer the run stops.
Step 3: Complete the value mappings in the Scenarios tab
Key idea: a value mapping translates a value in Factorial into the matching value in Sage. Every item marked with an exclamation mark (!) still needs your input.
Check in Factorial before the first run
Every contract has a French contract type. It sets the contract nature in Sage; if it is missing, that field stays empty and the run log shows a warning.
Working hours and their frequency are filled in. BrynQ uses them for the monthly working time (for example 35 h/week = 151.67).
Most value mappings, such as countries (3-letter codes like FRA) and civility, are already prefilled. You only need to check them.
Open the Scenarios tab and find the items marked with an exclamation mark.
Worked example: 'Legal Entity -> Paying Establishment and Dossier' You find this mapping in the scenario Registration. It is the most important mapping: it decides which Factorial legal entity syncs to which Sage company. We walk through it step by step; the other mappings work the same way.
Left side (📍 Factorial): find the legal entity ID and name under Settings > Company details.
📍 BrynQ: enter this value on the left side of the mapping. Syncing several entities? Add one row per entity.
Right side (📍 Sage 100 France): find the matching Raison sociale / dossier of the Sage PRH file. In this example the dossier is 'BRYNQ.PRH'.
📍 Sage 100 France: also find the matching 'Etablissement principal'.
📍 BrynQ: enter these values on the right side of the mapping. The result looks like this:
Confirm the mapping and save it.
Now you try: complete the other non-standard mappings in the same way (look up the value on each side, enter it, confirm, save):
Finally, check that the standard value mappings are correct for your company:
Step 4: Connect Factorial and Sage (Authorization tab)
Open the Authorization tab.
Factorial first: click Add authorization (TEST and LIVE), enter a recognisable name and click Connect to app.
Sign in with your Factorial ADMINISTRATOR account.
Make sure the TEST version is active before your first test run.
⚡ Heads-up: this can connect automatically! Are you already signed in to Factorial in this browser, with an active login (session cookie)? Then Connect to app connects straight away with that account, without asking you to sign in. So before you click: check that you are signed in to Factorial with the administrator account. If not, sign out of Factorial first, or use a private/incognito window.
Approve the requested access and save the connection.
Then Sage: add the Sage authorization.
Enter the BrynQ Agent URL in this format: https://[your-customer-slug].brynq-agent.com Where to find your slug: it is the first part of your BrynQ web address. The exact address is also in C:\ProgramData\BrynQ\Agent\config\public_url.txt on the Windows server. If you log in at https://acme.app.brynq.com, your slug is acme and the Agent URL is https://acme.brynq-agent.com.
Enter the BrynQ Agent Token: the same token you received earlier and entered in the installer.
Check the first run
✅ Checkpoint 2: after a controlled test run:
📍 Windows server: a new Excel import file appears in the company's import folder: <dossier>.xlsx for existing employees, and <dossier>_EN_ATTENTE.xlsx when there are new employees. Once imported, the Agent moves the files to a subfolder named importe le <date and time>.
📍 Sage 100 France: existing employees are updated, and new employees appear under Gestion > Salariés en attente. Hire them there: select the rows with Tout and click Embaucher. Start with the test employee IDs you entered in Step 2.
✖ Something went wrong?
No import file on the server: read the run log of the interface first (interface > Runs). No file is sent when the interface found no new or changed employees, or when all of them were filtered out (Factorial permissions, data, value mappings). Did the run log say a file was sent? Then BrynQ could not deliver it to the Agent: check the three BrynQ services (Part 1.C) and test the Sage authorization again.
'Import terminé avec succès', but no new employee: look under Salariés en attente first (Sage v9).
Import file is there, but Sage has no or wrong records: check the run log, the data in Factorial and the value mappings in the Scenarios tab, especially Registration.
Some employees are missing: check the run log. Common causes: Factorial permissions (reconnect with an administrator account), missing or wrong data in Factorial, or a value mapping that is not filled in.
Still stuck? See the troubleshooting section below, or contact BrynQ support and attach the support file (admin page > Troubleshooting > Download support file).
Troubleshooting
What you see
What to do
Any error you can't explain
Open the admin page (http://127.0.0.1:7071/admin) > Troubleshooting: it checks the services, the connection with BrynQ, folder access and more, and lists fixes for common problems. Share the support file with BrynQ support (see Find the Agent log files below).
Parts of the installation fail, or the Agent runs but cannot read or write files
Check the Windows permissions: run the installer as administrator, and make sure the Windows account of the Agent can read and write the Sage folders, PRH files, programFiles and programData. See the warning at the start of Part 1.B.
Installer: Next stays unavailable on Cloud connection
BrynQ does not accept the token yet. The page says why: copy the whole token, add the server's public IP address to the token in BrynQ, or use the agent token of this customer. Then click Check again. See Part 1.B, Step 1.
Installer: Next stays unavailable on Sage import models
A row still has a red cross, or Sage is still open. See Step 5 for what each message means; Close Sage (all sessions) once all three models are found.
Not all employees are synced
Read the run log of the interface first (interface > Runs). Common causes: the Factorial user cannot see all employees (reconnect with a Factorial administrator account), missing or wrong data in Factorial, a value mapping that is not filled in, or test employee IDs still in the Configuration tab. See Employees: Troubleshooting.
'Erreur mot de passe' on the Sage server (this happens often)
Check the code and token of the Sage service account first, then reinitialise the user or the dossier in Sage. See Fix 'Erreur mot de passe' below.
BrynQ cannot reach the Agent
Check that the three BrynQ services are running (Part 1.C), then open http://127.0.0.1:7071/admin on the Windows server and go to BrynQ connection: both This agent signs in to BrynQ and BrynQ reaches this agent must be OK. Next, test the Sage authorization again from the Authorization tab.
The installer cannot connect to SQL Server
Click Test connection and read the reason. Check that the server name is right (Step 3), choose the right login method (Windows or SQL Server authentication), try the ODBC driver with the highest number under Advanced..., and confirm that the account has access to the Sage databases.
An app used by the template is inactive
Activate it in Settings > Interfaces > Apps.
A manual Sage import works, but the automated run does not
Check the Agent on the admin page (http://127.0.0.1:7071/admin) under SAGE 100 France > Overview and Troubleshooting, then test the Sage authorization again from the Authorization tab.
You need to review or remove an authorization
Open Settings > Interfaces > Connections.
Find the Agent log files
📍 Where: the Windows server, in File Explorer. When something goes wrong, the Agent's log files usually tell you (and BrynQ support) why. There are two log folders. Which one you need depends on the problem:
Problem
Log folder
Importing data into Sage fails or gives wrong results
C:\ProgramData\BrynQ\Agent\logs\sage
General Agent issues, such as connection problems
C:\ProgramData\BrynQ\Agent\logs\agent
Sage import logs (for example connectimport and connectimport-error):
General Agent logs (for example application, requests and security):
You can also read the log files on the admin page: Troubleshooting > Log files (newest first; click a file to read it).
💡 Contacting BrynQ support? Attach the support file: on the admin page, go to Troubleshooting (or SAGE 100 France > Troubleshooting) and click Download support file. It holds the logs, the settings and the status of the services in one zip file (brynq-agent-support-<customer>-<server>-<date>-<time>.zip), with passwords and tokens left out. Admin page does not open? Run "C:\Program Files\BrynQ\Agent\brynq-agent.exe" --support-file in a Command Prompt as administrator; the file is saved on your Desktop. This usually saves a lot of back-and-forth.
Can't see the ProgramData folder? It is hidden by default. Type C:\ProgramData\BrynQ\Agent\logs directly into the File Explorer address bar.
Fix 'Erreur mot de passe'
📍 Where: Sage 100 France, on the Windows server. The error 'Erreur mot de passe' occurs quite often on the Sage server. It has two common causes:
The code or token of the Sage service account that the BrynQ import uses is not correct, or the token is no longer active. This is the likely cause when no import with this account has worked yet, or after someone changed the account in Sage.
Sage still holds an old session of the account. This is the likely cause when imports worked before. Reinitialise the user or the dossier (options A and B).
The admin page names the likely cause: open http://127.0.0.1:7071/admin > SAGE 100 France > Troubleshooting and read the latest import message.
Check the service account first
In Sage, go to Fichier > Droits d'accès > Utilisateurs and open the service account of the BrynQ import.
Check that Mode d'authentification is Compte de service and that Token actif is ticked. Note the Code.
Not sure the token is right? Click Générer for a new token, copy it and click OK.
On the Windows server, open http://127.0.0.1:7071/admin > SAGE 100 France > Service. Check that Sage user code matches the Code in Sage. If you generated a new token, click Replace token, paste it and save.
Wait for the next import cycle (15 minutes by default) and check the import message again.
Still 'Erreur mot de passe'? Reinitialise the session. Start with option A. Only use option B if A does not help.
Option A: reinitialise from within the company (try this first)
Open Sage 100 France and connect to the company (PRH file).
Go to Fichier > Droits d'accès > Utilisateurs.
In the Liste des utilisateurs, click Réinitialisation.
Try the connection again.
Option B: global reinitialisation of the dossier (use at your own risk)
⚠ At your own risk.Réinitialiser le dossier signs out all users of the dossier. Make sure nobody is working in payroll before you use it.
Go to Fichier > Utilitaires > Réinitialisation. Don't see it? This option is sometimes only visible when you are not connected to a company. Close the company first (Fichier > Fermer) and look again.
The Assistant réinitialisation de dossier opens. Click Parcourir... and select the dossier (PRH file) to reinitialise.
Click Réinitialiser le dossier. To sign out one specific user only, select that user and click Réinitialiser l'utilisateur instead.
Click Terminer and try the connection again.
Recap
The Agent on the Windows server receives the import files and imports them into the PRH files you selected. It reaches the Sage data through SQL Server.
The value mappings decide which Factorial entity lands in which Sage company. Take extra care with 'Legal Entity -> Paying Establishment and Dossier' in Registration.
The authorizations connect BrynQ to Factorial (admin account!) and to the Agent.
Stuck? Check the three BrynQ services first, and the Troubleshooting page of the admin page. Then contact BrynQ support and attach the support file.