Same for me for some of my EOBs. It would be helpful if we could put in the fields that are on our EOB and have QMEM calculate the other fields with an opportunity to override in the exception case. That would speed things up without my needed a calculator field or a physical calculator unless I want to do it myself. This would have an added benefit in that if there is a discrepancy - QMEM could reveal it.

Insurance 1 fields are:

Amount charged

Medicare approved

Medicare paid provider

you may be billed

Insurance 2 fields are:

Amount charged

Not covered

Amount allowed

Copay/Deductible

Benefit available (before coordination of benefits)

Insurance 3 fields are:

Amount charged by provider

Discount amount

Charges not covered

Deductible

Coinsurance

copayment

Payment by insurance

Insurance 4 fields are:

Fee charged

Covered expense

Plan Benefit

You folks have put your finger on one of the trickiest (and to me, most annoying) design challenges we've got. Namely, every insurance company shows different fields on their EOBs. Even if they contain the same data fields, they use different names. We've collected dozens of EOBs, and they are all different. Are they trying on purpose to confuse people? It makes me crazy.

OK, I'll stop ranting now... ;-)

Anyway, this is a very common request. So, in the next version, there will be different fields for "provider write-off" and "amount allowed" (same as "amount approved" or "negotiated charge"). You'll be able to use whichever one matches your EOB.

Sound good?

- Lisa

Yes, thanks Lisa and team. Of all the various "other" fields, "provider write off" or "amount allowed" are CERTAIN to be in all EOBs, and one is just the converse of the other, so not having to do a calculation to obtain one or the other will speed things up immensely.

Hey Lisa,

You & your project team will never be able to incoporate ever term used in the insuance industry. I'm most familiar with "Negoiated Amount"; "Amount Covered"; "Over Reasonable & Customary (R&C)" for a reason for amount unpaid.

Maybe allow the user the option to "change" the text in the options section or "ini" file if they don't like the default setting.

I'm sure you are already doing this -- always worth a reminder though. With the "Boomers" hitting their 50s & medicare not kicking in until 65 -- just want the project team to remember the rest of us not on medicare. Occasionally I'll notice posts requesting fields or something that seems geared toward "medicare" members in some way or another. Granted, a large % of your customer base will be on medicare(self/spouse) or by maintaining records for a relative/friend on medicare. However, there will be customers who may be eligible for medicare/medicaid/VA benefits due to disabilities/military service and customers who don't qualify for either and simply have "insurance" benefits.

So far, the program has been very helpful for me keeping our EOBs payments straight. I'm looking forward to v2. Some of the "fixes" I would like have already been discussed on these forums while others are somewhat different from those mentioned by those who have used standard Quicken products previously.

Barrie

Barrie,you are so right. There are just too many different terms. It would take a whole screen just to list them.

Yes indeed, the goal is to support all common types of insurance. In the past the team has had some questions about Medicare, because it's a little different from the corporate plans we're more familiar with. We appreciate all the help from folks in this forum. But we're not exclusively targeting Medicare or Quicken users; don't worry.

Thanks to you and everyone for the comments. The developers are making good progress on the next version. Stay tuned for more news to come...

- Lisa