July 31 Is a Benefits Compliance Collision for Employers

Why July 31 creates confusion

July 31 feels like a single date on the HR calendar.

For employer health plans, it is usually a cluster of different duties that happen to land on the same day. One duty may sit with the employer. Another may sit with a carrier, TPA, accountant, or benefits administrator. One may require a tax payment. Another may require an electronic annual report. A third may require an extension request before the original due date passes.

That is why employers miss July 31 even when they know July 31 matters.

They ask the wrong question.

The question is not, do we have a July 31 deadline?

The question is, which July 31 deadline applies to which plan, and which vendor has the data needed to finish it?

The first lane is PCORI

The IRS says Patient Centered Outcomes Research Trust Fund fees are due July 31 from issuers of specified health insurance policies and plan sponsors of applicable self insured health plans. The fee is reported and paid annually on Form 720.

The ownership point matters.

For a fully insured medical policy, the issuer is generally responsible for the PCORI fee. For an applicable self insured health plan, the plan sponsor is responsible. Employers that moved from fully insured to level funded, self funded, or an HRA based arrangement should not assume the carrier handled it.

The IRS filing date table shows a July 31, 2026 filing date for policy or plan years ending from January 2025 through September 2025 at $3.47 per covered life. IRS Form 720 instructions also show the rate increasing to $3.84 per covered life for policy and plan years ending on or after October 1, 2025 and before October 1, 2026.

That means a December 31, 2025 plan year generally uses $3.84, not $3.47.

For a plan with 180 average covered lives, the difference is simple:

• At $3.47, the fee is $624.60.
• At $3.84, the fee is $691.20.
• The dollars are not huge, but the missed filing is still a tax compliance problem.

Small penalties are not the real issue. The real issue is that the employer may discover, too late, that nobody owned the Form 720 workflow.

The second lane is Form 5500

Form 5500 is a different job.

EFAST2 says plan sponsors must generally file Form 5500 or Form 5500 SF by the last day of the seventh month after the plan year ends. For a calendar year plan, that date is July 31.

This is not a PCORI payment. It is an annual report for an employee benefit plan.

Many employers think of Form 5500 as a retirement plan filing. That is incomplete. ERISA health and welfare plans can also have Form 5500 duties, especially when participant counts, funding, trust assets, or plan structure put the plan outside an exemption.

For a mid size employer, the question is often not whether medical insurance exists. The better question is whether the employer has one wrap welfare plan, separate dental, vision, life, disability, medical, and FSA plans, or a mix of insured and unfunded benefits with different filing treatment.

That distinction changes the workload.

One wrap plan may mean one Form 5500.

Separate plans may mean several filings.

No one should be discovering that in the last week of July.

The third lane is the extension decision

July 31 also matters because it is the point where a calendar year Form 5500 filer needs to decide whether an extension is required.

EFAST2 guidance states that required forms, schedules, statements, and attachments must be filed by the last day of the seventh calendar month after the end of the plan year. A filer that needs more time generally uses Form 5558 before the original deadline to request more time.

An extension is not a failure. It is often the cleaner move when the employer is waiting on carrier data, trust information, Schedule A details, audit work, or a vendor correction.

The failure is letting the original deadline pass without filing or extending because everyone assumed someone else had it covered.

Employers should treat July 31 as a decision deadline, not just a filing deadline.

File now, extend now, or document why the plan is exempt.

A practical triage map

Start with a one page plan inventory.

List every benefit that touched the 2025 plan year:

• Medical
• Prescription drug
• Dental
• Vision
• Health FSA
• HRA
• EAP
• Life insurance
• Disability
• Stop loss
• Wellness or disease management program

Then put each benefit into one of four columns.

Column one: insured and carrier handled. This may include fully insured medical, dental, vision, life, or disability where the carrier handles its own tax or reporting piece.

Column two: employer action required. This may include self insured medical, level funded medical, certain HRAs, health FSAs, and welfare plans that need Form 5500 filing.

Column three: vendor data required. This is where many delays happen. Covered life counts, Schedule A data, commissions, policy numbers, plan numbers, and participant counts often live outside HR.

Column four: exemption or no action. This column needs evidence, not vibes. If a plan is exempt from Form 5500, write down why.

The exercise usually takes less than one hour. It can prevent days of deadline panic.

Where employers misread PCORI

PCORI confusion often starts with funding labels.

Level funded plans are commonly sold as a clean middle ground between fully insured and self funded. Operationally, they can still include an employer sponsored self insured component for PCORI purposes. The employer should ask the administrator, in writing, who files Form 720 and who pays the fee.

HRAs create another trap. An employer that offers an HRA alongside a fully insured medical policy may still have a self insured health plan for PCORI purposes. Depending on plan design and integration, there may be counting rules that reduce duplicate counting, but the employer should not assume the HRA disappears.

Health FSAs can also matter. Some are excepted benefits and may be excluded. Others may not be. The right answer depends on plan terms and contribution design.

This is why the first PCORI question should be factual:

Which arrangements were self insured health plans during the plan year?

Only after that should the employer calculate lives and dollars.

Where employers misread Form 5500

Form 5500 confusion usually starts with participant counts and plan documents.

An employer may know it has 130 employees but not know how many participants are counted at the beginning of the plan year for a specific welfare plan. Dependents are not counted the same way employees are counted. COBRA qualified beneficiaries can matter. Retirees can matter. Different plans may have different counts.

Plan documents create the next problem.

If the employer has a wrap welfare plan, the filing analysis may be cleaner. If each benefit is its own ERISA plan, the employer may have more than one filing question. The insurance spreadsheet is not the plan document.

The employer should pull three things before making the filing call:

• The plan document or wrap document
• The participant count at the start of the plan year
• Carrier or vendor Schedule A data when applicable

If those three items are missing on July 28, the extension conversation should start immediately.

A four day deadline week checklist

With July 31 three days away, do not start with a twenty item compliance project.

Start with a triage sprint.

Day one: identify plan inventory and owner. HR, finance, the broker, the TPA, and the accountant should agree who owns PCORI, Form 5500, and any extension.

Day two: confirm PCORI status. Identify self insured health arrangements, plan year end dates, average covered lives, applicable rate, Form 720 ownership, and payment workflow.

Day three: confirm Form 5500 status. Identify which welfare plans need filing, which are exempt, whether Schedule A data is available, and whether the signer has EFAST2 credentials.

Day four: file, pay, extend, or document exemption. A clean extension is better than a rushed filing with missing data.

This is not legal advice. It is an operating sequence for employers that need to turn a vague deadline into assigned work.

What to ask vendors before July 31

The email should be blunt.

Ask the medical administrator:

• Are we responsible for filing Form 720 for PCORI for the 2025 plan year?
• If yes, what average covered life count should we use?
• Which counting method did you use or support?
• Which rate applies to our plan year end?

Ask the broker or benefits administrator:

• Which health and welfare plans need Form 5500 filing?
• Do we have a wrap plan document?
• Do we have Schedule A information from each carrier?
• Do we need Form 5558 before July 31?

Ask payroll or finance:

• Who can submit payment through EFTPS if PCORI is owed?
• Who signs the filing or extension?
• Where will proof of filing and payment be stored?

Do not rely on a phone answer for any of this. Get it in writing.

The renewal connection

July 31 compliance work is not just about avoiding a missed form.

It also reveals whether the employer has control of its benefits data.

The same employer that cannot quickly identify covered lives for PCORI may struggle to produce a clean census for renewal. The same employer that cannot find a wrap document may struggle to explain plan structure during a carrier review. The same employer that waits on Schedule A data in late July may face the same vendor lag during open enrollment.

That is why Benefitra treats compliance dates as data quality tests.

If the July 31 sprint exposes missing plan documents, unclear vendor ownership, or late data, fix the process before renewal season. Waiting until the carrier quote arrives turns a paperwork gap into a pricing problem.

For related planning, see Benefitra's guides to Form 5500 filing for employer health and welfare plans, PCORI fee filing for construction employers, and employee benefits census data.

The clean answer for July 31

A strong July 31 file has four pieces.

First, it states whether PCORI applies and shows the covered life count, rate, Form 720 filing, and payment proof.

Second, it states whether Form 5500 applies and shows the filing, extension, or exemption basis.

Third, it identifies who signed, who filed, and where the confirmation lives.

Fourth, it captures the vendor gaps to fix before renewal.

That is the real value of the deadline. It forces the employer to prove whether the benefits operation has ownership, records, and a repeatable calendar.

July 31 is not just a date. It is a control test.

Source notes

The operating deadlines and rates in this article come from the IRS PCORI fee Q&A, IRS PCORI filing due dates and rates, IRS Form 720 instructions, and EFAST2 Form 5500 guidance.

Frequently Asked Questions

Is the PCORI fee due July 31, 2026?

For many plans, yes. The IRS says Form 720 for the PCORI fee is due July 31 of the calendar year following the last day of the policy year or plan year. The applicable rate depends on the policy or plan year ending date.

Who pays the PCORI fee for an employer health plan?

Issuers are responsible for specified health insurance policies. Plan sponsors are responsible for applicable self insured health plans. Employers should confirm ownership for level funded plans, HRAs, and other arrangements that may include a self insured component.

Is Form 5500 also due July 31?

For calendar year plans that must file, generally yes. EFAST2 says Form 5500 series returns are generally due by the last day of the seventh month after the plan year ends, which is July 31 for a calendar year plan.

Can an employer extend Form 5500?

Usually, yes. A plan can generally request extra time by filing Form 5558 before the original Form 5500 due date. Employers should confirm the filing process with their benefits administrator or tax adviser before the deadline.

Does every small employer health plan file Form 5500?

No. Some small welfare plans are exempt, especially when they meet participant count and funding conditions. The employer should document the exemption basis instead of simply assuming no filing is required.