Assisted operation
The AI follows the operation in real time and flags what needs action. It SUGGESTS; execution with real effect — changing a status, triggering a collection — only happens through the manual path or with your confirmation. The panel prioritizes; you decide.
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Hirings (S-2200)Remuneration (S-1200)Payments (S-1210)Terminations (S-2299)Send queue
The list shows
EventPeriodEnvironmentStatusProtocolReceiptGenerated onWarning / error
Form fields
EventoQual evento do eSocial este registro representa (S-1200, S-2200...).
PessoaPessoa a que o evento se refere.
CompetênciaMês de referência do evento.
SituaçãoGerado, enviado, aceito ou rejeitado.
ProtocoloProtocolo devolvido no envio.
ReciboRecibo do evento aceito. É a prova de entrega.
Motivo do erroO que o governo respondeu quando o evento foi rejeitado.
TentativasQuantas vezes o envio foi tentado.
Gerado emQuando o evento foi montado.
Enviado emQuando o evento foi transmitido.
Retorno emQuando o retorno do governo foi lido.
AmbienteProdução ou produção restrita. Restrita não tem valor legal.
Start here
What this screen answers
Prepares and tracks eSocial events (hiring, leave, payroll). The event follows the legal order: sending payroll before the table event means rejection at the source — the queue respects the dependency, not your hurry.
O que esta tela faz
Generation and submission of eSocial events from payroll: hiring (S-2200), remuneration (S-1200), payments (S-1210) and termination (S-2299). Each event is built from a layout versioned by effective date, filled with the real employee and payroll data, and enters a queue with status, protocol and return errors. Submission is gated: it only truly transmits with eSocial turned on, a real provider and an A1 certificate — in the sandbox everything is simulated.
Para que esta tela existe
Generation and submission of eSocial events from payroll: hiring (S-2200), remuneration (S-1200), payments (S-1210) and termination (S-2299). Each event is built from a layout versioned by effective date, filled with the real employee and payroll data, and enters a queue with status, protocol and return errors. Submission is gated: it only truly transmits with eSocial turned on, a real provider and an A1 certificate — in the sandbox everything is simulated. — this is the role of the "eSocial" screen within the platform.
Rules
O envio é gateado — sandbox não transmite
The banner at the top shows how submission is configured: eSocial on or off, environment (production or testing), provider and presence of the A1 certificate. There is only real transmission with eSocial on, a real provider and an A1 certificate present — if any of them is missing, the screen operates in sandbox: events are generated and enter the queue normally, but submission is simulated and nothing reaches the government. The Environment column of each event records in which mode it was processed.
Frequently asked questions
Que pergunta do dia a dia se responde aqui
"Are the eSocial events (hiring, payroll, payments, termination) being generated and transmitted?" — when that question comes up, this is the screen that answers it.
How to generate and send the payroll events
First select the payroll period in the selector — the generation buttons are disabled without it. Then generate what the month requires: Hirings (S-2200), Remuneration (S-1200), Payments (S-1210) and Terminations (S-2299). The events enter the queue with status, protocol, receipt and the return errors when there is an error. The Send queue button transmits the pending ones at once, with confirmation; an event with an error that can be reworked gets the resend button on its own row.
Was this article helpful?
In the same module: Square with the authorities12
Tax assessmentCalculates the month's taxes (DAS/DARF/ISS/INSS/FGTS) on revenue and payroll, with calculation memory and a d…Block KCheck the month’s Block K and post movements between items (K220) and prior-period corrections (K280).Sankhya connectorIntegrates Tenka with the Sankhya ERP by mapping entities between the two. The mapping is the critical piece:…Packing listGroups items and deliveries into a load to plan the route and check them off. The packing list is what the dr…Exportar lançamentos para o contadorOs lançamentos da competência no layout que o sistema do seu escritório contábil importa, com o hash para con…Outbound NF-eIssues and tracks the outbound electronic invoice. An authorized invoice is IMMUTABLE — correcting it means a…Owner's scoreboardThe few numbers the owner looks at every day: cash, results, sales, people. It's a scoreboard, not a report —…Global agendaThe layered agenda: yours, the team's, visits, and deliveries, overlaid. Each layer has an owner and visibili…
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.