Compliance — REGES-Online (in preparation)
Contracts will reach REGES straight from Workly, not through yet another portal
The integration is built but not yet active in production. Once activated, when you hire someone, the employee and contract registration is transmitted to REGES-Online directly from Workly, over an API connection — you don't export a file to upload manually into another portal. The data leaves once, from the flow where you already entered it.
What the law requires
The employer must register the individual employment contract in the general register of employees (REGES-Online) at the latest the day before work begins. Allowing someone to start work without the contract registered in time is undeclared work, penalised per person; a later erroneous submission is a separate offence with a different regime. Once activated, Workly prepares the transmission from the same flow in which you create the contract, so the deadline does not depend on a separate step.
From the contract created to the registration confirmed
Direct transmission over API
Workly sends the employee registration and the contract addition to REGES-Online over a direct, authenticated connection. You don't download a file to upload separately into another portal — the data leaves from Workly. The employee registration and the contract addition are covered; contract amendments, suspensions and terminations are not transmitted yet.
- Authenticated API connection to REGES-Online
- No manual export and re-upload into another portal
- The same data entered at hiring
Check before sending
Before transmission, Workly checks the employee's data: if a required field is missing, it shows you exactly which one, and the employee registration is not sent. For the contract, gaps are flagged, and the substantive validation is done by REGES; the result is read back.
- Completeness check of the employee's data
- Shows you exactly what is missing
- For the contract, REGES does the substantive validation
Reconciliation with the register
After transmission, Workly tracks what was actually registered in REGES, so you know the state in the app matches the register — you're not left assuming it “should be there”.
- Verifies what was actually registered
- App state aligned with the register
- No guessing about what reached the register
Data access, with an audit trail
Sensitive data — the national ID first of all — is encrypted, and every access to it for a transmission leaves an audit trail. You know who transmitted what and when, if needed.
- National ID and sensitive data encrypted
- Audit trail on every access
- Role-based access
Switched on separately from the rest of the app
The REGES integration is optional and stays off until it is activated: it needs the employer account in REGES-Online and the API keys. Until then Workly works normally without it, and nothing is transmitted.
- Optional, off until activation
- Nothing leaves without activation
- The rest of the app works independently
Frequently asked questions about the REGES integration
Does Workly actually transmit to REGES, or just generate a file?
It transmits directly, once the integration is activated. Workly sends the employee and contract registration to REGES-Online over an authenticated API connection. You don't download a file to then upload manually into another portal.
What happens if the employee or contract data is incomplete?
Before transmission, Workly checks the employee's data. If a required field is missing, it shows you exactly which one, and the employee registration is not sent until you complete it. For the contract, missing fields are flagged as notes but do not block sending: the substantive validation is done by REGES, and the result is read back into Workly.
How do I know the registration actually reached the register?
Workly reconciles what was transmitted with what was actually registered in REGES, so the state in the app matches the register — you're not left with a mere assumption.
Is the integration active right now?
Not yet. The integration is built, but transmission to REGES-Online is switched on separately, once the employer account in the portal and the API keys are set up. Until then the rest of the app works normally, and nothing is transmitted.
Built for Romanian compliance
Protected data (GDPR)
The national ID and sensitive data are encrypted, with an audit trail on access.
Local support, in Romanian
A support team in Romanian that understands the reporting obligations of Romanian companies.
Built for RO law
Built for the real compliance requirements in Romania, not adapted from another market.
Discover the related modules too
Ready to prepare your contracts for REGES without juggling portals?
We'll show you Workly on your company's workflow, in a short demo.
Request a demo