Interview Questions to Ask a Billing Supervisor
Interview questions to ask a billing supervisor candidate, for whoever is hiring the person who will run the billing desk: an office or practice manager, a head of revenue cycle, a controller. They go in the order the conversation usually does, from the candidate's background and numbers, through denials and receivables, compliance, and systems and audits, to how they manage billers, then a few judgment calls and questions about the job itself to finish on. The wording assumes medical billing, and the notes point out where to change it if you are hiring for general invoicing.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Background
How large was the last billing team you ran, and what did it bill for?
Why ask it
Scale and type come first, because supervising three billers in a single-specialty practice is a different job from running twenty across a hospital's professional claims. Get the monthly claim or invoice volume and the number of payers or customers behind it, then set those figures beside your own.
Which parts of the revenue cycle did your team own, and which belonged to someone else?
Why ask it
Billing can mean everything from charge entry to collections or only claim submission, and a job title does not say which. Whatever sat outside their team, such as registration, coding, payment posting or patient statements, is work they have watched but not run. If your role includes it, ask who they would lean on while they learned it.
What numbers did your manager hold you to, and what were they when you left?
Why ask it
A supervisor who ran the team by its numbers can recite them: days in A/R, denial rate, clean claim rate, the share of receivables past 90 days. Payer mix and specialty move all of these, so do not grade the figures against a benchmark you read somewhere. Grade whether they know them and can say why each one moved.
Which specialties, payers or customer types have you billed for, and which would be new to you here?
Why ask it
Billing knowledge is narrower than a resume suggests: orthopedics, behavioral health and a lab each go wrong in their own ways. A candidate who names what would be new, and how long the last unfamiliar area took to learn, is giving you a truer answer than one who says billing is billing. For general invoicing, ask the same about contract billing, recurring invoices and usage-based charges.
What was sitting unworked when you took over your last billing team, and where did you start?
Why ask it
The order of repairs shows how they think. Someone who began with the oldest unworked claims was chasing cash, and someone who began at charge entry was stopping new errors at the source. Both can be defended, so ask why that one, and what they chose to leave broken for a while.
Did you come up through billing yourself, and which seat did you hold longest?
Why ask it
Many billing supervisors were billers first, and the seat they held longest is where their judgment is sharpest. Years in follow-up produce a different supervisor from years in charge entry or coding. Find out which seat on the team they have never worked, since that is where they will have to take a biller's word for it.
What is making you look for a new billing job now, and what would keep you in this one?
Why ask it
Hold the reason up against what the references say later. A system conversion, a merger that centralized the department and months of covering empty seats are all reasons billing supervisors give, and each says something different about what they will put up with. The second half tells you whether whatever drove them out is waiting in your office too.
Denials and A/R
Walk me through a claim from the visit to a zero balance, and tell me where it most often got stuck on your team.
Why ask it
Someone who has run the whole line names the stations in order: registration and eligibility, charge capture, coding, the scrubber, submission, the payer's decision, posting, the patient balance. The sticking point should come with a cause and something they did about it. For general invoicing, ask for the same walk from a finished order or timesheet to cash applied.
How long did a charge usually wait between the visit and the claim going out, and what held up the slow ones?
Why ask it
Charge lag never shows on an aging report, because a claim that has not been sent is not yet receivable. The usual holds are an unsigned note, a coding query nobody answered and charges entered in weekly batches. A charge held long enough runs into the payer's filing limit, so the part to press on is who chased the held ones and what happened when a provider did not reply.
What was your denial rate, how did you measure it, and what were the top three reasons?
Why ask it
Denials get counted by claim, by line or by dollars, so the method matters as much as the figure. The three reasons are the real test: a supervisor who watched denials knows them from memory, and they tend to be dull things like eligibility, a missing authorization or a modifier. Which of the three did they bring down, and how?
When the same denial keeps coming back, how do you find out where it starts?
Why ask it
Reworking a denial fixes one claim, and tracing it fixes the next hundred. A good answer travels upstream: to the front desk for insurance details, to the provider for documentation, to whoever maintains the charge master or the claim edits. A candidate who only describes faster appeals is running a repair shop.
How did you work with registration or the front desk on eligibility and authorizations?
Why ask it
Much of what billing has to repair is created before the patient is seen, by people the billing supervisor does not manage. You want to hear about something that crossed the wall: a weekly list of errors by cause, a shared checklist, a seat at their meeting. Blame with no account of what they tried is a preview of how they will treat your other departments.
How do you decide which unpaid claims your team works first?
Why ask it
Expect a rule with more than one part, such as dollar value, age, and how close the claim is to the payer's filing or appeal deadline. Oldest first on its own lets large fresh balances age, and biggest first on its own lets small claims expire. Then ask who built the work queues and how often the rule changed.
How did your office calculate days in A/R, and what moved the number while you were there?
Why ask it
The method comes before the figure, since offices divide by different periods of charges and some leave credit balances in. A number that fell because old balances were written off is not the same achievement as one that fell because claims went out clean. If they never knew the figure, find out who did.
How do you make sure no claim misses a payer's filing deadline?
Why ask it
Filing and appeal windows differ by payer and by contract, so the answer should start with where those limits were written down for the team. After that comes a report: claims with no response after a set number of days, or charges still unbilled past a certain age. The last claim that timed out, and what changed afterward, is the story to get.
Tell me about an appeal your team won that was worth the effort, and one you chose not to file.
Why ask it
The win shows they can read a denial, find the contract term or the clinical note that answers it, and get a letter read. The one they skipped shows they weigh staff time against the money at stake. Was there a written threshold for that choice, or did each biller decide alone?
How did your team catch underpayments, where the payer paid but paid less than the contract said?
Why ask it
Underpayments hide because the claim looks closed. Ask how posted amounts were compared with the contracted rate: fee schedules loaded in the system, a monthly sample, or nothing at all. Someone who has recovered money this way can describe the pattern they spotted and how they raised it with the payer.
How do you handle patient balances, from the first statement to the point you stop chasing?
Why ask it
This is where billing meets the people the practice serves, and the supervisor sets the tone. A full answer has a schedule of statements and calls, payment plans that someone approves, and a defined point at which an account goes to an agency or is written off. What a practice may do to collect depends on where it operates and who the payer is, so ask how those rules were taught to the team.
What did you do about credit balances and refunds that were owed?
Why ask it
Credits get ignored because working them sends money out instead of bringing it in. How quickly an overpayment has to go back depends on the payer and on where you operate, so do not quiz them on a deadline. Ask how often the credit balance report was run and who signed off on refunds, then put the same question to a reference.
Compliance
How do you keep up with payer policy changes, and how does a change reach the people keying claims?
Why ask it
Reading the bulletins is half of it. The other half is the route to the biller's desk: a note in the system, a new edit in the scrubber, five minutes at a huddle. The proof is the last change that altered how the team worked, and how long it took to show up in the claims.
How did coding and billing divide the work where you were, and what happened when a biller thought a code was wrong?
Why ask it
Some offices have certified coders, some have providers choose their own codes, and some expect billers to do it, so first learn which arrangement they know. The second half matters more. A doubtful code should go back to the coder or the provider with the reason attached, and a biller who changes it alone to get paid is the habit you are screening for.
A provider asks you to change a code or add a modifier so that a claim will pay. What do you say?
Why ask it
You are checking that they can refuse someone senior, and how they would go about it. A sound answer ties the code to what the documentation supports, leaves any correction of the note to the provider under whatever your amendment policy allows, and names who they would tell if the pressure continued. Who that person is depends on your organization, so say who it would be here.
Have you been through a payer audit or a records request, and what was your part in it?
Why ask it
A supervisor who has lived through one remembers the letter, the due date, who pulled the charts and what the payer took back. If they have not, ask how they would find out what their team's claims would look like to an auditor. In both cases you see whether a payer's request is a clerical chore to them or something to escalate the day it arrives.
Who on your billing team could see what, and what was allowed to go in an email?
Why ask it
Privacy rules for health and payment data depend on where you operate and what your payer agreements say, so ask what applied in their last job and how the team was trained on it. The habits are what you can judge: individual logins, the least detail possible in a message, statements checked before mailing. One more question pays off here: when did something last reach the wrong person, and what did they do that day?
Tell me about a billing error you found that had been working in your employer's favor. What did you do?
Why ask it
Finding money that may have to go back is the test of whether compliance is real to them. The answer you want has them sizing the problem, telling a named person and seeing it corrected, not fixing it quietly from that day on. What the organization then owes is a question for your compliance lead or counsel, and a good candidate will say as much.
Before an invoice went out, how did your team check it against the contract, the purchase order and what was delivered?
Why ask it
This one is for general invoicing, where it takes the place of the coding questions. The counterpart of a denial there is a disputed or rejected invoice, and the usual causes are a wrong rate, a missing PO number or billing before the customer accepted the work. Find out who did the checking and against which document.
Systems and audits
Which billing systems and clearinghouses have you worked in, and what could you do in them that your billers could not?
Why ask it
Product names matter less than depth. A supervisor should be able to build a work queue, write or at least specify a report, and maintain claim edits, not only key claims. If your system would be new to them, ask how long the last unfamiliar one took and what they did in the first month to learn it.
Which reports did you run every week, and what did you do when one looked wrong?
Why ask it
The usual set is an aging by payer, denials by reason, unbilled charges and something on productivity. Then ask for one occasion when a report sent them digging and what they found. A candidate with a list of reports and no discoveries was forwarding them.
What was your clean claim rate, and what did you change in the scrubber or the edits to raise it?
Why ask it
The term means claims accepted on the first pass, though some offices measure it at the clearinghouse and others at the payer, so ask which. The better half of the answer is the edit they added after seeing the same rejection over and over. Someone who never touched the rules was relying on whoever set the system up.
How did you audit your team's work: how many claims, how often, and chosen how?
Why ask it
A real audit program has a sample size per biller, a schedule, and a way of picking claims that the biller cannot predict. Ask what was scored, such as the right payer, codes carried over correctly, accurate posting and a follow-up note the next person could act on. Audits that happened only after something went wrong were investigations.
What error rate did you treat as acceptable, and what happened when someone went over it?
Why ask it
There is no universal figure, so the test is whether they had one and applied it to everyone, their strongest biller included. The sequence should be recognizable: shown the errors, retrained on them, audited again, then a formal step. New hires are the exception worth asking about, and how long that allowance lasted.
Which write-offs and adjustments could your billers post on their own, and which needed your sign-off?
Why ask it
Adjustments are the quietest way for receivables to shrink without any cash arriving. You are hoping for dollar limits by role, a short list of permitted adjustment codes, and a report of adjustments by user that somebody read every month. What turned up the last time they read it?
How did you reconcile what was posted against what reached the bank?
Why ask it
Payment posting is where a billing team touches money, which makes this a controls question. The strong version is a daily tie-out of deposits and electronic remittances to postings, done by someone other than the person who posted. Then ask about unapplied or unidentified payments and how old the oldest one was.
What did month end look like for your billing team, and what had to be finished before the period closed?
Why ask it
A supervisor who owned the close can list it: the month's charges entered, payments posted and tied to deposits, unapplied cash cleared, adjustments reviewed, then the reports to whoever reads them. How a close runs depends on the office's accounting, so listen for whether they knew what finance needed from billing and by which day. For general invoicing, add how they made sure work done in the month was invoiced in the month.
Have you been through a system conversion or a clearinghouse change, and what happened to cash while it was going on?
Why ask it
Conversions are where receivables swell, and a supervisor who has been through one knows the ways it goes wrong: claims stranded between systems, payer enrollments that lapse, a team working two aging reports at once. Ask what they would insist on before the next one. With no change planned on your side it still shows how they handle a bad quarter.
The team
How did you divide the work among your billers: by payer, by alphabet, by task or some other way?
Why ask it
Every split has a cost. Dividing by payer builds expertise and leaves you stuck when that person is out, while dividing by task is easy to cover and means nobody owns an account from start to finish. Why did they choose theirs, and would they choose it again for a team your size?
What productivity did you expect from a biller, and how did you arrive at that number?
Why ask it
Claims worked per day or accounts touched per hour mean little without a quality measure beside them, because touching an account is not resolving it. A good answer pairs the count with an outcome, such as dollars collected or claims closed, and was built by timing the work. Ask how a biller once gamed the count and how they noticed.
How do you train a new biller, and when do you let them work claims unchecked?
Why ask it
Stages are what you hope to hear: watching, then working with every claim reviewed, then a sample. The release point should hang on audit results, not on a number of weeks. Ask what a new hire is given in writing, because a team trained only by sitting beside someone inherits that person's shortcuts.
Tell me about a biller whose error rate was too high. What did you do, week by week?
Why ask it
The timeline is the answer. Note how soon they showed the person the actual errors, whether the retraining was aimed at that specific mistake, and when it was first put in writing. How did it end, and did the same error then turn up in anyone else's work?
How do you correct an experienced biller who has done something the old way for years?
Why ask it
Long-serving billers often know more payer history than the supervisor does, and they know that they do. A workable approach puts the denied claim on the desk instead of arguing from rank. A supervisor worth hiring can also tell you about a time the biller turned out to be right.
What do you do when a biller is sitting on the accounts they find hard?
Why ask it
Every team has a pile that gets opened and re-noted but never resolved. A supervisor finds it by reading the notes and pulling accounts with many touches and no payment, not by asking how things are going. Did they take the accounts away, work a few alongside the biller, or change how the queue was assigned?
Billing work is repetitive and the phone calls can be rough. What did you do to keep your good billers?
Why ask it
When an experienced biller leaves, what they knew about each payer's habits leaves too, so this is a question about cash as much as morale. Specific answers sound like rotating the patient phone line, showing each biller the dollars their follow-up brought in, or cross-training someone out of a queue they had worked for years. Ask how many people left in their last year and what each one said on the way out.
How much billing did you still do yourself, and how did you choose which work to keep?
Why ask it
On a small team a working supervisor will carry a queue, so what counts is which one. Keeping the hardest payer or the appeals is defensible, and keeping whatever they enjoy most is not. If they did none, ask how they stayed sharp enough to check other people's claims.
How do you cover the accounts when a biller is out for two weeks, or leaves?
Why ask it
Filing deadlines keep running on an absent person's accounts. Look for cross-training that was done before it was needed, payer notes kept somewhere shared, and a decision about which work waits. Their last open seat is the proof: how long it stayed open, and what the aging did in the meantime.
What would you put in front of a biller applicant to find out whether they can do the work?
Why ask it
Certifications and years of experience are the easy things to screen on, and neither is a test. Better answers involve a task, such as reading a remittance and saying what to do next, or finding the problem on a sample claim. You will inherit their taste in people, so ask about a hire that did not work out and what they missed.
Have you managed remote billers or an outside billing company, and how did you know the work was getting done?
Why ask it
Skip this only if neither applies to you. The answer should rest on output they could see: queue reports, audit scores, turnaround on denials. For an outside company, ask what the service agreement promised and what they did the first time it was missed.
Judgment and fit
A provider or an owner is angry that collections are down this month. How do you explain it?
Why ask it
Have them do it aloud while you play the provider. A good explanation separates what the team controls, such as charge lag and denials, from what it does not, such as fewer visits or a payer holding payments, and puts a number on each. Notice whether they defend the team or explain the month.
Tell me about a complaint over a bill that was escalated to you. What did you find when you opened the account?
Why ask it
Angry calls end up with the supervisor. You are watching for whether they looked at the account before defending it, and whether they will admit the bill was wrong when it was. Ask what changed afterward, since one confusing statement usually has many copies in the mail.
What authority would you need over hiring, write-offs and system settings to do this job well?
Why ask it
This brings a mismatch into the open before it becomes a resignation. Some candidates expect to pick their own staff and change claim edits, and your organization may keep those with HR, finance or IT. Say plainly what the role controls and see how they take it.
In your first month here, what would you read and who would you sit with before you changed anything?
Why ask it
Expect reports, such as the aging, denials by reason and adjustments by user, and people: a morning beside each biller and one at the front desk. A candidate who arrives with the plan already written is bringing their last office's fix. Then ask what they would act on in the first week regardless, such as claims about to pass a filing limit or cash nobody has posted.
What would you ask to see of our billing before you said yes to this job?
Why ask it
Experienced candidates ask for the aging by payer, the denial report, the count of unbilled charges, the staffing and how long the oldest vacancy has been open. Their list shows what they think the job is. Answer honestly, because a supervisor who walks into a worse backlog than the one described tends not to stay.
How to interview a billing supervisor candidate
Practical guidance for the conversation itself
Build the interview from your own reports
Pull three reports before you write a question list
Print your aging by payer, your denials by reason and your count of unbilled charges. Whichever looks worst tells you where to spend the hour: an aging heavy past 90 days or a pile of held charges points to Denials and A/R, a run of coding denials or payer take-backs points to Compliance, and errors scattered across billers point to Systems and audits and The team. A candidate's answer about days in A/R is also easier to weigh when your own figure is on the table in front of you.
Write down what this supervisor would own
Before the first interview, settle whether the job covers coding, payment posting, patient collections and the phones, or only claims and follow-up. Settle the authority too: who approves a write-off, who hires a biller, who can change a claim edit. Half the questions under Background are about matching their last job to this one, and you cannot match against a role you have not defined.
Choose twelve to fifteen
A billing interview of about an hour has room for that many, because nearly every answer about a rate or a report needs a second question behind it. Take two or three from Background to place the candidate, spend most of the time on the group your reports pointed to, and keep one from Judgment and fit for the end. In a second round, go to the groups you skipped and bring in the person who would be this supervisor's peer at the front desk or in coding.
Swapping the wording for general invoicing
Outside healthcare the structure holds and the vocabulary changes. A payer becomes a customer, a denial becomes a disputed or rejected invoice, days in A/R is usually called DSO, and the coding questions give way to the one about checking invoices against contracts and purchase orders. The questions on adjustments, credit balances, reconciling postings to the bank, month end, audits and managing billers can be asked as written.
Weighing what you hear
Numbers recalled, with a reason attached
A candidate who managed by the reports gives a denial rate or a days-in-A/R figure without reaching for it, and then tells you what moved it. Round numbers with no story are a sign the reports went to someone else. Do not mark the figures against an industry average: specialty, payer mix and how each office does the arithmetic change them too much for that to be fair.
Whether the story goes upstream
The strongest answers on denials, held charges and patient complaints end somewhere other than the billing office: at registration, with a provider's documentation, in a fee schedule nobody had updated. A supervisor whose stories all finish with the team working harder has been cleaning up the same problems on repeat.
Which part was theirs
Billing results belong to many hands, so 'we got denials down' can mean the candidate led it or sat nearby. Ask once, plainly, what they personally did: built the report, wrote the edit, ran the meeting with the front desk. People who did the work answer quickly and in detail.
Rules they state too confidently
Filing limits, refund deadlines, what may be said to a patient who owes money and how privacy rules apply all differ by payer, contract and place. A careful candidate says 'where I worked, the rule was' and tells you how they checked. Be wary of anyone who quotes a single rule as if it held everywhere, and check what applies to your own office with your compliance lead or your payer contracts, not from the interview.
A work sample, then the references
An aging report with the names removed
Strip anything that identifies a patient or customer, then hand over a page of your aging and ask what they would work first and what they would want to know. You are watching the order their eyes go in: the largest balances, the oldest buckets, one payer that looks out of line. Their questions back to you count as much as their plan.
One denial, read aloud
Give them a remittance line with a denial reason on it, again with identifiers removed. Ask what it means, what the biller should do next, and who outside billing needs to hear about it. A minute of this shows more about their working knowledge than several questions about experience.
A sample audit sheet
Ask them to sketch the form they would use to audit a biller: what gets checked, how it is scored, what happens with the result. Candidates who ran audits can draw one from memory. The sheet also gives you something concrete to compare across everyone you interview.
Carry the answers into the reference call
Take the figures and stories they gave you and check a few with a former manager: the team size, the days in A/R, how the conversion went, what the credit balance report looked like when they left. Ask too what happened to the team's numbers in the months after the candidate moved on.
Where this hire tends to go wrong
Choosing the best biller in the room
Speed and accuracy on their own claims are what got most candidates noticed, and neither is the job. The questions under The team exist to find out whether they can get that standard out of other people, including people who have been billing longer than they have.
Interviewing with nobody in the room who has billed
A practice manager or controller who has never worked a denial can be told almost anything about one. If that is you, borrow someone for the technical half: a coder, a billing lead from another office, or a senior biller for one round. Failing that, lean on the work sample, where a vague answer is harder to dress up.
Describing the backlog as smaller than it is
If the aging is in poor shape or two seats are empty, say so in the interview. The right candidate will ask sharper questions and may want the job more, and the wrong one will withdraw now instead of in month three.
Leaving compliance questions for a later round
The questions about changing a code under pressure and about errors in the employer's favor are uncomfortable, which is why they get postponed and then dropped. Ask at least two of them in the first full interview. A supervisor's answer there sets the limit of what their billers will feel free to raise.