Billing operations guide

Schedule payer portal credential reviews around staff departures

A departure-driven access review that removes payer portal credentials quickly without breaking the billing queue.

Published 6 min read
On this page

Treat a departure as an access event

A staff departure is one of the few moments when payer portal access changes on a known date. Use that date to trigger a review instead of waiting for the quarterly access report. List every portal, clearinghouse, and payer site the person could reach, including shared logins they used but did not own. The goal is to remove access the same day while preserving the work that still needs an owner.

A shared login is the most common gap in this review. When three people use one portal account, removing the departing person from the team roster does nothing to the credential itself. Record who holds each credential and which individuals are authorized to use it. A portal account with no named owner should be disabled and replaced with individual access before the next billing cycle.

Build the departure checklist before it is needed

Write a checklist that covers the portal name, the account owner, the access level, the last login date, and the replacement owner for the open work. Add the clearinghouse administrator contact and the payer provider-services number for each site. Keep the checklist in the same place as the access register so the reviewer does not have to assemble it during a busy week. A checklist written during the departure is usually incomplete.

Include the recovery steps for multi-factor authentication and password resets. A portal that requires a code sent to a former employee's phone will lock the team out at the worst moment. Move the recovery contact to a role-based mailbox before the last day. Test the reset path on a non-critical portal so the team knows it works.

Reassign the work, not just the login

Open work in a portal is easy to forget because it lives behind a login rather than in the billing queue. Export the person's saved reports, draft claims, and open cases before access is removed. Assign each item to a named replacement and record the handoff date. A credential that is disabled while work is stranded creates a different kind of risk.

Give the replacement enough context to finish the item without the departing person. That means the claim numbers, the payer reference, the next action, and the deadline. A list of account numbers without a next step is not a handoff. Where the work is complex, schedule a short overlap session and record the decisions in the case notes.

Verify the removal and keep the evidence

After the last day, confirm in each portal that the account is disabled or the user is removed from the organization. Save a screenshot or an export of the user list with the date. Do not accept a verbal confirmation from a colleague as proof. The evidence should show the portal, the user, the action, and the reviewer.

Check the shared mailboxes and distribution lists as well as the portals. A password reset sent to a mailbox the person still controls is an open door. Remove the person from the billing alias, the payer notification list, and any vendor contact record. These small memberships are often missed because they are not labeled as access.

Review the register on a fixed rhythm

Run a quarterly review even when no one has left, because access tends to accumulate between departures. Compare the access register with the current team roster and with the portal user lists. Remove accounts that no longer match a role and add the ones that were granted informally. Record the review date and the person who performed it.

Use the quarterly review to test whether the departure checklist still matches the real environment. Portals add administrators, change multifactor requirements, and retire old sites. Update the checklist when a step no longer works. A register that is accurate in January and stale by June is not a control, and the next departure will expose the gap.

Close the gaps the checklist cannot see

Ask the departing person which portals they used outside the documented list. People often hold a personal bookmark or a vendor login that never reached the access register. Add every site they mention to the checklist and verify it with the portal owner. The exit conversation is one of the few chances to find shadow access.

Check the billing system, the clearinghouse, and the document storage separately from the payer portals. Access to a shared drive or a claim archive can expose more data than a single portal login. Remove the person from the groups that grant that access and confirm the removal with the system owner. A portal-only review leaves the largest stores of data untouched.

Record the date of the next scheduled review on the exit checklist. A departure review is a point-in-time action, while access accumulates continuously. The next quarterly review should start from the updated register rather than rebuild it. That continuity turns a one-time cleanup into a durable control.

Keep a short list of portals that require a separate administrator action, such as a delegate approval or a group removal. These steps are easy to miss because the main user account looks disabled. Assign each step to a named person and record the completion time. The extra list is small, but it closes the gaps that a standard disable action leaves behind.

Store the completed checklist with the access register rather than in the departing person's file. The next reviewer should be able to see what was removed and when without searching multiple systems. A simple folder with one file per departure is enough. That record answers an auditor's question in seconds and shows whether the process is actually followed.

Authoritative references

  1. FTC Business Guidance on Data Security
  2. NIST Cybersecurity Framework
  3. HHS HIPAA Security Rule
  4. CISA Identity and Access Management
  5. GAO Green Book

Philippines staffing intake

Define the role before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us