Billing operations guide
Create a payer portal access register for the revenue cycle team
A working register for payer portal accounts, roles, recovery paths, and access reviews that keeps the billing desk auditable.
On this page
Inventory every portal the team uses
Start the register with a complete list of payer portals, clearinghouse portals, and payment sites used by the billing desk. Include the payer name, the portal address, the business purpose, and the team that owns the relationship. Add the accounts used by outsourced staff as well as onshore reviewers. A portal that is missing from the inventory cannot be reviewed or recovered during an outage.
List each account separately instead of recording only a shared team login. Note whether the account is individual, shared, or service-based, and who can approve a new user. Record the enrollment or contract reference that gives the organization the right to use the portal. The register should answer why the access exists, not only who has it.
Record the access facts that matter
For each account, record the username, the role or permission level, the person assigned, the start date, and the last review date. Never store the password in the register. Use the approved password manager and record only the vault reference or recovery owner. Add the contact path for access problems and the expected response time.
Record which functions the role can perform, such as viewing claims, submitting appeals, updating enrollment, or changing bank details. A role that can change financial information needs a higher review standard than a role that can only read status. Capture the date the permission was last confirmed with the payer. Portal roles change quietly, so the register needs a review rhythm.
Separate user access from role permission
A person can have access to a portal without having permission to perform every task inside it. Keep the user record and the role record separate, because a transfer may remove one person and add another without changing the role. Review both layers when a team changes. A shared role with no named owner is a finding, even if every individual user is documented.
When a payer offers sub-accounts for different functions, map each sub-account to a business need and an owner. When the payer offers only one organization account, document the compensating controls such as a named operator, a second reviewer, and a session log. Do not describe a control as present when the portal does not support it. The register should state the limitation plainly.
Review access when people change roles
Run an access review when someone joins, leaves, changes teams, or stops working on a payer. Remove access on the last working day and confirm the removal with the portal administrator. Transfer ownership of any shared queue or saved search before the account closes. A departing user who remains in the portal is a risk that the register should catch.
Review the full register at least quarterly and after any major contract change. Compare the register to the payer's user list when the portal provides one. Investigate accounts with no recent activity, generic names, or owners who cannot confirm the business need. Record the reviewer and the date for each decision.
Test recovery before an outage
Test the password reset, multi-factor authentication, and administrator contact path before an outage forces a test. Confirm that the recovery email or phone belongs to a current employee or a monitored group mailbox. Record the last recovery test date and the person who ran it. An untested recovery path is an assumption, not a control.
Keep a current escalation contact for each payer and clearinghouse, including a backup when the primary contact is unavailable. Store the contact in the register and in the business continuity plan. Review the contact after a payer merger or portal migration. During an outage, the team should know who to call without searching old email.
Keep the register useful
Assign one owner to maintain the register and one reviewer to check it each quarter. Keep the format simple enough to update after every access change. Show the review status and the next review date at the top of the document. Link the register to payment posting and collections follow-up so staff know which portal supports each queue.
Respond when a portal access changes
A payer can change a portal role, require a new authentication step, or move the service to a new address with little notice. When that happens, update the register on the same day and note what changed. Tell the affected team which functions are unavailable and who is working on the fix. A register that is updated only at quarter end will be wrong when it is needed most.
If a user cannot complete a task because the role changed, do not ask them to borrow another person's login. Route the access request through the named approver and record the temporary workaround if one is approved. A shared login created during an outage often outlives the outage. The register should show any emergency access and its expiration date.
When a portal migration changes the administrator or recovery contact, verify the new path before closing the change. Test a password reset or a support contact with a low-risk account. Record the test date and the result. A migration that looks complete on paper can still leave the team locked out during a payer deadline.
Review the changed account at the next monthly check to confirm the new role works for the actual tasks. Ask the user to report any missing function instead of assuming the migration preserved it. Update the role description if the task has changed. The register stays useful when it reflects the work, not only the portal's account list.
Authoritative references
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