Pular para o conteúdo
Specialty · eSocial

eSocial in SAP: events, withholdings and reconciliation with DCTFWeb

eSocial is not a monthly file. It is a chain of signed events that build on each other. Payroll becomes remuneration, payment becomes its own event, and the closing is what carries social security debt and payroll income tax to DCTFWeb.

DFSpro focuses on how the data is born in SAP, where an event gets rejected, and how to prove that the DCTFWeb debt matches what was declared. For EFD-Reinf, see the dedicated obligation page.

Talk about eSocial in your SAP See the DCTFWeb reconciliation
Versão em português
Index

Go straight to the part of eSocial that fits your role

Four views of the same subject. Pick yours and go straight to the point.

01Payroll and HR

Which events to send, when, and with which pay item table.

Go to section

02Tax and fiscal

Withholdings, the contribution base, and the bridge to EFD-Reinf and DCTFWeb.

Go to section

03SAP IT

Event generation, messaging, sending order and reprocessing.

Go to section

04Accounting and audit

Debt reconciliation, contribution accrual and evidence for each closing.

Go to section
Direct links
Direct links:Periodic eventsPay item tableDCTFWeb reconciliationCommon errorsOfficial sourcesFrequently asked questions
Direct answer

Understand eSocial and what SAP needs to generate

eSocial is Brazil's national platform for the digital filing of tax, social security and labor obligations tied to the employment relationship. SAP must generate, sign and transmit the XML events in the right order.

  1. A national platform that unifies reporting

    Decree 8.373/2014 created eSocial as a way to unify the reporting of information, with digital bookkeeping, a receiving application and a national repository. The point at which each earlier obligation ends depends on the act of each agency: the GFIP case is in the mandatory-start schedule.ReferencesDecree 8.373/2014

  2. Who sends: anyone who hires an individual to work

    The Manual defines as obliged anyone who hires an individual service provider and has a labor, social security or tax obligation arising from that relationship, including those of an administrative nature. The term used is "declarant", and it covers employers, companies, public bodies and individuals treated as companies.ReferencesMOS S-1.3 (NO 11/2026)

  3. What SAP must generate: signed XML events, in the right order

    The declarant generates an XML file with the layout information, signs it with a digital certificate and transmits it to the National Environment, which returns a protocol and, after validating, the delivery receipt. The receipt is the reference for correcting or deleting. All of this can come from the declarant's own system or from third parties, with no offline validator program.ReferencesMOS S-1.3 (NO 11/2026)

  4. What is not tax work: payroll calculation and personnel records

    Payroll and personnel records are born in HR. What belongs to the tax layer is the nature and incidence of each pay item, the contribution base, the link to EFD-Reinf and the debt reconciliation in DCTFWeb. The decision on classification is always the company's.

Legal basis and governance

From decree to layout: who rules each layer

Three documents organize the obligation, and each one answers a different question.

Decree 8.373/2014

  • Art. 1: creates eSocial.
  • Art. 2: defines the national environment and provides, in paragraph 2, a simplified system for ME, EPP and MEI (micro and small businesses).
  • Art. 3: sets the principles, including simplifying obligations and removing redundancy.
ReferencesDecree 8.373/2014

Guidance Manual (MOS)

  • Version S-1.3, approved by Joint Ordinance RFB/MPS/MTE No. 13, of 25/06/2024.
  • Consolidated through NO 11/2026, published on 26/05/2026 and corrected on 28/05/2026.
  • Covers deadlines, closing, correction and deletion.
ReferencesMOS S-1.3 (NO 11/2026)

Layouts, tables and Technical Notes

  • Layout of each event, Annex I tables and Annex II rules.
  • XSD schemas published with each note.
  • Technical Notes change layouts; Guidance Notes change the Manual. Current version: S-1.3.
ReferencesTechnical documentation

What receipt does not mean

The Manual reminds us that eSocial receiving an event does not mean it recognizes the legality of the reported fact. An accepted event does not prove that the pay item was classified correctly, which is why classification is the decision and responsibility of whoever declares.

Event families

Five families, one role for each

The Manual separates events by what they represent. The family decides when the event is sent and what depends on it.

FamilyMain eventsWhen it is sentRole in the debt
Employer tablesS-1000, S-1005, S-1010, S-1020, S-1070Before any other event that uses themDefines the pay items, establishments and assignments that validate payroll
Non-periodicS-2190, S-2200, S-2205, S-2206, S-2230, S-2299, S-2300, S-2399When the fact happens, with no fixed dateBuilds the RET, the base for validating remuneration
PeriodicS-1200, S-1202, S-1207, S-1210, S-1260, S-1270, S-1280, S-1298, S-1299By calculation periodRemuneration, payment and closing: they form the debt
Occupational health and safetyS-2210, S-2220, S-2240As each event requiresReplaces CAT and PPP and supports special retirement
Returns and deletionS-5001, S-5002, S-5003, S-5011, S-5012, S-5013, S-3000Returns come from the National Environment; S-3000 is sent by the declarantThey show what was calculated and allow deleting an improper event

The events S-2299 and S-2399, for termination and for the end of work of a worker with no employment tie, are non-periodic but can carry remuneration. Because of this hybrid nature, they also open the payroll movement. eSocial records the taxable events of S-1200, S-1202, S-1207, S-1260, S-1270 and S-1280 on the accrual basis, and S-1210 on the cash basis.ReferencesMOS S-1.3 (NO 11/2026)

Mandatory start

Four phases, five groups and a history that still weighs

Entry into eSocial was staggered by employer group and, within each group, by event family. The portal publishes the dates and cites the ordinances that set them.

Group 1: annual revenue above BRL 78 million

  • Phase 1, tables: 08/01/2018
  • Phase 2, non-periodic: 01/03/2018
  • Phase 3, payroll: 01/05/2018
  • Phase 4, occupational health and safety: 13/10/2021

Group 2: up to BRL 78 million in 2016, outside Simples Nacional

  • Phase 1, tables: 16/07/2018
  • Phase 2, non-periodic: 10/10/2018
  • Phase 3, payroll: 10/01/2019
  • Phase 4, occupational health and safety: 10/01/2022

Group 3: Simples Nacional and nonprofit entities

  • Phase 1, tables: 10/01/2019
  • Phase 2, non-periodic: 10/04/2019
  • Phase 3, payroll: 10/05/2021
  • Phase 4, occupational health and safety: 10/01/2022

Group 3: individual employers, except domestic, and individual rural producers

  • Phase 1, tables: 10/01/2019
  • Phase 2, non-periodic: 10/04/2019
  • Phase 3, payroll: 19/07/2021
  • Phase 4, occupational health and safety: 10/01/2022

Group 4: public bodies and international organizations

  • Phase 1, tables: 21/07/2021
  • Phase 2, non-periodic: 22/11/2021
  • Phase 3, payroll: 22/08/2022
  • Phase 4, occupational health and safety: 01/01/2023

Source of the dates: Joint Ordinance SERFB/SEPRT/ME No. 71, of 29/06/2021, and Joint Ordinance MTP/RFB/ME No. 2, of 19/04/2022, as shown on the portal's schedule page. The page records that use of the system has been mandatory since 08/01/2018 and that the information is declaratory in nature, serving as a valid and sufficient instrument to demand taxes and charges that were not paid on time.ReferencesImplementation schedule

Replacing the GFIP, in two readings that do not match

Social security contribution

The portal's schedule indicates that the GFIP is replaced for social security contribution from August 2018 for Group 1, April 2019 for Group 2 companies with revenue above BRL 4.8 million, and October 2021 for the rest, with October 2022 for public bodies.ReferencesImplementation schedule

FGTS

The Manual says the FGTS Digital platform generates the FGTS payment slip based on eSocial from the March 2024 period. The schedule page still lists the GFIP replacement for FGTS as a date to be defined. The two sources disagree, and the company must follow what FGTS Digital requires for each period.ReferencesMOS S-1.3 (NO 11/2026)Implementation schedule

How the data is born

From payroll to the return, in seven steps

The Manual describes a logical sending sequence that leads to the idea of stacking: each event uses information from the earlier ones. Changing an old data point means checking what came after.

In the declarant's system

Step 01

Declarant

The S-1000 identifies the declarant and goes before everything else.

→
Step 02

Tables

S-1005, S-1010, S-1020 and, if there are proceedings, S-1070, sent right after.

→
Step 03

Registration and RET

Admissions and records form the RET, the base for validating payroll.

→
Step 04

Remuneration

The S-1200 carries each worker's pay items, on the accrual basis.

From payment to DCTFWeb

Step 05

Payment

The S-1210 reports the date and the net amount, on the cash basis.

→
Step 06

Closing

The S-1299 completes the totals of the period's bases.

→
Step 07

Return and DCTFWeb

The S-5011 returns the bases, and the debt moves on to DCTFWeb.

Where time is lost

Between steps 3 and 4. If the worker is not active in the RET, the remuneration is refused. The Manual gives the example: a registration change is accepted only if the hiring event S-2200 was sent first.ReferencesMOS S-1.3 (NO 11/2026)

Where money is lost

In step 2, in the nature and incidence of the pay item. They are declaratory, are not validated by eSocial and define how taxes and FGTS are calculated.ReferencesMOS S-1.3 (NO 11/2026)

Where proof is gained

In steps 6 and 7. The accepted closing and the return of S-5011 show what was calculated, and DCTFWeb confirms what was taken to debt.ReferencesMOS S-1.3 (NO 11/2026)DCTFWeb Manual 2025

Pay item table

Pay item, nature and incidence: where most differences begin

The S-1010 links each company pay item to eSocial's Table 3 of natures and reports the incidences of social security contribution, income tax and FGTS. In practice, this record is the starting point of almost every difference in the debt.

The four pay item types

TypeConceptExamples from the Manual
1: earnings, benefit or pensionAmount paid to the worker that does or does not form part of the basesSalary, 13th salary
2: deductionAmount deducted from what is paidSocial security and withheld income tax deductions
3: informationalNeither paid nor deducted, but may be the base of a tax or must appear on the payrollMaternity pay paid by INSS, health plan, life insurance
4: informational deductionNeither paid nor deducted, but may reduce the base of a tax or of FGTSRequires a justification in the notes field

The justification for type 4 will now be validated: the revised NT 07/2026 adds a validation requiring the notes field on an informational deduction pay item, planned for production on 23/11/2026.ReferencesMOS S-1.3 (NO 11/2026)NT S-1.3 07/2026 rev.

Pay item matrix, with examples from the Manual

Pay itemTypeNatureIncidencesWho decides
Salary, earnings11000CP 11, IRRF 11, FGTS 11Client
Social security contribution deduction2According to Table 3CP 31, IRRF 41, FGTS 00Client
13th salary advance15504FGTS applies in the month; CP and IRRF only on the annual payrollClient
13th salary, annual payroll15001According to the Manual, item 10.3.4Client
Supplementary 13th salary1500512 in CP, FGTS and IRRFClient
Informational amount only, no obligation to declare39989No incidenceClient
Base checks: 9901, 9902, 9903, 9904, 9907, 99083Own00 in CP and FGTS, 9 in IRRFManual rule

Four registration rules SAP must respect

Effective period

A pay item is registered once and is valid from the start of its effective period, with no need to repeat it by period. A change from a given date enters as a new inclusion. A correction within the same effective period goes in the change group and overrides the earlier event.ReferencesMOS S-1.3 (NO 11/2026)

Before the remuneration

For a pay item change to count in the remuneration and in the totals, it must happen before the remuneration event is sent. After that, you must correct or delete and resend the remuneration.ReferencesMOS S-1.3 (NO 11/2026)

Pay item code

The code cannot start with the word eSocial, in upper or lower case, because that coding belongs to the system's standard table.ReferencesMOS S-1.3 (NO 11/2026)

Informational amount only

An item with no duty to declare does not use a salary nature. The Manual says to post it under nature 9989, and gives the example of a base salary kept only for internal control.ReferencesMOS S-1.3 (NO 11/2026)

Client decision

Incidences are declaratory and eSocial does not validate them. Nature, incidence and any suspension lawsuit are company decisions. DFSpro adjusts SAP to the decision taken and shows that the result reconciles, but does not choose the tax position.

Periodic events

Remuneration, payment and monthly closing

Periodic events form the movement of one calculation period. The Manual's golden rule is uniqueness: payroll goes in a single event per worker, and the payment date goes in another.

S-1200: remuneration

A single S-1200 per worker in each period, with all amounts due, deductions and withholdings, each item under its own pay item, including those with no incidence. Several statements can go in the same event, identified by ideDmDev. Quantities go in decimal format: 1 hour and 20 minutes become 1.33.ReferencesMOS S-1.3 (NO 11/2026)

S-1210: payment

Reports the date and the net amount of each payment, linked to the remuneration statement. One S-1210 goes per beneficiary and per month, even with several payments on different dates. Every payment must have been reported before in a remuneration event, and the movement must be open.ReferencesMOS S-1.3 (NO 11/2026)

S-1299: closing

Completes the totals of the bases and allows the debts to be integrated with DCTFWeb. It is mandatory for everyone, even with no taxable events. The return arrives through the events S-5011 and S-5013. Until acceptance, you can add, delete and correct events of the period.ReferencesMOS S-1.3 (NO 11/2026)

S-1298: reopening

Reopens a closed movement, at any time, to correct, delete or send new periodic events. Reopening does not cancel what the earlier S-1299 already took to DCTFWeb. Only the new closing recalculates and replaces the calculation.ReferencesMOS S-1.3 (NO 11/2026)

Deadlines, according to the Manual and the DCTFWeb Manual

Event or declarationDeadlineWhen it falls on a non-business day
S-1200, monthly remunerationThe 15th of the following month, and always before S-1299Moves to the next business day
S-1200, 13th salaryDecember 20 of the reference yearMoves to the previous business day
S-1200, termination from day 1 to day 4Up to the tenth day after the termination, for the previous month's remunerationMoves to the previous business day
S-1210, paymentsThe 15th of the following month, or until payroll closes, whichever comes firstMoves to the next business day
S-1299, closingThe 15th of the following month, and December 20 for the 13th salaryMoves to the next business day
S-1298, reopeningAt any timeDoes not apply
Monthly DCTFWebLast business day of the following month, until 23:59:59Already the rule
DCTFWeb for the 13th salaryDecember 20According to the DCTFWeb Manual

Sending the 13th salary has its own rules: eSocial has two types of calculation period, monthly and annual, and in December two payrolls come out, the monthly one and the 13th, transmitted independently to DCTFWeb. The day-to-day cases detail the 13th.ReferencesMOS S-1.3 (NO 11/2026)DCTFWeb Manual 2025

The month in four movements

Movement 01

Until payroll closes

HR sends the new or changed pay items and then the S-1200 of all workers. Table first, remuneration after.

→
Movement 02

On the payment date

The S-1210 enters with the actual date and the net amount, even with a zero net amount if there was income or tax withheld.

→
Movement 03

Until the 15th

The S-1299 closes the period. An active worker with no remuneration raises a warning, and the fix goes through reopening.

→
Movement 04

Until the last business day

Tax checks the DCTFWeb debt against the return of S-5011 and transmits, or uses immediate transmission.

The bridge to DCTFWeb

Where the debt comes from and how to close the account

DCTFWeb is not filled in: it receives. Integration is automatic after eSocial or EFD-Reinf closing is sent successfully, and the system generates a single declaration per period, consolidating the sources.

S-1200Remuneration per workercloses in S-1299
S-1299Closing of the periodtriggers the calculation
S-5011Return per taxpayerbases by category and assignment
DCTFWebDebt by revenue codeis checked against the return
DarfPayment documentgenerated from the declaration

The return of S-5011 shows the total calculation base by worker category, by tax assignment and by establishment, and the contributions are calculated from it. A successful return of S-1299 triggers sending the calculated credits to the DCTFWeb Portal.ReferencesMOS S-1.3 (NO 11/2026)

What DCTFWeb receives from eSocial

As debts: remunerations, sale of rural production by individuals, income tax withheld on employment relationships and PIS/Pasep on payroll. As credits: family allowance and maternity pay, which can be linked to debts.ReferencesDCTFWeb Manual 2025

What you do not do in DCTFWeb

You cannot change the calculated debts in DCTFWeb. If the amounts are wrong, the adjustment is made in eSocial, in EFD-Reinf or in MIT, and a new closing replaces the earlier calculation.ReferencesDCTFWeb Manual 2025MOS S-1.3 (NO 11/2026)

Immediate transmission

At closing, eSocial lets you indicate that DCTFWeb is transmitted automatically. This is not possible when there is a debt with suspended enforceability in the books, in which case the suspension credit is linked in DCTFWeb itself.ReferencesDCTFWeb Manual 2025MOS S-1.3 (NO 11/2026)

Where to look first: three revenue codes from the DCTFWeb Manual

What to check in each

  • 1082-01, social security contribution of insured employees and individual contractors: the payroll deduction against the return of S-5011.
  • 1138-01, employer's social security contribution, employees and individual contractors: the employer base and the rates applied.
  • 1170-01, third-party contribution, education allowance: the FPAS code and the third parties registered in S-1000 and in S-1005.

Calculate the difference with your numbers

Payroll, S-5011 and DCTFWeb

Debt reconciliation: calculated minus confirmed

Turn on JavaScript to change the values. Example: total calculated in the events of BRL 212,480.00, total confirmed in DCTFWeb of BRL 209,930.00, a difference of BRL 2,550.00, or 1.2% of the calculated amount.

Illustrative example with no real company: it is not an opinion or an official calculation. The difference shows where to investigate, and the cause depends on the originating books. Before using it, take the rule to your company's legal team and accountant.

What the result means

A positive difference means eSocial calculated more than DCTFWeb confirms. A negative difference means the opposite. In either direction, the account points to the closing, to the credit linking or to the originating books, never to a direct adjustment in the declaration.

The bridge to EFD-Reinf

What stays with each obligation and where the two meet

The Manual treats eSocial and EFD-Reinf as complementary systems. The split decides where each piece of data is born, and it is where reconciliation usually breaks.

SubjecteSocialEFD-Reinf
Worker remunerationPayroll event, S-1200No
Income tax on employment incomeReported in eSocial, with the payment dateNo
Withholding under art. 31 of Law 8.212NoInformation sent through EFD-Reinf
Substitute social security contribution, on gross revenueNoInformation sent through EFD-Reinf
Sale of rural production by individualsS-1260S-1250 of eSocial was replaced by event R-2055 since 21/07/2021
Payment to the beneficiary of a deceased workerS-1210 is not sentThe person who received it is identified in EFD-Reinf

For the EFD-Reinf events, see the detail on events, closing and DCTFWeb on its own page. The detail of that obligation lives there, and the overview of the obligations is in the map of ancillary obligations and SPED.

Occupational health and safety

What occupational safety and health brings to the debt and to payroll

The three occupational safety and health events (SST) are the new way to meet the duty to issue the CAT and to prepare and update the PPP. The data is born in the safety and health area, but the effect reaches payroll and the special retirement contribution.

S-2210: work accident

Reports the accident, even without leave. The deadline is the first business day after the accident and, in case of death, immediately. The employer, the OGMO, the dock workers' union and public bodies are obliged, for those under the RGPS.ReferencesMOS S-1.3 (NO 11/2026)

S-2220: health monitoring

Carries the ASO and the complementary exams. The deadline is the 15th of the month after the ASO, and for the pre-employment exam it is the 15th of the month after hiring. It is mandatory for CLT employees, except domestic workers, and optional in several categories.ReferencesMOS S-1.3 (NO 11/2026)

S-2240: environmental conditions

Reports harmful agents, EPC and EPI. The deadline is the 15th of the month after the start of the obligation or after hiring, and on each change. Where it is mandatory, the event goes even with no exposure to risks.ReferencesMOS S-1.3 (NO 11/2026)

Interns do not need to send occupational safety and health events. The EPI information in S-2240 does not replace the record of equipment delivery required by regulation. The deadline of S-2220 does not change the legal deadline for carrying out the exams, only the one for the record in eSocial.ReferencesMOS S-1.3 (NO 11/2026)

Where occupational safety and health meets tax

The history of exposure to harmful agents is born in these events, but the declaration of the additional contribution to fund special retirement is made when the exposure level is reported in S-1200, with the codes of Table 2. If the safety and health area and payroll use different sources, the debt and the history diverge.

SAP

Where the subject lives in SAP

SAP Tax Declaration Framework for Brazil (TDF) is SAP's messaging layer for sending events like those of eSocial to the government.

What the help describes

TDF sends eSocial, EFD-Reinf and e-Financeira events to the government, and configuring the sending (services, certificates and destinations) is a step before the first event.ReferencesSAP Help: eSocial in TDF

Integration with SAP ERP HCM

When the two solutions are integrated, the events are generated in HCM and sent to the government through TDF. Integration depends on configuration on both sides and on the SAP Notes applied to the version.ReferencesSAP Help: integration with HCM

The explanation of messaging, sending paths and configuration is on the page about SAP TDF, which explains how eSocial is generated and reconciled.

Where DFSpro comes in

Tax layer, ABAP and tailor-made customization

DFSpro was founded in Curitiba in 2018 as an SAP Tax Governance consultancy. In eSocial, it handles the tax side; the overall SAP project design belongs to the integrator.

What DFSpro does

  • Implements eSocial in SAP, alongside the integrator and the client's IT team.
  • Delivers the ABAP code and the tax adjustments for service type, nature, withholding, events and reconciliation.
  • Reconciles payroll, EFD-Reinf and DCTFWeb with evidence for each period.

What it does not do

  • It does not decide the pay item nature, the classification or the tax position: the decision is the client's.
  • It talks about timelines only after getting to know your SAP environment.
  • The signature and the digital certificate remain the company's.

Anyone evaluating GUEPARDO Tax buys the license from DFSpro, which is an Authorized Channel; the product belongs to NTT DATA. To measure what SAP already delivers against what the obligation requires, there is the SAP Tax Diagnostic.

There is a page only about ABAP and tax customization.

Is there a closing that does not match?

Rejected event, a difference in DCTFWeb or a pay item table to review: describe the case to DFSpro.

Employer contribution

A base simulation times rate

The company's contribution to Social Security applies to the month's remuneration. The simulation shows the calculation, and the RAT, FAP and third-party rates are left to you, because they depend on your classification.

Art. 22, item I, of Law 8.212/1991 sets 20% on the total remuneration paid, owed or credited during the month to employees and dock workers. Art. 28 defines the contribution salary. Payroll tax relief, limits and substitute regimes are not part of the calculation.ReferencesLaw 8.212/1991

Law 8.212, art. 22 and art. 28

Simulated employer contribution

Turn on JavaScript to change the values. Example: a base of BRL 500,000.00 at 20%, with RAT adjusted and third parties blank, results in BRL 100,000.00 of employer contribution.

Illustrative example: it is not an opinion or an official calculation. The 20% rate is the one in art. 22, I; RAT, FAP and third parties are your own fields, with no pre-filled value. Take the rule to your legal team and accountant before applying the result.

Common errors

Error matrix, cause and fix

Ten situations that keep repeating. Causes and fixes come from the Manual. The Manual distinguishes an error, which rejects the event, from a warning, which accepts the event and only draws attention.

SymptomDocumented causeWhere to lookFix
Remuneration rejected because of a pay itemS-1010 not sent before, or pay item outside its effective periodSending order and table effective periodSend or adjust the table and resend the remuneration
Remuneration rejected because of a workerWorker without hiring in the RET, or outside the active periodS-2200, S-2300 and datesSend the registration first; treat as late if applicable
S-1210 rejectedPayment without a statement reported before, or a closed movementS-1200 and movement statusSend the remuneration or reopen with S-1298
Warning in S-1299Worker active in the RET with no remuneration in the periodList of active workers against payrollReopen, send the remuneration and close again
Remuneration correction rejectedS-1210 linked to the statementThe month's payment eventsDelete the S-1210, correct and resend, except for the Manual's exceptions
Deletion rejectedPeriod already closed by S-1299, or S-1210 linkedMovement and links between eventsReopen with S-1298 and delete the payment first
Key field cannot be correctedWrong CPF, registration number or calculation periodOriginal eventDelete the event and send a new one
DCTFWeb debt different from payrollPay item changed after the remuneration eventDate of the pay item changeCorrect or delete and resend the remuneration, and close again
Duplicate event warningSame event resent as an originalCorrection indicator and receipt numberDiscard the duplicate or send it as a correction with the receipt
Event rejected because of versionLayout outside the version accepted on the sending dayEvent version and coexistence periodGenerate in the accepted version and follow the Technical Notes

The sources for each line: error and warning, item 8.6; sending order, item 8.3 and S-1010; deletion, item 17; correction, item 15.2 and S-1298; versions, item 21.1, all from the Manual consolidated through NO 11/2026.ReferencesMOS S-1.3 (NO 11/2026)

Day-to-day cases

Four situations that keep repeating

The four cases are fictional and start from the Manual's rules and examples. They work as a diagnosis exercise and do not portray any client.

Case 1The 13th salary advanced in full in November
  • The Manual uses a 13th salary of BRL 1,045.00 and a contribution deduction of BRL 78.37. Paid in full in November, the net amount of BRL 966.63 goes into the S-1200 of 11/2020 with the advance pay item, nature 5504.
  • In December, the annual payroll carries the 13th owed as earnings, nature 5001, and as deductions the advance of BRL 966.63 and the contribution of BRL 78.37, with a zero net amount.
  • FGTS applies in the month of the advance, and the contribution and income tax only on the annual payroll. The common mistake is posting everything in November.
Case 2The termination on the 3rd
  • An employee is terminated on March 3. The S-1200 for February for that worker does not follow the 15th deadline.
  • For terminations from day 1 to day 4, the remuneration for the previous month is sent up to the tenth day after the termination, and before the S-1299.
  • If the date falls on a non-business day, the sending moves to the previous business day.
Case 3A retroactive hiring in a closed payroll
  • The declarant reported and closed the payrolls for January to March, and in April sends a hiring retroactive to January 15.
  • eSocial reruns the closing rules in the closed months. Since the new worker has no remuneration in them, the event is accepted with an inconsistency warning.
  • To avoid the warning, the declarant reopens the payrolls of the period before sending the hiring and then closes again.
Case 4The debt that does not match after a pay item change
  • A pay item had its incidence changed on August 10, after the July S-1200 had been sent.
  • The Manual says the change only takes effect on a remuneration and totaling event if it happens before that event is sent.
  • The diagnosis starts with the date of the pay item change. The fix is to correct, or delete and resend, the affected S-1200 and close again, and only then check DCTFWeb.
Tests and rollout

Test and rollout plan in waves

No project deadline: the waves give the order, not the duration. The Manual and the portal set the limits of the test environment.

  1. Inventory and diagnosis

    List the pay item table, the events that already go out, the last closing and the matching DCTFWeb, and note where the difference is born. It is the cheapest wave and the one that avoids the most rework.

  2. Generation and tables in restricted production

    The restricted production environment has no legal effect, limits one thousand worker ties per employer and serves functional tests, not load or performance. Every eSocial change goes into it first. The environment's layout version is S-1.3.ReferencesRestricted production

  3. Periodic events, closing and reconciliation

    Run S-1200, S-1210 and S-1299 in a test period and compare the return of S-5011 with the company's own calculation. Prove the reconciliation with DCTFWeb and keep the evidence of each closing.ReferencesMOS S-1.3 (NO 11/2026)DCTFWeb Manual 2025

  4. Go-live and follow-up

    Follow the first real closing in SAP's event monitoring, handle the warnings, and document the month's exceptions and the owner of each one.ReferencesSAP Help: eSocial in TDF

What to prove in each wave

  • Sending order: table, registration, remuneration, payment and closing in sequence, with the receipt of each event.
  • Nature and incidence: pay item by pay item against the client's decision, in an approved matrix.
  • Closing: S-1299 accepted and return of S-5011 checked and stored.
  • Debt: total calculated against the amount confirmed in DCTFWeb, with a reconciliation signed by tax.
  • Correction: reopening, fix and new closing, with the trail and the receipt of the original event.
Calendar and layout risks

What Technical Note 07/2026 changes in payroll and tax

NT S-1.3 No. 07/2026, in the version of 24/09/2026, brings adjustments in phases. The table shows only what touches pay items, payment and debt, with the restricted production and production dates the note publishes.

Restricted productionProductionWhat changes for payroll and tax
13/10/202626/10/2026The payroll closing rule starts to consider leave codes 44 and 45, and a field for a CPF change with no tie in the Revenue database in S-2299, S-2399 and S-2420
09/11/202623/11/2026Informational deduction pay item requires a note; the dependent's CPF is now validated against the Revenue database in S-1210; new value 3 for health plan reimbursement in S-1210 and in S-5002; pay items with incidence 21 or 22 are no longer allowed for dock workers, individual contributors and MEI
07/12/202614/12/2026New values 23, 24, 27 and 28 for contribution incidence on paternity pay in S-1010; paternity pay field in S-5011; new natures 4052, 4053, 9928 and 9929 in Table 3
Not reported18/01/2027Adjustments to S-8200, which covers the court-ordered annotation of the employment tie

The production XSD schemas follow the dates of 26/10/2026, 23/11/2026, 14/12/2026 and 18/01/2027, according to the technical documentation page. The NT 07/2026 documents carry changes from Law 15.371/2026 in the descriptions of Table 18, according to the note itself.ReferencesNT S-1.3 07/2026 rev.Technical documentation

What is already on the portal

XSD schemas through NT 06/2026 with production on 27/04/2026, and a version with alphanumeric CNPJ in production on 01/07/2026. Guidance Note 09/2026 covers adjustments for SESI and SENAI taxpayers that had a direct collection agreement.ReferencesTechnical documentation

Phase-out of payroll tax relief

eSocial was adjusted for Law 14.973/2024, which created the gradual end of payroll tax relief and no employer contribution on parts of the 13th salary for companies under that relief. The guidance is in Guidance Note S-1.3 01/2024.ReferencesMOS S-1.3 (NO 11/2026)

Coexistence of versions

As a rule, eSocial supports a single layout version, but there may be coexistence during a switch. In the migration from S-1.2 to S-1.3, the period was from 02/12/2024 to 02/02/2025. Late events follow the rules of the version in which they are sent.ReferencesMOS S-1.3 (NO 11/2026)

What to follow

The portal may publish a new note at any time, and the production calendar may change. Checking the effective date before each wave is part of the plan.

Checklist by area

Each area with its own list

Lists to split the closing work. Each item is a check point, with no guarantee of results.

Payroll and HR

  • New or changed pay items sent before the remuneration.
  • A single S-1200 per worker, with all the period's ties.
  • S-1210 also sent when the net amount is zero and tax was withheld.
  • Terminations from day 1 to 4 with their own deadline.

Tax and fiscal

  • Nature and incidence of each pay item decided and recorded.
  • Return of S-5011 checked against DCTFWeb by revenue code.
  • Split with EFD-Reinf noted for each fact.
  • Suspension lawsuit reported in S-1070 before the pay item.

IT and ABAP

  • Sending order guaranteed by the program.
  • Receipt number stored to correct or delete.
  • Event mapping parameterized by layout version.
  • Event and batch monitors with an owner and a reprocessing routine.

Accounting and audit

  • Contribution accrual reconciled with the DCTFWeb debt.
  • Differences of the month explained by period.
  • Receipt of S-1299, return S-5011 and DCTFWeb receipt stored.
  • Each exception of the month with an owner.

Occupational health and safety

  • Events S-2210, S-2220 and S-2240 with the deadline of each one.
  • Exposure level in S-1200 consistent with S-2240.
  • Equipment delivery record for EPI kept beyond the event.
  • Interns left out of occupational safety and health sending.

Governance

  • Who signs each event, with which certificate and, if applicable, with a power of attorney.
  • Layout versions and Technical Notes followed by an owner.
  • Client decision on each classification filed.
  • Calendar of restricted production and production by wave.
Official sources

Sources with links

Official documents behind the legal and technical facts.

Legislation

eSocial portal and manuals

Federal Revenue Service

SAP

Frequently asked questions

Frequently asked questions about eSocial in SAP

Service delivery4 questions, 01 to 04

01Does DFSpro implement eSocial in SAP? What is included, and what stays with the integrator or HR?+

Yes. In the eSocial integration with SAP, DFSpro provides the implementation, the ABAP and the tax customization, alongside the integrator and the client's IT team. The overall project design belongs to the integrator. Payroll calculation and personnel records belong to HR and the company's payroll system. The detailed split of who does what is settled in the first conversation, after reading the environment.

02Which events does DFSpro develop and test in ABAP?+

It depends on the environment. DFSpro's work is the tax layer: event generation, service type and nature, withholding and reconciliation with DCTFWeb. The events that need the most tax attention are the pay item table S-1010, the remuneration S-1200, the payment S-1210 and the closing S-1299, because they form the base of the debt. Which of them enter the project is defined with an inventory of what is already sent today.

03What must the client have ready before starting?+

Five things: the current pay item table, with nature and incidence already decided by the company; the worker records in the payroll system; the digital certificate and who signs the events, with a power of attorney where needed; one person each from HR, tax and IT; and the last closing together with the matching DCTFWeb. Without access to the restricted production environment, testing waits.

04How is the reconciliation with DCTFWeb proved?+

By comparing, period by period, the total calculated in the events with the debt DCTFWeb shows by revenue code, and keeping three pieces of proof: the receipt of S-1299, the return S-5011 and the DCTFWeb receipt. DCTFWeb does not let you change the calculated debt, so the difference is always solved at the source, in eSocial.

Contracting and scope4 questions, 05 to 08

05How is the scope defined?+

By the environment and the problem. The conversation starts from what the company already sends to eSocial, the pay item table and the last closing, and separates what is event generation, what is tax rule and what is reconciliation. Timeline and commercial terms are left for that conversation, after reading the environment.

06Does the work cover the full payroll or only the tax layer?+

DFSpro works on the tax layer and the ABAP of the eSocial integration. Payroll calculation, personnel records and the overall project architecture are not the focus. If the environment requires anything beyond that, the split with the integrator and HR is agreed in writing before starting.

07Who decides the pay item nature and the classification: DFSpro or the client?+

The client. The Manual says the incidences reported in each pay item are declaratory and are not validated by eSocial, which means the responsibility for the choice lies with whoever declares. DFSpro adjusts the system to the company's decision and shows that the result reconciles, without choosing the tax position.

08Does it work with payroll in a system other than SAP?+

From the standpoint of the obligation, yes. The Manual allows the file to be generated by the declarant's system or by third parties, as long as it is signed with a digital certificate. The SAP help describes that the eSocial component of SAP Tax Declaration Framework receives events from other systems, validates, stores and sends them to the government, and mentions integration with SAP ERP HCM through a BAdI. The design of a specific case depends on the environment.

Risks and objections4 questions, 09 to 12

09Why is eSocial rejected even with SAP configured?+

Because events depend on one another. The Manual calls this stacking: the remuneration is only accepted if the pay item and the worker already exist, the payment is only accepted if the remuneration was reported before, and the closing changes what can be corrected. Correct configuration does not prevent rejection when the sending order, the pay item's effective period or the movement status is wrong.

10What happens when eSocial, Reinf and DCTFWeb disagree?+

DCTFWeb receives the debts from eSocial and EFD-Reinf and consolidates them by calculation period. Since the calculated debt cannot be changed in DCTFWeb, the correction is made in the originating books and the new closing replaces the earlier calculation. That is why reconciliation starts with the question of which of the two filings carries the amount.

11How do you handle a layout change without redoing the project?+

By keeping the event mapping parameterized and following the Technical Notes. The portal publishes version S-1.3 and NT 07/2026 (version of 24/09/2026), with production XSD schemas on 26/10/2026, 23/11/2026, 14/12/2026 and 18/01/2027. As a rule eSocial supports a single version, with coexistence periods when there is a switch. What really changes are fields, rules and tables, and that is the work of each wave.

12What is the risk of the month closing without the closing event?+

The S-1299 completes the totals of the bases and allows the debt to be created in DCTFWeb. Without it, the social security debt and the payroll income tax do not reach DCTFWeb. The closing deadline is the 15th of the following month, and monthly DCTFWeb goes up to the last business day of the following month (IN RFB 2.237/2024, art. 6, as worded by IN RFB 2.248/2025). The DCTFWeb Manual provides for a fine notice for late filing of the declaration.

Reform and next steps4 questions, 13 to 16

13Does the tax reform change eSocial?+

In the official eSocial documents, the Manual consolidated through NO 11/2026 and Technical Note 07/2026, no IBS or CBS event or field appears. The obligation still deals with social security contributions, income tax and FGTS of the employment relationship. This does not close the subject, because new Technical Notes may change the picture. The point to follow is the publication of each note.

14How to start: diagnosis, pay item inventory or testing in the test environment?+

With the pay item inventory and the last closing. In practice, most differences are born in the nature and incidence of the pay item, and it is cheap to find that out before generating events. Only then is it worth testing in restricted production, which serves functional tests, with a limit of one thousand worker ties per employer, and not load tests.

15What evidence should be kept for an audit, and where is it?+

The exact list varies from auditor to auditor. The proof the rule itself produces is the delivery receipt of each event, the S-5011 return of the closing and the DCTFWeb receipt. The Manual describes an asynchronous event downloader in Web Geral, with requests of up to 31 days.

16How do eSocial and EFD-Reinf split the work, and how do the two pages complement each other?+

eSocial carries the employment relationship: remuneration, contributions on payroll, employment income tax and the payment date. EFD-Reinf carries the withholding under art. 31 of Law 8.212 and the substitute contributions on gross revenue. The EFD-Reinf in SAP page goes deeper into events R-2010 and R-4020 and the Reinf closing. eSocial, in turn, covers the payroll, occupational safety and health and return events. DCTFWeb is where the two meet.

Next steps

Start with the pay item that your closing still cannot explain

The conversation can start from the pay item table, the last closing and the matching DCTFWeb. With a rejected event, start with the error, cause and fix matrix.

DFSpro designs, configures and proves the behavior of SAP, with the integrator. Pay item nature, classification and tax position are the client's decision.

Talk about eSocial in your SAP Review the error matrix