For ben-admin · HRIS · payroll platforms
Your customers expect EDI to every carrier they care about. Building and maintaining that matrix is a multi-year engineering investment. Embed Velora as your EDI layer instead. We accept whatever record shape your DB already produces. AI builds the carrier-specific mapping. You stay in your codebase; we stay invisible to your users.
X12 5010 generation is the easy part. The hard part is the variance: different ID conventions, different effective-date semantics, different 999 dialects, different SFTP host fingerprints. Every new carrier resets the integration test matrix.
Carriers ship companion guide updates without API changes. Your integration silently rejects until a customer calls with a coverage gap. Velora’s companion-guide AI re-parses every guide on update and warns when a carrier’s rules tighten.
PHI encryption at rest, audit chain, BAA-ready logging, impersonation gating, host allowlist, transport-level PGP — each one is a sprint. Velora ships with all of them, signed off by a security audit.
Webhook us when an enrollment is finalized. We do the X12 generation, transmission, ack handling, AI rejection-explanation. Your customers see your UI. We are the EDI layer that doesn’t need a logo.
POST JSON, CSV, fixed-width, or tab-delimited. Send three sample records and Velora’s AI builds a complete mapping with confidence per field. High-confidence mappings auto-confirm.
Full OpenAPI 3.1 spec, TypeScript SDK type stubs published, webhook signing playground. Same surface every velora-edi customer integrates against.
Per-tenant API keys, per-tenant audit log, per-tenant impersonation gating. Cross-tenant queries impossible by construction; row-level security enforced at the DB.
Every file generated, every transmission attempted, every acknowledgment captured. Webhook your error sink for real-time visibility; export the ledger for compliance.
Surface Velora’s voice agent inside your product. Customer asks ‘why did this 834 reject?’ — agent reads the 999 segment, explains in English, proposes a fix. Branded as your product.
Subscribe to enrollment.transmitted, ack.received, rejection.explained, mapping.proposed. Failed deliveries land in a DLQ; replay path with HMAC verification preserved.
No data migration. No schema mapping for our internal model. Velora reads what you send, derives the carrier-targeting from your enrollment record, generates the X12 on the fly.
When a finalized enrollment is written to your DB, fire a webhook to Velora. Within seconds, the X12 834 is generated, sandbox-validated, and queued for the carrier’s next transmission window.
999 + TA1 acknowledgments are parsed, stored on Velora, and webhooked back to your event bus with a normalized status. Your customer-facing UI surfaces them as ‘sent · received · rejected · resolved’.
If you want Velora’s voice agent inside your product, embed the widget with your tenant’s API key. If you don’t, the API surface is sufficient.
Every customer endpoint a platform integrator needs: ingest, mappings, transmissions, acks, webhooks, billing meter, audit log.
Hash-chained, idempotent, with paired rollbacks. Includes RLS-protected audit log + impersonation_sessions + feature_flags + transmission_ledger.
X12 round-trip, AI mapping verification, transport-level SFTP over mock server, anomaly-alerter detection, webhook DLQ + replay.
WEBHOOK_DELIVERY_ENABLED · USAGE_METERING_ENABLED · PERSON_IDENTITY_ENABLED · PATH_B_IDENTITY_ENABLED · FLAT_FILE_AI_ENABLED · CRON_AI_ENABLED. Operator-gated rollout.
Walk through the platform demo, or send us your most-requested carrier list and we’ll tell you which ones are already in the matrix.