Skip to main content
Companion product · Velora Billing

Billing reconciliation is its own product.

Atlas is the agency hub. Carrier-invoice reconciliation is its own SaaS — velora-billing — sold standalone to employers, brokers, PEOs, and TPAs. Atlas surfaces recon counts on the account record (when both products are wired together), but the ingestion engine, EDI 820 parser, auto-recon loop, and immutable ledger all live in velora-billing. This page exists to point you there honestly instead of duplicating the capability inside Atlas.

Velora-native module
Velora productvelora-billing (standalone Velora product)

velora-billing is sold independently — buyers may have ZERO other Velora products. It runs on its own deploy, its own database tables, its own auth. Atlas can read recon summaries via HTTPS for tenants who own both products; otherwise the page below is purely informational.

Ingest the carrier invoice. Diff against the enrollment of record. Surface the variance.

Ingest

Carrier sends a monthly premium invoice as PDF, CSV, or EDI 820. velora-billing extracts every line — member, ID, tier, coverage period, premium — into a structured ledger. Our AI engine reads new carrier formats with no engineering setup; the EDI 820 native parser handles X12 inbound (BPR / ENT / NM1 / RMR / ADX) at the transaction-set level.

Diff

An enrollment snapshot (CSV today; EDI 834 round-trip when paired with velora-edi) is the source of truth. Each invoice line is matched member-by-LoC and date-verified. Mismatches are categorized: ghost dependent, retro term, plan-code drift, amount delta. Every match decision is recorded on a chain-hashed audit ledger.

Resolve

An auto-recon loop with typed gates classifies each delta and either drafts a carrier dispute (with a 2-minute undo window before send) or queues it for a human. ERISA Schedule H supplement export comes for free out of the same data.

What velora-billing actually ships. Roadmap is roadmap.

01

Zero-rule carrier ingestion

Our AI engine profiles every new carrier format on first invoice. Carrier signatures persist so the next month's run is fast. No 2–4 week onboarding sprint per new carrier — competitors require that; velora-billing doesn't.

Structural moat vs. AdminaHealth / Tabulera / Beneration
02

Member-by-LoC matching

Same member, multiple lines of coverage (medical + dental + vision) = multiple matched rows. Each line carries its own coverage period and tier. Multi-LoC is first-class, not approximated by aggregating to a person.

03

Ghost-dependent + retro-term detection

A dependent who aged off but is still on the bill. A spouse termed in a divorce QLE who never fell off. A retro term where the carrier owes a credit but the credit-memo never landed. The match engine flags each with the date evidence behind it.

04

Auto-recon loop with typed gates

Every delta runs through a state machine of typed gate codes (carrier-match, format-drift, dispute-allowed, undo-window). Decisions are recorded on the AutoActionLog. Send queue holds drafted disputes for a 2-minute undo window before transmission.

05

Chain-hashed audit ledger

Every mutation in the recon flow writes a SHA-256-chained AuditEvent. Tamper-evident by construction; pairs cleanly with HITRUST and ERISA fiduciary narratives. Most competitors have an audit table; few have chained audit.

06

EDI 820 native parser

433 LOC of X12 in the inbound path: BPR header, ENT loops with multiple LoCs per member, NM1 / REF / DTM / ADX / RMR / IT1 segments. Most cloud competitors punt EDI to a paid third-party vendor; velora-billing parses it directly today (and Track B will move parsing into velora-edi for cross-product reuse).

07

Brokerage white-label, day one

Brokerage tenants get per-tenant branding on every report and email out of the box. BROKER_ADMIN role + per-broker rollup view. Useful for agencies running recon as a service across their book.

08

ERISA Schedule H supplement export

Pulls auditor-ready CSV with plan-asset custody compliance flagged. Pairs with the fiduciary-litigation tailwind brokers are seeing in 2026; useful as a sales asset, not just a compliance checkbox.

09

What's NOT built yet — honest roadmap

Effective-dated rate cards (no RateCard / BenefitPlan model yet — expectedAmount is per-row today). Tier-drift detection requires that rate model, so it's roadmap, not claim. Self-funded / stop-loss billing is not started. GL connectors (QBO / NetSuite / Sage) are not built. MFA / SSO are not yet implemented (magic-link auth only). Allocation / cost-center splits are not modeled. Read BILLING_GAP_ANALYSIS.md in velora-billing for the full 210-question scorecard.

How Atlas and velora-billing fit together.

Atlas owns the agency CRM: contacts, organizations, deals, renewals, documents, activities. velora-billingowns the carrier-invoice recon ledger. When both products are wired for a tenant, Atlas reads a recon summary (pending tickets, urgent disputes, last-sync) over HTTPS and surfaces it on the account record. velora-billing never queries Atlas’s tables; Atlas never queries velora-billing’s. Each product is sold independently and works alone.
  • Ben AdminSource of enrollment when both products are present
  • EDIEDI 820 / 834 parsing migrating into velora-edi (Track B)
  • Broker CompSister Velora product on the same hub-and-spoke pattern
  • HRISTermination / life-event source for the enrollment snapshot
203
tests on the velora-billing recon engine

203 passing tests across 20 test files in velora-billing as of 2026-04-27. The recon engine itself is 1,543 LOC across 7 modules; the EDI 820 parser is 438 LOC with 20 dedicated tests. This is what Atlas used to ship a stub of — that scaffold is now retired in favor of pointing buyers at the real product.

Pilot-phase benchmark· Reference customers launching Q2 2026 · ask for a reference call

Questions brokers actually ask.

Why isn't billing-recon inside Atlas anymore?
Atlas had a half-built scaffold (3 prisma models, ~290 LOC matcher, ~1,180 LOC UI) that overpromised relative to what it actually did. Meanwhile velora-billing shipped 33 schema models, a 1,543-LOC engine, 203 tests, full EDI 820 ingest, an auto-recon loop, and a chain-hashed audit ledger as a standalone SaaS. Continuing to ship two billing-recon products inside the suite was dishonest to buyers and a maintenance tax. The Atlas-side scaffold was retired; this page now points at the real product.
Can I buy velora-billing without buying Atlas?
Yes. velora-billing is fully standalone — it works without Atlas, HelloHR, Ben AI, Pulse, or velora-edi. ICP is mid-market employers, PEOs, brokers, and small TPAs already on a fully-insured book.
If I buy both, what's the integration look like?
Atlas reads a recon-summary endpoint from velora-billing over HTTPS (API-key authenticated, tenant-scoped, rate-limited). On the account record in Atlas you’ll see pending recon ticket counts, urgent disputes, and last-sync time. Drilling in opens velora-billing in a new tab. No data is duplicated; no cross-database queries; degrades gracefully if velora-billing is unreachable.
What carriers does velora-billing support?
Any carrier — that’s the point of zero-rule ingestion. Our AI engine profiles new formats on first invoice, the carrier signature persists, the next month is fast. No 2–4 week per-carrier onboarding sprint. EDI 820 is parsed natively for carriers who send X12.
What about the features the old Atlas page promised — tier drift, rate-change verification?
Honest answer: those features require an effective-dated rate-card model (RateCard / BenefitPlan with version history) which velora-billing has scoped but not yet built. The old Atlas marketing claimed them; the new positioning matches reality. Both items are tracked in the gap analysis as RED with effort estimates and will ship before the v1 enterprise GA.
Is there an audit trail I can hand a fiduciary auditor?
Yes — every mutation in the recon flow writes a SHA-256-chained AuditEvent, and the ERISA Schedule H supplement export pulls the custody-compliance fields directly. Pair with the chain-hashed audit ledger and you have a tamper-evident timeline.

Open velora-billing and run a real invoice.

Sign up at velora-billing directly. Drop in a carrier PDF or 820, populate an enrollment snapshot CSV, and watch the recon engine run. If you’re also an Atlas customer, ask the team to wire the cross-product summary tile so you see the recon count on the account record.