Hiring or Terminating Employees in Brazil? The eSocial Deadlines That Do Not Wait for Monthly Payroll

Can the employer wait until October 15 to report the new employee?

Not without having completed the required admission reporting before the employee starts work.

Now consider another employee whose contract ends on September 2. The September payroll will not close until October 15, but the ordinary eSocial termination event must already have been transmitted by September 11.

That September 11 deadline is not a typo. The ordinary ten-day termination reporting period reaches Saturday, September 12, and eSocial requires the S-2299 filing deadline to be brought forward to the preceding fiscal business day.

Brazil’s payroll reporting system has several different compliance clocks operating simultaneously.

• Admission: Ordinary employment must generally be reported no later than the day before work begins.
• Preliminary admission: S-2190 can satisfy the initial reporting requirement, but must subsequently be completed through S-2200.
• Termination: Ordinary S-2299 reporting is generally required within ten days after termination, subject to an earlier filing deadline when the tenth day falls on a nonbusiness day.
• Termination settlement: The employer must pay the applicable employment termination entitlements within the legally required period.
• FGTS Digital: Certain termination-related FGTS obligations also follow a ten-day deadline instead of the ordinary monthly payment cycle.
• Monthly eSocial closing: The ordinary S-1299 deadline generally falls on the 15th of the following month.
• DCTFWeb: The ordinary monthly federal declaration generally has a separate deadline on the last business day of the following month.

Treating all seven obligations as one monthly payroll workflow creates preventable compliance risk.

This Ivvora guide constructs ten hypothetical employee events — five admissions and five terminations — throughout September 2026.

It calculates their individual reporting deadlines, identifies weekend and holiday adjustments, distinguishes labor settlements from tax payments, and follows the information through FGTS Digital, monthly eSocial closure and DCTFWeb.

The result is a practical deadline-by-deadline operating model for employers hiring and terminating workers in Brazil.

1. Brazil eSocial Deadlines in 2026: The Essential Comparison

The main event deadlines for ordinary private-sector employers are:

Obligation	Event or process	General deadline
Standard employee admission	S-2200	No later than the day before work begins
Preliminary employee admission	S-2190	No later than the day before work begins
Completion following valid S-2190	S-2200	Generally by the 15th of the following month, or sooner if a qualifying subsequent event must be filed
Ordinary employee termination	S-2299	Within 10 days after termination, with nonbusiness-day anticipation
Termination pay and required documents	CLT Article 477	Within 10 days after contract termination
Applicable termination FGTS	FGTS Digital	Generally D+10 for amounts classified as rescisory
Monthly remuneration reporting	S-1200	Generally by the 15th of the following month, before S-1299
Payment reporting	S-1210	Generally by the 15th of the month following payment
Monthly payroll closure	S-1299	Generally by the 15th of the following month
Ordinary monthly FGTS	FGTS Digital	Generally the 20th of the following month
Ordinary monthly DCTFWeb	DCTFWeb	Last business day of the following month

These deadlines are not interchangeable.

The admission and termination events are nonperiodic events. They arise because an individual employment relationship begins, changes or ends.

Monthly payroll events arise because remuneration and related taxable amounts must be reported for the relevant reporting period.

The distinction matters because a valid September payroll closing on October 15 does not retrospectively make a September admission or termination filing timely.

Official basis: eSocial Manual de Orientação, version S-1.3, consolidated through NO S-1.3 07/2026.

2. Original Ivvora Scenario: Five Hires and Five Terminations in September 2026

Assume a Brazilian company, Ivvora Brazil Operations Ltda., operates under the ordinary private-sector employment framework.

The company is a hypothetical employer used only for this analysis.

It has existing employees at the start of September and experiences ten personnel movements during the month.

Five people join. Five other employees leave.

The simulation assumes:

• All five new employees enter ordinary CLT employment, rather than a statutory public-service relationship or a special temporary-worker arrangement.
• The five departing employees have previously been fully registered in eSocial.
• The company uses the regular corporate eSocial payroll reporting workflow.
• National Brazilian holidays are applied to the date calculations.
• No municipal or state-specific holidays alter the illustrated deadlines.
• There is no judicial suspension, special extension or exceptional reporting arrangement.
• Each termination date is the legally applicable contract termination date recorded in eSocial, taking into account the employment notice arrangements.

All dates are actual calendar dates for 2026. Weekdays have been checked.

The ten employee movements

Employee	Movement	Effective date	Scenario
H01	Admission	September 1	Standard full admission
H02	Admission	September 8	Preliminary admission following national holiday
H03	Admission	September 14	Monday start requiring advance planning
H04	Admission	September 21	Preliminary admission near FGTS deadline
H05	Admission	September 30	Final-day-of-month hire
T01	Termination	September 2	Employer dismissal without just cause
T02	Termination	September 10	Employee resignation
T03	Termination	September 16	Scheduled expiry of fixed-term contract
T04	Termination	September 23	Mutual termination agreement under CLT Article 484-A
T05	Termination	September 29	Employer dismissal without just cause

The five hires and five departures are separate individuals.

That distinction matters because eSocial tracks individual employment relationships and their identifiers, not simply whether total company headcount increased or decreased.

A company can finish September with exactly the same employee headcount as it had on September 1 and still have ten distinct nonperiodic reporting obligations.

3. Five Hiring Scenarios: When Must S-2200 or S-2190 Be Sent?

For ordinary employment, employers generally must transmit the required admission information no later than the calendar day immediately preceding the employee’s first day of work.

There are two common reporting paths.

Full admission: The employer submits S-2200 with the necessary employee and contract information before work begins.

Preliminary admission: The employer submits S-2190 before work begins and then completes the registration through S-2200 within the applicable deadline.

S-2190 is optional. It is not a replacement for the full admission record.

Five-hire compliance matrix

Employee	First day	Filing path	Latest initial reporting date	Practical submission target
H01	Tue, Sep 1	Full S-2200	Mon, Aug 31	Aug 31
H02	Tue, Sep 8	S-2190 then S-2200	Mon, Sep 7	Fri, Sep 4
H03	Mon, Sep 14	Full S-2200	Sun, Sep 13	Fri, Sep 11
H04	Mon, Sep 21	S-2190 then S-2200	Sun, Sep 20	Fri, Sep 18
H05	Wed, Sep 30	S-2190 then S-2200	Tue, Sep 29	Sep 29

The practical submission targets are Ivvora’s operational recommendations, not substitute statutory deadlines.

This distinction is particularly important for weekend and holiday admissions.

H01: Employee starts September 1

The employee begins on Tuesday, September 1.

The full S-2200 should be accepted by Monday, August 31.

The employee’s September remuneration will subsequently be included in the applicable September payroll reporting.

No preliminary S-2190 is necessary because the full admission is submitted in advance.

Risk: Waiting until September 1 to submit the admission is not equivalent to submitting it by August 31.

H02: Employee starts September 8, immediately after a national holiday

September 7, 2026, is Brazil’s Independence Day holiday.

The employee starts on Tuesday, September 8.

The initial admission information must be submitted no later than the immediately preceding day, September 7.

Although electronic reporting may be technically possible outside normal office hours, a company should not depend on payroll staff processing a first-day admission during a national holiday.

A safer operational approach is to transmit S-2190 by Friday, September 4.

The employer then completes the registration through S-2200 by the applicable follow-up deadline.

For this case, the ordinary calendar deadline for completing S-2200 is October 15, provided no intervening event requires the full registration earlier.

H03: Employee starts Monday, September 14

The immediately preceding calendar day is Sunday, September 13.

Unlike the ordinary S-2299 termination deadline, the standard prior-day admission rule should not be treated as an automatic extension to the next business day.

For H03, the company should submit the full S-2200 no later than September 13.

Its recommended internal cutoff is Friday, September 11.

This is particularly important where employment contracts are finalized late on Fridays.

The practical issue: An HR team that only operates Monday through Friday can miss the statutory admission timing for a Monday starter even if it processes the information immediately upon returning to work.

H04: Employee starts Monday, September 21

The preceding calendar day is Sunday, September 20.

The company uses preliminary S-2190 reporting.

Its statutory prior-day admission requirement should be satisfied no later than September 20, with an internal target of Friday, September 18.

September 18 is also significant for the company’s August monthly FGTS payment, because September 20 falls on a Sunday.

Two separate workflows therefore converge on the same Friday:

1. The incoming employee must have admission reporting completed in advance.
2. The employer must settle ordinary August FGTS obligations that have not been accelerated to an earlier date.

H05: Employee starts September 30

The company submits S-2190 on September 29.

This allows the employee to start on September 30 while the full S-2200 is finalized afterward.

Under the ordinary completion rule, the full event is due by October 15.

However, that does not mean a preliminary registration can always remain incomplete until then.

If the employee experiences an event requiring a completed S-2200 — particularly a termination or a reportable absence — the employer must complete the full admission before transmitting that dependent event.

This becomes critical when an employee joins and leaves within a short period.

4. What Exactly Does S-2190 Allow an Employer to Delay?

S-2190 is the Registro Preliminar de Trabalhador.

It allows a qualifying employer to provide essential employment details before the employee starts without immediately transmitting every field required for the full S-2200.

For ordinary employees, the preliminary event includes core identifying and employment information, including the worker’s CPF, date of birth, admission date, registration number, category and other applicable fields required by the current layout.

However, the employer must subsequently submit the corresponding S-2200.

The three preliminary-admission cases

Employee	Preliminary S-2190 target	Full S-2200 ordinary deadline
H02	Sep 4	Oct 15
H04	Sep 18	Oct 15
H05	Sep 29	Oct 15

These dates assume the company does not need to transmit another nonperiodic event that requires the full admission record sooner.

In addition, completion of S-2200 must be coordinated with the September payroll closing.

A common misunderstanding

An employer might assume:

“We filed S-2190 before the employee joined, so we can wait until next month’s payroll to deal with everything else.”

That is incomplete.

The official eSocial manual states that S-2200 is required before certain subsequent events, including termination and temporary absence, and that full registration supports the relevant employment registration and CTPS obligations.

The 2026 manual also distinguishes the information required to comply with CTPS obligations from broader requirements concerning employment registration, RAIS and CAGED.

A preliminary event that is technically accepted does not necessarily prove every related labor-registration obligation has been satisfied.

Important qualification: The standard rule for ordinary direct hires should not be applied indiscriminately to workers hired by temporary-work companies under Law No. 6,019/1974. Their specific S-2200 reporting rules can permit five business days after work begins, subject to the applicable conditions. Transfers and statutory public servants also have different rules.

Source: eSocial MOS S-1.3 (2026), sections S-2190 and S-2200.

5. Five Termination Scenarios: The S-2299 Deadline Is Not the Monthly Closing Deadline

S-2299, Desligamento, is the principal termination reporting event for ordinary employment contracts.

The general eSocial deadline is ten days from the termination date, excluding the day of termination from the count.

The official manual makes an important adjustment:

If the tenth day falls on a nonbusiness day for fiscal purposes, the ordinary S-2299 transmission deadline is brought forward to the immediately preceding business day.

This is not the same weekend adjustment applied to ordinary monthly eSocial closure, which generally moves to the next business day.

Five-termination compliance matrix

Employee	Termination date	D+10 calendar date	Adjusted S-2299 deadline	Termination type
T01	Wed, Sep 2	Sat, Sep 12	Fri, Sep 11	Dismissal without just cause
T02	Thu, Sep 10	Sun, Sep 20	Fri, Sep 18	Employee resignation
T03	Wed, Sep 16	Sat, Sep 26	Fri, Sep 25	End of fixed-term contract
T04	Wed, Sep 23	Sat, Oct 3	Fri, Oct 2	Mutual termination agreement
T05	Tue, Sep 29	Fri, Oct 9	Fri, Oct 9	Dismissal without just cause

Four of the five cases require an earlier S-2299 filing date because the tenth calendar day falls on a weekend.

The fifth has a normal Friday deadline.

All five termination reporting deadlines occur before the October 15 monthly payroll closing deadline.

This is precisely why employers cannot manage terminations exclusively through their monthly payroll calendar.

T01: Dismissal on September 2

The worker’s employment ends on September 2.

Day one of the ten-day period is September 3.

Day ten is Saturday, September 12.

Because the ordinary S-2299 deadline cannot be carried forward to the following Monday under the general rule, the employer must transmit the event by Friday, September 11.

The company also needs to calculate the employee’s applicable termination entitlements.

For a qualifying employer-initiated dismissal without just cause, those may include:

• Outstanding salary balance.
• Applicable notice-period compensation.
• Accrued and proportional vacation entitlements with the applicable constitutional additional payment.
• Proportional 13th salary.
• Applicable FGTS deposits and the 40% indemnification based on the legally relevant FGTS balance.

The exact amounts depend on employment history, remuneration, notice treatment, already-paid entitlements and applicable legal or collective arrangements.

T02: Employee resigns on September 10

The worker resigns, and the legally relevant employment termination date is September 10.

Day ten falls on Sunday, September 20.

The S-2299 deadline therefore becomes Friday, September 18.

The employer still has termination reporting and settlement obligations.

However, an ordinary employee resignation generally does not trigger the same FGTS withdrawal and indemnification treatment as an employer dismissal without just cause.

The relevant September remuneration and FGTS amounts are ordinarily classified under the monthly FGTS cycle rather than automatically generating a rescisory FGTS payment due within ten days.

This is a major difference between S-2299 and FGTS Digital.

Every ordinary termination may require S-2299, but not every termination creates an FGTS Digital rescisory debt with a D+10 payment deadline.

T03: Fixed-term contract expires September 16

Assume a lawful fixed-term contract ends on its scheduled expiry date.

The S-2299 deadline falls on Friday, September 25, because day ten is Saturday, September 26.

A scheduled contract expiry may permit withdrawal of the FGTS balance under the applicable legal conditions. Consequently, the company must review the FGTS Digital classification and pay relevant rescisory FGTS amounts by the applicable deadline.

The employer should not automatically budget a 40% dismissal indemnity for every scheduled fixed-term expiry.

It must distinguish:

• Scheduled expiry of a fixed-term contract.
• Early termination by the employer.
• Early termination by the employee.
• Special contractual clauses or statutory exceptions affecting compensation.

Those scenarios can produce different termination entitlements even where their S-2299 reporting deadline calculation is identical.

T04: Mutual termination agreement on September 23

Assume the employment relationship ends through a valid agreement under CLT Article 484-A.

The ordinary S-2299 deadline is October 2.

This type of termination can involve reduced statutory notice-related compensation and a 20% FGTS termination indemnification instead of the normal 40% employer-dismissal indemnification, subject to the governing legal conditions.

The employer must calculate the lawful termination settlement rather than simply applying the same calculations used for a dismissal without just cause.

The relevant FGTS Digital rescisory obligations generally follow the D+10 framework.

T05: Employer dismissal on September 29

The worker’s contract ends on September 29.

Day ten is Friday, October 9.

No weekend adjustment is needed.

The important point is that the deadline falls in October even though the employment termination belongs to September.

The employer cannot wait until October 15 merely because the September payroll closing is due that day.

The S-2299 must already have been transmitted by October 9.

6. The Three Different Ten-Day Rules Employers Must Not Confuse

Three separate obligations often appear alongside termination.

They may share a ten-day reference period but are not identical legal processes.

Obligation	Authority/system	Key requirement
Report termination	eSocial S-2299	Generally D+10, with earlier submission if the tenth day is fiscally nonbusiness
Pay termination entitlements	CLT Article 477	Payment within ten days after the end of the employment contract
Deposit applicable rescisory FGTS	FGTS Digital	D+10, with payment deadline brought forward when it falls on a nonbusiness banking day

The safest practice is to create separate workflow records for each obligation.

For example, T01 requires the employer to:

1. Prepare and transmit S-2299 by September 11.
2. Pay and document the applicable termination settlement within the statutory period.
3. Deposit the applicable rescisory FGTS by the adjusted September 11 deadline.

These should not be treated as one payment.

The employee’s termination settlement is not the same transaction as the employer’s FGTS Digital deposit.

Nor does successful S-2299 acceptance prove that the employee was paid.

How should employers handle weekend termination pay?

Article 477, paragraph 6, of the CLT generally requires payment of the applicable termination amounts and delivery of the relevant termination documentation within ten days from contract termination.

For the five worked examples, Ivvora’s conservative operating schedule places employee settlement no later than the same Friday used for the adjusted S-2299 deadline.

That is an operational safeguard, particularly when a bank transfer would otherwise be scheduled for a weekend.

It should not be confused with a blanket assertion that every employment-law payment deadline follows precisely the same fiscal nonbusiness-day rule as S-2299.

Employers must verify their applicable payment method, collective agreements, judicial interpretations and the legally effective date of termination.

A late termination payment can trigger consequences under Article 477, including the statutory penalty described in paragraph 8, where applicable.

Source: Brazil’s Consolidation of Labor Laws — CLT, Articles 477 and 484-A.

7. FGTS Digital: Why an Early-Month Dismissal Can Accelerate the Previous Month’s Deposit

One of the least intuitive timing problems appears when an employee is dismissed near the beginning of a month.

The employer may assume all FGTS on the previous month’s wages remains payable on the ordinary 20th-day deadline.

That can be wrong.

For termination types that confer the relevant FGTS withdrawal right, FGTS Digital can classify outstanding deposits from the month immediately preceding termination as rescisory, requiring payment by the termination deadline.

The Ministry of Labor specifically explains this treatment for dismissals occurring between the 1st and 9th of a month.

T01: September 2 dismissal

Assume the employee’s August FGTS contribution remains unpaid on September 2.

The employer’s ordinary August FGTS deadline would be September 18, 2026, because the nominal September 20 deadline falls on a Sunday.

However, T01 is dismissed without just cause on September 2.

The termination-related payment date becomes September 11.

Under the applicable classification rules, the employee’s outstanding August FGTS can therefore become payable by September 11 rather than September 18.

Original Ivvora cash-flow example

Assume T01 had R$5,000 of FGTS-assessable August remuneration and was subject to the standard 8% deposit rate.

August FGTS:

R$5,000 × 8% = R$400.

Item	Without termination	With qualifying Sep 2 termination
August FGTS base	R$5,000	R$5,000
August FGTS liability	R$400	R$400
Original monthly payment date	Sep 18	Sep 18 before reclassification
Applicable final deposit date	Sep 18	Sep 11
Principal FGTS amount	R$400	R$400

The R$400 is not an additional tax or termination penalty.

It is an existing employer liability whose required payment date has been accelerated.

The acceleration is seven calendar days in this example.

If the August FGTS had already been correctly deposited, there would be no outstanding R$400 principal to accelerate.

The same employer must also calculate T01’s September termination-related FGTS and any applicable FGTS indemnification.

The termination classification controls which amounts are brought into the rescisory collection workflow.

Why T02 is different

T02 resigns on September 10.

An ordinary voluntary resignation generally does not create a rescisory FGTS collection with the same withdrawal treatment.

Its September remuneration-related FGTS ordinarily retains the monthly payment classification.

For September 2026, the ordinary monthly FGTS payment deadline is October 20, 2026.

This provides a useful comparison:

Employee	Termination reason	S-2299 due	September FGTS treatment
T01	Employer dismissal without just cause	Sep 11	Applicable rescisory FGTS by Sep 11
T02	Employee resignation	Sep 18	Generally monthly FGTS by Oct 20
T03	Scheduled fixed-term expiry	Sep 25	Applicable rescisory FGTS by Sep 25
T04	Valid Article 484-A agreement	Oct 2	Applicable rescisory FGTS by Oct 2
T05	Employer dismissal without just cause	Oct 9	Applicable rescisory FGTS by Oct 9

The table assumes the termination reason in each relevant case produces the stated FGTS classification under the current FGTS Digital rules.

The legally applicable classification, rather than the employer’s preferred payment schedule, determines the required deposit timing.

Sources:

Ministry of Labor — FGTS Digital: classification of monthly and rescisory amounts

Ministry of Labor — Automatic adjustment for early-month terminations

FGTS Digital official frequently asked questions

8. The Complete Date-by-Date Compliance Timeline: August–November 2026

The following timeline combines all ten employee movements with the relevant reporting and settlement milestones.

It is designed as an operational test case for payroll teams and external payroll providers.

Date	Event or obligation	Required operational action
Aug 31, Mon	H01 begins Sep 1	Submit full S-2200
Sep 1, Tue	H01 starts work	Confirm accepted admission and first-day eligibility
Sep 2, Wed	T01 terminated	Begin termination settlement and S-2299 preparation
Sep 4, Fri	H02 preliminary admission	Recommended early S-2190 filing
Sep 7, Mon	National holiday	H02’s statutory preceding-calendar-day admission deadline
Sep 8, Tue	H02 starts	Verify accepted S-2190
Sep 10, Thu	T02 resigns	Prepare S-2299 and settlement
Sep 11, Fri	T01 D+10 adjusted deadline	Submit S-2299, settle applicable FGTS and target final pay
Sep 11, Fri	H03 admission	Recommended full S-2200 submission before Monday start
Sep 14, Mon	H03 starts	Confirm prior admission accepted
Sep 16, Wed	T03 contract ends	Prepare S-2299, settlement and relevant FGTS
Sep 18, Fri	T02 D+10 adjusted deadline	Submit S-2299 and target employment settlement
Sep 18, Fri	August ordinary FGTS	Pay remaining August monthly FGTS
Sep 18, Fri	H04 admission	Recommended S-2190 submission
Sep 21, Mon	H04 starts	Confirm preliminary admission
Sep 23, Wed	T04 agreement termination	Prepare S-2299 and settlement
Sep 25, Fri	T03 D+10 adjusted deadline	Complete S-2299 and applicable rescisory FGTS
Sep 29, Tue	T05 contract ends	Begin settlement and S-2299 workflow
Sep 29, Tue	H05 preliminary admission	Submit S-2190 before Sep 30 start
Sep 30, Wed	H05 starts	Confirm admission receipt
Sep 30, Wed	Payroll period ends	Finalize September remuneration inputs
Oct 2, Fri	T04 D+10 adjusted deadline	Complete S-2299 and applicable rescisory FGTS
Oct 6, Tue	September ordinary salary payment target	Meet applicable fifth-business-day requirement, subject to payment rules
Oct 9, Fri	T05 D+10 deadline	Submit S-2299, complete relevant FGTS and settlement
Oct 15, Thu	September eSocial close	Complete required September S-1200, S-1210 and S-1299 events
Oct 15, Thu	Preliminary hires	Complete S-2200 for H02, H04 and H05 if not required earlier
Oct 20, Tue	September ordinary FGTS	Pay outstanding monthly FGTS obligations
Oct 20, Tue	Ordinary September federal payroll contributions	Settle applicable federal taxes subject to their own statutory due dates
Oct 30, Fri	September DCTFWeb	Transmit required declaration by the last business day
Nov 16, Mon	October eSocial close and payment reporting	Complete applicable October events, including S-1210 for relevant October payments

Important calendar notes

September 7 is a national holiday. September 20 is a Sunday, bringing the ordinary August FGTS deadline forward to September 18.

October 12 is a national holiday. It does not extend T05’s October 9 termination deadline.

October 15, 2026, is a Thursday. Therefore, the ordinary September eSocial closing deadline requires no weekend adjustment.

October 20 is a Tuesday. The ordinary September monthly FGTS deadline remains October 20, except where individual liabilities have already become subject to earlier termination-related payment deadlines.

October 31 is a Saturday. Consequently, the ordinary September DCTFWeb deadline is Friday, October 30.

November 15 is a Sunday. The ordinary October eSocial monthly deadline moves to Monday, November 16.

For the October 6 salary-payment entry, the ordinary fifth-business-day analysis counts Saturday as a business day for the relevant wage-payment calculation. Employers paying through banking systems must make sure employees receive funds on time and must consider applicable collective agreements and local rules.

The timeline is based on the national calendar and the specified scenarios. An employer must additionally check state holidays, municipal holidays, banking holidays, special payroll regimes and any formal government extension affecting its particular obligation.

9. The Critical Difference Between S-2299 and S-1200 in the Termination Month

There is another practical issue that ordinary deadline calendars rarely explain.

Employers sometimes expect every employee to appear in the same monthly S-1200 event, regardless of whether the employee remains active or was terminated during the month.

That assumption can cause duplicate or incorrect reporting.

For an ordinary terminated employment relationship, eSocial generally requires the employee’s termination remuneration and severance items to be included in S-2299, rather than creating an ordinary S-1200 for the same terminated relationship in that competence.

The system has defined exceptions, including certain continuity/transfer situations, multiple employment relationships and cases covered by its specific remuneration validation rules.

September reporting model

Worker	Employment position in September	Principal remuneration reporting
H01	Active from Sep 1	S-1200
H02	Active from Sep 8	S-1200
H03	Active from Sep 14	S-1200
H04	Active from Sep 21	S-1200
H05	Active from Sep 30	S-1200
T01	Terminated Sep 2	S-2299
T02	Terminated Sep 10	S-2299
T03	Terminated Sep 16	S-2299
T04	Terminated Sep 23	S-2299
T05	Terminated Sep 29	S-2299

This table shows the principal route for the illustrated employment relationship. It is not a prohibition against all possible S-1200 events for the same CPF where an explicit eSocial exception applies.

The important operational conclusion is that the September payroll reconciliation should not simply require ten S-1200 remuneration events for these ten individuals.

Five employees are active hires.

Five have termination remuneration reported through S-2299.

The correct employee-level reconciliation must understand both routes.

Why payroll closing still matters

The S-1299 closing event consolidates applicable data from periodic events and termination events.

The eSocial system then processes tax and FGTS bases and communicates the relevant information to downstream systems.

This means a termination submitted on September 11 can affect the September tax calculation ultimately consolidated through the October 15 closing process.

The fact that the termination was already reported does not make its financial effects irrelevant to the monthly reconciliation.

Source: eSocial MOS S-1.3, sections S-2299, S-1200 and S-1299.

10. A Second Calendar Trap: S-1210 Follows the Payment Month

The eSocial S-1210 event reports payments of employment income.

This creates an important distinction between:

• The period in which remuneration was earned.
• The period in which termination entitlements became due.
• The month in which cash was actually paid.

Consider the five termination scenarios.

For this simulation, assume the company makes the following actual employee settlement payments:

Employee	Termination date	Employee paid	S-1210 payment month	Ordinary reporting deadline
T01	Sep 2	Sep 11	September	Oct 15
T02	Sep 10	Sep 18	September	Oct 15
T03	Sep 16	Sep 25	September	Oct 15
T04	Sep 23	Oct 2	October	Nov 16
T05	Sep 29	Oct 9	October	Nov 16

The termination event remains part of the relevant employment and remuneration reporting for September.

However, the payment reporting follows the month in which the employee actually receives the payment, according to the applicable S-1210 rules.

T04 illustrates the difference particularly clearly:

1. Employment ends September 23.
2. S-2299 is transmitted by October 2.
3. Termination entitlements are paid October 2.
4. The applicable payment is reported through October S-1210.
5. October S-1210 is due November 16.

The payment date also matters for relevant withholding-tax treatment.

A September termination can therefore require a September termination event and an October payment event without either record being inherently inconsistent.

This is why a payroll reconciliation cannot blindly match every cash payment to an S-1210 with the same reporting period as the underlying S-2299.

Source: eSocial WEB Geral Manual — S-1210 payment reporting.

11. From Termination to Federal Tax Declaration: The Full eSocial–DCTFWeb Chain

The ten employee movements eventually feed the employer’s payroll tax position.

However, the underlying systems perform different functions.

Stage	System	Principal purpose
Admission	eSocial S-2190/S-2200	Establish employment information
Termination	eSocial S-2299	Declare employment termination and applicable remuneration
Ongoing remuneration	eSocial S-1200	Declare ordinary payroll earnings and relevant bases
Payments	eSocial S-1210	Report employment income payments
Payroll closing	eSocial S-1299	Close and consolidate the period
Tax declaration	DCTFWeb	Declare federal tax debts and credits
Federal tax settlement	DARF	Pay applicable federal tax liabilities
FGTS reporting and collection	FGTS Digital	Determine and collect applicable monthly and rescisory FGTS

DCTFWeb does not independently reconstruct every employee’s taxable earnings or recalculate all underlying payroll taxes from the raw personnel data.

Receita Federal’s official guidance states that the relevant debit calculations originate in eSocial, EFD-Reinf or MIT, depending on the tax and the reporting source.

DCTFWeb receives the resulting information.

That distinction determines how employers must handle corrections.

September reconciliation checkpoints

For the hypothetical company, finance should verify:

Checkpoint A — Admission completeness

Five employees started work.

All five should have accepted initial admission events by their respective deadlines.

For H02, H04 and H05, the corresponding full S-2200 records must also be completed within the applicable time limit.

Checkpoint B — Termination completeness

Five employees had employment relationships terminated.

There should be accepted S-2299 events for the five terminations, using the correct termination reasons and effective dates.

Checkpoint C — Remuneration completeness

The September reporting must cover the five new hires’ eligible remuneration and the departing employees’ applicable termination remuneration.

Checkpoint D — FGTS reconciliation

The FGTS records must distinguish ordinary monthly deposits from amounts that acquired rescisory payment dates.

T01’s outstanding August FGTS is a particularly important control because of the early-month payment acceleration.

Checkpoint E — Closing and tax declaration

The final September S-1299 closing should be reconciled to the resulting federal tax amounts and to the DCTFWeb declaration transmitted by October 30.

Where other sources such as EFD-Reinf or MIT apply, those values must also be included in the DCTFWeb reconciliation.

The company must not mistake an accepted S-2299 receipt for proof of tax payment or assume that a DCTFWeb receipt proves that individual employment settlement obligations were met.

12. What Happens If a Hire or Termination Is Reported Incorrectly?

Errors should be distinguished by the event and whether the corresponding reporting period has already been closed.

Error A: Employee started work before any admission event

Assume H03 begins work on September 14, but no S-2200 or valid S-2190 had been transmitted by September 13.

The employer discovers the omission on September 16.

Submitting the event on September 16 may correct the missing system record, but it does not retrospectively change the fact that the prior-day deadline was missed.

The employer should transmit the correct information as soon as possible, retain the accurate dates and assess any employment-registration compliance exposure.

It should not invent a later start date merely to make the filing appear timely.

Error B: The S-2190 has the wrong admission date

Assume H02 was correctly admitted on September 8 but the preliminary event incorrectly shows September 9.

The 2026 eSocial manual specifies that errors involving core identifying information — including the admission date and relevant identification fields — require the appropriate correction of S-2190 before the corresponding full S-2200 is submitted.

If the full S-2200 has already been transmitted, the manual provides a different correction path that must be followed.

The employer should preserve the true commencement date and ensure dependent records remain consistent.

Error C: Termination was filed with the wrong remuneration

Assume T05’s S-2299 was transmitted on October 9 but omitted an overtime entitlement of R$1,000 payable as part of the lawful termination settlement.

The employer must determine the correct treatment of the omitted amount, including its employment entitlement and the appropriate INSS, FGTS and income-tax incidence.

The correct amounts must be reflected in the originating eSocial information.

Simply changing an amount in a downstream payment worksheet does not correct the original eSocial event.

If the September closing has already been completed, the employer may need to:

1. Reopen the affected period using S-1298 where required.
2. Correct the relevant S-2299 or other originating records.
3. Submit a new S-1299 closing.
4. Review the recalculated eSocial totals.
5. Review the resulting DCTFWeb rectification.
6. Reconcile any additional federal taxes, credits and FGTS differences.

The specific retification sequence depends on whether the period was closed and which event is being corrected.

Why DCTFWeb needs separate attention

Receita Federal confirmed in its April 13, 2026 guidance that correcting information in an already-closed eSocial or EFD-Reinf period can produce a new DCTFWeb rectifying declaration in the status em andamento.

The employer must then address that pending rectification.

The tax authority’s DCTFWeb manual also explains that a rectifying declaration generated after an originating-system change must be transmitted, even where the tax totals ultimately remain unchanged, to maintain reporting integrity.

In other words:

Correcting an eSocial termination event is not necessarily the final step in correcting the company’s federal payroll tax reporting.

The correct procedure extends through the new closing and, where applicable, transmission of the resulting DCTFWeb retification.

Sources:

Receita Federal — April 2026 eSocial/EFD-Reinf and DCTFWeb correction guidance

Receita Federal — DCTFWeb Manual, January 2025

13. A Common Financial Error: Confusing the Ten-Day FGTS Deadline With the Twentieth-Day Monthly Deadline

Consider the employer’s September FGTS obligations.

The company’s active employees generally generate monthly FGTS liabilities payable by October 20.

But T01, T03, T04 and T05 each have termination types requiring analysis of rescisory FGTS deposits.

These deposits may be due on:

• September 11 for T01.
• September 25 for T03.
• October 2 for T04.
• October 9 for T05.

The payment dates depend on each contract termination and the classification of its FGTS debts.

If the employer pays all September FGTS through one ordinary monthly payment on October 20, it may have paid some rescisory liabilities late.

Conversely, if it treats every resignation as generating immediate rescisory FGTS, it may misclassify normal monthly obligations and create unnecessary payment reconciliation problems.

An employer’s September FGTS audit table

Employee group	Relevant payment cycle	Audit question
Active employees	Monthly FGTS	Was the correct amount included by Oct 20?
T01	Rescisory	Were the September termination amounts and any accelerated August amounts settled by Sep 11?
T02	Generally monthly	Was resignation correctly classified without an unwarranted rescisory FGTS debt?
T03	Relevant rescisory FGTS	Were applicable deposits settled by Sep 25?
T04	Relevant rescisory FGTS	Were the applicable agreement-termination deposits settled by Oct 2?
T05	Rescisory	Were the termination amounts settled by Oct 9?

The employer must compare each worker’s actual FGTS Digital assessment and paid guide, not just a single company-level monthly total.

14. What Can Go Wrong Even When Every Monthly Payroll Filing Is On Time?

A company may transmit all its monthly payroll events and DCTFWeb declarations within their deadlines but still have unresolved nonperiodic compliance failures.

Examples include:

Situation	Monthly payroll status	Separate compliance problem
Employee started before S-2190/S-2200	Monthly closing timely	Admission reporting late
S-2190 transmitted but S-2200 remains incomplete	Monthly closing may have occurred	Full admission or related registration obligations unresolved
S-2299 transmitted after D+10	Monthly closing timely	Termination event late
S-2299 submitted on time, employee paid late	eSocial event timely	Labor settlement deadline breached
S-2299 accepted, rescisory FGTS not deposited	eSocial event timely	FGTS payment outstanding
eSocial closing corrected but DCTFWeb retification not transmitted	eSocial correction made	Downstream declaration incomplete
FGTS monthly deposit paid October 20 despite earlier rescisory due date	Monthly payment may appear complete	Termination-specific deposit late

These are distinct operational failures.

They should not be collapsed into one generic “Brazil payroll filing completed” status.

The actual compliance evidence differs for each one.

15. Penalty Exposure: Which Error Creates Which Risk?

Brazil does not have one universal financial penalty that applies equally to every missed eSocial or payroll deadline.

Potential consequences depend on the breached obligation and governing law.

Breach	Potential consequence
Late admission reporting	Employment-registration and related administrative enforcement exposure
Incomplete or incorrect CTPS information	Related labor-registration and annotation compliance exposure
Late S-2299	eSocial reporting and potentially related employment-document compliance exposure
Late termination settlement	Potential Article 477 CLT penalty and related worker claims
Late FGTS deposits	Applicable FGTS collection charges, enforcement and labor consequences
Late federal payroll taxes	Tax-payment mora penalty and applicable interest
Late DCTFWeb	Separate declaration-filing penalty, where legally applicable

An employer should not automatically calculate a flat per-worker eSocial penalty without identifying the specific statutory infraction, applicable company category, enforcement procedure and current penalty schedule.

The Article 477 termination-settlement penalty is also distinct from tax late-payment penalties and FGTS charges.

A payroll provider may face contractual responsibility for missed filing obligations, but that must be assessed against the actual services contracted and the employer’s legal obligations.

16. The Employer–Payroll Provider Responsibility Matrix

An internationally managed company often relies on a local payroll provider to transmit eSocial and prepare statutory payment data.

This arrangement works only if the provider learns about admissions and terminations early enough.

For example, notifying the provider on September 8 that a worker already started that morning may be too late to satisfy the prior-day admission requirement.

Recommended operational responsibility split

Process	Employer/HR responsibility	Payroll provider responsibility
New hire approved	Confirm contract, actual start date and employment classification	Verify information required for eSocial
Before new hire starts	Supply complete and accurate information in advance	Submit S-2200 or valid S-2190 and return receipt
Preliminary admission completion	Resolve missing employment details	Submit complete S-2200 within deadline
Termination approved	Confirm actual legal termination date, reason and notice	Calculate entitlements and prepare S-2299
Within termination period	Authorize and fund settlement promptly	Submit S-2299 and prepare applicable payment details
FGTS settlement	Fund the required deposits	Reconcile FGTS Digital debts and guides
Monthly payroll	Approve remuneration and changes	Submit periodic events and close S-1299
Federal declarations	Confirm responsible signatory and filing accountability	Prepare or transmit DCTFWeb under agreed scope
Post-filing reconciliation	Review outstanding risks and approve corrections	Provide receipts, corrections and updated reconciliations

This is a recommended commercial workflow, not a substitution for statutory employer responsibility.

A strong service agreement should specify:

• The advance notice required for hires and terminations.
• Which party submits S-2190, S-2200 and S-2299.
• Who calculates and authorizes termination payments.
• Who generates FGTS Digital guides.
• Who actually initiates the payments.
• Who verifies accepted eSocial receipts.
• Who is responsible for eSocial and DCTFWeb correction workflows.
• How late employee information or rejected submissions are escalated.

Without this separation, each party may assume another is responsible for a deadline that has already passed.

17. A Better Compliance Control: Manage Employment Events Independently of Payroll Cycles

Monthly payroll calendars are useful, but they are insufficient to manage all employment-related events in Brazil.

For each new hire, maintain a record containing:

• Employee identifier and legally correct start date.
• Planned initial reporting method.
• Prior-day reporting deadline.
• Actual transmission date.
• Accepted eSocial receipt.
• Full S-2200 completion deadline if S-2190 was used.
• Evidence of completion.

For each termination, maintain:

• Employee identifier and actual legal termination date.
• Termination reason and applicable notice treatment.
• S-2299 deadline.
• S-2299 acceptance receipt.
• Employee settlement deadline and confirmed payment date.
• FGTS Digital classification.
• FGTS payment deadline and receipt.
• Required payment reporting month.
• Resulting tax and payroll reconciliation status.

The most effective control is an exception report triggered immediately whenever a new employment event is approved.

The provider should not wait for the ordinary month-end payroll data collection cycle to discover that an employee has joined or left.

Three distinct status indicators

For an operational audit, each movement should be independently classified as:

Event reporting: Was the correct admission or termination event accepted within the applicable deadline?

Financial settlement: Were employee entitlements and applicable statutory deposits paid within their respective deadlines?

Monthly reconciliation: Were the resulting payroll bases, tax declarations and payment records correctly reflected in the relevant monthly systems?

A completed monthly reconciliation does not repair an earlier filing delay.

A timely admission event does not prove that wages or later taxes were calculated correctly.

A timely termination event does not prove that settlement and FGTS payments occurred on time.

All three controls are necessary.

18. Frequently Asked Questions

What is the eSocial admission deadline in Brazil in 2026?

For an ordinary CLT employee, the full S-2200 admission must generally be transmitted no later than the day before work begins. An eligible preliminary S-2190 can be transmitted instead, followed by full S-2200 completion within the applicable deadline.

Can I register a Brazilian employee on their first working day?

For ordinary admissions subject to the prior-day rule, filing on the first day is generally late. The applicable admission information should already have been accepted by the preceding calendar day.

Is S-2190 sufficient to register an employee permanently?

No. S-2190 is a preliminary admission event. The employer must subsequently complete the registration through S-2200, subject to the timing and dependency rules.

What is the S-2299 termination filing deadline?

For ordinary termination cases, the employer generally has ten days after termination, excluding the termination date. If day ten falls on a nonbusiness day for fiscal purposes, the S-2299 deadline is brought forward to the previous business day. Special exceptions apply to certain transfers, CPF changes and statutory employment relationships.

Does the eSocial termination deadline move to Monday when it falls on Sunday?

Not under the general ordinary S-2299 rule. The deadline moves to the immediately preceding fiscal business day.

For example, T02 terminates September 10, 2026. D+10 falls on Sunday, September 20, so S-2299 must be transmitted by Friday, September 18.

Is the deadline for paying termination entitlements identical to the eSocial filing deadline?

They are separate obligations under different legal rules. Both generally involve a ten-day reference period, but the employer must evaluate the legally applicable payment conditions and any relevant nonbusiness-day treatment separately.

Does every employee termination require rescisory FGTS payment within ten days?

No. The FGTS payment classification depends on the legal reason for termination and the applicable withdrawal and deposit rules. Ordinary voluntary resignation generally retains monthly FGTS treatment rather than generating a termination-related FGTS collection.

Can a September dismissal require payment of August FGTS earlier than September 20?

Yes. For qualifying terminations, outstanding FGTS relating to the immediately preceding month can be accelerated to the rescisory payment deadline. The Ministry of Labor specifically addresses this issue for early-month terminations.

Does a terminated employee still appear in monthly S-1200?

The remuneration for an ordinarily terminated employment relationship is generally reported within S-2299 in the termination competence. Specific eSocial rules permit exceptions, including certain transfers and multiple-contract situations.

If an employee is terminated in September but paid in October, which S-1210 month applies?

The payment is generally reported in the month in which it actually occurred. An October settlement payment can therefore be reflected in October S-1210 even though the employment termination was reported for September.

Can an employer wait until monthly payroll closing to report a dismissal?

No. Ordinary S-2299 termination reporting follows its own ten-day deadline. The following month’s S-1299 payroll closing deadline does not replace that obligation.

What happens after an S-2299 correction changes payroll tax amounts?

The employer must correct the applicable originating eSocial information, address any required reopening and new closing, and review the resulting DCTFWeb rectification. Receita Federal confirms that a corrected originating closing can generate a DCTFWeb retificadora.

What is the ordinary September 2026 monthly eSocial closing deadline?

October 15, 2026, for the ordinary monthly S-1299 workflow used in the simulation.

What is the ordinary September 2026 DCTFWeb deadline?

October 30, 2026, which is the final business day of October.

19. Final Takeaway: Brazil Employment Events Must Be Managed Before Month-End Payroll

The ten-employee model produces three central findings.

First, admission reporting cannot normally wait until the first payroll run. Ordinary employees must have their initial S-2200 or eligible S-2190 reporting completed before starting work.

Second, termination reporting cannot wait until the following month’s payroll-closing deadline. The ordinary S-2299 event follows a ten-day reporting period, with an earlier deadline when day ten is not a fiscal business day.

Third, termination-related financial obligations do not all share one payment deadline. Employee settlement, FGTS deposits, federal payroll taxes and DCTFWeb declarations must be managed separately.

For the ten illustrative workers, the deadlines range from August 31 for the first admission to November 16 for certain October payment reporting.

A company can comply with all ordinary September monthly payroll deadlines while still missing an individual admission, termination, settlement or FGTS obligation earlier in the reporting cycle.

The proper operating model is therefore not a single monthly payroll checklist.

It is an event-driven compliance process that begins before a worker joins, responds immediately when employment ends, and carries the resulting information through eSocial, FGTS Digital, DCTFWeb and payment reconciliation.

For international employers hiring in Brazil, this distinction should be incorporated into every payroll operating procedure and every agreement with an outsourced payroll provider.

Ivvora helps international employers understand Brazil’s employment, payroll and statutory compliance requirements, including hiring, terminations, payroll costs and employer reporting responsibilities.

Explore more Brazil employer compliance resources at Ivvora.

---

Official Sources and Legal References

The following Brazilian government materials provide the primary legal and administrative basis for the procedures and timelines in this article.

1. eSocial — Manual de Orientação do eSocial, version S-1.3, consolidated through NO S-1.3 07/2026.

The principal 2026 technical reference for S-2190, S-2200, S-2299, S-1200, S-1210, S-1298 and S-1299. The manual establishes the core event deadlines, dependencies, reporting rules and correction mechanisms.

Official 2026 eSocial Manual (PDF)

2. eSocial — Manual WEB Geral.

Operational guidance for submitting admission and termination events, including weekend adjustments, the relationship between preliminary and full admissions and payroll reporting.

Official eSocial WEB Geral Manual

3. Brazil — Consolidação das Leis do Trabalho (CLT), Decree-Law No. 5,452/1943.

Article 477 governs relevant termination settlement obligations and deadlines. Article 484-A addresses termination by mutual agreement.

Official CLT consolidated text

4. Ministry of Labor and Employment — FGTS Digital classification and payment timing.

Official explanation of the monthly and rescisory classification of FGTS obligations, including changes in payment deadlines associated with terminating an employment relationship.

Official FGTS Digital classification guidance

5. Ministry of Labor and Employment — Accelerated previous-month FGTS deposits for early-month terminations.

Explains the automatic adjustment of relevant prior-month FGTS debts when a qualifying employee termination occurs during the first nine days of a month.

Official early-termination FGTS guidance

6. Ministry of Labor and Employment — FGTS Digital Frequently Asked Questions.

Provides clarification on payment timing, termination reasons, FGTS collection types, payment adjustments, and handling of corrected remuneration and termination information.

Official FGTS Digital FAQ

7. Receita Federal — DCTFWeb official service.

Confirms the monthly DCTFWeb reporting framework and its ordinary last-business-day filing deadline.

Official DCTFWeb service

8. Receita Federal — Integration of eSocial/EFD-Reinf corrections into DCTFWeb, April 13, 2026.

Confirms that changes to a closed originating report can generate a DCTFWeb retifying declaration, with the new declaration requiring subsequent attention.

Official April 2026 clarification

9. Receita Federal — DCTFWeb Manual, January 2025.

Technical explanation of DCTFWeb integration, originating-system calculations, rectification, transmission and subsequent compliance consequences.

Official DCTFWeb Manual (PDF)

10. Brazil — Law No. 8,036/1990.

Provides the underlying statutory framework for FGTS contributions, termination-related deposits and applicable indemnification.

Official FGTS legislation

Methodology and verification note: This is an original, fully synthetic employer simulation designed to illustrate the applicable 2026 deadlines. The ten personnel records are hypothetical and do not represent actual employees. Dates were calculated using the 2026 national calendar. The analysis assumes ordinary CLT employment and the specified termination categories, without unlisted state or municipal holidays, special agreements or legal exceptions. Specific employer classifications, public-sector rules, temporary employment, judicial decisions, individual notice arrangements and collective bargaining instruments may change the applicable requirements. The article reflects official materials available through October 16, 2026 and should be read alongside the current eSocial manual and the legally applicable documents for each employment relationship.