How do I email payslips to each employee separately?

Export a list from payroll where each row holds the employee's email address and the filename of their payslip PDF, keep the PDFs in one folder, and use a tool that reads the filename column to send one message per row. Each person receives only their own file, addressed to them alone, with nobody else visible.

Is it safe to email payslips this way?

Each employee is sent a separate message containing only their own attachment, so there is no shared recipient list and no possibility of one person seeing another's payslip in a To or CC field. The safeguards that matter are previewing before sending and using a tool that refuses to send a row whose attachment cannot be found, so nobody receives a blank payroll email.

Can I send payslips to personal email addresses?

Technically yes — the address column can hold any address. Whether you should is a policy question for your organisation, and many payroll teams send only to work addresses or send password-protected PDFs when sending externally. The merge tool does not change that decision either way.

Guide

Emailing payslips individually

Payroll produced one PDF per employee. Every one has to reach exactly one person and nobody else. This is the merge where a mistake is not an inconvenience — so it is worth doing with a preview and a tool that refuses to guess.

The one rule that matters here.

Every employee gets their own message, addressed to them alone. No CC, no BCC pile, no shared list — so there is no field in which one person can see another's name, let alone another's payslip.

What you need from payroll

Most payroll systems will export an employee list and a batch of individually named PDFs. You need the two to line up:

the employee's email address
the filename of their payslip
optionally their name and the pay period, for the message itself

Payroll systems often name payslip files by employee number rather than by name — E00417-2026-08.pdf. That is ideal, because employee numbers are unique in a way that names are not. Two people called Sam Ahmed is a real situation, and filename matching by name is where that becomes a serious incident.

Check the counts before you write anything

Sort the PDF folder by name and compare the file count against your spreadsheet rows. If payroll has 84 employees, you want 84 rows and 84 PDFs. A mismatch found now is a two-minute fix; found after sending, it is a conversation with someone who did not get paid information they were expecting.

Write the message once

Subject: Your payslip for {{Period}}

Hi {{FirstName}},

Your payslip for {{Period}} is attached. If anything looks wrong, reply to this message and we will check it.

Payroll

Keep it short. A payslip email is a delivery mechanism, and the recipient's attention is on the attachment. Do put the period in the subject — people search their mail for "payslip August" a year later.

The two safeguards

Preview before sending. A wrong column mapping is wrong for everybody at once. Reading the first three assembled messages, each showing its attachment, catches it in seconds.

Never send a row with a missing file. An employee receiving a payroll email with no payslip attached will assume something has gone wrong with their pay. Tellmerge holds that row back and names it, rather than sending an empty message and letting you find out later.

Sending from your own mailbox

Payslips should come from the address employees already recognise — payroll@, hr@, or your own. Sending through your Outlook mailbox means exactly that, with replies coming back to you and a copy in Sent Items as your record that each one went.

It also means no employee data passes through a third-party sending platform, which is usually the answer your organisation wants when it asks where the payslips went. What Tellmerge does and does not hold.

More Outlook mail merge guides · Mail merge with attachments · Install Tellmerge