Priya picked up her first shift at a garden centre outside Guildford the week her A-level exams finished, on £12.71 an hour for twenty hours a week — the new National Living Wage rate that came in this April. Her rota app promised her roughly £254 before tax for the fortnight. What actually landed in her bank account was £42 short, and the payslip blamed a tax code she had never seen before: BR.
She is not alone. Every July and August, thousands of students, seasonal staff and people starting a second job get shunted onto what HMRC calls an emergency tax code, and most of them have no idea it is happening until the money has already gone. The good news is that it is almost always fixable within a pay cycle or two, and in most cases you get every penny back.
Why summer and temp workers get hit hardest
An emergency code gets applied whenever your new employer's payroll system doesn't yet have your full tax history for the year on file. Hand over a P45 from a previous job, or complete the online starter checklist — the form that quietly replaced the old P46 several years ago — and your employer can usually apply your correct cumulative code from the very first payslip. Skip that step, or start a job with no PAYE history at all, which describes most first-time summer workers, and the system defaults to assuming the worst about your circumstances until it hears otherwise. Garden centres, festivals, warehouses and hospitality chains all take on large numbers of short-term staff at exactly this point in the calendar, and payroll teams processing dozens of new starters in a single week don't always chase down every missing form before the first pay run goes out. Some of it comes down to timing rather than carelessness: a starter checklist submitted on a Wednesday might miss a payroll cut-off that fell on the Monday before. That's the practical reason emergency tax clusters so heavily around July and August rather than spreading evenly across the calendar. It isn't a punishment, and it certainly isn't personal — it's a default setting built for caution, not accuracy.
Reading the damage on your payslip
Three different codes can turn up, and they don't all cost you the same amount.
- 1257L W1, 1257L M1 or 1257L X — you still get the standard tax-free Personal Allowance of £12,570 for 2026/27, but it's worked out per pay period rather than cumulatively across the year, so allowance you haven't used yet from earlier months doesn't automatically carry forward.
- BR taxes every single pound at 20%, with no tax-free allowance applied at all — someone earning £1,200 a month under a BR code loses roughly £240 in tax that shouldn't be due yet, instead of the far smaller amount they'd actually owe once the Personal Allowance is factored in.
- 0T also strips out the Personal Allowance and can push income into the 40% and 45% bands sooner than it should, which hits hardest above the £50,270 higher-rate threshold, though it can still bite a modest summer wage.
For most students working a single summer job at typical seasonal hours, BR is the one to watch. The 2026/27 PAYE threshold sits at £242 a week or £1,048 a month; below that, on the correct code, you'd pay no income tax whatsoever, which is exactly what makes a BR deduction on a part-time wage so galling once you work out what it's actually costing you.
Fix it at the source before it ever reaches HMRC
The starter checklist is worth ten minutes of anyone's time in the first week of a new job, and it costs nothing to fill in. Ask your employer for the link, or find it yourself on GOV.UK under "Starter checklist for PAYE" — it asks a handful of straightforward questions about whether this is your only job right now, whether you've had other taxable income earlier in the tax year, and whether you're receiving certain benefits or a student loan, and the answers let payroll assign the right code immediately rather than defaulting to BR or 0T out of caution. You'll need your National Insurance number to hand, which is printed on old payslips, P60s, or your Personal Tax Account if you've mislaid it. If you do have a P45 from an earlier job this tax year, hand it over on day one rather than a week in, because payroll cut-off dates matter more than most people realise. Miss the deadline for the current pay run by even a day and the correction slips to the following payslip, sometimes the one after that. A five-minute conversation with HR in week one routinely saves people forty or fifty pounds they'd otherwise have to chase down later. It's the single most effective thing anyone starting seasonal work can do, and almost nobody does it.
What to do if it doesn't correct itself
Most emergency codes fix themselves within one or two payslips, once HMRC's systems catch up and your employer applies the cumulative 1257L code properly. When that happens, the overpayment is usually refunded automatically through your wages — you'll see a noticeably larger net pay on the corrected payslip, rather than a separate refund turning up anywhere else.
Check your actual tax code through the HMRC app or your Personal Tax Account on GOV.UK in week one, not week six — it takes about two minutes to log in and see exactly what HMRC currently holds on file for you, and it's the fastest way to catch a mismatch before a second wrong payslip goes out. If two full months pass and nothing has changed, ring HMRC on 0300 200 3300; an adviser can push the correct code through to your employer directly, rather than leaving it to sort itself out by the end of the tax year. Don't sit on a letter that never arrives explaining what went wrong — nothing is coming until you ask for it.
Stopping work before April? File a P50
This is where a lot of summer workers lose money they never needed to lose. If your job ends in August or September and you don't start another one before the following 5 April, HMRC's system may not reconcile your overpaid tax until well into the new tax year — sometimes not until the following summer, when it eventually issues a P800 calculation off its own back. Rather than waiting for HMRC to catch up in its own time, you can submit form P50 on GOV.UK once you've been out of work, or not expecting further taxable income, for at least a month, and claim the overpayment back directly. It's a short online form, and you'll need your P45 and your National Insurance number to complete it.
Refunds through this route are usually processed within four to six weeks, which for a student heading back to university with an empty bank account in September is often the difference between a manageable term and a stressful one. A P800 letter through the ordinary post can turn up anywhere from a few months to nearly a year later, and while HMRC does eventually pay out correctly owed refunds without a formal claim in most cases, nobody should have to wait that long for money that was theirs from the first payslip.
The one case where BR genuinely is correct
Not every BR code is a mistake worth fighting. If you already have another job that's using your full Personal Allowance — a term-time part-time role running alongside the summer one, say — then BR on the second job is exactly right, because you can't have two tax-free allowances running at once. The test is simple: check whether your combined income across both jobs, added together, still sits comfortably under £50,270. If it does, and BR still feels punishing on the smaller wage, you can ask HMRC to split your Personal Allowance across both employers instead, so neither payslip gets hit with the full 20% from the first pound. Most people never think to ask for that split, largely because nobody tells them it's an option.
Emergency tax on a summer job isn't a scam, a glitch, or evidence that anyone's out to catch you out — it's a default setting that assumes the worst until you tell HMRC otherwise. Hand over the paperwork early, check your tax code through the app rather than trusting the payslip blindly, and if the job finishes before April, don't leave a P50 sitting unfiled on the assumption the system will sort it out for you. It usually does, eventually. It just does it on its own schedule, not yours.