ABA practice final pay separation and offboarding requirements in Oregon use different wage deadlines for a discharge or mutual termination, a resignation with at least forty-eight hours' notice, and a resignation with shorter notice. Estimates, disputed wages, promised benefits, unemployment requests, care continuity, supervision, PHI access, payer records, property, and health coverage require coordinated but distinct decisions.

In Oregon, the payroll clock starts before the farewell

A resignation or discharge can make an ordinary week feel suddenly compressed. The last home visit may be finished, but mileage, a caregiver call, supervision, a late note, an incentive, a device, and several payer accounts can still be open. ABA practice final pay separation and offboarding requirements in Oregon work best when the practice prepares the record before the employee's authority ends.

Begin with a dated account of who initiated the separation, the effective time, notice received, last authorized duties, available time records, pay method, promised benefits, active cases, supervision relationships, property, coverage, payer access, and systems. That shared record lets payroll move quickly without asking clinical or privacy work to fit inside a paycheck.

A discharge reaches the next business day quickly

Under the current Oregon wage-payment statutes, wages earned and unpaid after a discharge or mutual termination are due no later than the end of the first business day after employment ends. The BOLI final-pay page explains the same clock in plain language.

Count the business day from the actual effective event, not from the manager's later paperwork or the next payroll run. Payroll should know the date before the conversation whenever possible, with a workable delivery method and a named person who can authorize a correction.

Forty-eight hours of resignation notice changes the due date

When an employee without a definite-term contract gives at least forty-eight hours' notice, excluding weekends and holidays, Oregon generally makes final wages due on the last day. If that last day falls on a weekend or holiday, BOLI points to the next business day.

Preserve the notice exactly as received and calculate the excluded days rather than guessing. A practice that shortens a properly noticed resignation may create the discharge or mutual-termination clock, so counsel should review the actual sequence instead of relying on the label in the HR system.

Short notice uses the earlier of two routes

A worker who quits with less than the required notice generally must be paid within five days, excluding Saturdays, Sundays, and holidays, or on the next regular payday, whichever comes first. That is a different rule from simply waiting five business days.

Write both candidate dates on the separation record, identify the earlier one, and plan around payroll processing cutoffs. A calm explanation of the date and delivery method is much more useful than telling the worker that the payment is being handled.

Missing time records call for an estimate and a true-up

Oregon's statute addresses a practical problem: an employer may not have all the employee's time records by the accelerated deadline. The law provides an estimation route and then requires remaining earned wages within five days after the employee submits the records.

Use the best evidence available, document the assumptions, and invite a prompt correction. Schedules, EHR timestamps, messages, travel records, training logs, supervision records, and prior patterns can support a reasonable estimate. The estimate should protect timing, not become a low placeholder that nobody revisits.

A dispute does not freeze the amount everyone accepts

Section 652.160 requires the employer to pay, without condition and within the applicable termination deadline, the wages it concedes are due while leaving the disputed balance for resolution. A disagreement about one incentive should not hold ordinary salary, hours, or mileage hostage.

Separate each component on a working ledger: known wages, estimated work, leave or benefit pay, expenses, an incentive still under review, and any genuinely disputed amount. Give every unresolved item an owner, supporting record, and next review date.

ABA work can sit outside the appointment grid

A calendar of billable sessions rarely captures the whole final work period. Required documentation, parent communication, assessment preparation, supervision, team meetings, training, approved travel, and claim correction may all be compensable even when they never became a clean appointment row.

Compare the payroll record with the practice's operational evidence. The departing worker needs a private way to identify an omission, and the practice needs a way to investigate without restoring broad access or asking for unpaid cleanup after the employment relationship has ended.

Vacation and severance depend on promises already made

Oregon does not require an employer to create vacation, holiday, bonus, or severance benefits, but the current BOLI benefit guidance says an established policy or agreement must be honored. A balance in payroll is evidence, not the complete answer.

Retrieve the policy or agreement that applied while the benefit was earned, along with accrual history, eligibility terms, prior communications, and any consistent practice. A new exit memo cannot rewrite an older promise. Ambiguity belongs with Oregon wage counsel before the deadline.

Property return should not become informal leverage

A laptop, key, phone, purchasing card, assessment kit, or paper record may still be in transit while Oregon's short wage clock runs. BOLI cautions that employers may not delay wages as discipline or as leverage for employer property.

Use a prepaid return route, itemized custody list, remote security controls, and a courteous logistics contact. If the practice believes a lawful deduction may exist, counsel should review the facts and authorization while unaffected wages move on time.

Penalty exposure rewards preparation, not panic

Oregon permits continuing-wage consequences for a willful failure to pay final wages, subject to statutory limits and notice provisions. The point for an operator is not to predict litigation; it is to recognize that a late search for time records can become expensive.

Rehearse the workflow before a real departure. Managers should know whom to call, payroll should know how to issue an off-cycle payment, and the practice should have a narrow escalation path for uncertain commissions, leave, or deductions.

Frances Online and SIDES need a durable owner

The Oregon Employment Department's employer-responsibility page says former-worker information requests appear in Frances Online and may also move through SIDES. The agency uses the response to decide eligibility and displays questionnaires in the employer account.

Do not let the only login belong to the manager who just left or to an outside vendor nobody checks. Assign a monitored role, record the deadline shown on each request, submit the facts requested, and keep the confirmation with the separation file.

The unemployment story should be factual and modest

Oregon's employer guide explains that separation facts can affect a claim and the employer's tax account. The agency, not the practice, decides benefit eligibility. Medical labels, speculation, and unnecessary client details weaken rather than improve an employer response.

Build a short chronology from the resignation, notices, schedules, warnings if relevant, available work, final day, and separation payments. The worker-facing explanation, payroll record, unemployment response, and clinical handoff should recognize the same events even though they serve different purposes.

Care continuity gets its own clock

A pay deadline does not decide whether a client can safely continue tomorrow. The BACB Ethics Code supports responsible transition and continuity, while consent, competence, payer terms, privacy, and professional authority still govern who may deliver or supervise care.

A qualified clinical leader can review immediate communication and safety needs, select an interim contact, and decide which appointments continue, change, or pause. Families deserve a warm operational update without receiving the private reason for the employee's departure.

Supervision relationships need more than an inactive toggle

A departing BCBA, BCaBA, RBT, trainee, or mentor may remain connected to competency evidence, fieldwork verification, case oversight, signatures, and payer requirements. Deactivating the payroll profile leaves those relationships unresolved.

List every supervisee and affected case, confirm the last valid oversight, complete accurate records without backdating, and name a qualified successor or stop the activity. Legitimate verification should remain available after access closes.

PHI access should close along the route actually used

The HHS HIPAA audit protocol looks for termination procedures, changed access, returned devices, and supporting evidence. An ABA employee's route may include the EHR, scheduling, email, messaging, billing, payer sites, cloud storage, remote tools, doors, devices, and paper.

Before the effective time, compare the employee's real duties with every permission and document each cutoff or specifically approved transition window. Preserve authorship and audit logs. Security should prevent new unauthorized activity without erasing the history needed for treatment, payroll, supervision, and claims.

Payer offboarding often lags behind employment

A former clinician can remain visible in rosters, directories, authorizations, claim roles, portal permissions, supervision records, and later denial work. Oregon wage law does not set those payer effective dates.

Sort the payer inventory into past care, appointments still on the calendar, and services that have not begun. Use the current instruction for each insurer, retain its acknowledgment, and leave truthful historical attribution to the people who rendered, supervised, authored, or signed.

Coverage administration keeps a separate calendar

The federal COBRA employer guide generally brings a group health plan into COBRA when the prior-year employer count reached twenty. After an applicable event, the employer commonly has thirty days to notify the plan; Oregon continuation and the plan's own design may point elsewhere.

Ask the broker or administrator to confirm the governing route, coverage-loss date, recipients, election period, price, address, and delivery proof. The employee should receive a reliable contact instead of an improvised promise about continued coverage.

Cascade Learning Works loses a clinical coordinator

Cascade Learning Works is a fictional Eugene practice whose coordinator resigns on a Wednesday with less than forty-eight hours' notice. A weekend falls inside the period, one mileage report is missing, vacation follows a written policy, and the employee holds two payer logins plus a tablet.

The practice calculates the earlier statutory pay date, estimates the known mileage, creates a true-up path, reviews the benefit policy, and assigns different people to Frances, property, access, payers, supervision, and family calls. The example describes no real customer, worker, agency outcome, or legal conclusion.

A humane exit conversation reduces avoidable anxiety

The employee needs the effective time, remaining authorized duties, expected payment date and method, the basis of any estimate, benefit treatment, unemployment route, coverage contact, property process, confidentiality reminder, family transition, supervision contact, and a place to correct a fact.

Put the essentials in a form the person can keep, with language or disability access when relevant. Make room for an ordinary question. The practice can be direct about what remains under review without making earned wages depend on a release or continued work.

The closure file must outlive a manager's inbox

A later wage correction, benefit election, unemployment question, expense, tax form, payer update, device return, record request, or privacy concern may arrive after the team has reorganized. Personal notes and forwarded email are poor long-term controls.

Store the source event, work reconstruction, policy versions, calculations, delivery proof, agency submissions, benefit routing, access evidence, property, care and supervision handoffs, payer receipts, reviewers, and follow-up dates in a restricted record with clear retention ownership.

When something is wrong, repair the specific thing

If the practice finds a missed hour, bad estimate, leave error, inaccurate agency fact, lingering login, payer-date mismatch, or incomplete client handoff, define the affected person, period, amount, system, and evidence before acting.

Keep the first version so the history remains visible, protect the person from retaliation, and never manufacture an earlier date. Limit PHI while the responsible payroll, agency, benefit, security, insurer, or clinical lead makes the correction. Explain the change privately and leave a route for another factual concern.

Related resources

Sources