ABA practice final pay separation and offboarding requirements in Maryland generally require all wages due for work before termination by the payday that would have applied if employment had continued. Accrued leave payout turns on a specific written-policy and notice rule. Pay statements, deductions, unemployment requests, mass layoffs, clinical continuity, supervision, PHI access, payer records, property, and benefit coverage need coordinated but separate review.

Maryland keeps the ordinary payday while the exit keeps moving

The last client appointment can end days before an ordinary payday, yet the employee may still have notes, mileage, variable earnings, a benefit question, and access to several systems. ABA practice final pay separation and offboarding requirements in Maryland become easier to explain when payroll, unemployment, care continuity, and security are treated as related tracks rather than one final-day task.

A useful opening record names the separation event, effective time, last authorized work, regular payday, open earnings, promised leave, current cases, supervision, property, benefits, and every account the person can reach.

Final wages stay attached to the payday that would have applied

Maryland's current final-wage statute requires all wages due for work performed before termination by the day the employee would have been paid if employment had continued. The rule does not change with a discharge, resignation, or lack of notice.

Identify the actual pay period and payday before the conversation, then preserve the payroll calendar and delivery record. Earlier payment may be appropriate, but the ordinary deadline should not become a reason to postpone a known correction or leave the worker guessing about deposit timing.

Wages can include compensation beyond hourly time

Maryland defines wages broadly enough to include a bonus, commission, fringe benefit, overtime, and other compensation promised for service. A collection incentive or retention payment therefore needs its earning terms reviewed instead of being dismissed as future payroll.

Read the agreement that was in effect when the work occurred. Trace the service, remittance, milestone, approval, and any condition that remains genuinely open. Ordinary undisputed pay can move on time while a documented later calculation follows a named review date.

An ABA schedule is evidence, not the entire workday

Required documentation, caregiver calls, assessment preparation, supervision, training, authorized messages, travel, expense reconciliation, and claim corrections may not appear as billable visits. A final wage review that stops at scheduled sessions can miss work the practice required or accepted.

Payroll and the clinical lead can cross-check the time record against EHR activity, calendars, travel evidence, training history, oversight files, and approvals. Invite the worker to flag an omission privately, then investigate without asking a former employee to regain access or complete unpaid cleanup.

Vacation payout turns on a three-part written-policy rule

Section 3-505 allows nonpayment of accrued leave only when the employer has a written limitation, gave the required notice of leave benefits, and the employee is not entitled to payout under that policy. The state termination-pay guide explains that usable earned vacation is payable when no written policy limits it.

Find the version delivered at hiring, the employee's balance, prior use, and any vesting or forfeiture language. A newly written exit rule cannot repair missing notice. If policy language or past practice points in different directions, wage counsel should resolve the conflict before payroll closes.

Sick leave does not automatically follow the vacation answer

Maryland's guide treats unused sick leave as a contingency for illness rather than an automatic termination payment, unless a contract or employer policy provides otherwise. Combined PTO, front-loaded banks, and local leave rules can complicate that distinction.

Label each bank using the controlling document instead of the payroll system's shorthand. Record which hours were earned, which remained usable, what policy applied, and why an amount was or was not included. The explanation should be understandable without implying that every leave category receives identical treatment.

A shortened notice period is not automatically paid time

The state guide says an employer generally need not let a resigning employee work the entire notice period or pay for unworked notice time unless a contract, agreement, or policy says otherwise. That question is separate from wages already earned.

Preserve the resignation, the proposed last day, the practice's acceptance or acceleration, and any promise about notice pay. Clinical leaders should also state when treatment and documentation authority ended, because an early access cutoff must not quietly turn required final work into unpaid work.

Equipment is not collateral for the whole paycheck

Maryland describes deductions as extraordinary. The deduction guidance identifies court authority, law, commissioner approval, or express written employee authorization as the principal routes and cautions that other wage protections still apply.

A missing laptop, key, assessment kit, phone, or purchasing card deserves a secure return process, not an improvised wage hold. Use remote controls, itemized custody, prepaid return options, and counsel-reviewed deduction analysis while paying unaffected earnings on time.

The final statement should make the math traceable

Maryland's current pay-statement statute requires details such as the pay period, hours for nonexempt workers, rates, gross and net pay, deductions, and additional pay bases. A final statement should reconcile to the underlying time and variable-pay records.

Review the statement as a reader would. A worker should be able to see the covered period, rate, additional compensation, leave payout, and each deduction without decoding an internal label. Later compensation deserves its own equally clear statement when it becomes due.

An unemployment request brings its own stated deadline

Maryland sends a Request for Separation Information after a former employee files a claim. Current employer guidance directs employers to BEACON, SIDES, or mail, requires return by the due date on the notice, and describes a fee when the response is late.

Route the notice to a durable role rather than the departed manager's inbox. Preserve the actual due date, the submission, and its confirmation. If the agency asks for more detail, answer the question asked with dates and records rather than an argument about eligibility.

Severance language must match unemployment reporting

Maryland unemployment guidance treats several payments as severance, including dismissal pay, pay instead of notice, wage continuation, and other separation remuneration. The label on a private agreement may not control how the agency allocates it.

Keep earned wages, leave, expenses, incentive pay, notice pay, and severance on separate ledger lines. Report the amount, covered period, and payment date requested by the agency. The employee can then receive a clear explanation without the practice predicting the benefit decision.

A large reduction may trigger a separate state report

Maryland's employer page calls for a Dislocation Event Form when a mass layoff, including a temporary one, affects twenty-five or more workers. That state process is distinct from any federal WARN analysis and from individual claim responses.

Before a payer withdrawal, site closure, or program pause is announced, count affected workers and timing with counsel. Assign the mass notice, individual pay, unemployment replies, benefit routing, family transitions, and security work to named owners so one filing is not mistaken for the entire closure plan.

The separation story should remain recognizable to everyone involved

A useful response identifies who initiated the ending, the final work, relevant policy, prior communications, available work, and each separation payment. Medical speculation, character labels, or unnecessary client information make the record less reliable and more harmful.

Write a short chronology from source documents and allow a factual correction path. Payroll, the worker-facing explanation, unemployment submission, payer effective dates, and clinical handoff should describe compatible events even though the legal standards applied to them differ.

A family handoff can be warm without disclosing the dispute

The BACB Ethics Code supports responsible transition and continuity. It does not give a former employee continuing treatment, documentation, supervision, or family-contact authority after employment, consent, payer, privacy, competence, or professional conditions end.

A qualified interim clinician can review immediate safety, communication, and scheduling needs and decide which services continue or pause. A warm family message names the care contact and next step while keeping the private reason for the employment change out of the conversation.

Supervision may outlast the calendar event

A separating BCBA, BCaBA, RBT, trainee, or mentor may be linked to competency records, fieldwork verification, signatures, payer oversight, and active plans. Marking a person inactive in payroll does not settle those relationships.

Review every affected supervisee and case, identify the last valid oversight, complete accurate records without backdating, and appoint a qualified successor or stop instruction. Legitimate verification records should remain obtainable without leaving the former worker's credentials active.

Access removal needs evidence and a human owner

Termination controls in the HHS HIPAA audit protocol include changing access, recovering devices, and retaining evidence that the process occurred. In an ABA practice, the relevant path can include the EHR, scheduling, billing, payer portals, email, messaging, drives, remote tools, doors, devices, and paper.

Trace the person's real role before the effective time. Record each revocation and any narrow, approved transition window while preserving authorship and audit logs. The goal is to stop new unauthorized activity without erasing the history needed for care, supervision, payroll, or claims.

Payer offboarding follows payer time, not payroll time

A former clinician may linger in network participation, directories, open approvals, claim roles, oversight files, portals, denial work, or a later recoupment. Each payer may require a different form, notice route, and effective date.

Sort completed services from booked and future care, then follow each current payer instruction. Keep the confirmation. Historical claims should continue to identify the people who actually rendered, supervised, authored, and signed.

Benefit continuation belongs with the plan administrator

The federal COBRA employer guide generally applies to qualifying group plans after the prior-year twenty-employee threshold is met and commonly gives an employer thirty days to notify the plan of an applicable event. Maryland continuation, plan structure, beneficiaries, and coverage loss may change the route.

Have the broker or administrator confirm the governing program, last covered day, recipients, election period, price, address, and proof of delivery.

Harbor Point Behavior closes a satellite intake role

Harbor Point Behavior is a fictional Annapolis practice consolidating intake at its main office. The departing coordinator has unused vacation, a referral bonus under review, two payer accounts, a laptop, and responsibility for several family intake calls.

The practice anchors wages to the normal payday, reviews the written leave policy, keeps the bonus on a dated path, and separates unemployment, benefits, property, access, payer, and family work. This invented example describes no Finni customer and reaches no legal, agency, benefit, clinical, or employee conclusion.

A calm conversation gives the employee something usable

The worker needs the effective time, authorized remaining duties, pay date and method, open compensation, leave treatment, unemployment route, coverage contact, property return, confidentiality reminder, family transition, supervision contact, and correction channel.

Put the important details in writing, with language or disability access where relevant, and leave room for practical questions. The conversation can acknowledge uncertainty about a later bonus without making earned wages depend on a release or post-separation work.

Later questions need a record that survives inbox changes

A claim notice, benefit election, delayed commission, expense, tax form, payer correction, equipment return, records request, or privacy concern may arrive well after the last day. A personal spreadsheet or former manager's mailbox is a fragile place for those events.

Keep the reason, dates, reconstructed work, governing policies, statement and payment proof, agency submissions, plan routing, access evidence, property, client and supervision handoffs, payer confirmations, reviewers, and future checkpoints together in a restricted durable file.

Correction is a process, not a rewritten history

If the practice finds missing pay, a leave error, a late UI response, lingering access, a wrong payer date, or an incomplete transition, identify the affected worker or client, period, amount, system, and source before changing anything.

Choose one repair lead, preserve the original evidence, reject retaliation and backdating, protect PHI, and coordinate payroll, wage, unemployment, benefits, privacy, payer, and clinical reviewers. Tell the former employee privately what changed and how another factual concern can be raised.

Related resources

Sources