What is Siltra?

Siltra is the application every company in Spain uses to exchange information with the Social Security (TGSS/INSS). Among the files it receives is the FIE file (Fichero INSS Empresas), which reports the sick-leave activity of the company's workers: initial certificates (partes de baja), confirmation certificates, discharge certificates (partes de alta), relapses, cancellations and INSS resolutions.

The Factorial – Siltra integration reads that file and turns those official communications into Factorial leaves, so HR does not have to re-type medical absences that the Social Security has already communicated.

Before you start

Main features

• Import of the official FIE file (.msj) downloaded from Siltra.
• Preview before writing: the integration shows exactly what it would create, link or close, for whom, and what it would leave out and why.
• Creation of sick leaves in Factorial as absences of the leave type the company chose for each official contingency.
• Closing of leaves when the discharge certificate (parte de alta) arrives.
• Linking of leaves already registered by hand, instead of creating a duplicate.
• Duplicate control across days: the FIE file repeats ongoing leaves every day, and the integration recognises what it has already imported.
• Summary by email to the addresses the company configures, after every import.

Setting up the integration

When the integration is installed, Factorial opens a setup screen. There are only two things to configure, and both can be revisited later from the app's settings.

1. Contingency mapping

The Social Security classifies every temporary-disability process into one of five official contingencies. Each company names its own leave types in Factorial, so the integration needs to know which leave type each contingency corresponds to.

2. Who receives the import summary

The import runs in the background, so the result is sent by email. On the same screen you list the addresses that should receive it.

Leaving the list empty is valid: it is how a company turns these emails off.

Importing a file

1. Download the file from Siltra
   Download the transmission from Siltra as usual. It is a .msj file.
    
2. Step 2 — Upload it to Factorial
   In Factorial, go to Calendar and click Import FIE. Drop the .msj file in the upload screen that opens.
   

   The Import FIE button appears only if the Siltra integration is installed and you have the permissions to use it. If you cannot see it, check with your administrator.

    
   Two optional settings are available on this screen:
   1. Hide health data — the preview and the summary email show [hidden: health data] instead of the leave type, since the type reveals the contingency.
   2. Show other benefits — lists the file's non-sick-leave benefits, which the integration does not synchronise, with their raw detail.
      
      Nothing is written at this point.
      

      

3. Review the preview
   The integration reads the file, compares it against what Factorial already holds, and shows a report:
    

The employee name shown is the one in Factorial, not the one in the file: the point of the review is to confirm that the right person was matched.
 

4. Step 4 — Confirm

If there is something to apply, the button reads Apply the N updates. Confirming launches the import in the background; you can close the screen.

If there is nothing to apply, the only option is Understood, close — no import button is offered that would do nothing.

Step 5 — Receive the summary

When the import finishes, the configured recipients receive an email with the full report: what was created, what was linked, what was closed, what did not change, and what could not be imported and why.

What the integration writes in Factorial

The integration writes under its own identity: it does not act on behalf of any administrator, and it does not approve the absences it creates.

What is not imported and why

Nothing is discarded silently. Every case below appears on the preview screen and in the summary email, with its reason.

Not covered yet

These arrive in the file, and the integration reads, shows and counts them — but does not act on them yet:

• Confirmation certificates (partes de confirmación): the absence is not extended.
• Cancellation of a sick leave: the absence created earlier is not voided.
• Cancellation of a discharge: the absence is not reopened.
• Contingency change decided by the INSS: the absence's leave type is not changed.
• Benefits other than temporary disability (maternity, paternity, care of a minor…): out of scope.
   

Files the integration refuses

The whole file is rejected — there is no partial import — when:

• it does not have the .msj extension;
• the download is truncated (the file's own control totals do not match what was read);
• the transmission concatenates several messages: download them separately;
• the message version is not FIE V5.0.

Changing the configuration

Open the integration's settings to revisit the contingency mapping or the list of recipients. The new configuration applies to the next import; absences already created are not touched.

Worth re-opening the settings when the company creates or renames its leave types, or when the people who should receive the summary change.

Uninstalling the integration

Uninstalling deletes the integration's own configuration: the contingency mapping, the list of recipients, and the record of which sick leave became which absence.

The absences already created in Factorial are not deleted — they are the company's own data.

If the integration is installed again, the mapping has to be configured from scratch. The absences that already exist are recognised by their dates, so they are linked rather than duplicated.

Frequently Asked Questions

1. Does the integration connect to the Social Security automatically?
   No. The company downloads the file from Siltra and uploads it to Factorial. The import is manual, and every import is confirmed by a person.
    
2. How often should I import the file?
   The Social Security generates the FIE file daily. Importing it daily keeps Factorial up to date; importing it less often does not lose information, because ongoing leaves are repeated in later files.
    
3. What happens if I upload the same file twice?
   Nothing is duplicated. The second import reports every event as Already imported.
    
4. Does it create employees who are not in Factorial?
   No, never. A sick leave is not sufficient evidence to create an employee record. The case is reported so HR can act on it.
    
5. Are the absences it creates approved automatically?
   No. They are created as absences of the configured leave type; approval follows the company's usual process.
    
6. Can I tell an imported absence from one registered by hand?
   Yes. Every absence the integration creates carries a note in its description saying it came from the Social Security, with the transmission and the import date.
    
7. What happens to a sick leave that somebody had already registered by hand?
   The integration links it instead of creating a second one, and manages it from then on — so the discharge certificate closes the absence that already exists.
    
8. Who can see the medical information?
   The preview is shown to the person doing the import, and the summary email goes only to the addresses configured in the integration's settings.