Advanced guide / Timing exceptions

Not wrong yet: timing exceptions vs. real discrepancies

For analysts who've had a dispute bounced with "that's already in process."

The setup

An employee drops spousal coverage effective July 1. The change is keyed in the ben-admin system on June 27, which is on time by any reasonable standard. The EDI file goes out that night.

The carrier generated its July bill on June 24. That bill shows the employee at EE+SP:

July billShould bill (EE)Carrier billed (EE+SP)Variance
July$320.09$687.59$367.50

A line-by-line reconciliation flags it immediately. Census says EE, bill says EE+SP, the rate difference is $367.50. Every number on that line is correct, and calling it an error today is still wrong.

Why it isn't an error yet

The change reached the carrier three days after the July bill was produced. No carrier process could have put it on that bill. Carrier billing systems handle this the same way: next cycle, bill the current month at the new tier and generate a retroactive adjustment for the month that printed before the change arrived.

So the July line is a timing exception: a known, expected variance with a specific bill where it should resolve. It turns into a discrepancy only if that bill doesn't resolve it.

A timing exception is a prediction, not a finding: "August should show EE at $320.09 and a July credit of −$367.50." The finding comes when August arrives and the prediction is checked.

Why disputing too early backfires

Send the July variance to the carrier and the answer is predictable: the change was received after the cycle cutoff and will adjust on the next bill. The carrier is right. Now your team has spent a dispute and some credibility on something that was never wrong.

Do that a few times and two things happen. The carrier's service team learns that your disputes are often premature. Your own analysts learn that a variance on a recent change usually sorts itself out. Both lessons are mostly true, which is what makes them dangerous. They are exactly how the cases that don't sort themselves out get through.

August: four possible outcomes

When the August bill arrives, the timing exception resolves one of four ways:

OutcomeAugust current monthJuly credit on AugustStill owed to youStatus
A — CleanEE, $320.09−$367.50$0.00Closed
B — Credit missingEE, $320.09none$367.50Discrepancy
C — Partial creditEE, $320.09−$183.75$183.75Discrepancy
D — Never appliedEE+SP, $687.59none$735.00Discrepancy, aged from July

Outcome D is the easy one to catch: the current month is still wrong, and any check of the August bill finds it. Outcome C, here exactly half the credit, usually means the carrier applied the change from the wrong date or prorated a change that should have been a full month.

Outcome B is the one to worry about. The August bill is correct: right member, right tier, right rate. Every check of the current bill passes. The only evidence of the problem is something that isn't on the bill, a July credit that never arrived. A reconciliation that only checks the current month against the census can't see it, and one that already wrote July off as "probably timing" has stopped looking.

The three inputs that tell them apart

Classifying a variance correctly takes three pieces of information that rarely sit in the same place:

Change keyedThis billClassificationAction
Before cutoffWrongDiscrepancyDispute now
After cutoffWrongTiming exceptionPredict the resolution; check next bill
After cutoffNext bill fully resolvedClosedNone
After cutoffNext bill partly or not resolvedDiscrepancyDispute the remaining amount, aged from the first affected month

The retro clock doesn't wait for the classification

A timing exception still uses up retro window. Carrier retro caps run from the coverage effective date, not from the date someone noticed the variance.

In the example above, the change was keyed four days before it took effect, so the window is barely touched by the time August arrives. Now change one fact: the same EE+SP → EE change was effective May 1 and keyed on June 27. It's still a timing exception on the July bill, because it arrived after cutoff. But by the time it can be checked on August's bill, May is already about 90 days back. On a 90-day contract, part of the recovery is at risk before anyone has done anything wrong. (The full mechanics are in the retro window guide.)

That's why late keying and cycle cutoffs need to be tracked together. Each one on its own looks harmless. Combined, they can push a correctable error out of the window.

What to do with this

How a TareSum audit handles it: every exception is classified as timing or discrepancy. Timing exceptions carry forward with their expected resolution and are checked against the next cycle's bill. If the correction or the retro credit doesn't appear in full, the item becomes a discrepancy with its full history attached. Book the 20-minute call →
← Advanced guide Next: The credit you passed through →

How many timing exceptions never resolved?

Send us three months of bills and your enrollment file with change dates. We'll show you which variances were timing, which ones closed, and which ones are still owed.

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.