The person reading your bills

Sean McLaughlin

Founder

I've spent two decades building and repairing the systems this industry runs on — enrollment platforms, healthcare EDI pipelines, claims processing, and the premium billing engines that generate the list bills TPAs send out every month.

That last part is the reason TareSum exists.

Why a billing engineer audits bills

I've written the code that produces carrier bills: the proration rules, the volume-rated life calculations, the retroactive adjustment logic that reaches back through six prior billing periods and reconciles what was billed against what should have been. When you've built the machinery that generates an adjustment section, you know exactly where errors enter one — which join silently drops a member, which effective-date comparison quietly bills a termed employee one more month, which rate lookup falls back to last year's table without telling anyone.

Every error pattern in the field guide is something I've either fixed in a billing system or found in a carrier's output. The audit isn't a checklist someone handed me. It's the accumulated list of everything I've watched go wrong.

Where TareSum came from

TareSum grew out of Resolute Concepts, my integration and automation consultancy. Across billing modernizations, EDI integrations, and claims pipelines for benefits organizations, the same pattern kept surfacing: the enrollment system was right, the carrier bill was wrong, and nobody was positioned to prove it — because proving it requires recomputing every line, every month, against the enrollment record and the contract. That's not a job for a spreadsheet or a spare afternoon. So I built the machinery to do it, and TareSum is that machinery with a front door.

What that means for you

When you send files, the person who built the reconciliation engine is the person accountable for your audit. When the review call walks through an exception, you're talking to someone who can explain the arithmetic down to the day-count — and who has sat on the TPA side of carrier disputes and knows what documentation makes them move. No account layers, no offshore review queue, no junior analyst learning the domain on your bills.