A landlord is waiting for proof of income, a mortgage broker has set a deadline, or an overseas organisation has asked for confirmation of employment. The request lands in a shared HR inbox, often with no standard form, no clear consent record and no indication of whether salary information is required. Someone then searches payroll, copies an old letter, obtains a signature and sends a PDF, hoping the details are correct.
An employment letter of verification should be more controlled than that. In the UK, it sits between ordinary employee administration, data protection and, in some cases, immigration compliance. Treating it as a governed workflow helps HR confirm the right facts, disclose only what's authorised and retain evidence that shows how the decision was made.
Table of Contents
- What an Employment Letter of Verification Actually Is
- Core Content Every UK Verification Letter Must Cover
- Writing the Letter Without Crossing into a Reference
- Approving and Delivering the Letter Securely
- Retention, GDPR and Right-to-Work Evidence
- Common Mistakes and Practical Next Steps
What an Employment Letter of Verification Actually Is
An employment letter of verification is a factual document issued by an employer to confirm that a person works, or worked, for the organisation. It normally confirms the employment relationship, job title, employment dates and status. Where the employee has clearly authorised disclosure and the recipient needs it, the letter may also confirm pay.
Typical requesters include landlords, mortgage providers, background-screening organisations, prospective employers, pension bodies and consulates. HR teams may see different labels for the same underlying request, including employment confirmation letter, salary verification letter, status confirmation, proof of employment and work verification. The wording varies, but the control question doesn't: what information has the employee consented to disclose, and can HR support it with an authoritative record?
What the letter confirms
A defensible letter confirms facts held in HR or payroll systems. That might include:
- Employment status: Current, former, fixed-term or another accurately recorded status.
- Role: The employee's current or relevant historic job title.
- Tenure: Start date and, for former employees, the end date held in the personnel record.
- Pay: Gross salary or another approved pay field, only where the request and employee authority justify disclosure.
- Purpose: The recipient or reason for which the letter has been issued.
UK employers don't usually have to provide a reference. GOV.UK explains that an employer doesn't usually have to give one, but if it does, the reference must be fair and accurate. The same guidance identifies exceptions, including regulated areas such as financial services, where references may be required. That means a routine verification is usually a discretionary service, but issuing one creates a duty not to mislead through false statements or misleading omissions. See the related distinction between employment contracts and other employment documents before reusing contractual wording.
What the letter isn't
A verification letter isn't a character reference, performance appraisal, disciplinary declaration or promise about future employment. It also isn't proof of a person's right to work in the UK. A Home Office right-to-work check is a separate compliance activity, completed before employment begins, with evidence retained by the employer.
The distinction becomes important when an overseas consulate, EEA pension body or UK student-loan company asks for a formal letter. The recipient might have its own format, translation or authentication expectations, but HR should still separate factual employment confirmation from opinion. If the requester needs a reference, that should follow the organisation's reference policy and approval route, not be smuggled into a verification letter.
Core Content Every UK Verification Letter Must Cover
A reliable letter starts with the organisation's identity and ends with an authorised signatory. The document should be easy for a third party to validate and easy for HR to reconcile against Dynamics 365, payroll and the employee record.
Build the document in factual blocks
Use the following structure:
- Company block: Full legal entity name, registered office and, where appropriate, the Companies House number. Use the correct employing entity, not the trading brand.
- Recipient line: Name the landlord, lender, authority or screening provider where possible. Use “To whom it may concern” only when the requester hasn't supplied a named recipient.
- Subject line: Identify the employee and the purpose without adding unnecessary personal data.
- Employee identification: Use the full name. A date of birth or employee reference may be appropriate only where the recipient requires it and the employee has authorised it.
- Employment facts: State whether the person is current or former staff, their job title, start date and, where relevant, end date, notice status or fixed-term position.
- Working arrangement: Record full-time or part-time status and hours only when that information is relevant and verified.
- Pay: Include gross salary only when the employee has given written consent and the recipient has requested it. Treat bonuses, allowances and variable pay as separate fields, not assumptions.
- Sign-off: Add the authorised signatory's name, job title, business contact details and signature. Check whether the recipient accepts a qualified electronic signature or requires a wet-ink document.
ACAS guidance describes a basic reference as often limited to job title and employment dates, while a more detailed reference may include skills, disciplinary records and the reason employment ended. That supports a conservative approach for verification letters. The Home Office's right-to-work framework deals with eligibility evidence, not with replacing a factual employment letter, so HR shouldn't present the two documents as interchangeable.
| Content Block | Required for All Letters | Include Only With Employee Consent or On Request |
|---|---|---|
| Legal employer identity | Full legal name and business contact details | Companies House number or registered office where relevant |
| Employee identity | Full name | Date of birth, employee reference or other identifier |
| Employment facts | Job title, start date and current or former status | End date, notice period, leave status or TUPE context |
| Working arrangement | Only where necessary to explain status | Hours, working pattern or employment classification |
| Compensation | Not automatically required | Gross salary, bonus, allowance or pay frequency |
| Commentary | Factual wording only | Reference information under a separate approved policy |
| Authentication | Authorised signatory and contact route | Wet ink, seal, translation or apostille-ready wording if the recipient requires it |
UK practice is usually terse, factual and issued on headed paper. EU requirements aren't uniform. A German or French landlord may ask for a translated, sealed document or wording suitable for later authentication, but the employer must confirm the recipient's exact requirement rather than assume that one national format applies across the EU. Local employment, payroll, tax and privacy rules can also differ by member state.
Writing the Letter Without Crossing into a Reference
The safest employment letter of verification is short enough to audit and specific enough to answer the request. Put the date at the top, address the named recipient, state the confirmed facts in one paragraph and close with an authorised signature and verification contact.
A suitable sentence might read:
Ms Patel has been employed by Example Services Ltd as Senior Quantity Surveyor since 4 March 2021. Her current gross annual salary is £58,000, as authorised in writing for disclosure to the named mortgage provider.
That sentence does useful work. It identifies the employer, role, start date and pay, and it makes the scope of authority visible. It doesn't assess performance or promise anything about the future.
Keep opinion out of the document
Don't write that Ms Patel is “one of our most reliable employees” or that the organisation “would happily re-employ her”. Those statements turn a factual confirmation into a reference-style assessment. They may also create inconsistency with a later reference, internal performance record or legal disclosure.
Promotion history can be recorded factually: “The employee held the role of Quantity Surveyor from the recorded promotion date and has held the role of Senior Quantity Surveyor since the later recorded date.” For parental leave, use only the status needed by the recipient and confirmed in the relevant record. Don't disclose medical detail.
Redundancy in progress needs particular care. Confirm the current employment status accurately and avoid presenting a future termination as completed. A TUPE transfer should identify the correct employing entity and relevant continuity facts only when the records and request support them. If the signatory isn't the line manager, wording such as “According to our HR records” or “To the best of my knowledge based on the records available to me” prevents the letter from implying personal knowledge.
A reusable paragraph
An HR administrator can paste this into Word or a Dataverse template:
This letter confirms that [full name] is employed by [legal entity] as [job title], having commenced employment on [start date]. Their current employment status is [status]. [If authorised and requested: Their current gross [annual/monthly] salary is [amount].] This confirmation is based on the organisation's employment records and is provided to [named recipient] for [stated purpose].
Use present tense for current employment. Once the employment record has ended and the P45 has been issued, use past tense and the recorded end date. Never let a template populate a field merely because the field exists. The approval decision should determine what appears.
Approving and Delivering the Letter Securely
A secure process begins before anyone drafts the document. The employee or authorised requester should submit the request through a Microsoft 365 form or employee self-service channel, identifying the recipient, purpose, deadline and fields required. HR should then authenticate the requester against the employee record in Dynamics 365 and Dataverse, rather than relying on an email signature or an attachment supplied by the requester.
Use two approvals for sensitive fields
For ordinary employment facts, HR operations can prepare the draft from authoritative records. If the request includes salary, leave status, an end date, a notice period or unusual wording, route it to the HR Business Partner and line manager for a two-stage review. The line manager should validate operational context, while the HR Business Partner confirms policy, consent and disclosure scope.
Power Automate can create the approval actions, record decisions in Dataverse and prevent issue until the required approvals are complete. Store the requester, employee, recipient, purpose, fields disclosed, approvers, decision dates, document version and delivery route as structured audit fields. A PDF generated through SharePoint, Word templates or a custom HR application should carry the approved content, not a manually edited copy.
The operational layer can sit within an HRManagement365 workflow, while the underlying solution is built in Power Platform, Dynamics 365 and Dataverse. Standard Microsoft capabilities should be distinguished from custom development. A customer may need a custom approval rule, a specialist integration with a screening portal, an expiry reminder or a bespoke letter application, and those requirements can be developed without treating every organisation's process as identical. The HR document centre is a useful model for organising controlled documents and access.
Deliver only through a controlled route
Use a secure third-party portal, controlled SharePoint sharing or another approved transfer method. Don't send an unprotected PDF to an address copied from an unverified email. If a file must be sent as an attachment, protect PDFs with PDFKing and communicate the password through a separate approved channel.
Record the recipient's name, organisation, contact details, delivery date and document identifier. If the recipient reports an error, revoke the superseded document where the delivery system allows it, issue a corrected version with a new identifier and preserve the reason for reissue. Logging the verifier also helps when a later background-check provider asks whether a document came from the organisation.
Retention, GDPR and Right-to-Work Evidence
An employment verification letter contains personal data, so retention needs a defined purpose and an end point. Employers should record what they hold, why they hold it and how long it is needed. UK GDPR's storage-limitation principle means an issued letter should not remain indefinitely in SharePoint or Dataverse because storage is available.
Retention depends on the transaction. A mortgage or tenancy request may justify keeping the request and issued copy while that application is active. A visa or pension matter may require retention for the relevant legal obligation or challenge period. In the case record, capture the purpose, lawful basis, access restrictions, review date and disposal action. A single blanket rule rarely fits every employee document.
| Record type | Typical retention | Legal basis | Disposal action |
|---|---|---|---|
| Verification request and consent | While the request and any challenge remain active | Employment administration and documented request handling | Delete or anonymise when the purpose ends |
| Issued verification letter | For the stated mortgage, tenancy, pension or visa purpose | Necessary employment administration, legal obligation where applicable, or another documented basis | Secure deletion or restricted archival treatment |
| Approval and audit record | For the organisation’s governance and challenge requirements | Accountability and employment records management | Retain only under the approved schedule, then delete or anonymise |
| Right-to-work evidence | In line with the Home Office compliance requirement and the organisation’s documented policy | Legal obligation | Secure disposal when no longer required |
A practical data retention guide for support teams can help HR and IT assign ownership, define deletion actions and align operational records. The resulting policy must still reflect UK GDPR, employment records and the organisation's legal advice.
Keep right-to-work evidence separate
A verification letter confirms employment. It does not replace a right-to-work check. Employers must check an applicant's right to work before employment begins, then retain copies of the evidence and the date of the check. Home Office routes include share codes, original documents and identity service providers using IDVT. The right-to-work checks guidance for employers explains how that evidence should be handled alongside the wider verification process.
From 6 April 2022, employers could use IDVT through an identity service provider for certain checks, as set out in Home Office right-to-work employer guidance. The prescribed checks have applied from 1 October 2022 under the Home Office framework. Where the Employer Checking Service issues a Positive Verification Notice, it permits hiring or extending a contract for 6 months from the date specified in the notice. Store that notice in the right-to-work record, rather than attaching it to the employment letter as a substitute for the underlying evidence.
Digital status, eVisas and share codes make the evidence trail more important. In Dataverse, link the verification request to a separate right-to-work case, while keeping the records distinct. Power Platform can apply role-based access, route exceptions for approval and trigger reminders for relevant expiry or review dates. Dynamics 365 can retain the relationship between the employee, request, approver and final document without giving every HR user access to immigration evidence.
A subject access request should retrieve the letter, consent and relevant audit history. Employees also need a route to challenge factual errors. Configure deletion as a controlled workflow, with a review decision and disposal record, rather than relying on an administrator to remember when a folder should be cleared.
Common Mistakes and Practical Next Steps
Most failures are procedural rather than literary. HR teams know how to write a sentence, but they don't always know who authorised the disclosure, which system supplied the value or where the final copy went.
Watch for these recurring mistakes:
- Unchecked identity: A request arrives from a personal email address, and the administrator signs without confirming the requester or employee authority.
- Subjective language: A factual document includes praise, criticism, disciplinary commentary or a promise about future employment.
- Unsecured delivery: HR sends an unprotected PDF to a third party without confirming the recipient's details.
- Poor retention: The letter remains in a shared mailbox or personnel folder after the stated purpose has ended.
- Record mismatch: The letter uses a job title, salary or date that differs from Dynamics 365, payroll or the signed contract.
A defensible process uses a standard template library, a named approval policy, structured consent, controlled delivery and a searchable record trail. Start by auditing recently issued letters, then identify which fields caused manual checking or rework. Build the request and approval workflow in Power Platform, connect it to Dataverse and the relevant Dynamics 365 records, and brief managers on the difference between verification and reference language.
HRManagement365 is a UK and EU HR solution powered by Hubdrive and Microsoft technology. It extends Hubdrive and Microsoft with specialist implementation, integrations, customisations, workflows and HR applications, including customer-specific processes across the employee lifecycle. A governed verification workflow can therefore sit alongside employee records, document management, Power Automate approvals, Power BI reporting and integrations with Business Central or Finance and Operations, without forcing HR to rebuild every connector from scratch.
Speak to an HRManagement365 specialist to design a governed employment verification workflow around your Dynamics 365, Dataverse and Power Platform environment. Discover how HR Management 365 can help improve and automate your HR processes across the UK and EU, then phone +44 1522 508096 today or send us a message.
