Mass payslip email, finally reliable and auditable.
Send every finalized payslip PDF to the right address in one click — with up-front mail-server validation, per-employee routing, and a full delivery audit log so every payroll run lands, every time.
Payroll teams still open payslips one by one to print, export, and email them — a routine that eats hours every pay cycle and breaks silently when an employee's email is missing or wrong. Native Odoo Payroll has no batch send, no routing control, and no way to know who was actually reached until an employee complains.
Select an entire pay run and send every payslip PDF in a single action. Mail-server readiness is checked up front, each employee's email is validated before send, and a routing rule decides whether the PDF goes to their work address, private address, or both — with a fallback so no one is skipped. A consolidated report and an audit log show exactly who received what, and where.
Everything a payroll team needs to send with confidence
Every capability below is implemented in the module.
One-Click Mass Send
Select a whole pay run or any set of payslips and send every PDF by email in a single confirmed action — no per-employee steps.
Per-Employee Email Routing
Route each payslip to the employee's work email, private email, or both — configurable per employee, with sensible defaults.
Fallback Address
If the routed address is missing or invalid, the payslip automatically falls back to a defined alternate email so no employee is skipped.
Up-Front Mail-Server Validation
Outgoing mail configuration is checked before the batch starts, not discovered mid-send when it's too late to fix.
Employee Email Validation
Every recipient address is validated before sending, catching missing or malformed emails before they cause a silent failure.
Consolidated Failed-Recipient Report
After every batch, see exactly which employees were not reached and why — no email, invalid address, or mail-server error.
Delivery Audit Log
Every payslip email is logged with the exact address used and the outcome, giving payroll a clear compliance and dispute-resolution trail.
Per-Payslip Send-State Tracking
Each payslip carries its own To Send / Sent / Failed status directly on the record, always visible from the list.
Configurable Send Trigger & Daily Limit Awareness
Choose whether sending happens on confirmation, on payment, or manually, and get warned before a large run risks the outgoing daily mail limit.
How it works
Confirm payslips
Run payroll as usual in Odoo Payroll and confirm the pay period's payslips.
Select and launch
Select the payslips to send — one, several, or a whole batch — and open the mass mail wizard.
Validate and send
The app checks mail-server readiness and each employee's routed address, then sends every PDF in one action.
Review the outcome
Check the failed-recipient report and the delivery audit log to confirm every payslip reached the right inbox.
See it in action
The mass send wizard, delivery tracking, and routing configuration in Odoo Payroll.
The payslip list gains an Email Status column — To Send, Sent, or Failed — visible at a glance across the whole batch.
Select any set of payslips from the list, choose Send Payslips by Email from the Action menu, and send the whole batch in one confirmed action.
Each payslip's Email Distribution tab shows its send state and sent-to address, with a smart button linking to its email logs.
Every send attempt is recorded in the Payslip Email Log, with sent and failed rows kept side by side for review.
A failed log entry shows the exact error reason, so HR knows immediately whether it was a missing address or a mail-server problem.
Each employee's HR Settings tab lets HR choose work, private, or both addresses for payslips, plus a fallback email and a live recipient preview.
The Payroll settings block sets the company-wide default routing, the send trigger (on confirm, on paid, or manual), and the daily send-limit warning.
Frequently asked
Does this replace Odoo's native payslip email?
No — it builds on Odoo Payroll's existing send pipeline, adding mass selection, routing, validation, and delivery tracking on top of it.
What happens if an employee has no valid email address?
The employee is flagged in the failed-recipient report with the reason (no address, invalid address, or mail-server error) instead of being silently skipped.
Can different employees receive their payslip at different addresses?
Yes — routing (work, private, or both) is configurable per employee, with a fallback address if the primary is empty or invalid.
Which Odoo editions and versions are supported?
This app is built for Odoo 19 Enterprise and is also available for Odoo 18 and Odoo 17, on top of the standard hr_payroll module.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Mass Payslip Send by Email brings one-click bulk sending, per-employee routing, up-front validation, and a full delivery audit log to Odoo Payroll.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Payroll (hr_payroll) • Employees (hr) |
| Lines of code | 668 |
| Technical Name |
cerevantix_mass_payslip_send_by_email |
| License | OPL-1 |
| Website | https://cerevantix.com |
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