Support Center - Accounts Receivable Supervisor

We need to output HTML fragment with sections: Benefits, Role Overview (maybe heading "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map sections accordingly. We have content: Benefits list: Free food & snacks, Wellness resources, 401(k) matching, Bonus based on performance. Also later "Benefits include: Full time - 40 hours Variety of shifts offered, between 6:00 am and 5:00 pm No nights or weekends Paid holidays, sick leave, and vacation days Health Reimbursement Account with monthly company contributions Monthly performance-based bonuses, in addition to base pay Paid parking at our downtown location Paid lunch breaks Advancement opportunities & internal growth Welcoming, open-minded, and low stress office environment Consistent customers that are happy with our services and book with us often Helping small business owners (our franchisees) - not just a huge corporate company". That's also benefits. So we need to combine all benefits into a Benefits section. We have Role Overview: "The Support Center AR Supervisor is responsible for the day-to-day management and performance of the Accounts Receivable (AR) function within the Support Center. This role ensures AR workloads are effectively prioritized and executed, program deadlines and service levels are met, and franchisees receive consistent, high-quality support. The AR Supervisor also leads AR team development, establishes best practices, and partners with the Support Center Director (SCD) to continuously improve the AR Program." We have Key Responsibilities: list of items. We have Key Performance Indicators (KPIs): list. We have Required Qualifications: list. We have also "Call Center Experience is a plus" maybe under Skills? Could be a skill. We have "Physical Requirements" maybe not needed? Not in allowed headings; we could drop as boilerplate? It's not EEO but it's physical requirement; maybe we can include under Requirements? But instruction: only include sections when posting has real specific content. Physical Requirements is specific; but not one of the allowed headings list. Could we put under Requirements? Probably better to include as a

after Qualifications? The instruction says use headings for those specific categories; other info can be in

. So we can put Physical Requirements as a paragraph after Qualifications. We also have "The position is full-time in-person/on-site." etc. That could be Schedule? Actually schedule is about hours/shifts. We have shift info in Benefits include: "Full time - 40 hours Variety of shifts offered, between 6:00 am and 5:00 pm No nights or weekends". That could be Schedule section. But we already have Benefits section; we could separate Schedule. The instruction: include a section ONLY when posting has real, specific content for it. We have schedule info: full-time 40 hours, variety of shifts between 6am-5pm, no nights or weekends. That's specific. So we should create a Schedule section with that info. Pay: we have "Monthly performance-based bonuses, in addition to base pay". Also earlier "Bonus based on performance". So we have pay info: base pay plus monthly performance-based bonuses. That's specific enough for Pay section. Thus sections: Benefits, Pay, Schedule, About the role (Role Overview), Responsibilities, Requirements (maybe Qualifications), Skills (Call Center Experience is a plus), maybe KPIs could be under Responsibilities? But KPIs is separate; we could make a section "Key Performance Indicators" but not in allowed headings list. Could incorporate into Responsibilities or Requirements? Probably better to make a separate section but heading must be from list; we could put KPIs under Responsibilities as a subsection? But instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. KPIs could go under Responsibilities (as part of responsibilities) or under Requirements? Probably Responsibilities. Qualifications: we have Required Qualifications list. Skills: Call Center Experience is a plus. We also have "Experience working in a fast-paced environment" maybe under Qualifications or Skills. We need to preserve all substantive info. So we need to include all details somewhere. Let's structure:

About the role

The Support Center AR Supervisor is responsible for the day-to-day management and performance of the Accounts Receivable (AR) function within the Support Center. This role ensures AR workloads are effectively prioritized and executed, program deadlines and service levels are met, and franchisees receive consistent, high-quality support. The AR Supervisor also leads AR team development, establishes best practices, and partners with the Support Center Director (SCD) to continuously improve the AR Program.

Responsibilities

• Outbound AR Communications: Meet weekly and monthly volume goals of customers contacted and interactions logged on SENet to partner with all franchisees enrolled in the AR Program.
• AR Operations & Workload Management: Organize and prioritize the AR team’s workload to consistently meet AR Program deadlines, performance expectations, and service-level requirements for SENet tickets and AR-related emails.
• Process & SOP Development: Develop, maintain, and continuously improve AR SOPs, workflows, and best practices for the AR Team and franchisees. Identify and implement opportunities to improve efficiency, response times, program adoption, and financial outcomes in collaboration with SCD.
• Team Onboarding & Development: Lead the onboarding and training of new AR Representatives. Maintain accurate and effective AR training materials and resources within FUSE.
• Performance Management: Conduct monthly check-ins and biannual performance reviews with AR Representatives, providing coaching and development while holding team members accountable to established KPIs, service standards, and job responsibilities.
• Franchisee Support & Engagement: Serve as an AR subject-matter expert for franchisees, helping resolve complex issues, increasing adoption of the AR Program, and promoting best practices that improve collections and franchisee satisfaction.
• Key Performance Indicators (KPIs):
• Days Sales Outstanding (DSO): ≤ 5 days
• AR Program Adoption & Engagement: ≥ 75% of franchisees opted in and actively engaged with the AR Program
• Franchisee Satisfaction: ≥ 75% satisfaction with the AR Program
• Invoice Activity: 100% of invoices interacted with at least once every two weeks
• Response Time: ≤ 45-minute median first-response time for all SENet tickets and AR-related emails

But we have nested ul inside li; maybe better to have separate section for KPIs but not allowed. Could make KPIs as a

after responsibilities? But we need to preserve all info. Could make a

Key Performance Indicators

but not allowed. However instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't explicitly forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect only those headings. Safer to stick to those. Thus we can embed KPIs as a

after responsibilities, maybe as a separate

but without heading. But we need to keep the KPI label. Could do

Key Performance Indicators (KPIs):

then
...
. That's okay. Now Qualifications:

Qualifications

• High School Diploma, or GED equivalent
• 2+ years working with account receivable
• 2+ years of management or lead experience
• Experience working in a fast-paced environment
Skills:

Skills

• Call Center Experience is a plus
Benefits: We need to combine both benefit lists. First list: Free food & snacks, Wellness resources, 401(k) matching, Bonus based on performance. Second list: Full time - 40 hours, Variety of shifts offered, between 6:00 am and 5:00 pm, No nights or weekends, Paid holidays, sick leave, and vacation days, Health Reimbursement Account with monthly company contributions, Monthly performance-based bonuses, in addition to base pay, Paid parking at our downtown location, Paid lunch breaks, Advancement opportunities & internal growth, Welcoming, open-minded, and low stress office environment, Consistent customers that are happy with our services and book with us often, Helping small business owners (our franchisees) - not just a huge corporate company. Note: Some of these overlap with Pay and Schedule. But we already have Pay and Schedule sections; we should avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all info, but we can allocate appropriately: Pay section for base pay + bonuses; Schedule section for shift details; Benefits section for other benefits like free food, wellness, 401k, paid holidays, health reimbursement, paid parking, paid lunch breaks, advancement opportunities, office environment, consistent customers, helping small business. We must not duplicate info. So we need to parse. Pay: base pay + monthly performance-based bonuses (also Bonus based on performance). So Pay section: base pay plus monthly performance-based bonuses. Schedule: Full time - 40 hours, Variety of shifts offered, between 6:00 am and 5:00 pm, No nights or weekends. Benefits: Free food & snacks, Wellness resources, 401(k) matching, Paid holidays, sick leave, and vacation days, Health Reimbursement Account with monthly company contributions, Paid parking at our downtown location, Paid lunch breaks, Advancement opportunities & internal growth, Welcoming, open-minded, and low stress office environment, Consistent customers that are happy with our services and book with us often, Helping small business owners (our franchisees) - not just a huge corporate company. Also maybe "Bonus based on performance" already in Pay. Now we need to output HTML fragment only. Let's craft. We'll have:

About the role

...

Responsibilities

...

Key Performance Indicators (KPIs):

...

Qualifications

...

Skills

...

Benefits

...

Pay

Base pay plus monthly performance-based bonuses.

Schedule

Full-time, 40 hours per week. Variety of shifts offered between 6:00 am and 5:00 pm; no nights or weekends.

Check we didn't miss any info: "Paid holidays, sick leave, and vacation days" included in Benefits. "Health Reimbursement Account with monthly company contributions" included. "Paid parking at our downtown location". "Paid lunch breaks". "Advancement opportunities & internal growth". "Welcoming, open-minded, and low stress office environment". "Consistent customers that are happy with our services and book with us often". "