An outside biller needs your practice software, clearinghouse and payer portals to do the job. This guide shows you how to grant that access so it stays personal, limited, logged and easy to shut off, with a checklist that saves your progress.
Last updated November 2026 · Reviewed by the PracticeAlpha billing team
Before a remote biller gets any login, have a business associate agreement that meets 45 CFR 164.504(e) reviewed by your attorney. Then give each person their own login in every system, turn on multi-factor authentication, set a billing-only role in your practice management software, keep payer portal and clearinghouse admin accounts in the practice's name, review user lists and audit logs every quarter, and disable every account the same day the biller leaves.
Picture a two-provider practice hiring a remote biller to clean up insurance AR. On day one that person needs the practice management system, the clearinghouse, several payer portals and the scanned EOBs: every patient's name, date of birth, subscriber ID and ledger, plus the ability to send claims under your NPI and tax ID.
The access is the whole point. A biller who cannot see the ledger cannot fix it. So the goal is not to keep the biller out. It is to make their access personal (tied to one named person), limited (only what the job needs), visible (logged and reviewed) and revocable (you can shut it off in an hour without breaking your billing).
Outsourcing does not move the responsibility off your desk. The Security Rule says a covered entity may let a business associate create, receive, maintain or transmit electronic PHI on its behalf only if it obtains satisfactory assurances that the information will be safeguarded, documented in a written contract (45 CFR 164.308(b)). Your practice is still the covered entity. If you are still deciding whether to bring billing outside at all, our guide to outsourcing dental billing covers the business side; this page is the security side.
The tool below follows the life of a billing relationship: before anyone gets a login, day one, every quarter, and the day the biller leaves. Your ticks save in this browser.
Tick what is already true for your practice. Progress saves in this browser, so you can finish it after talking to your IT provider or attorney.
0 of 0 done
1. Before access · 0 of 8
2. Day one · 0 of 8
3. Every quarter · 0 of 6
4. Offboarding · 0 of 8
HHS describes a business associate as a person or entity, other than a member of your workforce, who performs functions or services for a covered entity that involve access to protected health information. A billing company handling your claims fits that description. So does a subcontractor working for that billing company. HHS spells this out on its sample business associate agreement provisions page.
One wrinkle: a remote biller who is your own employee is part of your workforce, not a business associate, so your policies, training and access controls apply instead of a BAA. If the person is a 1099 freelancer, ask your attorney which bucket they fall into.
The required terms live in 45 CFR 164.504(e)(2), with security add-ons in 45 CFR 164.314(a). Here is what the contract must do:
| The contract must | What it means for a billing relationship | Cite |
|---|---|---|
| Establish permitted and required uses and disclosures | Say what the biller may do with PHI (submit claims, post payments, work denials) and nothing beyond it | 164.504(e)(2)(i) |
| Bar other uses or disclosures | No use outside the contract or what the law requires | (e)(2)(ii)(A) |
| Require appropriate safeguards and Security Rule compliance for ePHI | The billing company has to run its own security program, not just promise to be careful | (e)(2)(ii)(B); 164.314(a)(2)(i)(A) |
| Require reporting of unauthorized uses or disclosures, including breaches of unsecured PHI, and security incidents | They must tell you when something goes wrong | (e)(2)(ii)(C); 164.314(a)(2)(i)(C) |
| Flow the same terms down to subcontractors | Anyone they hire to touch your data signs the same restrictions | (e)(2)(ii)(D); 164.314(a)(2)(i)(B) |
| Support patient access, amendment and accounting of disclosures | If a patient requests records, the biller helps you meet your obligations | (e)(2)(ii)(E) to (G) |
| Follow Privacy Rule duties it performs for you | If they take on one of your obligations, they meet the rule for it | (e)(2)(ii)(H) |
| Open books and records to HHS | HHS can review their practices when checking your compliance | (e)(2)(ii)(I) |
| Return or destroy PHI at termination, if feasible | When the relationship ends, your data comes back or is destroyed, with no copies kept; if that is not feasible, protections continue | (e)(2)(ii)(J) |
| Authorize you to terminate for a material violation | You can end the contract if they break a material term | (e)(2)(iii) |
HHS published its sample provisions on January 25, 2013, and is candid about their limits: use is not required for compliance, they alone may not form a binding contract under state law, and relying on them does not replace consulting a lawyer. Treat them as a reference, not a form to sign.
The sample also flags terms worth raising with your attorney:
The rule puts a duty on you too. Under 164.504(e)(1)(ii), a covered entity that knew of a pattern of activity or practice by its business associate that was a material breach of the contract is out of compliance unless it took reasonable steps to cure the breach and, if those failed, terminated the contract if feasible. If you see your biller emailing unencrypted EOBs to a personal account and shrug, that knowledge is yours.
This guide explains the regulation; it is not legal advice. Have a healthcare attorney review any BAA before you sign it, especially if the billing company hands you its own template.
The technical safeguards section of the Security Rule lists unique user identification as a required implementation specification: assign a unique name and/or number for identifying and tracking user identity (45 CFR 164.312(a)(2)(i)). The word that matters is tracking. A shared login makes every action anonymous.
Here is how that plays out. Three people use a login called "billing." A large write-off shows up on a patient ledger in March. Nobody remembers it, the audit trail says "billing," and you cannot tell whether it was a legitimate adjustment, a mistake or something worse.
The fix is boring and effective: every human gets their own account in every system. If a system truly allows only one account, keep that credential in a business password manager, limit who can see it and change it every time someone with access leaves.
The rule also requires procedures to verify that a person seeking access to ePHI is the one claimed (164.312(d)). The section as currently published does not name a specific method. In practice, a password plus a second factor (an authenticator app, a hardware key or a push approval) is the most practical way to meet that standard when the person logging in is sitting in another city.
Turn it on for the remote access tool, email, the clearinghouse, any cloud PMS and every payer portal that offers it. Prefer an authenticator app or hardware key over text codes where you can.
This trap has nothing to do with hackers. A biller sets up the practice's admin account on a payer portal and enrolls their own cell phone for the codes. Months later they leave, and now nobody at the practice can log in as admin without that person's phone. The rule of thumb: admin accounts send codes to the owner or office manager. The biller's own sub-account sends codes to the biller. Never the other way around.
Not sure if outsourcing is worth it for your numbers? A free AR analysis shows you your real collection rate, days in AR, and how much is recoverable, before you decide anything.
Get a free AR analysisThe Privacy Rule's minimum necessary standard asks covered entities and business associates to make reasonable efforts to limit PHI to the minimum necessary to accomplish the intended purpose (45 CFR 164.502(b)). The Security Rule adds information access management: policies for granting access and for establishing, documenting, reviewing and modifying a user's access rights (164.308(a)(4)). In a dental office, that comes down to one question: what does the biller's user role allow?
Most practice management systems let you build user groups or permission sets. The menus differ between Dentrix, Eaglesoft, Open Dental and the cloud systems, so ask the vendor's support line to walk you through yours. Our practice management software guide covers the main systems.
| Task | Billing role | Notes |
|---|---|---|
| Create and send claims, attach x-rays and narratives | Yes | The core of the job |
| Post insurance payments and ERAs | Yes | Review postings in your monthly report |
| Insurance adjustments and write-offs | Yes, with limits | Set a threshold that needs your approval |
| Edit patient insurance and demographics | Yes | Needed to fix eligibility and subscriber errors |
| View clinical notes and charting | View only, if needed | Narratives need context; editing clinical records is not billing work |
| Delete or void posted payments | No, or with approval | One of the first places to look in an audit |
| Change transaction dates or edit closed periods | No | Lock past months if your software supports it |
| Edit fee schedules or provider setup | No | Changes ripple through every future claim |
| Export full patient lists or mass reports | No | Bulk exports are how data walks out the door |
| Security and user administration | Never | Only the owner or office manager |
The owner or office manager should hold the only administrator account, and that account should not be the one used for everyday work. Separation of duties helps too: the person posting payments should not also be the only person who can approve write-offs with no second look. That protects an honest biller as much as it protects you. Our list of common dental billing mistakes shows where unchecked access tends to bite.
Cloud-hosted systems such as Curve and Denticon are reached through a browser login. Server-based systems usually mean the biller connects to a computer in your office. Each route has its own weak spot.
| Method | Main risk | Minimum controls |
|---|---|---|
| Cloud PMS login in a browser | Stolen password; sessions left open on a home computer; downloads to a personal device | Individual login, MFA, automatic logoff, IP restrictions if the vendor offers them |
| Remote support app, attended (someone at the office approves each session) | Staff approve sessions without checking who is asking | Named accounts, MFA, a rule that only known users get approved, session history kept |
| Remote support app, unattended (always-on agent) | Anyone with the account gets in at any hour; agents get forgotten after the biller leaves | MFA, named accounts, a list of every machine with an agent, removal at offboarding |
| Remote desktop opened directly to the internet | Constant password-guessing attempts against an exposed port | Do not do this. Put it behind a VPN or a remote desktop gateway |
| VPN, then remote desktop | The biller's device effectively joins your office network | Practice-managed or vetted device, MFA on the VPN, access limited to one machine |
| Hosted virtual desktop | Depends on the provider's setup | BAA with the provider, MFA, copy and download controls |
Here is a scenario that costs real money. A biller sets up five payer portal accounts using their personal email, plus the clearinghouse login. They quit without notice. Now the practice has to go through account recovery with each payer, proving who it is, while claims sit unworked and some creep toward their timely filing limits. None of that is a hack. It is just ownership set up backward.
A one-page list does more than any policy binder. For each system, record who the admin is, which named users exist, where MFA codes go and when you last reviewed it. No passwords on the list; those live in a password manager or with each user.
| System | Admin | Users | MFA goes to | Last reviewed |
|---|---|---|---|---|
| Practice management system | Owner | Office manager, biller (billing role) | Each user | Quarterly |
| Clearinghouse | Office manager | Biller | Each user | Quarterly |
| Each payer portal | Owner or office manager | Biller sub-user | Admin to practice; sub-user to biller | Quarterly |
When billing happens in someone's spare bedroom, their laptop and their Wi-Fi become part of your security. The Security Rule requires physical safeguards for all workstations that access ePHI, to restrict access to authorized users (45 CFR 164.310(c)), and policies governing hardware and electronic media that contain ePHI (164.310(d)(1)). You cannot inspect a home office, but you can set expectations in writing and ask how they are enforced.
Encryption appears in the rule as an addressable specification (164.312(a)(2)(iv)). It also matters for breach notification. HHS's breach notification page explains that notification duties apply to breaches of unsecured PHI, and that its guidance specifies encryption and destruction as the methods for rendering PHI unusable, unreadable or indecipherable to unauthorized people. A stolen laptop that was properly encrypted under that guidance is a very different conversation from one that was not.
With a billing company, ask how they enforce these rules across their team. A policy document is easy to send; device management is what makes it real.
The Security Rule requires audit controls: mechanisms that record and examine activity in systems containing ePHI (45 CFR 164.312(b)). It also requires procedures to regularly review records of information system activity, such as audit logs, access reports and security incident tracking reports (164.308(a)(1)(ii)(D)). Logging is half of it. Somebody has to look.
That somebody is usually the owner or office manager, and thirty focused minutes a quarter covers the essentials.
Logs tell you who did what. Your billing reports tell you whether the results make sense. If write-offs climb while your collection rate drops, ask why. Our guide to dental billing KPIs explains which numbers to watch, and the billing health check gives you a quick baseline.
Keep a short note of each review. The Security Rule requires its documentation to be retained for 6 years from creation or the date it was last in effect, whichever is later (45 CFR 164.316(b)(2)(i)). Your access reviews belong with that documentation.
The Security Rule lists termination procedures as an addressable specification: procedures for terminating access to ePHI when the employment of, or other arrangement with, a workforce member ends (45 CFR 164.308(a)(3)(ii)(C)). For a remote biller, the hard part is not the principle. It is remembering every place they had access.
Say your biller quits by text at 4 p.m. on a Friday. This is the order to work in.
| When | Step |
|---|---|
| Within the hour | Disable (do not delete) the PMS user so the audit trail stays attached to their name |
| Within the hour | Revoke remote access and remove any unattended-access agent from office computers |
| Within the hour | Disable their email, fax and shared-drive access |
| Same day | Remove their clearinghouse user and every payer portal sub-user |
| Same day | Change every password they ever saw, including shared ones and any admin password they were given |
| Same day | Remove their phone or authenticator from MFA on every account |
| Within a week | Collect the handoff: open claims, appeals in progress with deadlines, the aging report, payer correspondence and call reference numbers |
| Within a week | Get written confirmation that practice PHI was returned or destroyed, as the BAA requires |
| Within a week | Review the last 30 days of activity in the PMS and remote access logs |
| Within a week | Update the credentials inventory and note what changed |
The other half of offboarding is revenue. Pull the insurance aging report the day they leave and sort by age; anything drifting toward 90 days and beyond gets worked first, because filing and appeal deadlines do not pause for staffing changes.
With a billing company, the person on your account can change without you hearing about it. Ask that the service agreement require them to tell you when someone assigned to your practice leaves and to remove that person's access to your systems. Our guide on what to look for in a dental billing company includes the questions to ask up front.
The HIPAA Breach Notification Rule, at 45 CFR 164.400 to 414, requires covered entities and business associates to provide notification after a breach of unsecured PHI. Know its shape before something happens.
A breach is generally an impermissible use or disclosure that compromises the security or privacy of PHI. An impermissible use or disclosure is presumed to be a breach unless you can show a low probability that the PHI was compromised, based on a risk assessment of at least four factors (45 CFR 164.402):
There are three narrow exceptions; let your attorney decide whether one applies.
| Who | Notifies | Deadline |
|---|---|---|
| Billing company (business associate) | Your practice | Without unreasonable delay, no later than 60 calendar days after discovery (164.410(b)) |
| Your practice | Affected patients | Without unreasonable delay, no later than 60 calendar days after discovery (164.404(b)) |
| Your practice | Prominent media outlets | Only if more than 500 residents of a state or jurisdiction are affected; same 60-day limit (164.406) |
| Your practice | HHS | 500 or more individuals: at the same time as patient notice. Fewer than 500: log it and report within 60 days after the end of the calendar year (164.408) |
The business associate's notice must identify, to the extent possible, each individual involved. HHS notes the covered entity stays responsible for patient notices but may delegate sending them to the business associate; settle that in the BAA. The 60 days is a ceiling, not a target, which is why a shorter reporting window is worth negotiating into the BAA.
A breach is treated as discovered on the first day it is known, or would have been known with reasonable diligence. For a covered entity, knowledge of a workforce member or agent (other than the person committing the breach) counts (164.404(a)(2)). Whether your billing company counts as your agent here is a legal question that can move your start date; ask your attorney before you need the answer.
When you interview a billing company, ask to see its BAA, who exactly will log in to your systems and how it handles staff changes. At PracticeAlpha, a dedicated, US-based team is assigned to each practice and works inside your existing software, so the names on your user list belong to a team assigned to you. To see what your AR looks like before you hand anyone the keys, our free AR analysis takes 30 minutes.
If the biller is an outside company or contractor performing billing for your practice with access to patient information, HHS describes that as a business associate relationship, and the HIPAA Rules generally require a written business associate agreement before access begins. If the biller is your own employee working from home, they are part of your workforce instead, and your policies and training apply. Ask your attorney to confirm which category a freelancer falls into.
It must set the permitted uses and disclosures of PHI, bar other uses, require appropriate safeguards and Security Rule compliance, require reporting of unauthorized uses and breaches, flow the same terms to subcontractors, support patient access, amendment and accounting requests, open records to HHS, require return or destruction of PHI at termination if feasible, and let the practice terminate for a material violation. Have an attorney review the final agreement.
No. The Security Rule lists unique user identification as a required specification at 45 CFR 164.312(a)(2)(i), so each user can be identified and tracked. A shared login makes every action in your practice management system, clearinghouse or payer portal anonymous, which means you cannot tell who posted a payment, made an adjustment or deleted a transaction. Give every person their own account in every system.
The Security Rule requires procedures to verify that a person seeking access to electronic PHI is who they claim to be (45 CFR 164.312(d)), and the section as currently published does not name a specific method. Multi-factor authentication is the most practical way to meet that standard for someone logging in remotely. Turn it on for remote access, email, the clearinghouse, cloud software and any payer portal that offers it.
It can be, with the right setup. Avoid opening remote desktop directly to the internet; place it behind a VPN or gateway instead. Use named accounts with multi-factor authentication, keep session logs, set automatic logoff after inactivity, and turn off file transfer and clipboard sharing unless they are needed. Keep a list of every computer with an unattended access agent so you can remove them when a biller leaves.
The practice should. Register the clearinghouse account and every payer portal administrator account to the practice, using an email address on a domain the practice controls, with the owner or office manager as administrator. Give the biller individual sub-user access. If a biller creates these accounts under a personal email and then leaves, the practice may face account recovery with each payer while claims go unworked.
Within the hour, disable their practice management login rather than deleting it, revoke remote access and disable email and fax access. The same day, remove clearinghouse and payer portal users, change any password they saw and remove their device from multi-factor authentication. Within a week, collect a handoff of open claims and appeals, get written confirmation that PHI was returned or destroyed, and review the last 30 days of activity.
Under 45 CFR 164.410(b), a business associate must notify the covered entity without unreasonable delay and in no case later than 60 calendar days after discovering a breach of unsecured PHI. That is an outer limit. HHS's sample agreement language notes that parties may agree to a stricter reporting timeframe, so ask your attorney about writing a shorter window into the business associate agreement.
It is safer if they do not. A shared or personal computer may lack encryption, updates and screen locks, and may be used by other people in the household. Ask for a work-only device that is practice-managed or managed by the billing company, with full-disk encryption, automatic screen lock and current updates, and set a rule that reports and EOBs are never downloaded to the local drive or printed at home.
At least quarterly, plus every time someone joins or leaves. The Security Rule requires regular review of system activity records such as audit logs and access reports (45 CFR 164.308(a)(1)(ii)(D)). A practical quarterly review compares user lists to current people, checks the audit trail for deleted payments and large adjustments, looks for logins at odd hours and confirms permissions still match the job. Keep a short note of each review.
Free AR analysis. We pull your aging report, calculate your real collection rate, days in AR, and denial rate, and show you whether outsourcing would actually move the number. 30 minutes. No commitment.