Advanced guide / EOI and approved coverage

When the census is the one that's wrong: EOI, guarantee issue, and approved coverage

For anyone reconciling supplemental life, spouse life, or voluntary disability.

The setup

At open enrollment, an employee elects $300,000 of supplemental life effective January 1. The plan's guarantee-issue limit is $150,000. Coverage above that requires Evidence of Insurability (EOI), a health questionnaire the carrier underwrites before the higher amount takes effect.

The employee submits EOI in December. The carrier approves it March 15. Under this policy, approved increases take effect on the first of the month following approval: April 1.

The synthetic rate is $0.20 per $1,000 of volume per month. Here's what each system shows:

MonthCensus volumeCensus × rateCarrier billedCorrect
January$300,000$60.00$30.00$30.00
February$300,000$60.00$30.00$30.00
March$300,000$60.00$30.00$30.00
April$300,000$60.00$60.00$60.00

A census-vs-bill reconciliation flags January through March as $30.00 a month under-billed, $90.00 in total. All three flags are wrong. The carrier billed exactly the coverage that was in force. The census shows the election, which is not the same thing as the coverage.

For coverage subject to EOI, the ben-admin system knows what the employee asked for. Only the carrier knows what the employee has. A reconciliation that treats the census as the truth for every field will generate false findings here every open enrollment.

The failure modes that actually cost money

The false flag above wastes time. The real errors run the other way, and EOI has more of them than any other part of the bill:

What happensResult
Carrier bills the elected amount while EOI is pendingPremium on $150,000 of coverage that isn't in force: $30.00/month overbilled. Payroll is usually deducting for it too.
EOI is denied, but the elected amount stays on the carrier's record or in payrollPremium collected for coverage that will never exist. If there's a claim, it pays $150,000 and there's a refund conversation with the beneficiary.
EOI is approved, but the carrier's billing never picks up the increaseUnder-billed by $30.00/month. Worse: the carrier's enrollment record may also show $150,000, and that's where a claim conversation starts.
Increase applied from the wrong dateApproval date vs. first-of-following vs. election date: a partial month or several full months at the wrong volume.
EOI never submittedMany policies void the excess election after a set number of days without EOI. The ben-admin system often keeps showing it, and keeps deducting for it.

The second and fifth rows tend to surface at the worst possible time, when a claim is filed. Until then, everything looks normal: the employee sees a deduction, the bill has a line, and nobody compares the two to the EOI decision.

Payroll is the third party to this

Supplemental life is usually employee-paid. If payroll deducts on the elected $300,000 from January while the carrier bills $150,000, the employee overpays $30.00 a month for three months. The carrier bill is correct, the reconciliation against the bill passes, and the employee is still owed $90.00. It's only visible when deductions, approved coverage, and billed premium are compared together.

Which system owns which field

The underlying skill isn't arithmetic. It's knowing, field by field, which system is authoritative:

FieldSystem of record
Elected amountBen-admin
EOI status (pending, approved, denied, not submitted)Carrier
Approved amountCarrier
Effective date of an approved increasePolicy terms, applied by the carrier
Guarantee-issue limitPolicy / rate exhibit
Salary, when volume is salary-basedHR / payroll, as of the policy's salary-definition date
Employee deductionPayroll

A reconciliation that knows this table checks the bill against approved volume, checks payroll against approved volume, and checks the ben-admin election against EOI status. Three comparisons, and each one catches a different failure.

The same pattern, elsewhere

What to do with this

How a TareSum audit handles it: volume-rated lines are recomputed against the approved amount when EOI data is available, so elections that aren't in force don't generate false findings. Pending, denied, and missing-EOI cases are reported separately, because they're problems with what's in force, not just with the price. Book the 20-minute call →
← The credit you passed through Next: One stale salary, three wrong numbers →

How much of your supplemental life is elected but not in force?

Send us the bills, the census, and whatever EOI status you have. We'll separate real findings from election noise.

Book the 20-minute call

Four steps, and the first is a 20-minute call. No files, no member data. Or write to letslook@taresum.com.