Skip to content

🤖 Explain with AI

Electronic filings

Settings → Payroll → Tax & Compliance → Electronic filings lists the periodic filings of your compliance country: the period due now, its due date, the status you recorded, the agency reference and the acknowledgement. For Costa Rica it also generates the CCSS SICERE file.

In short

For: payroll administrators and the accountant who files with the agency.
Time: 5 minutes per period.
Result: the official file generated, the filing tracked and the acknowledgement stored.

For whom
Owner, workspace admin and accounting
Time
5 minutes per period
Level
Intermediate
Result
Filing tracked with its evidence

What the console does — and what it does not

The console works in three levels, declared per obligation:

Level What it means
API A connector submits to the agency and stores the receipt. Today only the Costa Rican INS payroll uses it.
Official file The console generates the official file, you upload it to the agency portal and record the acknowledgement. Costa Rica SICERE works this way.
Manual The console tracks the deadline, the reference and the evidence; the filing is made in the agency portal.

4Geeks does not file on your behalf. There are no intermediary aggregators: the client always provides its certificate and authorization, and the client uploads the file (or authorizes the API connection when one exists). The acknowledgement link is mandatory in practice: it is what proves the filing.

The filing calendar

Each obligation has an agency, a scope (social security, income tax, other), a periodicity (monthly, annual, event), a delivery level and a due rule. The console:

  • computes the period that is due now (the month that just ended for monthly obligations);
  • computes the due date with weekends and the country holidays;
  • marks it Overdue, Due soon (within 7 days) or Upcoming;
  • keeps a timeline of every status change (pending → generated → submitted → accepted/rejected) in payroll_filing_events.

Record a filing

  1. Open the obligation in the list.
  2. Click Record (or Update).
  3. Choose the status: Pending, Generated, Submitted, Accepted or Rejected.
  4. Fill in the reference (agency folio or planilla number), the acknowledgement URL and an optional note.
  5. Save.

The row stores who changed it and when; the audit trail keeps the history. A rejected filing keeps its reason in the note.

Costa Rica: the CCSS SICERE file

The CCSS “Grandes Clientes” flow receives a fixed-length ANSI file. The console builds it from the payroll data and the configuration below.

1. Configure SICERE

In the CCSS SICERE file card, set:

Field Format Notes
Patronal number 18 digits Patron type, legal id, segregated and sector, as registered with the CCSS
Branch 4 digits CCSS branch the patron is attached to
Segregated 3 digits, optional Only when the patron has segregated numbers
Default occupation code 4 digits Used when the employee has no specific code
Default ID type 0 national, 7 foreign Used when the employee has no specific type
Default insurance class C or A C = SEM, IVM and Banco Popular; A = pensioner (SEM and Banco Popular)
Default journey class and hours EXT/ACU/DIU/MIX/NOC/VES/PAR + 2 digits Used when the employee has no specific journey

The defaults are fallbacks. The real codes belong to each employee: in the employee form (Costa Rica only) set the CCSS occupation code, the CCSS ID type and the CCSS insurance class.

2. Generate the file

  1. Select the period (the console proposes the previous month).
  2. Click Generate SICERE file.
  3. The console validates every record. If something is missing (a cédula, an occupation code), it lists the issue and does not generate the file.
  4. The file downloads with the official name pla_<patronal>[-<segregado>]_<MMAAAA>.txt, in ANSI (Windows-1252).
  5. The filing moves to Generated and stores the file name and its SHA-256.

3. Upload and record the acknowledgement

Upload the file in the CCSS Oficina Virtual (Grandes Clientes → Validación y Carga de Archivos), wait for the official validation and then record Submitted or Accepted with the CCSS reference and the acknowledgement link.

The CCSS validates; the console does not

A generated file is not an accepted filing. The CCSS log is the final authority: review it, fix what it reports and upload again if needed.

What the file contains

The layout follows the Manual de Usuario Sistema de Grandes Clientes GF-DSCR-P004-M001 v2.04, section 9:

Record Length Content
25 30 (31 with suspension) Patronal number, branch, period YYYYMM; S in position 31 suspends the number
35 174 One per movement: id type and number, surnames, name, occupation (4), salary in cents (15), insurance class, change type, journey hours/class, change code, start and end dates
15 33 Control: PAT, generation date, total records 25 and total records 35

Movement types: IC inclusion, SA salary change, OC occupation change, JO journey change, CS insurance-class change, PE unpaid permit, IN incapacity/leave, EX exclusion. The console derives IC, SA, EX, IN and PE from the payroll data; occupation and journey changes are supported by the file builder but still manual.

A month without movements is valid: the file has the record 25 and the control 15 with zero records 35.

Country channels

Country Main agency Channel today
Argentina ARCA (SICOSS/F931, Libro de Sueldos Digital) Official file; API with the client’s certificate is possible
Bolivia Gestora Pública / CNS / SIN File or portal
Brazil eSocial / Receita Federal / FGTS Digital API with the client’s A1/A3 certificate (not implemented yet)
Chile Previred / SII Previred file; SII API with certificate
Colombia PILA operator / DIAN File or operator portal
Costa Rica CCSS SICERE / INS / Hacienda SICERE file generated by the console; INS API
Dominican Republic TSS SUIR / DGII File or portal
Ecuador IESS / SRI File (batch) or portal
Guatemala IGSS / SAT File or portal
Honduras IHSS / SAR / DEI File or portal
Mexico IMSS-INFONAVIT (SUA/IDSE) / SAT SUA file and IDSE portal
Nicaragua INSS / DGI Manual or file
Panama CSS (SIPE) / DGI File or portal
Peru SUNAT PLAME / AFPnet File or portal
Paraguay IPS / SET File or portal
El Salvador ISSS / AFP / MH File or portal
Uruguay BPS / DGI Portal
Venezuela IVSS / SENIAT Manual

Troubleshooting

Symptom Cause and fix
“Generate SICERE file” does not appear The compliance country is not Costa Rica, or SICERE is not configured yet.
The file is not generated and the screen lists issues Missing cédula, occupation code or a leave without an end date. Fix the employee or the leave and generate again.
“No movements” The month has no inclusions, salary changes, exclusions, leaves or permits. The console still generates the 25 + 15 file.
The CCSS rejects the file Check the file name, that it is ANSI and the record lengths; then compare with the CCSS log. The console does not submit or validate with the CCSS.
The acknowledgement is not saved The evidence URL must start with http:// or https://.

FAQ

Does the console upload the file to the CCSS?

No. It generates the file, stores its hash and tracks the status. You upload it in the CCSS Oficina Virtual and record the acknowledgement.

Can I use an intermediary or aggregator?

No, by product decision. Where the agency has no public API, the console stays at official file + evidence. The client provides the certificate and authorization for any direct API.

What happens if I change a rate after generating the file?

The file is a snapshot: it does not change. If the change affects the period, generate it again before uploading; the new file gets a new hash and the filing is updated.

Where is the evidence stored?

The acknowledgement is a URL you record on the filing; the generated file name and its SHA-256 are stored in the filing row. Keep the file in your own document store.

Is the SICERE file valid for the first payroll?

The first payroll is created by the CCSS. The console’s file reports movements from the following periods.


Still have questions? Ask on Discord or explore the tutorials.