For employers with staff in Romania · Employee register workflows · Sources reviewed 7 Oct 2026
Employers with staff in Romania, and their contracted providers
Art. 1 · Romania compliance module of RDCopilotOS
RDCopilot REGES prepares register operations from your HR data, has a colleague check them, and keeps the REGES-ONLINE response attached to the change it belongs to. Submissions run through your employer’s own REGES-ONLINE access: by hand, or in API mode set up with the employer’s API keys.
Submissions run through your employer’s own REGES-ONLINE access: by hand, or in API mode set up with the employer’s API keys.
Art. 2
Dated facts. Sources at the foot of the page.
REGES-ONLINE replaced Revisal as the general employee register. Each hire, change, suspension and termination is still prepared by someone, checked by someone and submitted by a person the employer has designated in writing, or by a contracted provider. That is the part we organise.
Art. 3
Six operation types, one row each.
Each operation starts from a change in your HR data and ends with the register’s response attached. The specialist responsible confirms the legal basis and timing for each case.
| No. | Operation | Typical source in HR | Fields that change | Supporting document | Checked by | Details |
|---|---|---|---|---|---|---|
| 01 | Hire | New employee file | Contract number and date, start date, COR occupation, contract type and duration, workplace, working time, gross base salary and allowances | Signed employment contract | HR lead | |
| ||||||
| 02 | Change | Approved amendment | Salary, role and COR code, working time, workplace, allowances | Amendment or decision | HR lead | |
| ||||||
| 03 | Suspension | Leave or suspension decision | Suspension type, start date, expected end | Decision, supporting request | HR lead | |
| ||||||
| 04 | End of suspension | Return to work | Suspension end date | Return notice | HR operator + HR lead | |
| ||||||
| 05 | Termination | Termination decision | End date, legal basis as set by specialist | Termination decision | Employer representative | |
| ||||||
| 06 | Correction | Error found in an earlier entry | Only the corrected field, linked to the original entry | Internal note with reason | HR lead | |
| ||||||
Art. 4
Example record RG-2026-001482.
Step through an example salary change. The record keeps what was there before, what changed, who checked it and what the register answered.
| Field | Before | After |
|---|---|---|
| Salary | added: RON 6,850 | |
| Role | Human resources officer (COR 333304) unchanged | |
| Working time | 8 h/day unchanged | |
| Effective date | — | added: 1 Oct 2026 |
| Supporting document | Amendment no. 3 / 22 Sept 2026 · PDF · 2 pages | |
RDCOPILOT RECORD SUMMARY
Example data. The seal shows the time the outcome was confirmed.
State 1: Prepared
Values taken from the approved amendment.
State 2: Checked
Four-eyes check passed. Document matches the values.
State 3: Submitted
Submitted in REGES-ONLINE by the user the employer designated in writing (manual or API mode, see Art. 7). Attempt no. 1.
Mode: manual · response attached by A. PopIn API mode: set up with the external-system credentials the employer generates in REGES-ONLINE, tied to the designated user’s ID.
State 4: Response received
Register response stored with the entry.
Needs reconciliation if needed
If the response is missing or unclear, the entry waits in a queue with an owner. It never shows as done by itself.
State 5: Outcome confirmed
Response checked against the change and filed. Entry closed.
Submission always runs through the employer’s own REGES-ONLINE access, by the designated user by hand or in API mode.
Art. 5
§1–§3 · what the licence covers, and how it compares.
§1
We map the fields of your HR system or spreadsheet to register operations: employer, employee and contract identities stay separate, and values that need a specialist’s judgement are flagged instead of copied.
§2
Every operation is prepared from an approved change and checked by a second person before it goes to the designated user. Corrections become new versions linked to the original.
§3
Each entry moves through clear states, from prepared to outcome confirmed. The register’s response stays with the change, and anything uncertain waits in a reconciliation queue with an owner.
A qualitative comparison, no estimates.
| Spreadsheet and manual entry | With RDCopilot REGES | |
|---|---|---|
| Where values come from | Retyped from the HR file | Taken once from the approved change |
| Second check | Arranged case by case | Required before submission |
| Supporting document | In a separate folder | Attached to the entry |
| Register response | Screenshot or email, if kept | Filed with the change |
| Corrections | Earlier value overwritten | New linked version |
| Who did what | Depends on how access is shared | Named person per action |
Fig. 2
Screens from the product UI.
| Entry | Employer | Operation | Employee | Effective | State | Owner |
|---|---|---|---|---|---|---|
RG-2026-001485 | Example Retail SRL | Termination | Mihai D. | 2 Oct 2026 | Needs reconciliation | R. Dinu |
RG-2026-001484 | Example Logistics SRL | Correction | Elena V. | 15 Sept 2026 | Prepared | A. Pop |
RG-2026-001483 | Example Services SRL | Hire | Radu T. | 13 Oct 2026 | Awaiting check | M. Ionescu |
RG-2026-001482 | Example Services SRL | Change — salary | Ioana M. | 1 Oct 2026 | Outcome confirmed | M. Ionescu |
RG-2026-001479 | Example Logistics SRL | Change — working time | Sorina P. | 1 Oct 2026 | Submitted | A. Pop |
RG-2026-001476 | Example Services SRL | End of suspension | Andrei C. | 1 Oct 2026 | Outcome confirmed | M. Ionescu |
| Person | Example Services | Example Logistics | Example Retail |
|---|---|---|---|
| A. PopHR operator · designated user | PrepareSubmit | Prepare | —no access |
| M. IonescuHR lead | Check | Check | —no access |
| E. StanHR operator | —no access | —no access | Prepare |
| R. DinuHR lead · designated user | —no access | —no access | CheckSubmit |
Every access given or withdrawn is logged with person, employer and time.
Screens from the product UI with example data. Names and identifiers are invented.
Art. 6
Four steps, each with a named owner.
The amendment or decision is approved in your HR system or file.
Who HR
RDCopilot prepares the register operation; a colleague checks values against the document.
Who HR operator + HR lead
A person the employer designated in writing, or a contracted provider, submits the operation: by hand in REGES-ONLINE, or through API mode set up with the employer’s REGES-ONLINE API keys.
Who Designated user
The register’s response is attached to the change and the entry is closed or sent to reconciliation.
Who HR lead
Art. 7
Two submission modes, defined once.
Access is set per employer, per person and per action. Contracted providers working for several employers see only the employers assigned to them.
(a) Manual
The designated user submits the prepared operation in REGES-ONLINE. The register’s response is then attached to the entry in RDCopilot.
(b) API
API mode uses the user ID and employer ID from the REGES-ONLINE API keys and the external-system credentials your employer generates, so API access stays tied to the designated user and the employer. The response is attached to the entry and checked before the entry closes.
Which mode applies to which operation is agreed during discovery against the current official documentation. Branches with hiring authority can be set up as their own employer context.
Art. 8
Part of RDCopilotOS: five connected products.
One register record, fed by the products you already use.
Art. 9
One setup fee, one monthly licence. Hosting and access.
I. Discovery: operations in scope, roles, current HR source, access arrangement and submission mode per operation.
II. Mapping: field dictionary, identities, document rules, review steps.
III. Pilot on one operation type with your team, end to end to the response.
IV. Remaining operations, access review, handover and go-live.
Example schedule. Phases and dates are confirmed in your offer.
Scope and availability are confirmed with your offer.
Annex A
Eight questions we are asked before an offer.
No. REGES-ONLINE remains the legal register run by Inspecția Muncii. RDCopilot REGES prepares and checks each operation and keeps the register’s response with the change; the obligation to submit stays with the employer.
A person the employer has designated in writing, or a contracted provider’s designated employee. In manual mode that person submits in REGES-ONLINE. In API mode, submission uses the API keys and external-system credentials the employer generates in REGES-ONLINE, tied to the designated user’s ID and the employer ID. Either way, the RDCopilot history shows who prepared, checked and submitted each operation, and for which employer (see Art. 7).
API mode is set up with the API keys and external-system credentials your employer generates in REGES-ONLINE, following the official technical specifications. Operations you prefer to submit by hand stay manual, and the record still keeps the register’s response.
The entry does not show as done. It moves to a reconciliation queue with an owner, the response (or its absence) is kept, and a correction is prepared as a new version linked to the original. Warnings REGES-ONLINE raises, such as a salary below the national minimum, are kept with the entry and resolved before it closes.
No. We map your current system or spreadsheet to register operations. We map RDCopilot HR or Payroll the same way as any other source. Your Revisal history is already in REGES-ONLINE, so nothing needs to be migrated there.
Yes. Access is set per employer and per person, so each colleague sees only the employers assigned to them, and every action is logged under the right employer. Under HG 295/2025 your designated employees submit for each employer, the service cannot be subcontracted, and public institutions keep the register in-house.
No. It prepares, checks and keeps the evidence, but it does not replace legal or HR advice. Your specialist decides the legal basis and timing of each operation, and the employer stays responsible for the data.
Data is hosted in the EU. Pricing is a one-off setup fee plus a monthly licence, quoted after a short discovery call.
Art. 10
Closing article.
Closing article
Tell us which operations you handle, how many employers you work for and where your HR data lives. We reply with a scoped offer: setup, monthly licence and a plan with the phases confirmed.
Guides
Who may prepare, check and submit for each employer, where the REGES-ONLINE credentials are kept, and what happens when someone leaves.
Read guideFrom the approved amendment to the confirmed outcome: versions, attempts, and what to do when the answer is missing or unclear.
Read guideKeep employer, employee and contract apart, prepare only the fields that change, and flag what needs a specialist’s decision.
Read guideSources reviewed 7 Oct 2026.
RDCopilot REGES supports your team’s work; it does not replace legal or HR advice. Under HG 295/2025 the employer remains solely responsible for the data sent to the register. The responsible specialist confirms the legal basis and timing for each operation. RDCopilot is not affiliated with Inspecția Muncii.
© 2026 R&D COPILOT Made in EU Contact form
