How to Generate and Email Payslips
Payslips stay as screenshots and never reach inboxes
Staff print PDFs manually and miss people on leave.
No proof a slip was emailed when employees dispute delivery.
Slips generated before approval change again after recalculation.
Why this happens
- Generating slips before the run is Approved.
- Company email provider not configured.
- Employees missing work and personal email on the HR profile.
- Relying on browser print only with no bulk send.
Biznsbook addresses this through GeneratePayslips, payslip preview, EmailPayslip, EmailPayslipsForRun, IsEmailed flag when Payroll is licensed with HR Management — attendance and leave feed calculation, while Accounting posts accrual and payment.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Generate and Email Payslips
Built for HR and finance teams running Biznsbook Payroll under HRMS — salary structures, periods, runs, payslips, loans, and accounting posting on one tenant.
- Reach Approved or later. Payslips generate only for Approved, Posted, or Paid runs.
- Generate payslips. On Run details, Generate payslips. Existing slips are skipped.
- Preview or print. Use PreviewPayslip or Payslip details (/HRMS/Payroll/Payslips) for the print layout.
- Confirm employee email. Ensure Work Email or Personal Email exists on the employee record.
- Email one or all. EmailPayslip for a single slip or EmailPayslipsForRun for the whole run.
- Check emailed flags. IsEmailed and EmailedDate update when send succeeds via the company email provider.
- Handle bounce-backs. Fix emails and resend; generation does not need to run again if the slip already exists.
Review results after the first full each pay period cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: Generating slips before the run is Approved. Repeating this each month usually shows up first in pay accuracy, tax withholding, and GL close quality.
- Mistake 2: Company email provider not configured. Repeating this each month usually shows up first in pay accuracy, tax withholding, and GL close quality.
- Mistake 3: Employees missing work and personal email on the HR profile. Repeating this each month usually shows up first in pay accuracy, tax withholding, and GL close quality.
- Mistake 4: Relying on browser print only with no bulk send. Repeating this each month usually shows up first in pay accuracy, tax withholding, and GL close quality.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- Reach Approved or later — Payslips generate only for Approved, Posted, or Paid runs.
- Generate payslips — On Run details, Generate payslips.
- Preview or print — Use PreviewPayslip or Payslip details (/HRMS/Payroll/Payslips) for the print layout.
- Confirm employee email — Ensure Work Email or Personal Email exists on the employee record.
- Email one or all — EmailPayslip for a single slip or EmailPayslipsForRun for the whole run.
Teams that finish settings and periods before Calculate, clear exclusions before Approve, and reconcile tax and loan reports before Close period keep payroll and GL aligned.
How Biznsbook supports this workflow
GeneratePayslips is documented in Biznsbook Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
payslip preview is documented in Biznsbook Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
EmailPayslip is documented in Biznsbook Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
EmailPayslipsForRun is documented in Biznsbook Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
IsEmailed flag is documented in Biznsbook Payroll capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
Process Payroll and ApprovePayroll are separated so clerks can calculate while controllers approve and post.
Suggested implementation timeline
- Week 1: Document current process gaps and configure GeneratePayslips with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using related help and leadership dashboard.
Metrics to track monthly
- Open payroll periods matching company frequency
- Runs calculated with zero unexplained exclusions
- Tax withheld matching accrual TotalTax
- Payslips emailed (IsEmailed) after generate
- Loan EMI recovered on posted runs
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook GeneratePayslips and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Timing | ❌ Any draft status | ✅ Approved / Posted / Paid only |
| Delivery | ❌ Manual PDF share | ✅ Bulk email from the run |
| Proof | ❌ No system flag | ✅ IsEmailed + EmailedDate |
| Content | ❌ Totals only | ✅ Earnings, reimbursements, tax, attendance |
| Duplicates | ❌ Risk of re-create | ✅ Skips existing slips |
| Automation | ❌ None | ✅ PayslipGenerated event published |
Frequently asked questions
Can I email before posting to accounting?
Yes, once the run is Approved you can generate and email before or after Post.
What if email fails?
Check company email settings and employee addresses; the slip remains available to print.
Do off-cycle runs support payslips?
Yes — same generate and email actions on Off-Cycle and Bonus runs.
Is there a REST API for slips?
No. Payslip processing is through MVC screens today.
How this differs by industry
Retail
Store HR emails slips after Mark paid so cashiers receive net pay confirmation the same day.
Wholesale & distribution
HQ payroll bulk-emails the monthly run then monitors IsEmailed for exceptions.
Manufacturing
Plant offices print shop-floor slips for staff without email, then email office staff in bulk.