IRS Notice CP 220J

You should start by confirming that IRS Notice CP220J is what it appears to be. an Employer Shared Responsibility Payment assessment under Internal Revenue Code section 4980H. CP220J is the bill the IRS sends after it finishes the Employer Shared Responsibility Payment process for an applicable large employer under the Affordable Care Act. Before CP220J arrives, the IRS sends Letter 226J, which is the initial proposal of the payment, and then a Letter 227 series response after the employer replies. CP220J is the assessment that closes that loop and shows the final amount the IRS charged, any payments and credits applied, and the balance due. So the first job is to pull the Letter 226J, the employer response, and the Letter 227 that the IRS sent earlier, because CP220J should reconcile to those documents. Read the notice line by line and confirm the tax year. Employer Shared Responsibility Payment cases run by calendar year, so the notice points to one specific year of Forms 1094-C and 1095-C. Confirm the employer identification number on the notice matches the entity that filed those forms. Large organizations with several related entities sometimes file under more than one EIN, and a payment can land against the wrong member of a controlled group. A misdirected assessment is easier to fix early, while the account is fresh, than after it has aged into collection. Match the dollar figure on CP220J to the proposed amount from the prior correspondence. The Employer Shared Responsibility Payment is built from a per employee monthly amount. The section 4980H(a) amount applies when an applicable large employer did not offer minimum required health coverage to substantially all full time employees and at least one full time employee received a premium tax credit. The section 4980H(b) amount applies when coverage was offered but was not affordable or did not provide minimum value. The two parts are calculated very differently, so confirm which one the IRS used and for which months of the year. Here is a worked example. Greenfield Logistics, an applicable large employer with 300 full time employees, received Letter 226J on March 14, 2025 proposing a section 4980H(a) payment of 264,000 dollars for the 2023 year. The IRS used a figure of 80 full time employees who were allowed a premium tax credit across the year, but the company actually offered coverage to all but 12 of them and had the 1095-C codes to prove it. After the company responded and the IRS issued Letter 227, CP220J arrived on September 2, 2025 showing a revised assessment of 39,600 dollars and a balance due. The company paid that reduced amount. The lesson is that the number on CP220J is only as good as the response the employer filed earlier in the process. A common mistake is treating CP220J as the first contact and panicking. By the time CP220J issues, the response window from Letter 226J has usually closed, so an employer that ignored the earlier letters has fewer options. Another mistake is paying the full balance without checking whether the underlying 1095-C coding was correct, because coding errors are the most frequent cause of an inflated Employer Shared Responsibility Payment. A third mistake is filing the notice away without reading it, then losing track of a payment due date that triggers penalties and interest. An edge case worth flagging. if the employer never received Letter 226J because it went to an old address, the assessment may still be valid on its face, but the employer can contact the IRS and may be able to reopen the matter or pursue abatement. Keep proof of the address the IRS used, because that record can support a request to reconsider. If your firm received CP220J and the number does not match what you expected, do not pay or dispute blindly. Pull the prior correspondence and the source forms first, then decide on a path that fits the facts.

The IRS explains the assessment in its guide at Understanding Your CP220J Notice, and the proposal stage in Understanding Your Letter 226-J. The broader framework sits at Employer Shared Responsibility Provisions. For a full read of your CP220J support options, see IRS audit, refund and notice assistance, or start a review with The Reed Corporation at new client inquiry.

You should not assume IRS Notice CP220J is correct just because it carries an IRS assessment. The Employer Shared Responsibility Payment is generated largely from automated matching of Forms 1094-C and 1095-C against individual tax returns that claimed the premium tax credit. That matching is only as accurate as the codes an employer reported on each 1095-C, and those codes are a frequent source of error. A wrong code on line 14 or line 16 of Form 1095-C can make the IRS believe an offer of coverage was never made when it actually was, which inflates the payment the IRS proposes and then assesses. Walk through how the figure is built so you can test it. For each month, the IRS looks at whether the applicable large employer offered minimum required health coverage, whether that coverage was affordable, whether it provided minimum value, and whether a full time employee received a premium tax credit for buying marketplace coverage. The section 4980H(a) liability is triggered when the employer failed to offer coverage to substantially all full time employees and at least one of them got a premium tax credit. The section 4980H(b) liability is triggered per employee when coverage was offered but fell short on affordability or minimum value. The IRS reduces the section 4980H(a) calculation by a number of allocated full time employees before multiplying by the monthly rate, so a single miscount of full time status can swing the result by tens of thousands of dollars. Here is a worked example. Harbor Point Manufacturing received CP220J for the 2022 year assessing 191,000 dollars under section 4980H(a). The company reviewed its records and found that 47 of the employees the IRS counted as full time were actually seasonal or part time under the look back measurement method, and that two employees flagged for a premium tax credit had in fact declined the company plan in writing. After Harbor Point gathered the measurement period spreadsheets and the signed waivers and sent them with a clear cover letter, the IRS adjusted the account and the corrected assessment fell to zero for those months. The lesson is that the IRS started from its own counts, not from the company truth, and the company had to supply the difference. A common mistake is assuming the IRS already saw the affordability safe harbor the employer used. The IRS only knows what the 1095-C codes told it. If the employer used the federal poverty line safe harbor, the rate of pay safe harbor, or the W-2 wages safe harbor but coded it wrong or left the code blank, the assessment will not reflect it, and the employer has to point to the safe harbor with records. Another common mistake is reading a section 4980H(a) assessment as if it were a section 4980H(b) assessment, because the (a) amount is far larger and is not capped the same way. An edge case. an employee who enrolled in marketplace coverage and got a premium tax credit even though the employer offer was affordable and adequate can still trigger an IRS inquiry, because the marketplace and the IRS do not always have a record that the offer existed. The employer record, not the employee choice, controls whether the payment is owed, so the documentation the employer keeps is what settles it. Another edge case is a controlled group. members of an aggregated applicable large employer group are tested together for status but assessed separately, so an assessment can be right about the group and wrong about which member owes it. The verified takeaway is that CP220J reflects IRS records and IRS assumptions, not a final truth. Check the 1094-C and 1095-C coding and the full time counts against your own measurement records before you accept the number, and respond with the specific months and employees in dispute.

The rules behind the calculation are set out by the IRS at Employer Shared Responsibility Provisions and in the Questions and Answers on the Employer Shared Responsibility Provisions. The assessment guide is Understanding Your CP220J Notice. Payroll and 1095-C level review is part of payroll compliance and ongoing tax compliance.

How fast you need to respond to IRS Notice CP220J depends on whether you agree with the assessment and whether a balance is due. CP220J itself is the assessment, so unlike the earlier Letter 226J, which gives a fixed response window of about 30 days from the date of the letter, CP220J presents a balance and a due date for payment. If you agree, the practical deadline is the payment due date on the notice, because interest and failure to pay penalties accrue on an unpaid Employer Shared Responsibility Payment the way they do on other assessed amounts. The longer the balance sits, the more it grows. If you disagree, time still matters even though the formal proposal stage has passed. Once the IRS assesses the Employer Shared Responsibility Payment and issues CP220J, the cleanest path to dispute it is often to contact the IRS promptly, explain the error, and provide the corrected Forms 1094-C and 1095-C support. Waiting lets the account move into collection, where the IRS can issue further balance due notices and eventually pursue enforced collection through levy or lien. Acting within a few weeks of the notice date keeps the matter in a posture where a phone call and a documented response can still fix it administratively, before it hardens. Here is a worked example with real dates. Cedar Valley Health Group received CP220J dated June 5, 2026 for the 2024 year with a balance due of 88,000 dollars and a payment due date of July 6, 2026. The group believed the figure double counted a month already resolved in its Letter 227 response. It called the number on the notice on June 12, 2026, was told to submit a written explanation, and mailed a packet on June 16, 2026 with the prior Letter 227, the corrected month, and a one page summary. Because it acted inside the first two weeks, the account was placed in a hold status while the IRS reviewed, and no collection notice issued in the interim. Had the group waited until after July 6, the first thing it would have seen next was a balance due notice with added penalty and interest. A common mistake is doing nothing because the dollar figure feels negotiable. The Employer Shared Responsibility Payment is not subject to the same deficiency procedures as income tax, so there is no automatic Tax Court petition right tied to a 90 day letter here. That makes a prompt, well documented administrative response more important, not less, because the usual income tax dispute road is not available in the same form. Another common mistake is paying the balance to stop the clock and planning to sort it out later. Once paid, recovering an overpayment of the Employer Shared Responsibility Payment is harder and slower than correcting an open assessment, so it is usually better to respond first when you have grounds. An edge case. if you need more time to assemble measurement period data, call before the payment due date and ask about your options rather than letting the date pass in silence. A documented contact is far better than a missed date, and it shows the IRS you are engaging in good faith. The short version. if you agree, pay by the due date on the notice. If you disagree, contact the IRS within the first couple of weeks and back it with the source forms.

The IRS describes the response sequence in Understanding Your Letter 227 and the assessment itself at Understanding Your CP220J Notice. The underlying provisions are at Employer Shared Responsibility Provisions. We help corporate filers meet these dates through corporate returns and IRS audit, refund and notice assistance.

The records needed for IRS Notice CP220J are specific to the Employer Shared Responsibility Payment, so do not send a generic stack of tax documents. The core records are the Forms 1094-C and 1095-C that the applicable large employer filed for the year named on the notice, because those forms drove the assessment. Pull the as filed copies, not a fresh draft, so you can see exactly what codes the IRS received and matched against employee returns. Start with the prior correspondence. Gather Letter 226J, the employer response you sent, and the Letter 227 the IRS issued in reply. CP220J should reconcile to the last of those, and any gap between the Letter 227 figure and the CP220J figure is the first thing to investigate. Keep the envelopes or mailing proof if the dates matter, because the timeline can itself be part of your record. Next, assemble the records that prove your offer of coverage and your full time counts. That means the plan documents and enrollment records showing who was offered minimum required health coverage each month, the affordability safe harbor support if you used the W-2 wages method, the rate of pay method, or the federal poverty line method, and the measurement period spreadsheets that show which employees were full time under the look back measurement method. If an employee the IRS flagged actually declined coverage, find the signed waiver or the enrollment system record of the declination. These are the documents that move a number. Here is a worked example. Northwind Retail received CP220J for 2023 assessing a section 4980H(b) amount of 42,500 dollars. The IRS flagged 17 employees as receiving a premium tax credit while the company offered unaffordable coverage. Northwind pulled its payroll records and showed that for 11 of those employees it had correctly applied the rate of pay affordability safe harbor, with the monthly employee cost below the threshold percentage of monthly wages. It sent the payroll detail, the plan rate sheet, and a per employee schedule that tied each name to a month and a dollar figure. The IRS removed those 11 from the calculation and the assessment dropped to 9,750 dollars. A common mistake is sending the entire payroll system export and asking the IRS to find the answer. That slows the review and can create confusion. The cleaner method is to identify the exact employees and months in dispute, then send only the records that prove your position for those employees and months, with a short index that the reviewer can follow without guessing. Another common mistake is sending originals. Keep originals and send labeled copies with proof of mailing or upload, so nothing irreplaceable leaves your hands. An edge case. if your 1095-C codes were genuinely wrong, you may need to consider corrected forms in addition to the response, because the IRS account and the filed information should match. Coordinate the correction and the CP220J response so they tell one story rather than two conflicting ones. One more practical note on format. number the pages, write a short cover letter that names the year, the notice number, and the exact months in dispute, and put the per employee schedule on top so the reviewer sees your math before the backup. A reviewer who can follow the logic in two minutes is far more likely to make the adjustment than one who has to reconstruct it from a pile. A further record worth keeping is the proof of how the IRS reached you. If the address on CP220J is outdated, save the envelope and note the date you actually received it, because a late delivery can matter to your options. The principle is that better paper beats more paper. Name the issue, prove that issue, and stop.

Form coding and filing details sit in the IRS Employer Shared Responsibility Questions and Answers, with assessment context at Understanding Your Letter 226-J and Understanding Your CP220J Notice. Ongoing filing accuracy is part of tax compliance and payroll compliance.

The Reed Corporation can help with IRS Notice CP220J by treating it as an Employer Shared Responsibility Payment matter rather than a generic balance due notice, because the path to resolving it runs through the Affordable Care Act rules under section 4980H, not through ordinary income tax procedure. We start by reading CP220J against the earlier Letter 226J, your response, and the Letter 227 the IRS issued, so we can see whether the assessed figure matches where the case left off. A surprising number of these notices contain a figure that does not reconcile to the last IRS letter, and that gap is where relief usually lives. From there we review the Forms 1094-C and 1095-C that produced the assessment. Most Employer Shared Responsibility Payment problems are coding problems. a line 14 offer code that understated the coverage offered, a line 16 safe harbor code that was left blank, or a full time count that swept in seasonal and part time workers who should not have counted. We compare those codes to your enrollment records, your plan documents, and your look back measurement method spreadsheets to find where the IRS figure overstates the liability, then we document each correction. We also separate the section 4980H(a) exposure from the section 4980H(b) exposure, because they are calculated differently and call for different proof. For a section 4980H(a) assessment we focus on whether you offered coverage to substantially all full time employees and on the allocated employee reduction. For a section 4980H(b) assessment we focus on affordability and minimum value for the specific employees who received a premium tax credit. Getting that split right often changes the number more than any single document. Here is a worked example of how that looks in practice. A 220 employee distribution company brought us a CP220J for the 2023 year showing 156,000 dollars due. We pulled the 1095-C file, found that the affordability safe harbor code had been omitted for two thirds of the workforce even though the plan was affordable under the W-2 wages method, prepared a per employee schedule and corrected coding, and sent a documented response. The IRS reduced the assessment to 14,000 dollars, which the company paid. The work was not clever argument. It was matching records to months and showing the IRS what its data missed. A common mistake we help clients avoid is paying the full balance to make the notice go away. If the underlying coding was wrong, paying locks in an error that a documented response could have removed. The opposite mistake is fighting a number that is actually correct, which wastes time and lets penalties build while the account stays open. We also help with the practical close. once the IRS adjusts the assessment, we confirm the account reflects the change and that no stray balance lingers, because a corrected case that never gets posted can resurface as a new notice. We also keep the response proportionate to the dollars at stake. a six figure section 4980H(a) assessment justifies a full measurement period rebuild, while a small section 4980H(b) figure for two employees may only need two affordability schedules. Matching the effort to the exposure keeps the work fast and the cost sensible for the client. And we plan for the next year while we are in the file. the same coding habit that produced the assessment will produce another one unless the 1095-C process is fixed, so we note the fix for the following filing season so the employer is not back here a year later. The point is not to argue with every assessment. It is to find out, with evidence, whether CP220J is right, wrong, or partly right, and then respond precisely.

For the official IRS framing, see Understanding Your CP220J Notice, Employer Shared Responsibility Provisions, and Understanding Your Letter 227. Begin with IRS audit, refund and notice assistance or payroll compliance, or reach us at new client inquiry.