A salary certificate is a short signed letter confirming that a named person works for you, in which role, since when, and what they are paid. Somebody outside the company has asked for proof: a bank, a landlord, an embassy, a lender. The letter exists to restate facts already sitting on the employee record, which is why it should take minutes and usually takes days.
The queue forms for one reason. Each request gets retyped from scratch, chased to a signer, and then retyped again when the person spots that their job title is a year out of date.
What people actually ask for
Six requests cover almost all of it, and they are not the same document.
| Request | What it confirms | Usually for |
|---|---|---|
| Employment confirmation | That the person is employed now, their role and start date | Landlords, immigration checks, professional bodies |
| Salary certificate | Employment plus current pay, sometimes with allowances | Banks, mortgage and loan applications |
| Service or experience letter | Dates of employment and roles held, issued on exit | The employee's next employer |
| Visa or embassy letter | Employment, pay, and that leave has been approved for named dates | Consulates |
| Bank account opening letter | Employment and salary, addressed to a named institution | Payroll onboarding in a new market |
| Reference | Whatever your reference policy allows | A prospective employer |
Deciding which of these you issue, and in what form, is a policy question you answer once. Answering it per request is what makes the work feel endless.
Where the wording comes from
Every field on the letter should be a field on the record: legal name as it appears on the identity document, job title, contract type, start date, hours, current pay with its effective date, and currency. Pull them, do not type them.
Article 5(1)(d) of the GDPR requires personal data to be accurate and, where necessary, kept up to date, with every reasonable step taken to erase or rectify inaccurate data without delay. A letter typed from memory is how an old job title or a superseded salary leaves the building with a signature under it. When the letter is generated from the pay history, the figure it carries is the figure payroll used, and the two cannot drift apart. Employee records: what to keep, where, and for how long sets out what that history needs to hold.
One caution on content. A letter confirms facts about employment and pay. It should not restate why someone was absent, what their health is, or what a manager thinks of them. Those are held under narrower access on the record for a reason and they do not belong in a document handed to a landlord.
References follow different rules
A reference is not a certificate. In the UK an employer does not usually have to give one at all, unless there was a written agreement to provide one or the industry is regulated, financial services being the common example. If you do give a reference it must be fair and accurate, and it is allowed to be brief: job title, salary and the dates of employment satisfy most requests.
The practical policy is to pick a form and apply it to everyone. A one-line reference for one leaver and a warm paragraph for the next is the version that ends up being compared.
The day-one statement is a separate obligation
An employment letter does not discharge the statutory one. In the UK, employees and workers must be given a document stating the main conditions of employment when they start work. The principal statement is due on the first day and covers the employer's name, the job title or a description of the work, the start date, how much and how often they are paid, hours and days of work and whether they vary, holiday entitlement, the workplace, probation terms and any obligatory training. The wider statement, which includes pensions, collective agreements and the disciplinary and grievance procedure, follows within two months of the start of employment.
That document belongs on the record as a record, issued and acknowledged on day one. The employee lifecycle, from signed offer to final day puts it in sequence with the rest of the joining paperwork.
Turning it into a five-minute job
The mechanism is dull and it works. Build a template per letter type with merge fields that read from the employee record. Give each template a named approving role. Let the employee raise the request themselves, from their own profile, so the first HR touch is an approval rather than a transcription. Sign it electronically and file the signed copy back onto the record, so the issue log answers who confirmed what, to whom, on which date.
Two details that get missed. Letters going to a consulate or a bank often need to be in the local language, so the template needs a language variant rather than a translated copy pasted into the same file, and right-to-left layouts need to render properly rather than approximately. And a letter that quotes a future bonus or an unconfirmed promotion is a commitment, so keep generated letters to facts with an effective date behind them.
Publish your own turnaround, measure it, and put the number in the policy. Two working days for a standard certificate is a commitment somebody can hold you to, which is the point of stating it.
When you have to say no
Some requests cannot be answered as asked, and refusing them cleanly is part of the policy. A third party ringing to ask about someone's sickness record gets nothing without the employee's own instruction. A request to confirm a rise agreed in November that does not take effect until January gets a letter stating today's figure with today's effective date. A former employee asking about a period you no longer hold records for gets the truth about what you still have, which beats a reconstruction.
Write the refusals into the policy in advance. They arrive at the worst moment otherwise, usually with a deadline attached and a manager already promising something on the phone.
When the queue is the symptom
If one person spends a day a week on letters, the letters are rarely the whole problem. It usually means the record is incomplete, so each request needs a hunt, and that the same hunt happens for payroll inputs and for every audit. When managed HR services cost less than a second HR hire works through the cost comparison when that day a week is not the only one. Teams that hand the running of it over keep the approval: prepared by us, approved by you, and the signature stays with the role you named.
Answered here.
- What is a salary certificate?
- A short signed letter confirming that a named person is employed by your organisation, in which role, since when, and what they are paid. Banks, landlords, embassies and lenders ask for one as proof of income. It states facts already on the employee record and adds nothing else, which is why it can be generated rather than written.
- Do we have to give an employment reference?
- In the UK an employer does not usually have to give a work reference, unless there was a written agreement to do so or the role is in a regulated industry such as financial services. If you do give one it must be fair and accurate, and it can be brief. Many employers limit references to job title, salary and dates of employment, applied to everyone.
- Who should sign an employment letter?
- One named role, not whoever is at their desk. Pick the role in your policy, record the signature against the request, and keep the issue log so you can answer later who confirmed what to which bank. Letters that leave over an individual manager's signature are the ones that get contradicted.
- Can an employee ask for their whole file instead of a letter?
- Yes. Article 15 of the GDPR gives them confirmation of whether their data is processed and a copy of the personal data undergoing processing, along with the purposes, the recipients and the storage period. That is a different request from a salary certificate and usually has a different owner and deadline, so route it separately.