Carrier billing
The invoice detail for the period: who was billed, for which plan and tier, over which dates, at what amount.
Typically: Subscriber identifier, plan, coverage tier, billed period, amountHow it works
Three files in. A result you can run again.
Every stage produces something you can inspect before the next one runs. Nothing advances on an inference you were not shown.
The workflow
Five stages
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.
What you need
Three exports covering the same period
Only the fields needed to reconcile a person, a plan, a period, and an amount. Tallyvant proposes the column mapping and asks you to confirm it.
Payroll deductions
What was actually deducted from pay in the period, per employee and per plan.
Typically: Employee identifier, plan, deduction date, amountHR enrollment
Who was enrolled in what, with the employment and coverage dates that bound it.
Typically: Employee identifier, plan, coverage tier, enrollment dates, employment datesData minimisation. Tallyvant asks for the fields it needs to reconcile and no more. It does not need medical information, claims data, or compensation detail, and you should not send them.
Provenance
Every run records what it read
The period, each file with its content hash and row count, and the rows the engine could not assess. A finding can always be traced back to the exact file it came from.
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.
Synthetic data. Exceptions are reported, never silently discarded.
Recovery lifecycle
Six states, and only one of them is money
Each state means something specific. The difference between the fifth and the sixth is the difference between a carrier's promise and your bank balance.
| State | What it means |
|---|---|
| Potential | Found by a rule. Not yet reviewed by anyone. |
| Validated | A reviewer examined it and attached it to a case. Not agreed by the carrier. |
| Approved for dispute | An Authorized Approver approved the package. Nothing has been sent by Tallyvant. |
| Submitted | A user recorded that the package was submitted to the carrier externally. |
| Credit approved | The carrier said it will credit. Not yet seen on an invoice or a payment. |
| Realised | Fully covered by verified carrier credits. This is money actually recovered. |
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.
Synthetic data. Verified credits are tracked against the amount claimed.
Submission is yours. Tallyvant never contacts a carrier. It assembles and records; you submit through the channel you already use, then record the outcome so the case can be tracked.
Run it against one period
A demo walks through a single month of your own records end to end — upload, mapping, reconciliation, findings, and evidence — so you can judge the output rather than the pitch.