Accounts Receivable Analyst

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, etc. Also remove application instructions. Must preserve all substantive info. Let's parse the posting. Content: - Opening: "We are looking for an Accounts Receivable Analyst with a minimum of 2-4 years' accounting, accounts receivable, collections, customer service, or finance experience required. - Location: Coppell (onsite two days in office Tuesday/Wednesday)- 40 hours/week - start time 8-8:30 am- Project Length - 6-12 months with possible extension- W2/hourly rate with benefits" That's location, schedule, hours, start time, project length, compensation type. - "What you will work on" then bullet points (list). Actually they are sentences separated by periods. We'll treat as list items. - "What you will bring" then bullet points (list of requirements/qualifications/skills). - "What you can expect" includes inspirational place etc and compensation statement: "Compensation commensurate with your qualifications, experience, and other factors including geographic location, market and operational factors. Total Rewards include: Medical, Dental, Vision, Life Insurance, Disability Insurance, 401(k) Savings Plan, Employee Stock Purchase Plan, Professional Development Program, Paid Time Off and Paid Sick Time (in geographies where legally required)." - "What we do At RGP..." is company description, maybe not needed but could be considered "About the role"? Actually "About the role" is not present; we could put "About the role" as a heading for company description? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content. The posting includes "What you will work on" (Responsibilities). "What you will bring" (Requirements/Qualifications/Skills). "What you can expect" includes Benefits and maybe Pay (though compensation is vague). Also location/hours/project length could go under Schedule? Actually schedule includes hours/week, start time, onsite days. Project length maybe under Schedule or separate? There's no explicit heading for project length; we could include under Schedule or maybe a separate "Assignment Details". But we only allowed headings from list; we could put schedule info under Schedule heading. Pay heading only if posting actually states them; they say "Compensation commensurate with your qualifications..." which is vague, not specific numbers, so we should NOT create Pay section because it's not specific (commensurate with experience). The rule: 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 the posting actually states them. For Pay, they have vague statement, so we should not create Pay heading. For Benefits, they list specific benefits: Medical, Dental, Vision, Life Insurance, Disability Insurance, 401(k) Savings Plan, Employee Stock Purchase Plan, Professional Development Program, Paid Time Off and Paid Sick Time. That's specific, so we can create Benefits heading. Schedule: they have location, onsite two days, 40 hours/week, start time 8-8:30 am, project length 6-12 months with possible extension. That's specific enough for Schedule heading. So we can include Schedule. We also might include "About the role" heading for a brief description of the role? The posting starts with "We are looking for an Accounts Receivable Analyst...". That could be considered About the role. It's specific. So we can include About the role. Responsibilities: from "What you will work on". We'll list each bullet. Requirements/Qualifications/Skills: from "What you will bring". Could split into Requirements (experience, education) and Skills (MS Office, Excel, etc). But we can combine under Requirements heading or separate. The instruction: prefer a few substantive sections over many thin ones. So we could have Requirements covering experience, education, skills. Or we could have Requirements and Skills separate if they are substantive. Let's see: "Minimum of 2-4 years' accounting, accounts receivable, collections, customer service, or finance experience required" (experience). "Advanced MS Office suite (e.g. Excel, PowerPoint, Word) Excel skills needed: Pivots, lookups, shortcuts – power queries a plus. Will use PowerPoint and Word templates to put together client facing recaps." (skills). "Ability to reconcile multiple customer accounts efficiently" (skill). "Bachelor's degree in Accounting, Finance, or related field is a plus (not required)" (qualification). "Working knowledge of Commercial Finance industry or experience with financial analysis, accounting, accounts receivable, customer interaction, and technology preferred" (experience/knowledge). So we could have Requirements (experience + education) and Skills (MS Office, Excel, reconciliation). But to keep few sections, maybe combine into Requirements. However the instruction list includes Requirements, Qualifications, Skills as separate possible headings. We could include Requirements (experience), Qualifications (education), Skills (technical). That's three sections but each substantive. Let's decide. We need to avoid filler. All content is specific. Thus sections: - About the role (short paragraph) - Responsibilities (ul) - Requirements (experience) maybe combine experience and knowledge? Could be "Requirements" for experience and knowledge. - Qualifications (education) - Skills (technical) - Benefits (ul) - Schedule (ul or p? schedule details could be list) We must not repeat job title as heading. So no h3 for Accounts Receivable Analyst. We must not include Job ID etc. We must remove boilerplate: EEO statement, "What we do At RGP..." maybe considered company description but not required; could be omitted as it's not about the role? It's about the company; could be considered "About the role"? Not exactly. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "What we do At RGP..." is substantive about the company; but is it required? It's not about the role directly but could be considered part of posting. However typical job posting includes company overview; we could keep it under "About the role" or a separate heading like "About the company". But allowed headings list does not include About the company; only About the role. So we could incorporate that into About the role section. That would be substantive. Thus About the role could include both the role description and company overview. Let's craft About the role paragraph: "We are looking for an Accounts Receivable Analyst with a minimum of 2-4 years' accounting, accounts receivable, collections, customer service, or finance experience. The role is based in Coppell (onsite two days in office Tuesday/Wednesday), 40 hours/week with start time between 8:00‑8:30 am, for a 6‑12 month project with possible extension. RGP is a global talent solutions provider with over 2,600 experts across four regions, delivering on‑demand talent, next‑generation consulting, and outsourced services to Fortune 100 companies and emerging disruptors." That preserves details. Now Responsibilities: list each bullet from "What you will work on". Let's extract: - Responsible for ensuring alignment of billing and customer payment practices, accurate payment posting and timely resolution of discrepancies and disputes, while strengthening customer relationships and minimizing delinquency. - Primary point of contact for assigned accounts throughout the account life cycle: origination through termination. - Interact directly with customers, and internal departments to achieve reconciliation, financial analysis, problem solving and proactive account maintenance objectives for customer accounts. - Identify variances between billing and payments through effective account reconciliation and analysis following up with the customer to collect past due amounts or issue refunds when applicable. - Provide timely resolution of discrepancies and disputes to minimize delinquency and strengthen customer relationships. We'll put each as

. Requirements: experience: "Minimum of 2-4 years' accounting, accounts receivable, collections, customer service, or finance experience required." Also "Working knowledge of Commercial Finance industry or experience with financial analysis, accounting, accounts receivable, customer interaction, and technology preferred". Could combine. Qualifications: "Bachelor's degree in Accounting, Finance, or related field is a plus (not required)". That's a qualification. Skills: "Advanced MS Office suite (e.g. Excel, PowerPoint, Word) Excel skills needed: Pivots, lookups, shortcuts – power queries a plus. Will use PowerPoint and Word templates to put together client facing recaps." Also "Ability to reconcile multiple customer accounts efficiently". We'll list skills as bullet list. Benefits: list: Medical, Dental, Vision, Life Insurance, Disability Insurance, 401(k) Savings Plan, Employee Stock Purchase Plan, Professional Development Program, Paid Time Off and Paid Sick Time (in geographies where legally required). Schedule: details: Location: Coppell (onsite two days in office Tuesday/Wednesday); 40 hours/week; start time 8-8:30 am; Project Length - 6-12 months with possible extension; W2/hourly rate with benefits (but we already have benefits). Could include W2/hourly rate as compensation type but we avoid Pay heading. Could include in Schedule as note: "W2/hourly rate". That's specific enough? It's a compensation type but not a specific amount; still it's a detail about compensation type. The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state W2/hourly rate with benefits. So we can include that in Schedule or maybe a separate "Compensation type" but we don't have heading for that. We'll include in Schedule as part of details. Thus Schedule list: - Location: Coppell (onsite two days in office Tuesday/Wednesday) - 40 hours/week - Start time: 8:00‑8:30 am - Project length: 6‑12 months with possible extension - Employment type: W2/hourly rate Now ensure we don't include filler like "commensurate with experience". We avoided Pay section. Now produce HTML fragment: use

for each heading, then content:

for prose,

• for lists. We must not include or . Just output the fragment. Let's craft. Section About the role:

  About the role

  ...

  Responsibilities:

  Responsibilities

  • ...
  ...
  Requirements:

  Requirements

  • ...
  ...
  Qualifications:

  Qualifications

  ...

  (or could be list but single item). Use

  . Skills:

  Skills

  • ...
  ...
  Benefits:

  Benefits

  • ...
  ...
  Schedule:

  Schedule

  • ...
  ...
  Check that we didn't repeat job title. Good. Now ensure we preserve all substantive information: we included location, hours, start time, project length, W2/hourly rate, benefits list, responsibilities, experience, qualifications, skills, company overview. We omitted the "What you can expect" inspirational place sentence: "An inspirational place for you to do your best work, be engaged in meaningful ways, and continually develop the