Reconcile Article 31 appointments to encounters and charges with a clear exception process for cancellations, missing notes, and duplicates.
Appointment reconciliation explains the path from scheduled care to documented services and reviewed charges without assuming those counts should always be equal. A clinic that simply compares three totals may find a mismatch without learning whether it represents missing work, a duplicate, or a legitimate difference.
For a New York Article 31 MHOTRS program, build the reconciliation around the services the clinic actually delivers and the way its staff document them. The purpose is to make handoffs visible. It is not to create a billable service from every calendar entry.
Article 31 appointment reconciliation needs defined units
Begin by defining appointment, encounter, service, charge, and claim line in the clinic's own systems. One group appointment may have several participants. A single patient visit may involve more than one documented activity. A charge can be held or corrected before a claim is submitted.
The OMH MHOTRS programmatic guidance describes program services and documentation. Use that reference with the clinic's policies to identify the expected record for each type of activity. Then ask the billing lead to map the corresponding administrative workflow separately.
Create a simple relationship table. For individual psychotherapy, record how the appointment relates to the patient's encounter and reviewed charge. For group care, record how the shared session relates to individual participation. Keep exceptional workflows explicit rather than forcing everything into the individual-visit model.
Build a dated activity ledger
Choose a date range and list the scheduled activity in scope. Include stable identifiers, service date, site, assigned professional, appointment status, encounter identifier, documentation status, charge status, and exception owner. Avoid using names as the only matching key.
Identify the date used for each comparison. An encounter documented on Wednesday for a Monday service can legitimately appear in different daily reports depending on the date field. A monthly comparison using service date on one side and charge creation date on the other will create apparent gaps even when all work is accounted for.
Retain enough history to explain rescheduled appointments and corrections. If the same appointment changes location or time, the reconciliation should not accidentally treat the old and new versions as two services. Ask the system owner how identifiers behave after edits.
Classify exceptions before assigning work
Separate exceptions into categories staff can resolve. A completed appointment with no encounter is different from an encounter with an unsigned note, which is different from a reviewed charge awaiting submission. Each has its own evidence and owner.
| Exception | First investigation |
|---|---|
| Appointment marked complete, no encounter | Confirm whether care occurred and whether documentation is elsewhere |
| Encounter without a matching appointment | Check walk-in, unscheduled, imported, or incorrectly linked activity |
| Documented encounter, no reviewed charge | Check nonbillable status, holds, and billing dependencies |
| More than one apparent charge | Check service structure, corrections, and possible duplication |
| Canceled appointment with clinical activity | Confirm whether the calendar status or encounter association is wrong |
Do not resolve every exception by changing a status until totals agree. The status should represent the facts of the encounter and the authorized administrative action, not a desired dashboard number.
Route clinical questions to clinical owners
Operations can detect a gap, but it may not know whether a service took place. A clinical owner should determine what happened and what documentation action follows under the organization's policies. Keep that distinction visible in the worklist.
For a fictional example, a clinician sees a patient during a same-day schedule change. The original appointment is canceled, and an encounter exists under the replacement slot. The correct resolution may be to link the existing record, not to create another encounter or charge.
Record the resolution reason and supporting identifier. If staff repeatedly investigate the same mismatch, that evidence can identify a configuration or training issue. A reconciliation process should improve the workflow over time rather than become permanent manual detective work.
Treat charge review as a separate control
The OMH MHOTRS billing and fiscal guidance provides a billing reference distinct from the clinical program guidance. Use current payer and program instructions when deciding how documented services become reviewed charges.
A note's presence does not establish that the service is payable. A charge's presence does not establish that the clinical record is complete. Keep coverage, provider, location, coding, authorization, and other applicable reviews in the clinic's billing process.
When evaluating software, ask what creates the charge and which changes cause recalculation or review. If a clinician corrects a service duration after a draft charge exists, determine who sees the change. A silent discrepancy between the note and charge is exactly the kind of handoff a reconciliation should detect.
Measure unresolved work with stable definitions
Report both the number of exceptions and the activity volume in scope. A growing clinic may identify more exceptions while improving its exception rate. Conversely, a declining count may simply reflect fewer encounters or a narrower filter.
Track opening exceptions, new exceptions, resolved exceptions, and ending exceptions. Group them by cause and owner. Use aging to identify stalled work, but name the date from which age is measured. The service date and the date the issue reached a reviewer are not interchangeable.
Sample resolved cases periodically under the organization's quality process. Check whether staff used the correct resolution reason and whether duplicates were handled without erasing legitimate history. Reconciliation is strongest when both the open and closed sides of the ledger are understandable.
Test the workflow with a small fictional day
Build a test day containing an attended individual session, a canceled session, a rescheduled visit, a group session, an unscheduled encounter, a nonbillable activity, and a corrected charge. Write the expected relationships before running the software report.
Have operations, clinical, and billing staff review the same ledger. Ask each person to identify their next action and the point at which responsibility passes to another role. If two people assume the other owns an exception, fix that ambiguity before launch.
Ease Health is the publisher of this guide and sells behavioral health software. Use the same test pack with any shortlisted vendor. Explore the RCM overview, unsigned note worklist guide, and Article 31 evaluation checklist for related context.
The deliverable is a reconciled activity ledger with explained differences and named owners for unresolved items. Equal totals can be reassuring, but explained records are what make the process useful.
Related reading
Frequently Asked Questions
Should appointments, encounters, and claim lines have identical counts?
Not necessarily. Cancellations, group sessions, multiple documented services, nonbillable activity, and claim structures can produce legitimate differences. Define the expected relationships for the clinic's own workflows.
Who should own a completed appointment with no encounter?
Operations can identify the exception, but a clinical owner should determine whether the service occurred and what documentation action is appropriate. Billing staff should not infer clinical facts to create a charge.
How often should reconciliation run?
Choose a cadence based on the clinic's volume, documentation process, and billing operations. A daily operational review and a broader periodic reconciliation may serve different purposes; document who handles each.
Does a reconciled encounter guarantee payment?
No. Reconciliation establishes that records follow the expected workflow. Coverage, coding, authorization, contract terms, and payer adjudication remain separate considerations.
