Invoices and payroll disagree
A carrier invoice is assembled from the carrier’s record of who is covered. Payroll deductions are assembled from yours. The two are reconciled by hand, if at all, and they drift.
Benefits Financial Assurance
Find what you’re overpaying. Verify what you’re owed.
Tallyvant reconciles benefits billing, payroll deductions, and enrollment records to uncover potential overpayments, coverage discrepancies, and financial exposure — with evidence behind every finding.
Pre-production: accepting demo and pilot-interest requests from employers. There is no self-service signup, and nothing is sold from this website.
- Not a payroll system
- Not an accounting system
- Not an insurance carrier
- Not a benefits broker
- Not an automatic refund guarantee
Findings · September 2026 reconciliation
Synthetic dataFinancial positions · Sep 2026
Employer overpayment$18,402.603 findings. Recoverable once validated.
Owed to employees$1,284.005 findings. Not a recovery.
Employer exposure$946.124 findings. Cost the employer bears.
Coverage questionsNo amount claimed2 findings. Needs carrier verification.
These four positions are reported separately and are never added together.
Findings
| Finding | What it is | Amount |
|---|---|---|
| F-2291Rule BR-01 | Employer overpaymentEMP-10427 · Medical PPO, billed after termination | $4,210.00 |
| F-2301Rule BR-02 | Owed to employeesEMP-11204 · deduction above expected contribution | $318.00 |
| F-2308Rule BR-06 | Suspected coverage discrepancyEMP-10755 · deducted with no carrier billing line | No amount |
The findings view, drawn with synthetic data. No customer results and no employee records appear anywhere on this site.
The problem
Benefits reconciliation is hard for structural reasons
Not because anyone is careless. Because three systems describe the same month differently, and nothing in the ordinary course of business forces them to agree.
Changes land on different dates
A hire, a termination, a dependent added, a plan switched — each reaches payroll, the carrier, and your HR system at a different time. A discrepancy in one month is often a timing artefact in another.
Wrong deductions cut both ways
A deduction taken above the expected employee contribution is money owed back to an employee. One taken below it is a cost the employer quietly absorbs. Neither is recoverable from the carrier.
Manual review does not reproduce
A spreadsheet review is as good as the analyst who built it and the afternoon they had. Run it again next month against the same files and you will not reliably get the same answer.
Approved credits go untracked
A carrier agreeing to issue a credit is not the same as the credit appearing on an invoice. Without tracking through to realisation, an approved recovery can be counted once and received never.
How it works
Five stages, from three files to a reproducible result
Each stage produces something a person can inspect. Nothing advances on an inference you were not shown.
Step 1: Upload your records
Three files for the period you want to examine: carrier billing, payroll deductions, and HR enrollment. Each upload is stored with a content hash, so every later finding can be traced to the exact file it came from.
Step 2: Review proposed mappings
Tallyvant proposes how each file’s columns map to plans, employees, and coverage periods, and how identities line up across the three sources. You confirm or correct the mapping before anything is reconciled.
Step 3: Reconcile identities, periods, and amounts
A deterministic engine matches people across sources, aligns coverage periods, and compares amounts in minor units. The same files and the same mapping produce the same result every time.
Step 4: Investigate evidence-backed findings
Each finding names the rule that produced it, the source rows it rests on, the amount it claims, and the qualifiers that limit it. A finding you cannot trace back to its evidence is not one you should act on.
Step 5: Track recovery and monthly assurance
Approved cases move through a recorded lifecycle to realisation, and each month’s reconciliation produces a report you can reproduce from the same inputs.
Supported workflow. File upload is the supported workflow today. Tallyvant does not currently connect directly to carrier or payroll systems, and nothing on this page should be read as describing a live integration.
Four financial outcomes
Four kinds of money, kept apart
Each has a different owner, a different remedy, and a different degree of certainty. Treating them as one figure is the most common way a reconciliation result gets misquoted.
Recovery
Identify potential carrier overpayments.
Premium the employer appears to have paid and should not have — a terminated employee still billed, a dependent billed after removal, a duplicated line, a rate applied to the wrong tier.
Recoverable from the carrier once validated. Not a saving until it is credited.Exposure
Surface payroll and suspected coverage discrepancies.
Deductions that sit above or below the verified expected employee contribution, and employees being deducted with no corresponding carrier billing line.
Money owed back to employees, or a cost the employer bears. Neither is recoverable from the carrier.Prevention
Detect recurring errors and verify corrections.
A discrepancy that reappears month after month is a process defect, not an incident. Tallyvant shows which findings recur, and whether a correction you believe you made actually took effect.
Prevention is measured by a defect not recurring, not by a projected future saving.Assurance
Produce reproducible monthly reconciliation reports.
A monthly report stating what was reconciled, which rules ran, what each rule found, what it could not assess, and which source-data limitations applied.
A reconciliation with no findings is evidence that the rules found nothing — not an assurance that nothing is wrong.Reported separately, never summed. These four are reported separately and are never added together. A recovery owed by a carrier, a refund owed to an employee, a cost the employer absorbs, and a coverage question carrying no amount are different kinds of money. A single combined “savings” figure would misrepresent all four.
Product preview
What you actually work in
Five views, drawn with synthetic data and the application's own vocabulary. The labels, rule identifiers, and lifecycle states are the real ones; the figures are illustrative.
Reconciliation overview
Reconciliation · run RUN-2026-09
Synthetic dataPeriod1 – 30 September 2026
RunRUN-2026-09 · completed
Source files
| Source | Content hash | Rows | Status |
|---|---|---|---|
| Carrier billing | sha256:9f2c41a8… | 1,482 | Accepted |
| Payroll deductions | sha256:4d81be07… | 1,391 | Accepted |
| HR enrollment | sha256:b70e5c2f… | 1,404 | 12 exceptions |
Exceptions are rows the engine could not assess. They are listed, never discarded.
Each run records the period, the three source files, their content hashes, and the rows the engine could not assess.
Financial findings
Findings · filtered to employer overpayment
Synthetic dataFinancial positions · Sep 2026
Employer overpayment$18,402.603 findings. Recoverable once validated.
Owed to employees$1,284.005 findings. Not a recovery.
Employer exposure$946.124 findings. Cost the employer bears.
Coverage questionsNo amount claimed2 findings. Needs carrier verification.
| Finding | Rule | Qualifier | Amount |
|---|---|---|---|
| F-2291 | BR-01 | Coverage end derived | $4,210.00 |
| F-2294 | BR-01 | Requires carrier verification | $612.40 |
| F-2297 | BR-01 | Duplicate source lines collapsed | $13,580.20 |
Every qualifier that limits a finding travels with it, in the list and in the export.
Findings grouped by category, each carrying the rule that produced it and the qualifiers that limit it.
Evidence detail
Finding F-2291 · evidence
Synthetic dataCategoryEmployer overpayment
RuleBR-01 · billed after coverage end
Amount$4,210.00
BasisPremium billed for 2 months after the derived coverage end date.
Source rows
| File | Row | Field | Value |
|---|---|---|---|
| carrier_billing | 1182 | billed_period_end | 2026-09-30 |
| hr_enrollment | 212 | employment_end | 2026-07-31 |
| payroll_deductions | 740 | last_deduction | 2026-07-24 |
Coverage end derived. The coverage end date was derived from the employment termination date under the plan rule, not stated directly by the carrier.
The source rows behind one finding, from all three files, with the derivation stated.
Recovery case management
Case CASE-2026-09-004 · recovery
Synthetic dataClaimed$12,840.00
Findings4 · all employer overpayment
Approved byAuthorized Approver · 14 Oct 2026
Verified credits$3,610.00 of $12,840.00
Lifecycle
- Potential
- Validated
- Approved for dispute
- Submitted
- Credit approved
- Realised
Submitted externally. Tallyvant does not transmit disputes. A user recorded that this package was sent to the carrier through the employer’s own channel. It becomes realised only when verified credits cover it in full.
A case moves through a recorded lifecycle. Approved is not the same as realised, and the interface never lets the two merge.
Monthly assurance reporting
Monthly assurance · September 2026
Synthetic dataRule coverage
| Rule | Outcome | Findings | Exceptions |
|---|---|---|---|
| BR-01 | Executed | 3 | 0 |
| BR-02 | Executed | 9 | 4 |
| BR-05 | Needs input | 0 | 8 |
| BR-06 / BR-07 | Executed | 2 | 0 |
Report hashsha256:2a77d019…
ReproducibleRe-running the same inputs and mapping reproduces this hash.
BR-05 found nothing because it could not run. A rule that needs input has not cleared the period — it has been prevented from assessing it. A clean report is not an assurance that nothing is wrong.
What ran, what it found, what it could not assess, and a hash that lets the report be reproduced.
Who it's for
Three people with the same records and different questions
Reduce manual reconciliation work.
Replace the month-end spreadsheet comparison with a run you can repeat, hand over, and defend.
- Three uploads instead of a rebuilt workbook
- Proposed identity and column mappings to confirm
- Exceptions listed explicitly rather than silently dropped
Understand financial exposure and recoveries.
See each financial position on its own terms, with the basis it was computed from and the limits that apply to it.
- Separate positions, never one blended number
- Recoveries tracked through to realisation, not to approval
- Month-over-month reports reproducible from the same inputs
Investigate deduction discrepancies with supporting evidence.
Open a discrepancy and see the payroll row, the carrier line, and the enrollment record it was derived from.
- Source rows attached to every finding
- Expected contribution shown with its derivation
- Timing qualifiers flagged before anyone is contacted
Security and trust
What is implemented, and what is not
Everything below is built and covered by tests. The limits beneath it are stated with the same prominence, because a security page that lists only strengths is not informative.
Role-based authorization
Access is granted by role — Organization Owner, Benefits Administrator, Payroll Administrator, Finance Controller, Authorized Approver, Platform Operator — and each endpoint checks the specific permission it requires rather than only that a user is signed in.
Tenant isolation
Every request is scoped to one organization at the router, before a handler runs. Isolation is covered by tests that attempt to reach another tenant’s records on each endpoint and assert that the attempt fails.
Source-data provenance
Uploaded files are recorded with a content hash. Each finding references the rule that produced it and the source rows it rests on, so any figure can be traced back to the exact file and row it came from.
Audit trail
Consequential actions are written to an append-only audit record identifying the actor, the action, the affected records, and the time.
Human approval for consequential actions
No financial claim advances on its own. A recovery package must be approved by a user holding the Authorized Approver role, and Tallyvant does not transmit disputes to carriers.
Encryption and secure data handling
Traffic is served over HTTPS. The application requires a TLS-verified database connection, with a startup check that fails rather than falling back to an unverified one. Sessions use signed, HTTP-only cookies, and sensitive values are redacted from logs.
Tallyvant holds no SOC 2 report, no HIPAA compliance attestation, and no independent third-party security audit. Any statement to the contrary would be false.
The product is pre-production. It has not been operated against live employee data, and it should not be until a privacy and security review is complete.
This website is a separate deployment. It has no database access, no application credentials, and no path to employee data.
FAQ
Questions worth asking first
What does Tallyvant reconcile?
Three sources for a billing period: carrier billing, payroll deductions, and HR enrollment. It matches people across them, aligns coverage periods, and compares amounts — producing findings for potential carrier overpayments, deductions above or below the expected employee contribution, and employees deducted with no corresponding carrier billing line.
Does Tallyvant replace payroll software?
No. Tallyvant is not a payroll system, an accounting system, a carrier, or a benefits broker. It does not run payroll, issue payments, or hold the record of what anyone is owed. It reads exported records and tells you where they disagree.
What information is required?
A carrier billing file, a payroll deduction file, and an HR enrollment file covering the same period, each as a delimited export. Tallyvant proposes how columns and identities map and asks you to confirm before reconciling. Only the fields needed to reconcile a person, a plan, a period, and an amount are required.
Does Tallyvant automatically submit carrier disputes?
No. Tallyvant assembles an evidence package and records its approval, and nothing leaves the system. Submission to the carrier is performed by you, through your existing channel, and then recorded in Tallyvant so the case can be tracked.
Can it verify recovered credits?
Yes, and it distinguishes the two states that are usually conflated. A carrier saying it will credit is recorded as credit approved. A finding becomes realised only when it is fully covered by verified carrier credits. Only the second is money actually recovered.
Is Tallyvant available for a pilot?
Tallyvant is pre-production and is being prepared for early pilots with a small number of employers. There is no public self-service signup. If a pilot would be useful to you, request a demo and say a little about your situation.
How is employee information protected?
Access is scoped to one organization and checked per permission at the router; uploads are recorded with a content hash; consequential actions are written to an append-only audit trail; and the application requires a TLS-verified database connection. Tallyvant holds no SOC 2 report or HIPAA attestation, and has not been operated against live employee data. The details, and the limits, are set out on the security page.
See it against your own records
A demo runs through one period of your carrier billing, payroll deductions, and enrollment records, and shows you the findings with their evidence. Tallyvant is pre-production and is being prepared for early pilots.