Billing Analyst

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to see if posting includes Pay, Schedule, Benefits specifics. It mentions "We Offer Competitive Compensation And Comprehensive Benefits." It lists benefits: competitive medical, dental, vision, life insurance; employee assistance program; 401K plan with company match; host of voluntary benefits. Also mentions hybrid remote/office work arrangement, new HQ in Charlotte, etc. It does not give specific pay numbers or schedule details (like hours). It mentions "Primarily office-based, with regular use of computer and standard office equipment. May participate in after-hours or weekend support during billing cutovers, migrations, or month-end cycles. Minimal travel may be required (up to 5%)." That's schedule-ish but not explicit schedule like "Full-time, 40 hrs/week". It's more work conditions. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits (list). It does not state specific pay numbers, but says "Competitive Compensation". That's vague but still mentions compensation. However "Competitive Compensation" is not a specific number; but it's still a statement about compensation. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits (list). It does state compensation (competitive compensation). It does not give explicit schedule but mentions after-hours/weekend support, minimal travel. Could we include a Schedule section? The posting does not explicitly state schedule like "Full-time" or "Monday-Friday 9-5". It mentions after-hours/weekend support, but that's more work conditions. Probably we should not create a Schedule section unless explicit schedule info. So we will include Benefits section (since we have specific benefits). Possibly also a Compensation/Pay section? The phrase "Competitive Compensation And Comprehensive Benefits." It mentions compensation but not specifics. The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation (competitive compensation). However it's vague; but it's still stating compensation. The instruction about filler/placeholder text: "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive Compensation" is not exactly placeholder but still vague. Might be considered filler? The rule says never emit a heading followed by filler/placeholder text. If we put a Pay section with just "Competitive compensation" that might be considered filler? It's not a specific number, but it's still a statement. I'd lean to include a Pay section with that statement, as it's substantive (they say they offer competitive compensation). However we also have Benefits section with details. We also need About the role, Responsibilities, Requirements, Qualifications, Skills sections. We need to parse the posting. Let's extract: Job description: The Billing Analyst plays a critical role... Reporting to the Billing Supervisor... ensures data accuracy, revenue assurance, operational efficiency through cross-functional collaboration... Key Responsibilities: bullet list under headings: - Billing Execution and Analysis - Execute monthly billing cycles across multiple business segments using SAP BRIM. - Review and validate rating, charging, and invoicing data to ensure accurate application of pricing, taxes, discounts, and contractual terms. - Perform detailed pre- and post-billing reconciliations to ensure invoice integrity and completeness. - Identify, document, and resolve discrepancies in source data, usage feeds, or customer hierarchies. - Data Validation and Quality Assurance - Conduct audits of billing data to ensure compliance with company policies, SOX controls, and tariff or contractual obligations. - Partner with IT, Finance, and Product teams to ensure BRIM master data (subscriptions, charges, price plans) are accurate and up to date. - Support revenue assurance activities, reconciling billed versus unbilled usage and validating invoice-level revenue alignment. - System Support and Continuous Improvement - Participate in User Acceptance Testing (UAT) and Operational Readiness Testing (ORT) during system releases, migrations, or new product implementations. - Identify and recommend process improvements or automation opportunities to enhance billing efficiency and accuracy. - Reporting and Collaboration - Develop and maintain billing dashboards and KPI reports to track cycle completion, accuracy rates, and exceptions. - Collaborate with Accounting, Collections, Customer Service, and Revenue Operations teams to support billing dispute resolution and ensure end-to-end transparency. - Communicate recurring issues, root causes, and recommended process enhancements to leadership. Company Description: At Brightspeed, we are reimagining... (the paragraph). We'll keep that as About the role? Actually "Company Description" could be considered About the role or About the company. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe combine company description and role summary). We'll include About the role with the description of role and company. Qualifications: Education & Experience bullet list: - Bachelor’s degree in Accounting, Finance, Business Administration, or a related field preferred, or equivalent combination of education and experience. - 2–4 years of experience in billing operations, preferably in telecommunications, SaaS, or subscription-based billing environments. - Experience with SAP BRIM modules (Convergent Invoicing, FICA, SOM) preferred. - Familiarity with telecom product hierarchies, usage-based billing, and taxation (E911, USF, SLED, etc.) is a plus. Skills & Competencies: bullet list: - Proficiency in Microsoft Excel (VLOOKUP, pivot tables, data validation, and reconciliation). - Strong analytical and investigative skills, with the ability to identify and explain complex data anomalies. - Excellent organizational and time management skills to manage concurrent billing cycles. - Effective communication and collaboration skills for cross-departmental interaction. - Working knowledge of SQL, Power BI, or Looker preferred. - Core competencies include: - Analytical Accuracy: Ensures precision in billing data and reporting. - Ownership & Accountability: Takes initiative in resolving issues and ensuring full billing cycle execution. - Collaboration: Works effectively with technical and business partners to maintain seamless billing operations. - Process Innovation: Seeks continuous improvement in efficiency and billing accuracy. - Customer Focus: Promotes transparency and trust through timely, accurate billing. Preferred Qualifications: bullet list: - Experience in telecommunications billing systems or enterprise-scale SAP BRIM environments. - Knowledge of financial reporting and revenue recognition principles. - Certification or formal training in SAP BRIM or related modules. Physical Demands & Work Conditions: bullet? It's a paragraph: Primarily office-based, with regular use of computer and standard office equipment. May participate in after-hours or weekend support during billing cutovers, migrations, or month-end cycles. Minimal travel may be required (up to 5%). This could go under a section like Work Conditions, but we don't have a heading for that. Could incorporate into Responsibilities or Qualifications? Probably better to include as a separate section like "Work Conditions" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put work conditions under Responsibilities or maybe under About the role. But we need to preserve all substantive information. We could add a

  under About the role describing work conditions. Or we could add a separate section like "Work Conditions" but that's not in the list; but the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.) implying those are typical but not exclusive? It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections. It doesn't say we cannot use other headings, but to be safe we should stick to those. So we need to fit work conditions into one of those sections. Perhaps under Responsibilities (as part of role) or under Qualifications (as part of experience). I'd put it under Responsibilities as a bullet about work schedule. But we also have a Benefits section: we have details about benefits. Pay section: we have "Competitive Compensation". Could include that. Schedule section: we have after-hours/weekend support, minimal travel. That's schedule-ish. Could include schedule info. But we must avoid creating sections with filler/placeholder text. The schedule info is specific: after-hours or weekend support during billing cutovers, migrations, or month-end cycles; minimal travel up to 5%. That's substantive. So we can create a Schedule section with that. Pay section: "Competitive Compensation" is vague but still a statement. Might be considered filler? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Compensation" is not exactly those, but it's still vague. However it's a statement about compensation. I'd include it. Now we need to remove duplicated lines: The posting repeats "WHY JOIN US?" and "We Offer Competitive Compensation And Comprehensive Benefits." twice. We need to deduplicate. Also remove EEO/equal-opportunity boilerplate, privacy notices, accommodation request, etc. We need to preserve all substantive information: company description, role summary, responsibilities, qualifications, skills, preferred qualifications, physical demands/work conditions, benefits, compensation, schedule (after-hours/weekend support, travel). Also maybe mention hybrid remote/office work arrangement, new HQ location, etc. That's substantive. We need to format using

  headings,

  • for lists,

    for prose. We must not include markdown code fences. We need to output only HTML fragment. Let's structure:

    About the role

    ... combine role summary and company description and maybe work location/hybrid.

    Responsibilities

    • ... each bullet.
    We have multiple subheadings within responsibilities (Billing Execution and Analysis, etc.). Should we keep those as subheadings? The instruction says use

    for section headings. It didn't forbid using

    for subheadings, but we could keep them as or just as part of list items. To preserve structure, we could keep them as

    inside the

    ? But that might be non-standard. Better to keep them as within list items or as separate

    but not required. Since the instruction only mentions using

    for section headings, we can use other headings for sub-sections if needed, but not required. To keep it simple, we can flatten