Built by operators who ran ABA clinics.

Visit verification, built in. Not a separate portal.

Electronic Visit Verification captured on the same schedule your team already uses, with state Medicaid rule packs and verified visits that feed billing directly.

EVV, not a bolt-on
Built-in
Medicaid rules per state
State packs
captured where you work
On schedule
verified visits → claims
Bill-ready

The short answer

What is EVV in ABA?

Electronic visit verification (EVV) is a federal Medicaid requirement under the 21st Century Cures Act to electronically confirm six facts about every in-home visit: who received the service, who delivered it, what service was delivered, where it took place, and the date and time it began and ended.

Each state chooses its own EVV model and aggregator, so what you must send — and to whom — is set by the state Medicaid program rather than nationally.

What is ABA EVV software?

Electronic Visit Verification — native to the ABA workflow.

ABA EVV software captures the who, what, where, and when of each session to satisfy Medicaid Electronic Visit Verification mandates. The difference is whether it is native or bolted on. Wilma® captures EVV on the same schedule your RBTs and BCBAs already use, applies state-specific rule packs, and lets verified visits feed billing directly — no second app, no manual reconciliation against a separate EVV portal.

Every visit verified — who, what, where, when.

Time- and location-stamped visit verification captured at clock-in/out, aligned to Medicaid requirements, attributed to the right staff and client.

Time + location

Geofenced clock-in/out where your state requires it.

Attributed

Visit tied to the right staff, client, and service.

Tamper-evident

A defensible record for Medicaid audits.

Offline-tolerant

Capture in the field; sync when back online.

EVV lives where the session is booked.

Because EVV is part of the same authorization-aware schedule as the rest of Wilma, there is no separate app to open and nothing to reconcile after the fact.

One workflow

Book, deliver, verify — in one place.

Authorization-aware

Verified visits checked against authorized units.

In-home + community

Designed for field-based ABA delivery.

Telehealth too

Virtual sessions verified on the same calendar.

Each state’s EVV rules, encoded per visit.

EVV requirements vary by state and aggregator. Wilma applies the right rule pack per visit so you are compliant wherever you operate, including multi-state.

Per-state rules

State-specific EVV requirements applied per claim.

Aggregator-ready

Built to align with state EVV programs.

Multi-state

Operate across states without workarounds.

Kept current

Rules maintained as state programs change.

Verified visits flow straight into billing.

A verified visit is a billable visit. EVV data feeds claims on the same record, so there is no export, no re-keying, and no mismatch between what was delivered and what was billed.

No re-keying

EVV data feeds the claim directly.

Match guaranteed

Billed = verified, on one record.

Denial prevention

Missing-verification gaps flagged pre-claim.

Clean audit trail

Visit-to-claim lineage for every session.

Buyer's Checklist

Evaluating ABA EVV software? Demand every line.

FAQ

Questions operators ask about ABA EVV.

What is ABA EVV software?

Is Wilma’s EVV built in or an integration?

Does it handle different state EVV requirements?

Does EVV work for in-home and telehealth sessions?

How does EVV connect to billing?

How much does it cost?

Is Wilma HIPAA compliant?

See EVV that doesn’t need a second app.

Thirty minutes. Bring your state’s EVV requirements — we’ll show verified visits flowing straight into billing.

Choosing an EVV setup

How to evaluate ABA EVV software

Electronic Visit Verification is a compliance requirement with an operational tail. The question is never whether a system has EVV — it is whether the verified visit and the billable session are the same object.

  • 1Is the verified visit the appointment, or a copy of it?When EVV runs in a separate app or a state aggregator portal, every day produces two lists that mostly agree. The ones that do not agree are unbillable visits, and they surface late — usually at month end, past the point where anyone remembers what happened. When verification happens on the appointment itself there is nothing to reconcile, because there is only one record.Red flag: EVV described as a scheduled export you upload somewhere on a cadence.
  • 2Does it match your state's programme specifically?EVV requirements, aggregators and data formats are set state by state and change. A practice operating across state lines needs each handled correctly rather than a generic implementation that satisfies none of them precisely. Ask about your states by name and ask when each was last updated.Red flag: A generic claim of being EVV compliant with no reference to specific state programmes.
  • 3What happens when verification fails in the field?Devices lose signal, batteries die, and clinicians arrive at homes with no coverage. You need a defined fallback that still produces a defensible record, and a queue of unverified visits that somebody owns — not a silent gap discovered when claims are rejected.Red flag: No offline capture, or a fallback that produces a visit no reviewer can later verify.
  • 4Does verification prove the visit was billable, or only that it happened?A verified visit delivered against an exhausted authorization, or by someone whose credential lapsed that week, is verified and still unbillable. Verification and billability are different checks, and the schedule has to enforce both at the point of booking.Red flag: Authorization balance and credential expiry visible in the record but not enforced when the appointment is created.
  • 5Who fixes it when the aggregator rejects a batch?Rejections happen for format and data reasons that are rarely the clinician's fault. Establish whether resolving them is your admin team's job or the vendor's, and what the turnaround looks like — that answer is most of your real EVV workload.Red flag: Rejection handling that lands in a shared inbox with no owner.

Before you sign

Questions worth asking on the demo

  • Show me a visit being verified on the appointment itself, not in a separate app.
  • Which state EVV programmes have you implemented for practices like mine, and when were they last updated?
  • What happens if the device has no signal at clock-in?
  • Where do I see unverified visits, and who works that queue?
  • Does booking check remaining authorization units and staff credential expiry?
  • When the aggregator rejects a batch, who resolves it and how quickly?

Glossary

The terms you will hear

Electronic Visit Verification
Electronic capture of who delivered a service, to whom, where, when and for how long. Federally required for certain Medicaid services and implemented state by state.
EVV aggregator
The state-designated system that collects visit data from providers. Some states mandate a specific aggregator; others accept data from provider systems directly.
Geofencing
Confirming a clock-in occurred within a set radius of the service address, used to satisfy the location element of verification.
Unverified visit
A delivered session whose EVV record is missing or incomplete. Generally not reimbursable until resolved, which is why the queue needs an owner.
Manual edit
A correction to a verified visit after the fact. Most state programmes permit these with a reason code and track the rate, because a high edit rate is itself an audit signal.
Authorization units
Billable 15-minute units a payer approved over a date range. A verified visit beyond the balance is still unbillable.

Keep reading

Related guides on running an ABA practice — the same operation, from a different angle.