Ireland Payroll ROS
Retrieve RPNs and submit the Payroll Submission Request to Revenue on or before each pay date, signed with your own ROS certificate.
Store price is USD 298 all-in: installing this also pulls the 1 paid ERP Heritage module it depends on.
Why this module
Ireland Payroll ROS
On or before the pay date
Retrieve the latest RPN before a run, build the Payroll Submission Request from the payslips, and submit it to Revenue. Endpoints and authentication follow Revenue's published REST API.
Your certificate, encrypted
Authentication uses your own ROS digital certificate with IETF HTTP Signatures. The certificate and password are encrypted at rest and never shown again. Live calls are blocked while automated tests run, so nothing leaves the building by accident.
A resend is not a duplicate
Each submission carries a stable identifier and a content hash, matching Revenue's on or before resubmission model. A failed transport is recorded against the submission, not crashed, and can be resent as the same submission.
Day in the life
Submitting a pay run to Revenue.
After a pay run is confirmed, one action builds a submission line for each payslip, carrying the pay, income tax, USC and PRSI already computed on the payslip. The request is signed with the employer certificate and sent to Revenue, and the response is reconciled against the run. You test it against the Public Interface Test environment first, then submit in production with the same flow.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Each submission has a stable identifier and a content hash, so resending after a transport hiccup is the same submission, not a duplicate filing.
A hard guard blocks any live call to Revenue while automated tests run, so a test can never file a real submission.
A transport failure is recorded against the submission and posted to its log, rather than raised as a crash that loses the run.
The PPS numbers it carries and the ROS certificate and password are encrypted at rest, with the certificate restricted to payroll managers.
What is inside
Built to do the job, end to end.
- RPN. Retrieve and store Revenue Payroll Notifications, and apply them to the employment.
- Payroll submission. Build the submission line items from the payslips and submit on or before the pay date.
- Signed transport. One signed request chokepoint using HTTP Signatures and your ROS certificate.
- Status and reconciliation. Poll the submission and run status, on a schedule or on demand.
- Configuration. Employer registration, agent identifier and the test or production environment, in one place.
Honest about the edges
What this does not do, so nothing surprises you.
- It requires your own ROS digital certificate, in p12 form, from Revenue. No certificate is shipped.
- Verify it against the Public Interface Test environment before submitting in production.
- The exact submission field set should be confirmed against Revenue's current developer specification before go live. The module is built so a field is configuration, not a code change.
- It requires the Irish payroll engine and Odoo Enterprise Payroll.
- It files payroll submissions. It does not pay the tax or operate your Revenue account.
PAYE Modernisation Odoo, real time payroll submission Ireland, RPN retrieval, Payroll Submission Request, Revenue Online Service, ROS digital certificate, HTTP Signatures, on or before reporting, Irish payroll Revenue filing, Odoo Enterprise Irish payroll ROS
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
End to end French B2B and B2G electronic invoicing for the DGFiP reform, generating Factur-X PDF/A-3 with embedde...
Sync attendance clock events from the Employment Hero people platform into the stock Odoo Attendances app, keyed...
The Singapore country pack for the ERP Heritage Employment Hero integration
The complete ERP Heritage Employment Hero integration in one install
Sync timesheet entries from the Employment Hero people and payroll platform into the standard Odoo Timesheets app...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Payroll (hr_payroll)
• Invoicing (account) • Discuss (mail) • Notes (note) • Employee Contracts (hr_contract) • Employees (hr) • Time Off (hr_holidays) • Calendar (calendar) |
| Community Apps Dependencies | Show |
| Lines of code | 2439 |
| Technical Name |
eh_l10n_ie_hr_payroll_ros |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module