Money One-page note UK only
HMRC Tax Refunds: Real or Scam?
"HMRC: you're due a tax refund, click here." Real HMRC never texts you that. Here's how to spot the fake and claim the real thing for free. Save this page.
Good to know
UK. Checked Nov 2026. General info, not financial advice.
What's on the page
The note as text, so you can read it, copy it or use a screen reader.
HMRC will never…
- Email, text, WhatsApp or call about a tax rebate
- Ask for bank or card details that way
- Make you click a link to get a refund
Scam red flags
- "You're owed £…, click here"
- Robot call: "lawsuit, press 1"
- Sender names can be faked
Real refunds
- Paid too much tax on your pay
- Job costs: uniform, tools, work mileage
- Claim free on GOV.UK (back 4 tax years)
- Paid via your tax code or a refund
Refund agents
- Fees up to 50% of your claim
- Wrong claim? You repay the full refund
- Same info you'd give HMRC yourself
Report it
- Texts: forward to 60599
- Emails: phishing@hmrc.gov.uk
- Lost money? Report Fraud
Do / Don't
- Sign in via GOV.UK, not a link
- Hang up on calls you can't verify
- Don't open attachments or links
- Don't sign an agent deal without reading the fees
Sources
- GOV.UK: Avoid and report internet scams and phishing – Report scam HMRC messages, calls and social media accounts
- GOV.UK (HMRC): Examples of phishing emails, suspicious phone calls and texts (updated 15 Dec 2025)
- GOV.UK (HMRC): Check if a text message you've received from HMRC is genuine (updated 5 Oct 2026)
- GOV.UK: Check how to claim a tax refund
- GOV.UK: Claim tax relief for your job expenses
- GOV.UK (HMRC press release): No frosty surprises when you claim tax relief directly with HMRC (28 Dec 2023)
- GOV.UK (HMRC): Receive Income Tax or PAYE repayments on behalf of others
How we checked this
Every fact on this note comes from the 7 sources listed here, checked against official or peer-reviewed sources where possible. AI tools help with drafting; a person checks every fact against the sources. How we research
Spotted a mistake? Tell us and we'll fix it and log it on the corrections page.