eSocial: from the payroll system to the receipt
We build the technical path between your payroll system and eSocial: generating, validating and sending events, and tracking the response through to the receipt.
Who it's for
For companies whose payroll system does not work well with eSocial and that rely on manual submissions.
What it solves
- Events are exported from one system and sent by hand through another.
- A rejected event goes unnoticed for days.
- Payroll, time tracking and HR sit in systems that do not talk to each other.
- Nobody can say which events already have a receipt and which are still pending.
What we do
- Who handles what
- Payroll rules and event content stay with a payroll specialist and your accounting team.
- Integration between systems
- Payroll, time tracking, HR and employee records connected, so events start from the source data.
- Generation and validation
- Events built to the eSocial layout and validated against the schema before sending.
- Signing and sending
- Events signed with the company's digital certificate and sent in batches through the web service.
- Responses and receipts
- Checking the result of each batch, storing the receipts and recording rejections.
- Pending queue
- Rejected or unanswered events in a visible queue; the specialist fixes the content and the system resends.
- Testing in restricted production
- The whole flow tested in eSocial's restricted production environment before real submissions.
What you get
- Integration between payroll, time tracking and HR, in production
- Generation, validation and submission of events to eSocial
- A record of every batch, protocol and receipt
- A dashboard of pending, rejected and receipted events
- Alerts for rejections and for batches with no response
How we do it
Mapping
Source systems, the events the company sends and how this is done today.
Rules with specialists
The payroll specialist and your accountant define the content; we define the technical flow.
Development
Integration, generation, sending and response checks, tested in restricted production.
Go-live
Real submissions supervised, with the specialist checking the first receipts.
Follow-up
Alerts, the pending queue and adjustments whenever the layout changes.
Technology examples
- XML
- XSD
- XMLDSig
- SOAP
- PostgreSQL
- RabbitMQ
In Brazil, we handle
- eSocial
- The federal system for employers' labour, social security and tax obligations.
This service is delivered with a specialist partner.
Related services
FAQ
Does Balkan run payroll?
No. Payroll rules and event content stay with a payroll specialist — your own or the partner agreed for the project — and with your accounting team. Balkan handles the integration, the submissions and tracking the responses.
Who answers for an event with the wrong content?
Content belongs to whoever sets the rules: the specialist and your accounting team. Balkan looks after the technical flow: the event leaving, arriving and having its response recorded.
Will it work with the payroll system we already use?
It depends on what it exposes: an API, files or database access. If it already produces the events, we integrate sending and responses; if not, we build generation from its data.
What happens when the eSocial layout changes?
The specialist assesses what changes in the rules and we adjust generation and validation. We test in restricted production before using the new version.
Write to Balkan
Talk to us about your project