Already know the bills are wrong? Replace the machinery that produces them.

The TareSum platform is for TPAs, brokers, and benefits agencies who are ready to run consolidated billing, carrier remittance, payroll deduction feeds, enrollment management, and benefits EDI on one system built around their book. We host it for you, or we build it into your own cloud and hand you the keys.

Your benefits admin system stays the system of record. BAA before any file moves.

When an audit isn't enough anymore

An audit checks the bill someone else produced. Some teams are past that point. They're the ones producing the bill, cutting the payroll file, and keying the carrier changes, and they're doing all of it by hand.

SIGN 1

You pay the carriers

You consolidate premium, invoice each employer group, and remit to each carrier with backup. Some carriers self-bill and others send a list bill you reconcile. The workbook that ties it all together has one owner, and nobody else touches it.

SIGN 2

Your files are built by hand

Every group has a payroll system that wants deductions in its own layout and on its own calendar. Someone exports, reformats, and sends. Each start, stop, and change gets the same handling, every pay period.

SIGN 3

The source is right, but nothing downstream reads it

Your ben admin platform has the correct census, elections, and rates. The carriers that don't take a feed, the payroll systems, and the invoices are still updated from it one keystroke at a time.

What we build

Every module runs on one managed copy of your enrollment data. Start with the one that hurts most and add the rest as each goes live. Billing usually goes first, because it forces the enrollment data to be right, and everything after it builds on data that's already proven.

Enrollment

Enrollment management

One validated, versioned enrollment record for every group, member, plan, and tier, loaded from your ben admin system on a schedule. Every other module runs on it.

  • Scheduled census and election imports, validated field by field, with rejected rows reported before anything bills
  • Group, carrier, plan, and member matching that catches duplicates and mismatched IDs at the door
  • Full change history, so retro changes keep both the original and the corrected effective dates
  • Missed terminations, dependents aging out, and plan-year rollovers flagged automatically
  • Every add, term, and tier change routed to each carrier the way it accepts them: a feed, or a keying task list in Excel or your CRM
Billing

Consolidated billing & carrier remittance

A client invoice per employer group and a remittance statement per carrier, produced from the same calculation, so the two always tie out.

  • Cover, summary, and participant-detail invoice workbooks
  • Proration, volume-rated life and disability, and retro adjustments through prior periods
  • Self-funded and level-funded fees: admin, PEPM, stop-loss
  • Optional breakout by division or location for multi-entity groups
Reconciliation

Carrier bill reconciliation

The audit engine, running as part of your operation. Drop in a carrier's list bill as a PDF, Excel file, or EDI feed, and get back a reconciliation you can act on.

  • Every line recomputed against enrollment and contract rates
  • Last-change date from your ben admin system, to tell timing from true error
  • Unresolved items carry forward until they clear and raise a new task if they don't
Payroll

Payroll deduction feed builder

Start, stop, and change deduction files on each group's own pay calendar, for any payroll system that accepts a file.

  • Full start, full stop, and scheduled change files, with or without term records
  • Deductions keyed to the actual effective date or snapped to the pay period, per feed
  • Deduction codes imported from your ben admin template, not re-keyed
  • Auto-send, or notify an owner to review before release
Enrollment EDI

Carrier enrollment & eligibility feeds

Outbound 834 files built to each carrier's companion guide, with the delta and resend handling that carrier feeds actually need.

  • Full-file and change-only feeds, with carrier-specific mapping
  • Plan-year rollover, dependent add/remove, and division or group moves
  • 999 and TA1 acknowledgement tracking, with error and resend workflows
Claims EDI

Claims & TPA data integration

For self-funded books and the TPAs that administer them: claims, remittance, and status data from many carriers, normalized into one pipeline.

  • 837 claim intake and 835 remittance, plus carrier-proprietary claim files
  • Undocumented carrier layouts reverse-engineered and mapped
  • Duplicate detection, batch validation, hold and resubmit workflows
  • Claims data ready for stop-loss, lag, and plan-performance reporting

Need something these don't cover? If it sits between your ben admin system, your carriers, your payroll vendors, and your books, it's the kind of thing we build. Tell us what you're doing by hand today →

The EDI underneath

Benefits data moves through a handful of X12 transactions and a much longer list of carrier-specific files that only resemble a standard. We handle both.

TransactionWhat it carriesWhat we do with it
834Benefit enrollment & maintenanceBuild outbound carrier feeds, and read inbound feeds as an enrollment source
820Premium payment & remittance adviceGenerate remittance detail with each carrier payment, and reconcile carrier-sent 820s against the bill
837Professional, institutional & dental claimsIngest, validate, de-duplicate, and route by group and division
835Claim payment & remittance adviceMatch payments to claims and load them for reporting and reconciliation
270 / 271Eligibility inquiry & responseVerify eligibility against carrier records and flag mismatches
276 / 277Claim status inquiry & responseTrack claims in flight and surface the ones that stall
999 / TA1Functional & interchange acknowledgementsConfirm every file was accepted and alert when one wasn't
Everything elseProprietary flat files, payroll layouts, PDF and Excel list billsMap once, version it, and alert when a carrier changes the layout without warning

Connected to what you already run

We import from the systems that hold your data and deliver to the ones that act on it. Census, elections, rates, and contribution strategies stay where they're maintained today. We don't make your team re-key any of it.

Employee Navigator bswift PlanSource Selerix Dynamics 365 Salesforce Applied Epic Payroll systems, by file Accounting / GL exports Microsoft Entra ID SFTP REST API & webhooks

Most ben admin platforms integrate by scheduled file rather than live API. That's fine. We start with the exports your team already produces, move to scheduled drops, and become a direct feed recipient where the platform allows it. None of those steps changes what's built.

The billing rules are already written

The hard part of a billing platform isn't the invoice template. It's the hundred small rules that decide what each line should be. Every error pattern in the field guide is a rule this engine already computes correctly.

PRORATION

Your contract's rule, per plan

Full month, daily proration, the 15th rule, or a configurable day-of-month cutoff, set per carrier and plan rather than once per system. Why that matters →

VOLUME

Life and disability, rated correctly

Rates per $10, $100, or $1,000 of coverage, with age bands, smoker status, and guarantee-issue caps handled as part of the rate, not as afterthoughts. Why that matters →

RETRO

Adjustments that reconcile

Retroactive changes recalculated against several prior billing periods. Each adjustment accounts for what was billed, what was already corrected, and what should have been billed, so nothing gets credited twice. Why that matters →

Where it runs is your call

The platform is built the same way wherever it runs. It's containerized, with infrastructure-as-code for both Microsoft Azure and AWS. The only differences are who owns the environment, who operates it, and how it's priced.

Option A

We host it

Runs in TareSum's secure cloud, with your data isolated in its own database and storage. Your team signs in with your existing Microsoft accounts. We handle monitoring, backups, and upgrades.

Fastest to first bill. Implementation fee, then a monthly subscription that scales with groups or covered lives. Hosting and support are included.
Option B

We build it in your cloud

Deployed into your Azure or AWS account. You own the code, the data, and the environment. Your IT team operates it and we support it.

Simplest story for your security review. Fixed project fee per phase, an optional support retainer, and you pay cloud consumption directly.
Option C

Start hosted, convert later

Go live on Option A while IT completes its review. When you choose, we redeploy into your cloud, migrate the data, and cut over.

Takes the hosting decision off the critical path, so IT evaluates a running system instead of a proposal.

How a build runs

The work is phased so something real is live early and each module builds on data the previous one has already proven. It runs forward deployed — our engineer sits with your billing team through each phase, so the rules we encode are the ones your analysts actually apply, not the ones a requirements document guessed at. A first live bill is typically about three months from kickoff.

Phase 0 · About a month

Foundation

BAA, a secure file channel, and sample exports from your ben admin system. We stand up the platform, choose pilot groups, and re-baseline the plan on your actual file formats.

Phase 1 · The first module

Usually billing

The enrollment pipeline and billing engine, followed by invoices, remittance, and reconciliation. Pilot groups run in parallel with your current process for two cycles before anything goes live.

Phase 2+ · Overlapping

Payroll, carrier changes, EDI

Pay calendars and deduction feeds, carrier change routing by feed or task list, and claims integration. These run on the data billing has already validated.

As needed

Integrations

Direct ben admin feeds, CRM task routing, agency management, and accounting exports. We scope these as you go, once you know which ones are worth it.

Security your IT team will ask about

Census, enrollment, and claims data is PHI. These controls apply the same way whether we host the platform or you do, and we'll provide a written controls summary and walk your IT team through it directly.

BEFORE ANYTHING

BAA first

Your form or ours, executed before any member data moves. Until it's signed, we work from synthetic or de-identified samples.

ACCESS

Your identity, your policies

Single sign-on with Microsoft Entra ID, so your existing accounts, MFA, and offboarding apply automatically. Roles control who can release a bill or a payroll file.

EVIDENCE

Every file kept, every release logged

Encryption in transit and at rest, and secrets in a managed vault. Every inbound file and released output is archived, and every download and release is logged, so the evidence is there when a carrier dispute comes up.

Three ways to work with us

Plenty of teams use more than one. The format mapping and billing rules worked out during an audit carry straight into the Watch or a build.

You want toWhat changesStart withThen
Bill auditFind out whether the bills you're paying are rightNothing. The audit sits beside your process.One group's last three bills, and a 20-minute callMonthly, per group, cancel any month
Stop-Loss WatchKnow your self-funded clients' stop-loss money is collected before the runout closesNothing. You send one more drop a month.A self-funded audit of one group's plan yearMonthly, per group, cancel any month
PlatformProduce the bills, files, and tasks yourself, correctly, every cycleManual steps become scheduled outputs, built by a forward deployed engineer inside your teamA scoping session on the modules you need firstA phased build, hosted or in your cloud, with pilot groups billed in parallel before go-live

Bring us the process you want off spreadsheets.

Tell us which ben admin system you run, which carriers you work with, and what your team is building by hand today. The first conversation is a scoping session. You don't need to bring files or member data.

Email us to scope a build

Not ready to build? Start with an audit instead. Or write to letslook@taresum.com.