Revenue Cycle Managed Services Billing Supervisor

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to extract content. First, identify sections: - About the role: The posting starts with description: "This position is listed on behalf of a partner company... This role provides frontline leadership..." etc. So we can put that as About the role. - Responsibilities: The "Accountabilities" section lists duties. So we can map to Responsibilities. - Requirements: The "Requirements" section lists education, experience, knowledge, skills. - Qualifications: Might be overlapping with Requirements. But we can separate: maybe Requirements = education/experience; Qualifications = certifications, preferred skills? However guidelines: Use headings only when posting has real specific content. We can decide to have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Pay and Schedule only if present. Pay: not mentioned specific salary; only "Potential eligibility for an annual performance bonus". That's not a specific pay figure, but it's a benefit. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention benefits: remote work, potential eligibility for annual performance bonus, additional benefits may be available, opportunity to lead team, exposure, etc. So we can include Benefits section. Pay: no specific salary or pay range, so we should not create Pay section. Schedule: mentions role is remote, occasional travel required. That's schedule info? Could be considered schedule (remote, occasional travel). The rule: never create Schedule section unless posting actually states them. It does state remote work and occasional travel. So we could include Schedule section with that info. However we need to avoid filler like "varies". It's specific: remote, occasional travel. So we can include Schedule. But we also have Benefits section already covering remote work etc. Might be duplication. Better to put remote work and travel under Schedule, and benefits under Benefits (bonus, etc). Let's see. The posting says: "The role is remote, with occasional travel required for client implementations, training, and onboarding activities." That's schedule/location. Also benefits list includes remote work opportunity within US, potential eligibility for annual performance bonus, additional benefits may be available, opportunity to lead team, exposure, etc. So we can separate. Thus sections: - About the role (paragraph summarizing role description) - Responsibilities (list of accountabilities) - Requirements (education, experience, knowledge, skills) - Qualifications (maybe certifications, preferred experience like Epic, bilingual, CPB/CRCR, managing offshore/nearshore, etc.) - Skills (maybe leadership, communication, etc.) But we could combine skills into Requirements or Qualifications. However we need to avoid thin sections. Let's see what content we have: Requirements section includes: - High school diploma or equivalent required; associate/bachelor's preferred. - At least 3 years healthcare billing, revenue cycle, patient accounting, or related experience, including 1-2 years in supervisory/team lead. - Strong knowledge of professional/hospital billing processes, claim submission workflows, payer requirements, reimbursement methodologies. - Experience working with Medicare, Medicaid, commercial, managed care, government payers. - Working knowledge of claim edits, denials, modifiers, coordination of benefits, eligibility verification, authorization requirements, billing compliance. - Experience with EHRs, practice management systems, clearinghouses, payer portals, Microsoft Office; proficiency with Excel and workflow reporting tools expected. - Epic experience preferred, familiarity with Cerner, Meditech, or other enterprise patient accounting systems valuable. - Ability to interpret payer policies, billing guidelines, remittance advice, operational reports, performance metrics. - Strong understanding of healthcare revenue cycle processes, reimbursement methodologies, applicable billing regulations. - Excellent leadership, communication, organization, time-management, problem-solving, decision-making skills. - Ability to manage teams across US and nearshore locations and foster accountability, collaboration, continuous improvement. - Experience supporting large, multi-facility health systems, physician organizations, or complex revenue cycle environments preferred. - Experience managing offshore or nearshore teams, bilingual English/Spanish capability, and a CPB, CRCR, or related revenue cycle certification are advantageous. - Ability to travel occasionally for client implementations, training, and onboarding activities. - Candidates located in California or Texas are preferred. Thus many items. We could split: Requirements = education, experience, core knowledge. Qualifications = certifications, preferred experience (Epic, bilingual, CPB/CRCR, managing offshore/nearshore, location preference). Skills = leadership, communication, etc. But many of those overlap. Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine into two sections: Requirements (includes education, experience, knowledge, skills) and Benefits (remote, bonus, etc). And maybe Schedule (remote, travel) but that's already in Benefits? Actually remote work is a benefit; travel is schedule. Could combine remote and travel under Benefits? But they said Benefits section only if posting actually states them. It does state remote work opportunity within US, potential eligibility for annual performance bonus, additional benefits may be available, opportunity to lead team, exposure, etc. So we can put those in Benefits. Travel could be considered part of Benefits? Not really. But we could put travel under Schedule. However we might avoid Schedule section if we can incorporate travel into Benefits as "occasional travel required". But that's not a benefit; it's a requirement. Might be better to have Schedule section for remote and travel. Thus we could have sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Check if we need Qualifications/Skills separate: we can fold them into Requirements. Thus output:

About the role

... paragraph ...

Responsibilities

• ... each accountability ...

Requirements

• ... each requirement ...

Benefits

• Remote work opportunity within the United States.
• Potential eligibility for an annual performance bonus for salaried employees.
• Additional benefits and perks may be available depending on employment terms.
• Opportunity to lead a team of billing professionals and contribute to complex healthcare revenue cycle operations.
• Exposure to multi-payer, multi-specialty, and multi-facility healthcare environments.
• Opportunities to support client implementations, workflow improvements, system enhancements, and operational transformation initiatives.
• Collaborative environment focused on professional development, accountability, and continuous improvement.

Schedule

• Remote role with occasional travel required for client implementations, training, and onboarding activities.

We must ensure we don't repeat job title as heading. Not include Job ID etc. Remove boilerplate like "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "This position is listed on behalf of a partner company..." that's part of About the role but we need to keep substantive info. The first sentence: "This position is listed on behalf of a partner company, who manages all applications and next steps." That's meta about application process; could be considered boilerplate? It's about partner managing applications; maybe we can drop as it's not substantive about role. But it's not explicitly boilerplate like legal; but it's about application process. The instruction: remove application instructions. That sentence is about partner managing applications; could be considered application instruction. Safer to drop it. So About the role should start from "Our partner is looking for a Revenue Cycle Managed Services Billing Supervisor based in United States." Actually that's also about partner. Might be considered meta. Better to start with "This role provides frontline leadership for healthcare billing operations across professional and facility billing environments." That's substantive. Thus About the role paragraph: combine sentences describing role, oversight, etc. Let's craft About the role paragraph: "This role provides frontline leadership for healthcare billing operations across professional and facility billing environments. You’ll oversee a team of 10–15 billing representatives across U.S. and nearshore locations, ensuring accuracy, productivity, and service quality. The position combines daily operational management with hands-on resolution of complex billing and claims issues. You’ll work closely with coding, accounts receivable, denials, patient access, and clinical operations teams to strengthen revenue cycle performance. Your work will directly support clean claim submission, timely reimbursement, regulatory compliance, and client outcomes. This is an opportunity to lead process improvements, develop billing talent, and contribute to complex healthcare revenue cycle initiatives." That seems good. Now Responsibilities: list each accountability from "Accountabilities" section. We need to extract each bullet: - Oversee daily billing work queues, including claim generation, editing, submission, rebilling, follow-up, and resolution of billing issues. - Monitor claim volumes, aging, productivity, service levels, unbilled accounts, charge lag, and other operational metrics to identify trends and improve performance. - Review and resolve billing edits, claim rejections, front-end denials, payer-specific requirements, authorization issues, modifier concerns, and other escalated claims. - Ensure accurate and compliant claim submission across Medicare, Medicaid, commercial, managed care, workers’ compensation, and other payer environments. - Conduct quality audits and ensure billing activities comply with HIPAA, CMS requirements, payer guidelines, state regulations, and organizational policies. - Prepare productivity, quality, timeliness, claim acceptance, and operational reports for leadership and support month-end close activities. - Lead, coach, train, and evaluate billing representatives while conducting team huddles, one-on-ones, performance discussions, and competency development activities. - Develop and implement action plans to address productivity, quality, attendance, or performance concerns and support continuous improvement initiatives. - Provide guidance on billing regulations, payer requirements, claim submission processes, reimbursement methodologies, and system workflows. - Collaborate with coding, patient access, accounts receivable, denials, cash posting, compliance, clinical operations, and client delivery teams to improve clean claim rates and reduce revenue leakage. - Partner with management and client leadership to identify operational challenges, escalate payer issues, and implement workflow improvements. - Participate in operational and client meetings and support system upgrades, implementation projects, workflow enhancements, and client transitions. Make each as

. Now Requirements: we need to list each requirement item as

. Let's list: - High school diploma or equivalent required; an associate or bachelor’s degree in healthcare administration, business, finance, or a related field is preferred. - At least 3 years of healthcare billing, revenue cycle, patient accounting, or related experience, including 1–2 years in a billing supervisory or team lead capacity. - Strong knowledge of professional and/or hospital billing processes, claim submission workflows, payer requirements, and reimbursement methodologies. - Experience working with Medicare, Medicaid, commercial insurance, managed care organizations, and government payers. - Working knowledge of claim edits, denials, modifiers, coordination of benefits, eligibility verification, authorization requirements, and billing compliance. - Experience with EHRs, practice management systems, clearinghouses, payer portals, and Microsoft Office applications; proficiency with Microsoft Excel and workflow reporting tools is expected. - Epic experience is preferred, with familiarity with Cerner, Meditech, or other enterprise patient accounting systems also valuable. - Ability to interpret payer policies, billing guidelines, remittance advice, operational reports, and performance metrics. - Strong understanding of healthcare revenue cycle processes, reimbursement methodologies, and applicable billing regulations. - Excellent leadership, communication, organization, time-management, problem-solving, and decision-making skills. - Ability to manage teams across U.S. and nearshore locations and foster accountability, collaboration, and continuous improvement. - Experience supporting large, multi-facility health systems, physician organizations, or complex revenue cycle environments is preferred. - Experience managing offshore or nearshore teams, bilingual English/Spanish capability, and a CPB, CRCR, or related revenue cycle certification are advantageous.