A three-provider dermatology practice called us in March because their biller of eleven years had gone on medical leave with two days' notice. The office manager opened the billing system and found 340 claims in a work queue she did not understand, a folder of payer portal passwords on a sticky note, and a spreadsheet named "denials FINAL v7." Nobody else knew which payers wanted corrected claims on paper, which secondary payers needed the primary EOB attached, or why every Tuesday she ran a report called "the Tuesday report."
That practice did not have a staffing problem. It had a documentation problem that looked like a staffing problem. Billing office standard operating procedures, or SOPs, are the written answer to "how do we do this here," and most practices under ten providers have none, or have a binder from 2016 that describes a billing system they no longer use. The knowledge lives in one or two heads, and it leaves when they do.
This piece lists the twelve SOPs we think every practice billing office should have, the format that gets them read, and the habits that keep them current. It is written for the practice manager or physician owner who has been meaning to do this for years.
Key takeaways
- An SOP is a one- or two-page instruction for a single recurring task, with an owner, a trigger, the steps, the system screens involved and the check that proves it was done.
- Twelve SOPs cover the recurring work of a small billing office, from eligibility verification to month-end close; write the ones with the highest cash impact first.
- SOPs go stale when they are stored as documents nobody opens; tie each one to a named owner and a review trigger (a payer bulletin, a system update, a denial trend) instead of a calendar date alone.
- The fastest way to find out whether an SOP works is to hand it to someone who has never done the task and watch.
What a billing SOP is, and what it is not
A standard operating procedure is a written description of how one recurring task is done in your office: the steps in order, the screens or reports used, the decisions along the way and the evidence the task is finished. It is not a policy ("we verify eligibility for every patient") and not a job description ("the biller posts payments"). Policies say what; SOPs say how, with enough detail that a competent new hire can do the task on their first day without asking.
The test we use is simple. If the person who usually does the task were out for a month, could someone else follow the document and get the same result? If the answer requires "well, she would know to check the Aetna portal first," the SOP is not finished.
Length matters. A 40-page procedure manual is a filing exercise; nobody reads it and nobody updates it. One task, one or two pages, screenshots where a screen is confusing, and a short "how you know it worked" line at the end. A dozen of those, kept in one shared folder with a table of contents, does more than any manual.
The twelve SOPs and who owns each one
The list below is what we build for a practice that has nothing. The order is roughly cash impact: the first four protect money before the claim leaves, the middle four move money after it does, and the last four keep the office honest. Each has a natural owner and a natural trigger for review.
| # | SOP | Typical owner | Runs | Review trigger |
|---|---|---|---|---|
| 1 | Eligibility and benefits verification | Front desk lead | 2 days before visit and at check-in | Payer adds or drops a plan; new clearinghouse |
| 2 | Prior authorization request and tracking | Clinical or referral coordinator | At order | Payer changes its PA list (often January and July) |
| 3 | Time-of-service collections | Front desk lead | Every check-in and check-out | Fee schedule or policy change |
| 4 | Charge capture and daily reconciliation | Biller | Daily | New service line, new provider, EHR update |
| 5 | Claim scrubbing and submission | Biller | Daily | Rejection rate rises; payer companion guide changes |
| 6 | Payment posting and ERA reconciliation | Payment poster | Daily | New payer EFT or ERA enrollment |
| 7 | Denial work by category | Biller or denial specialist | Daily, from the denial queue | New top-five denial reason |
| 8 | Appeals, with payer deadlines and templates | Denial specialist | As denials are upheld | Payer changes appeal address, form or deadline |
| 9 | Patient statements and payment plans | Biller | Statement cycle | Statement vendor or policy change |
| 10 | Credit balances and refunds | Payment poster and manager | Weekly review | Any payer recoupment letter |
| 11 | Credentialing and enrollment maintenance | Manager or credentialing lead | Monthly expirables check | New provider, new location, revalidation notice |
| 12 | Month-end close and KPI report | Manager | Monthly | Any change to the reports it depends on |
Practices with an in-house coder often add a thirteenth SOP for coding review and query, and surgical practices add one for surgical case posting. Do not add more than you will maintain. Twelve is already a lot for an office of three.
The one-page format that gets read
Every SOP we write uses the same eight headings, in the same order, so a reader knows where to look. It fits on one page, two at most with screenshots.
- Task and purpose. One sentence: "Verify eligibility and benefits so the patient is told the right amount at check-in and the claim goes to the right payer."
- Owner and backup. Names, not titles. If a name changes, the SOP changes.
- Trigger and timing. When the task starts (the appointment reminder run, the 835 file landing, the first of the month) and by when it must be done.
- Systems and access. The practice management system, the clearinghouse, each payer portal, and where credentials are managed (a password manager, never the SOP itself).
- Steps. Numbered, one action each, with the report name or screen name exactly as it appears. "Run Claims Rejected, Last 1 Day" beats "check rejections."
- Decision points. The forks: "If the patient's plan shows a deductible over $500 remaining, flag the account for the collections script."
- Proof of completion. What exists when the task is done: a report saved to a folder, a queue at zero, a log line.
- Last reviewed and by whom. Date and initials. This line is what tells a new manager whether to trust the document.
A worked example, abbreviated. SOP 6, payment posting: trigger is the daily 835 (the electronic remittance advice) import at 7:30; steps are to import, auto-post, then open the exceptions list and resolve each line by matching to the bank deposit; decision points cover a payment with no matching claim (post to unapplied and message the biller) and a zero-pay line with a CO-45 or PR adjustment (post the adjustment code exactly as received, never lump to "contractual"); proof of completion is that the posted total equals the deposit total on the bank feed for that day, written on the deposit log. That last line is the one that catches a misposted $4,000 in the same week instead of at year end.
Keeping SOPs current: triggers, not anniversaries
The usual plan is "we'll review the SOPs annually." It never happens, because January is busy and nothing forces it. Reviews tied to events work better. When a payer bulletin changes a prior authorization list, SOP 2 gets opened that week. When the practice management system pushes an update that moves a menu, whoever notices fixes the screenshot in SOP 5 that afternoon. When a new denial reason enters the top five on the monthly report, SOP 7 gets a new subsection. The review trigger column in the table above is that list.
Three mechanics make this stick. First, keep the SOPs where the work happens: a shared folder linked from the billing system's home screen or the office intranet, not a binder in the manager's office. Second, keep a change log at the bottom of each SOP: date, what changed, who changed it. Three lines a year is fine; zero lines in three years means the document is fiction. Third, put "SOPs touched this month" on the agenda of the monthly billing meeting so review is a habit that other people can see.
Resist the urge to make SOPs perfect before publishing them. A rough SOP that a second person has actually followed once is worth more than a polished one nobody has tested. Write the first draft in an afternoon by watching the person who does the task and typing what they do, including the things they say "everyone knows."
Using SOPs to train and cross-train
SOPs are the training plan. A new hire's first two weeks can be structured as "read SOP 1, do it with the owner watching, do it alone with the owner checking the proof of completion, sign off," repeated through the list in cash-impact order. Cross-training works the same way in reverse: each existing staff member is the backup on two SOPs they do not own and runs each of those tasks one day a month so the knowledge stays warm.
The sign-off matters for compliance as much as for competence. When an auditor asks how staff are trained on refund handling or on how patient balances are calculated, a signed SOP training record is a direct answer. Our RCM training courses are built around this idea: the exercises are the same recurring tasks, practiced in a training EHR where a wrong click costs nothing, so the person arriving at your office already knows the shape of the work and only needs your SOPs to learn the local version.
One caution. SOPs describe your office's process, not payer rules. Do not copy a payer's timely filing limit or appeal address into the body of an SOP where it will go stale silently. Keep a separate payer grid (one row per payer: filing limit, appeal deadline, appeal address, portal, provider relations phone) and have the SOPs point to it. Then there is one place to update when Aetna changes an address, not eight.
Questions we hear
We are three people. Is this really worth the time?
Three people is exactly when it is worth it, because any one absence removes a third of the office's knowledge. Budget an afternoon per SOP, two SOPs a week, and the set is done in six weeks. The first time one of you is out for a week and the claims still go out, the time is repaid.
Our billing is outsourced. Do we still need SOPs?
Yes, for the parts you still own: eligibility, collections at the desk, charge capture, authorization, the monthly review of the vendor's reports, and credentialing. Ask the vendor for their SOPs on the parts they own; a good medical billing partner has them and will share how denials and payment posting are handled for your account. If they cannot produce one, that tells you something.
Where should SOPs live so they are actually used?
In one shared, access-controlled folder with a table of contents at the top, linked from wherever staff start their day. Not in email, not in someone's personal drive, and never with passwords inside them. If your practice management system allows attachments to a home dashboard, put the link there.
What to do this week
- List the twelve tasks above and write next to each one the name of the only person who currently knows how to do it. Every name that appears alone is a risk.
- Pick the two SOPs with the highest cash impact where a single name appears and draft them this week by watching the owner do the task.
- Create the shared folder, the table of contents and the payer grid, and move any password out of any document into a password manager.
- Add "SOPs touched this month" as a standing line on the monthly billing meeting agenda.
- Hand one finished SOP to the person least familiar with the task and watch them follow it; fix what they stumble on before writing the next one.
