Skip to main content
Time & Attendance covers Electronic Visit Verification, exception maintenance, and aggregator export. This is where a planned visit becomes a verified one. Nothing bills until a visit clears here.

​
Who can use it

Organization Admins, Location Admins, Human Resources staff, and EVV Maintenance staff.

​
The exception queue

Above the tabs, the EVV maintenance queue lists visits needing correction. Work this queue daily — every unresolved exception is revenue that cannot be billed and, in Texas, an EVV compliance data point.

​
Tabs

Electronic Visit Verification records with clock-in/out, geofence results, reason codes, and aggregator status.Columns: Member · Attendant · Clock In · Clock Out · Units · Geofence · Status · Reason Code · Aggregator
Planned visit instances materialized from recurring schedules, with unit and conflict tracking.Columns: Member · Attendant · Date · Start · End · Units · Status · ConflictsConflicts flags visits that clash with an authorization limit or another assignment.

​
Working exceptions

A visit in EXCEPTION status needs a reason code before it can proceed to billing.
1

Open the exception queue

Start with the oldest. Aggregator submission windows are time-bound.
2

Identify why it failed

Common causes are a failed geofence, a missing clock-out, or units that exceed the schedule.
3

Apply the correct reason code

The reason code must reflect what actually happened. It is submitted to the state aggregator.
4

Confirm the visit reaches COMPLETED

Only completed visits without outstanding exceptions can bill.
5

Check aggregator status

A visit accepted locally still has to be accepted by the aggregator.
Reason codes are a regulatory record, not a way to clear a queue. Applying a code that does not match what happened misrepresents visit data to the state. If you cannot determine what happened, escalate rather than guess.

​
Geofence failures

A failed geofence means the clock event did not register at the member’s location. It does not by itself mean the visit did not happen — a wrong address on the member record produces the same result.
1

Check the member's address

An incorrect address in Members causes systematic geofence failures for that member.
2

Check whether care was delivered elsewhere legitimately

Some services are delivered in the community.
3

Apply the reason code that matches

Then correct the underlying address so the failure does not recur.

​
Where visits go next

See Billing and EVV to paid claim.

​
Troubleshooting

Scheduling

Where planned visits come from.

EVV matching

How verified visits become claim lines.