Does my UK tax code affect my US tax return?

Yes, though indirectly. The code decides how much UK tax your employer deducts in each pay period, and for a cash basis filer the foreign tax credit follows UK tax actually paid. IRS Publication 514 confirms that cash method taxpayers claim the credit only in the year the tax is paid and that withheld taxes are treated as imposed on you. A code change therefore moves credit between US calendar years even when your UK liability is unchanged.

Can I just use the tax figure on my P60 for Form 1116?

Only after checking what it contains. A P60 covers a UK tax year to 5 April, so it straddles two US calendar years, and the tax deducted figure can include collections for an earlier UK year, coded-out investment income, or the High Income Child Benefit Charge. Use the P60 as a control total, then build the US year from payslips and the coding notice, translating each period at the rate applying when the deduction was made.

What happens if HMRC collects an old UK underpayment through my current code?

Real cash leaves your pay now for a liability that belongs to an earlier UK year. GOV.UK confirms HMRC will adjust your code to collect the tax over one or more tax years where possible. On the paid basis that tax is creditable in the US year the deductions run, but it must be identified and characterised against the earlier year's income rather than folded into the current year's employment tax on Form 1116.

Should I elect to claim foreign tax credits on the accrued basis?

It removes coding-notice noise from credit timing, because the credit follows the year the UK liability accrues rather than the week payroll ran. But Publication 514 states that once the choice is made you must follow it in all later years, and it applies to all qualifying foreign taxes. Translation also changes, generally to the average rate for the year the taxes relate to. It is a permanent decision, so model it before making it.

Why am I on an emergency tax code after moving to the UK?

Because a new arrival has no P45 to give a UK employer. GOV.UK explains that emergency codes ending W1, M1 or X tax you on what you are paid in that week or month only, as if you were paid that amount every period, and that HMRC can take up to 35 days from the start of the job to issue a proper code. The usual result is heavy early over-withholding, concentrated in your first US calendar year of UK residence.

Should I have my Self Assessment balance collected through my tax code?

Treat it as a US timing decision, not just a cash-flow one. GOV.UK requires the return to be filed by 11:59pm on 30 December for the balance to be coded out, against the normal 31 January payment date. Coding out means the tax is paid through payroll across a later UK tax year, so on the paid basis the credit can land in a US year well after the year in which the income was reported.

PAYE Coding Notices and Your US Tax Return

US UK tax returns preparation PAYE coding notice questions come down to a single point: your HMRC coding notice is an estimate of the UK tax you should pay across the year, not a statement of what you finally owe, and that estimate decides how much creditable UK tax actually lands in each US calendar year. For a US citizen or green card holder earning well in Britain, that distinction is not academic. The foreign tax credit for a cash basis filer follows UK tax paid, so a code that over-withholds or under-withholds shifts credit between US years even when the underlying UK liability has not moved by a penny.

In the returns we prepare, the coding notice is one of the first documents we ask for and one of the last documents anyone thinks to send. Filers hand over a P60 and assume the tax deducted figure is a clean measure of the year. It very often is not. It can contain tax being collected for an earlier UK year, tax on benefits that will later be corrected on a P11D, and the aftershock of an emergency code operated in the first months of a new job. Every one of those distorts Form 1116 if it is carried across unexamined.

What is a PAYE coding notice and what does it actually do?

A PAYE coding notice, issued to the individual as a form P2, is HMRC's explanation of the tax code it has told your employer or pension provider to operate. The code is an instruction, not a bill. GOV.UK puts the mechanism plainly at https://www.gov.uk/tax-codes/what-your-tax-code-means, where it explains that the numbers in your tax code tell your employer or pension provider how much tax-free income you get from them in that tax year. HMRC begins with your Personal Allowance, subtracts untaxed income and deductions such as company benefits, and reduces the result to a code the payroll software can operate week by week or month by month.

The letter carries almost as much information as the number. The same GOV.UK page sets out that L means you are entitled to the standard tax-free Personal Allowance, T means your code includes other calculations to work out your Personal Allowance, 0T means your Personal Allowance has been used up or your employer does not have the details they need, BR taxes all income from that source at the basic rate, D0 at the higher rate and D1 at the additional rate, NT means no tax is deducted on that source, and S and C signal the Scottish and Welsh rates. A high earner with a second employment, a large benefits package or a tapered allowance will frequently see T, 0T, D0 or a K code rather than the plain L that most published guidance assumes.

The critical property for cross-border work is that the code is forward looking and provisional. HMRC builds it from what it believes your year will look like. Nothing in the code guarantees that the tax withheld across the year equals the tax due for that year. Reconciliation happens afterwards, through the employer's year-end return, the P60, the P11D and, for anyone with the sort of income profile we deal with, the Self Assessment calculation.

Why does an HMRC tax code matter so much to a US return?

Because the US foreign tax credit is a timing-sensitive creature. The IRS explains at https://www.irs.gov/individuals/international-taxpayers/foreign-tax-credit that only income, war profits and excess profits taxes qualify, that the tax must be imposed on you, and that individuals claim the credit on Form 1116. Publication 514, at https://www.irs.gov/publications/p514, sets out the four tests a foreign tax must meet, that you must have paid or accrued the tax, that it must be the legal and actual foreign tax liability, and that it must be an income tax or a tax in lieu of an income tax. Publication 514 is equally clear that a taxpayer using the cash method can claim the credit only in the year in which the tax is paid.

That last sentence is where the coding notice acquires teeth. PAYE deductions are payments of UK tax, and Publication 514 confirms that taxes withheld are considered to be imposed on you. So for a cash basis filer, the amount of UK tax that reaches Form 1116 for a given US calendar year is, in substance, whatever the code caused the payroll to deduct in that window. Change the code and you change the year in which the credit arises. The UK liability for the UK year may be identical either way. The US result is not.

The knock-on effects are real money. Too little UK tax paid in a US year can leave residual US tax due on income that is fully taxed in Britain across the pair of years. Too much can create excess credits that sit unused unless they can be carried back or carried over, which Publication 514 permits where qualified foreign taxes exceed the credit limit, but only within the general limitation basket and the periods the statute allows. Either way, a filer whose code has swung is paying for a distortion created by an administrative estimate.

Which coding adjustments distort a high earner's position most?

GOV.UK lists the triggers for a code change at https://www.gov.uk/tax-codes/why-tax-code-change, including starting a new job, an additional job or pension, savings interest above the Personal Savings Allowance, an employer telling HMRC that benefits have started or stopped, claiming expenses that attract tax relief, paying the High Income Child Benefit Charge through wages or pension, and having been on the wrong tax code and owing tax. In practice a handful of these do nearly all the damage to a cross-border return.

Tapering or removal of the Personal Allowance. GOV.UK states at https://www.gov.uk/income-tax-rates/income-over-100000 that the personal allowance goes down by 1 pound for every 2 pounds that adjusted net income is above 100,000 pounds, reaching nil at 125,140 pounds or above, on a page describing the tax year 6 April 2026 to 5 April 2027. Because HMRC has to estimate adjusted net income in advance, a variable-bonus earner is routinely coded on a projection that the year then disproves in either direction.
Benefits in kind coded through the year against a later P11D. HMRC reduces the code by the estimated taxable value so tax is collected as you go, then the P11D reports the actual value after the year ends. The estimate and the outturn rarely match, and the difference is squared up later, in a different US calendar year.
An adjustment collecting an underpayment from an earlier UK year. GOV.UK confirms at https://www.gov.uk/tax-codes/if-youve-paid-too-much-or-too-little-tax that HMRC will estimate how much tax you owe when your tax code is updated and adjust your tax code to collect the tax over one or more tax years if possible. This is the single most misread item on a coding notice.
A restriction collecting the High Income Child Benefit Charge. GOV.UK notes at https://www.gov.uk/child-benefit-tax-charge that the charge can be paid through PAYE rather than through Self Assessment. The amount collected is not tax on your employment income at all, yet it appears inside the PAYE deduction on your payslip.
Untaxed investment income coded out. Dividends, interest and property income can be collected through the code rather than paid with the Self Assessment balance. That moves cash forward and, on a cash basis US return, moves the credit with it.
K codes. GOV.UK explains at https://www.gov.uk/tax-codes/k-in-your-tax-code that a K code means you have income or deductions higher than your tax-free Personal Allowance that are not already being taxed, and that employers and pension providers cannot take more than half of your pre-tax wages or pension when using a K code.

That 50 percent limit is a quietly important cross-border detail that almost nobody writes about. It is a regulatory cap on collection speed, not a reduction in what is owed. Where a large restriction cannot be collected within the year because of the cap, the balance spills into a later code or a later payment. In foreign tax credit terms, the cap is a deferral mechanism: it pushes creditable UK tax out of one US year and into the next, purely because of a payroll protection rule.

How should a prior year UK underpayment collected through your code be treated?

Carefully, and separately. This is the failure mode we see most often. A code carrying an adjustment to collect an earlier year's underpayment causes real cash to leave your pay in the current year. The payslip and the P60 will show it inside the total tax deducted. The instinct is to take the P60 figure, convert it and put it on Form 1116 as the year's UK tax. That instinct produces a return that overstates current-year credit and understates the credit attributable to the year the liability actually belongs to.

There are two things to keep apart. The first is when the tax was paid, which for a cash basis filer determines the US year in which the credit is available. The second is which UK year and which income the tax relates to, which determines the income category and the source basket on Form 1116, and which matters enormously if you have made the accrual election. Cash timing and liability attribution are different questions and a coding notice is the only document that lets you answer the second one, because it names the adjustment and the year it relates to.

The other trap runs the other way. Where a Self Assessment balance is instead coded out into a future year, the cash does not leave in the year the return is filed. GOV.UK sets the mechanics at https://www.gov.uk/self-assessment-tax-returns/deadlines, which states that to have tax collected through your PAYE code you must submit the return by 11:59pm on 30 December, while the ordinary online filing and payment deadline is 31 January. Elect to code out, and a UK liability for one UK tax year can be paid through payroll deductions spread across a later UK tax year, which for a calendar-year US filer can push the creditable payment into a US year two removed from the income. That election is presented in Britain as a cash-flow convenience. For a US filer it is a foreign tax credit timing decision and should be made as one.

What do emergency and week 1 month 1 codes do in your first UK year?

They distort exactly the year you can least afford a distortion. GOV.UK explains at https://www.gov.uk/tax-codes/emergency-tax-codes that you are on an emergency code if your code ends in W1 when you are paid weekly, M1 when you are paid monthly, or X when your pay dates vary, and that in that case your tax is worked out based on what you are paid in that week or month only, taxed as if you are paid that amount every week or month of the year. The same page says HMRC will usually update the code once it has details from your new and previous employers, that this can take up to 35 days from when you start the job, and that giving your new employer a P45 helps take you off the emergency code.

For someone who has just moved to the UK there is no P45 to give, so an emergency or 0T code is close to inevitable at the outset. Two things then happen at once. Withholding for the opening months is calculated on a non-cumulative basis that ignores allowances already used or not used, and any sign-on payment or first bonus is taxed as though it repeated every period. The result is usually significant over-withholding early, followed by a correction once a cumulative code is issued. That whole sequence lands inside the first US calendar year of UK residence, which is the same year the filer is navigating a first return as a UK resident, often with a part-year picture, and frequently while deciding between the foreign earned income exclusion and the foreign tax credit. Publication 54, at https://www.irs.gov/publications/p54, is explicit that you cannot deduct, exclude or take a credit for any item related to amounts you exclude as foreign earned income or foreign housing amounts, so an inflated first-year withholding figure interacts directly with that choice.

Which documents actually drive the US return: the P60, the P11D or the coding notice?

The reconciliation documents drive the return. The coding notice is evidence of intent and a reconciliation key, not a source of final figures. GOV.UK sets out at https://www.gov.uk/paye-forms-p45-p60-p11d that an employer gives you a P45 if you stop working for them, a P60 if you are working for them at the end of the tax year, and a P11D if you get company benefits. Those are the outturn documents. The coding notice tells you why the outturn looks the way it does.

P60. The authoritative record of pay and UK tax deducted through PAYE for the UK tax year to 5 April. It is the closest UK analogue to a Form W-2 for withholding purposes, but it is a UK-year document and it does not tell you which year the tax related to.
P11D. The actual taxable value of benefits after the year ends. GOV.UK gives the deadlines at https://www.gov.uk/employer-reporting-expenses-benefits/deadlines and requires employers to report expenses and benefits by 6 July after the tax year ends, give employees a copy by 6 July, and pay Class 1A National Insurance by 22 July, or 19 July if paying by cheque.
Payroll records where benefits are payrolled. GOV.UK explains at https://www.gov.uk/guidance/payrolling-tax-employees-benefits-and-expenses-through-your-payroll that where benefits are payrolled the taxable amount is added to pay, the tax codes of employees receiving those benefits are amended to take out the benefit adjustment, and no P11D is needed for payrolled benefits, although a P11D(b) is still required for Class 1A. If your employer payrolls, the benefit adjustment disappears from your code and the noise moves into gross pay instead.
The Self Assessment calculation. For a high earner this is the document that states the final UK liability for the UK year, after the code, after the P11D, and after everything else. It is the anchor for attributing tax to the correct UK year.
The coding notice itself. Kept for its narrative value: it names each adjustment, identifies prior-year collections, and lets you separate what was paid in a period from what it was paid for.

Does the accrued basis election solve the problem?

It can, and it is a one-way door. Publication 514 states that even if you use the cash method of accounting you can choose to take a credit for foreign taxes in the year they accrue, by checking the accrued box on Form 1116, and that once you make that choice you must follow it in all later years, with the choice applying to all foreign taxes qualifying for the credit. Made deliberately, the election takes the coding notice out of the equation for credit timing, because the credit follows the year to which the UK liability relates rather than the week the payroll ran.

There is a price. The election is binding for every subsequent year and for every foreign tax, not just UK PAYE. It also changes the translation rule. Publication 514 provides that for taxes paid you use the rate of exchange in effect on the date you paid the foreign taxes, while accrued taxes generally use the average exchange rate for the tax year to which the taxes relate. The Form 1116 instructions at https://www.irs.gov/instructions/i1116 say the same for the paid basis, directing you to the rate of exchange in effect on the day you paid the foreign taxes or on the day the tax was withheld, and requiring amounts to be reported in US dollars. The IRS also confirms at https://www.irs.gov/individuals/international-taxpayers/foreign-currency-and-currency-exchange-rates that you use the exchange rate prevailing when you receive, pay or accrue the item, and that where more than one rate exists you use the one that most properly reflects income. There is no single official IRS rate you can simply cite.

The practical consequence of the paid basis for a PAYE filer is unglamorous and important: the correct translation is done period by period, at the rate applying when each deduction was made, not once a year on a single P60 total. Where a code changed mid-year, or a bonus month carried a very large deduction, doing it as one annual conversion produces a different and less defensible number.

How do you handle the 5 April to 31 December mismatch?

By apportioning rather than by adopting a UK year wholesale. Publication 54 confirms that worldwide income is generally subject to US income tax regardless of where you live, and the US return is prepared for the calendar year. A UK tax year running 6 April to 5 April straddles two US calendar years, so a single P60 covers roughly nine months of one US year and three months of the next. Preparing a return by taking one P60 and calling it the year is a shortcut that survives only until the year in which the code changes materially, or a large bonus falls in a particular month, or an underpayment adjustment starts running.

The workable method is to build the US year from monthly payroll data rather than from annual summaries. Take each pay period that falls in the US calendar year, take the UK tax deducted in that period, identify from the coding notice how much of that deduction is attributable to the current UK year rather than to a prior-year collection or a non-employment item, and translate at the rate applicable to that period. Where the code changed part-way through, the coding notices for both codes are what let you split the year credibly. This is also why the coding notice should be filed alongside the payslips, not thrown away when the next one arrives.

Worked illustration: how a coding change moves credit between US years

The following is an illustration only, using round numbers to show the mechanism. It is not a computation for any real filer, and it assumes an exchange rate of 1.25 US dollars to the pound throughout purely as an assumption for arithmetic clarity. Actual returns require period-by-period rates as described above.

Assume a US citizen employed in London on a stable salary, with UK PAYE deductions of 8,000 pounds per month under a cumulative code. In September, HMRC issues a new coding notice carrying an adjustment to collect an underpayment from an earlier UK year, raising deductions to 10,000 pounds per month from October. Nothing about the current year's UK liability has changed. The extra 2,000 pounds a month is collecting an old debt.

For the US calendar year, the first nine months deduct 72,000 pounds and the final three deduct 30,000 pounds, so the payslip total for the calendar year is 102,000 pounds, which at the assumed rate is 127,500 US dollars. Lift that straight onto Form 1116 on the paid basis and you have claimed credit for 6,000 pounds, or 7,500 US dollars at the assumption, that relates to an entirely different UK year and a different tranche of income. The current year's own UK tax was 96,000 pounds. The 6,000 pounds is creditable, and it is creditable in this US year on the paid basis, but it must be identified and characterised as tax on the earlier year's income rather than silently folded into the current year's employment figure. If the filer has instead elected the accrued basis, that 6,000 pounds does not belong in this year's Form 1116 at all: it belongs to the year in which the liability accrued, and claiming it here is simply wrong.

Turn the illustration around and the same mechanism creates the opposite exposure. A filer who elects on Self Assessment to have a balancing payment coded out has not paid that tax by 31 January. It will be collected through payroll across a later UK tax year, and on the paid basis the credit arrives in the US year or years in which those deductions actually run. If US tax on the same income was assessed in the earlier year, the credit and the tax it was meant to relieve are now sitting in different returns.

What should you collect and reconcile before preparing the US return?

The reconciliation is not difficult, it is simply almost never done. Before a Form 1116 is prepared for anyone paid through PAYE, we want the documents below and a reconciliation that ties them together. The test is simple: can you explain every pound of UK tax deducted in the US calendar year, say which UK year and which income it relates to, and state the rate at which it was translated?

Every coding notice issued for the period, including in-year replacements, not just the one issued before the start of the tax year.
All twelve payslips covering the US calendar year, including any additional bonus or equity vesting payslips, showing tax and the code operated in each period.
The P60 for each UK tax year touching the US calendar year, so both ends of the straddle are covered.
The P11D, or confirmation that benefits were payrolled instead, together with the underlying benefit values.
The Self Assessment calculation and the record of any balancing payment, payment on account, or election to code the balance out.
A schedule reconciling the sum of the payslip deductions to the P60 total for each UK year, with any difference explained.
A schedule splitting the deductions for the US calendar year between current-year employment tax, prior-year collections, coded-out investment income, and any High Income Child Benefit Charge collected through the code.
The exchange rate applied to each period, with the source recorded, since the IRS publishes no official rate for this purpose.

One caveat worth stating for completeness: not every filer needs Form 1116 at all. The Form 1116 instructions describe an exemption where total creditable foreign taxes are not more than 300 US dollars, or 600 US dollars on a joint return, and all the income is passive category income reported on qualified payee statements. A high earner on UK PAYE will not be within a mile of that, so the analysis above applies in full.

How we handle coding notices in cross-border return preparation

We treat the coding notice as a working paper rather than as correspondence. It is read for what it says about HMRC's estimate, for the adjustments it names, and above all for the year each adjustment relates to. It is then reconciled against payslips and the P60, and the resulting split of UK tax between US calendar years is documented so that the position is defensible if it is ever examined and so that the same basis is applied consistently in later years. Where the accrual election has been made, or is being considered, the analysis has to be built on liability years rather than payment dates from the outset, because the election cannot be unwound.

None of this is exotic. It is the ordinary discipline of preparing a US return for someone whose foreign tax is withheld by a system that was never designed to align with a calendar year. The reason it goes wrong so often is that the two halves of the problem sit in different professions: UK payroll people understand coding notices and do not prepare Forms 1116, and US preparers understand Form 1116 and are handed a single P60 number. The coding notice is the document that joins them, and it should be in the file every year.