A former administrator may still have bank access. A location manager may be able to see payroll across the entire practice. An outside accountant’s temporary access may remain active long after a catch-up project ends.

A periodic financial access review asks a practical question: does each person or connected service still need the access it currently has? The practice owner or responsible manager reviews current permissions, approves what should remain, and tracks changes through verification.

For a staffed private medical practice, this is a financial-control workflow—not simply an IT exercise. It helps protect provider and administrative payroll, payment authority, bank information and financial reporting. A completed checklist documents the review; it does not establish regulatory compliance or guarantee that inappropriate access has been eliminated.

Define the Scope and Assign Responsibility

Start with systems that can move money, change financial records or expose sensitive financial information. Include every relevant location and legal entity, rather than assuming one accounting login represents the entire practice.

System or access point What to review Practice-specific concern
Banking and treasury portals Account visibility, payment initiation, approval, transfers and user administration A manager may need operating-account visibility but not authority over every entity’s cash
Payroll Employee details, pay-rate changes, payroll submission, bank-detail changes and administration Provider compensation and staff payroll may require different access
Accounting Viewing, posting, editing, closing periods and administering users A bookkeeper’s posting role does not automatically require payment authority
Bill payment and expense systems Vendor creation, payment-detail changes, payment release and card administration One person may hold several conflicting permissions
Financial reporting and shared folders Report access, exports, distribution lists and shared links A location manager may need a location P&L without practice-wide compensation details
Payer and payment portals used by finance Receipt reports, settlement information and account-change permissions Reconciliation access may be broader than the task requires
Connected applications and service accounts Purpose, owner, permissions and active connections An old connection may remain after a reporting or bookkeeping project ends

Name a review coordinator, usually the practice manager or finance lead. Assign a business approver who understands each user’s work, and identify the administrator authorized to implement changes. For sensitive access, the approver should not simply approve their own permissions without another responsible person’s review.

In a small team, one person may perform several roles. Make that limitation visible and arrange an owner review or another appropriate independent check.

Set a Risk-Based Schedule

Choose the review frequency with the practice’s financial, IT and other qualified advisers as appropriate. Consider payment authority, staff turnover, outside-adviser access, system capabilities and the complexity of the practice’s entities.

Higher-risk permissions deserve closer attention than limited report viewing. Document the chosen cadence and its rationale rather than treating an arbitrary interval as a regulatory deadline.

Also trigger reviews when circumstances change:

  • An employee leaves, changes roles or moves between locations.
  • An outside adviser’s engagement ends or narrows.
  • The practice changes banks, payroll providers or accounting systems.
  • A new location or entity is added.
  • An unexpected administrator, payment change or unfamiliar account appears.

Do not wait for the next scheduled review to handle a departure or suspected unauthorized access. Follow the practice’s offboarding or incident process promptly.

Run the Access Recertification Workflow

1. Obtain Current User and Permission Lists

Ask each system administrator for a current user export or available permission report. If exports are unavailable, document a controlled review of the user-management screens. Record the system, entity or account scope, extraction date and person who supplied the information.

Capture enough information to make a decision:

  • User name or internal identifier and account type.
  • Current role and employment or engagement status.
  • Assigned permissions and accessible locations, entities or accounts.
  • Administrator, payment and user-management authority.
  • Last activity, if available and meaningful.
  • Business sponsor for external users and connected services.

Include pending invitations, delegated access and report-sharing links where the system exposes them. A list of active employees alone will not reveal every access route.

Do not collect passwords, authentication codes, recovery keys or full banking credentials. Avoid screenshots containing unnecessary payroll or patient information. Keep the review file in a restricted location, not a broadly shared operations folder.

2. Match Each Account to a Current Person or Purpose

Compare the lists with the current staff roster, role assignments and external-adviser engagements. Resolve unfamiliar accounts with the relevant manager instead of guessing from an email address.

For every account, ask:

  • Who is responsible for this access?
  • What current task requires it?
  • Which location, entity or financial account does that task involve?
  • Is the current permission level necessary?
  • Should access end when a project or engagement ends?

A dormant account is a review flag, not automatic proof that access is unnecessary. An owner may use an approval account infrequently, while a connected service may operate without an ordinary interactive login. Confirm the purpose before making a change.

Shared staff logins make individual accountability difficult. Identify them explicitly and plan a transition to named accounts where supported. Do not disable a shared account without first understanding payment, payroll or reporting dependencies.

3. Review Permissions Against Actual Work

Evaluate what the user can do, not just the role label. “Standard user” may mean different things in different systems.

For example, a practice manager who reviews payer receipts may need settlement reports but not permission to change deposit instructions. A location manager may need a local P&L without access to other entities’ bank accounts. A payroll preparer may need to enter approved changes while a separate person reviews payroll before release, where the system and staffing allow.

Look particularly for combinations such as creating a vendor, changing its bank information and releasing its payment. Where separation is not practical, document an additional review, such as owner review of payment details and supporting records.

For multi-entity practices, confirm both system-level and account-level scope. Access to shared-cost reporting does not necessarily justify access to every entity’s banking or payroll details.

4. Confirm External Adviser and Service Access

Review accountants, bookkeepers, payroll advisers, temporary consultants and other external users individually. Confirm their current engagement, required work and practice sponsor.

Ask whether an old project account can be removed or narrowed. An adviser who previously cleaned up historical books may now need reporting access only—or no access at all.

For service accounts and connected applications, identify a responsible owner and the workflow they support. Coordinate changes with the administrator so that removing unnecessary access does not interrupt payroll posting, bank reconciliation or another necessary process. The review register should identify the connection without containing its secret credentials.

5. Approve, Implement and Verify Changes

Use clear decisions: retain, reduce, remove or investigate. Record a reason for each decision, especially when elevated access remains.

Assign every change to an authorized administrator and set a due date based on risk and operational dependencies. Escalate suspected unauthorized access through the appropriate incident process rather than leaving it in a routine task queue.

After implementation, verify the result using an updated user list or another suitable system record. An approval to remove access is not evidence that removal occurred. Where feasible, have someone other than the implementer verify sensitive changes.

Access-Recertification Checklist

Use this checklist for each review cycle. An unchecked item should remain visible as an open action or documented exception.

  • [ ] Confirm the systems, entities, locations and financial accounts in scope.
  • [ ] Assign the coordinator, business approvers, administrators and verifier.
  • [ ] Obtain current user lists and available permission details.
  • [ ] Match staff accounts to current roles and employment status.
  • [ ] Confirm external advisers’ engagements and business sponsors.
  • [ ] Identify dormant, shared, unfamiliar and pending accounts.
  • [ ] Review service accounts and connected applications with their owners.
  • [ ] Check administrator rights, payment authority and payroll-change permissions.
  • [ ] Check location/entity restrictions and financial-report sharing.
  • [ ] Record retain, reduce, remove or investigate decisions with reasons.
  • [ ] Assign remediation owners and risk-based due dates.
  • [ ] Verify completed changes and retain appropriate evidence.
  • [ ] Escalate unresolved items and approve any temporary exceptions.
  • [ ] Record manager sign-off and the next planned review.

Sample Manager Sign-Off Register

The following is an illustrative example, not a record of an actual practice. Use internal identifiers where practical and keep detailed evidence in a restricted repository.

System / scope User or account Decision and reason Approver Remediation owner / due point Verification and status
Banking / operating entity Former administrator Remove; employment ended Practice owner Bank administrator / urgent offboarding action Pending confirmation of removal
Payroll / practice-wide Payroll coordinator Reduce; preparation needed, release authority not needed Practice owner Payroll administrator / before next payroll submission Open; verify revised role
Reporting / location-specific Location manager Retain local P&L; remove unrelated entity reports Finance lead Reporting administrator / assigned review deadline Open; check report scope
Accounting / catch-up project External adviser Confirm ongoing need before recertification Practice owner Finance lead / before engagement renewal Investigate; engagement scope unresolved
Accounting connection Service account Retain; supports an active workflow Finance lead System administrator / next scheduled review Purpose and owner confirmed

The manager’s sign-off should identify the review period, scope, evidence location, completed actions and outstanding exceptions. Include who accepts each exception and when it will be reconsidered.

Distinguish review completed from remediation completed. A manager can finish reviewing the inventory while changes remain open, but should not describe all access as resolved until those changes have been verified.

Where AI Assistance Fits—and Where It Does Not

Access recertification is a human approval process. It differs from initial permission design, which establishes roles, and authentication, which checks a person’s identity when signing in. Reviewing access does not replace either activity.

If the practice has an approved tool and suitable data-handling arrangements, automated comparisons or AI-assisted analysis may help flag roster mismatches, inconsistent role labels or accounts requiring investigation. Those flags are review inputs, not final decisions. Incomplete exports, ambiguous names and legitimate exceptions still require human judgment.

Do not assume a tool can retrieve permissions, monitor activity or remove users unless those capabilities have been verified. Do not place patient-identifiable information or credentials into a general-purpose AI tool or ordinary Slack conversation.

Lucid Financials provides CPA-led bookkeeping, tax and CFO services for U.S. private medical practices, combining AI-assisted financial work with a human finance/CPA team and support through Slack. That financial support can inform discussions about staff responsibilities and location/entity visibility; it should not be confused with a verified access-governance or automated compliance service.

Keep Evidence Useful and Proportionate

Retain the review scope, source-list dates, decisions, approvals, remediation assignments and verification records in a controlled location. Choose retention practices with qualified advisers rather than assuming a universal period applies to every access-review record.

The IRS guidance on business recordkeeping supports complete business records and bank reconciliation. An access review complements those financial routines; it does not replace reconciliation or transaction review.

Where financial workflows involve patient information, minimize what enters the review file. The HHS guidance on the minimum necessary standard explains the standard and its exceptions. Obtain qualified guidance about applicable responsibilities rather than treating this checklist as a HIPAA determination.

FAQs

How often should a medical practice review financial access?

Set a documented schedule based on risk, payment authority, staff turnover and qualified advice. Supplement scheduled reviews with event-driven checks for departures, role changes, ended engagements and system changes. Do not postpone urgent access removal until the next routine review.

Should every dormant account be deleted?

No. First identify the owner and business purpose. Infrequent approval accounts and service accounts may still be needed. Remove or restrict access that lacks a current justification, while coordinating changes that could affect essential workflows.

Who should approve the practice manager’s access?

The practice owner or another appropriately authorized reviewer should assess it against current responsibilities. Avoid self-approval of elevated banking, payroll or administrator access. Document any staffing limitations and the additional oversight used.

Does a signed checklist prove compliance?

No. It records a control activity and its results. It does not prove every permission is appropriate, every change was implemented or every applicable legal obligation was met. Keep unresolved items visible and obtain qualified advice where needed.

Make the Review an Owner-Level Control

The useful outcome is not a signed spreadsheet alone. It is a current, justified access list, verified changes and clear ownership of unresolved issues. Start with the systems that can move money or change payroll, then work through accounting, reporting and connected services. That makes periodic access review a practical part of managing the practice’s finances.