Tallyvant reads three exported records for one period, resolves who is who, aligns the periods, compares the amounts, and reports what disagrees — with the source rows attached.
Each has a different owner and a different remedy. Tallyvant reports them separately and offers no way to blend them.
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.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.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.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.Six properties that decide whether a reconciliation result is usable in a dispute or only interesting in a meeting.
The same person appears in carrier billing, payroll, and HR enrollment under different identifiers, sometimes with different spellings and dependants attached in different ways. Tallyvant proposes a match, shows you what it matched on, and asks you to confirm before any amount is compared.
A billed period, a deduction period, and an employment or enrollment period rarely share boundaries. Periods are aligned explicitly, and where a coverage end date has to be derived from an employment termination date, the finding says so.
Money is compared as integer minor units, never as floating-point values, and the browser performs no arithmetic on an amount. Every figure shown is one the engine computed, so nothing on screen can disagree with what was tested.
The same inputs and the same mapping produce the same findings, in the same order, with the same identifiers. A result you can reproduce is a result you can defend in a conversation with a carrier.
Rows the engine could not assess are listed as exceptions rather than dropped. A rule that could not run is reported as needing input, which is not the same as having found nothing wrong.
A finding carries the rule that produced it, each source row it rests on, the basis of its amount, and the qualifiers that limit it. If you cannot trace it, you should not act on it.
The qualifier that limits a finding travels with it everywhere — in the list, in the detail view, and in the export.
Financial positions · Sep 2026
| 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 filtered to one category, each with its rule and qualifier.
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 |
The source rows behind a single finding, drawn from all three files.
The distinction most reconciliation reporting loses. Tallyvant records approval and realisation as different states, and only the second is money you have.
Lifecycle
A recovery case, with verified credits tracked against the amount claimed.
Rule 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 |
The monthly report, including the rules that could not run.
The workflow page walks through the five stages in order. The security page sets out what is implemented and what is not.
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.