Accounts Receivable Manager

We need to output HTML fragment with sections: About the role (maybe "About the role" heading), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: About The Role (description). Role Responsibilities (list). Required Experience (list). Nice to Have (list). Benefits (list). Estimated Starting Salary Range (Pay). No explicit Schedule info (though hybrid position based in Columbia, mention hybrid schedule may make commute workable). That's schedule info: hybrid schedule. So we can include Schedule section with that detail. Also maybe location info? Not required. We must not repeat job title as heading. Use

for each section heading. Use

• for lists. Use

  for prose. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: EEO, Export Control, Recruiting Fraud Alert, etc. Also remove navigation, cookie, legal. Also remove duplicated lines. We need to include sections: About the role, Responsibilities, Requirements (maybe combine Required Experience and Nice to Have? But we can have Requirements heading with required experience list, and maybe Skills heading with AI & Automation Fluency etc? However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have About the role (prose). Responsibilities (list). Requirements (list of required experience). Qualifications maybe similar to Requirements; but we can combine. Skills maybe list of specific skills (NetSuite, Excel, AI tools). Benefits list. Pay (salary range). Schedule (hybrid). We should not create empty sections. Let's extract content: About the role: paragraph after "About The Role". It includes description: "The Accounts Receivable Manager will play a critical, hands-on role in building and running the company’s billing and receivables operations as The Nuclear Company continues to grow. The company’s receivables profile is low-volume and high-complexity contract-governed services billings, joint venture cost reimbursements and fees, and intercompany settlements, so this role centers on billing accuracy, contract-to-cash discipline, and cash visibility rather than high-volume collections. As the first dedicated AR resource, this position will design the billing architecture and own customer invoicing, cash application, unbilled receivables tracking, reconciliations, and AR close and reporting. As revenue streams expand and contract complexity increases, this individual will build the receivables processes, controls, and automation required to keep pace without proportional headcount growth. Note: This is a hybrid position based in our downtown Columbia, South Carolina office. The role has been posted in Charlotte and surrounding markets for visibility, as the hybrid schedule may make the commute workable for candidates living outside the immediate Columbia area. Candidates should be within commuting distance of Columbia or open to relocation." We can keep that as prose. Responsibilities: list under "Role Responsibilities". Items: - Billing & Contract-to-Cash: Own customer invoicing end to end, ensuring invoices are accurate and issued in accordance with contract terms—including milestone, time-and-materials, and cost-reimbursable structures—and that billing requirements are captured at contract signing in partnership with Legal and Business Development. - Accounts Receivable Operations: Manage cash application, account reconciliation, credit adjustments, and resolution of billing discrepancies across a multi-entity structure, ensuring accuracy and timely execution. - Intercompany & Joint Venture Billing: Prepare and manage cost reimbursement, fee, and intercompany billings arising from the company’s joint venture and multi-entity structure, including settlement tracking and supporting documentation. - Unbilled Receivables & Revenue Coordination: Track unbilled receivables and contract assets, and coordinate with Technical Accounting to ensure billing aligns with revenue recognition (ASC 606) treatment. - Collections & Aging Management: Monitor aging and outstanding balances, resolve the documentation, certification, and contract issues that hold up payment, and escalate issues or trends that could impact cash flow. - Cash Flow & AR Reporting: Maintain accurate reporting and visibility into receivables, unbilled balances, aging, and expected cash inflows, feeding Treasury’s cash forecasting and providing meaningful insight to Accounting, Finance, and business leadership. - Month-End & Year-End Close: Own AR-related close activities, including account reconciliations, adjustments, intercompany settlement support, and supporting schedules required for accurate and timely financial reporting. - Internal Controls & Audit Support: Maintain effective controls, procedures, and documentation across billing and receivables operations; provide AR-related schedules and documentation in support of internal and external audits. - Automation, Process & Systems Improvement: Use AI tools and automation to streamline invoicing, cash application, and reporting; evaluate and improve AR workflows as the business evolves; partner with Business Systems on data flows between NetSuite and operational platforms, including NOS. - Cross-Functional Partnership: Partner closely with Accounting, FP&A, Treasury, Legal, Sales & Business Development, and Project teams to resolve issues, support customer and contract requirements, and ensure receivables activity aligns with broader business needs. We can keep each as

• . Required Experience: list under "Required Experience". Items: - Experience: 6+ years of progressive accounts receivable, billing, or related accounting and finance experience, including experience owning or managing core AR or billing activities. - Education: Bachelor’s degree in Accounting, Finance, Business Administration, or a related field, or equivalent relevant professional experience in lieu of a degree. - Billing & AR Expertise: Strong hands-on experience across the full receivables lifecycle with emphasis on contract-based invoicing—milestone, time-and-materials, or cost-reimbursable billing—plus cash application, account reconciliation, and discrepancy resolution, including experience in multi-entity or intercompany environments. - Accounting Knowledge: Strong understanding of GAAP and the relationship between receivables, revenue, unbilled balances, and cash, including working familiarity with revenue recognition concepts (ASC 606) sufficient to partner effectively with Technical Accounting. - Systems: Proficiency with modern cloud ERP required, with hands-on NetSuite experience strongly preferred, along with strong Excel skills. - AI & Automation Fluency: Demonstrated use of AI tools and automation in daily work, with experience implementing automated workflows (invoicing, cash application, reporting) that scale operations without proportional headcount growth. Nice to Have: list under "Nice to Have". Items: - Start-up or high-growth company experience, particularly building or scaling a finance function - EPC, construction, power, energy, or other project-based industry billing experience - Government or cost-reimbursable contract billing experience - Experience with complex customer contracts, milestone billing structures, and unbilled receivable / contract asset accounting - Experience with NetSuite billing, invoicing, or advanced revenue management modules - Experience supporting financial audits and strengthening internal controls and documentation within receivables - Experience supporting ERP implementations or system enhancements related to billing and AR - CPA or CMA certification is a plus, but not required We could include Nice to Have under Requirements or Qualifications? The instruction says we can have Requirements, Qualifications, Skills sections. We could put Required Experience under Requirements, Nice to Have under Qualifications, and maybe Skills under Skills (AI & Automation Fluency, NetSuite, Excel). But we must not create sections with filler. We have content for each. Thus sections: - About the role (prose) - Responsibilities (list) - Requirements (list of required experience) - Qualifications (list of nice to have) - Skills (list of specific skills: NetSuite, Excel, AI tools, GAAP, ASC 606, etc.) Could combine some. But we must avoid duplication. The required experience already includes Systems, AI & Automation Fluency, Accounting Knowledge, etc. If we create Skills section, we might repeat. Better to not create Skills if it duplicates. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Required Experience and Nice to Have into Requirements (or Qualifications). But we have headings list: Requirements, Qualifications, Skills. We could use Requirements for required experience, Qualifications for nice to have, and skip Skills. Or we could use Skills for the specific technical skills (NetSuite, Excel, AI tools) and keep Requirements for experience/education. However that would split the required experience list. Might be okay but risk duplication. Given the instruction to prefer few substantive sections, maybe we just have About the role, Responsibilities, Requirements (combining required experience and nice to have), Benefits, Pay, Schedule. That's 5 sections. That seems fine. Thus:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ... required experience items ...
  • ... nice to have items ...
  but we need to separate? Could keep as two sublists? But we can just list all items; it's okay. But we should preserve the distinction? Not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep all items; mixing required and nice to have is okay as long as we don't lose info. However we might lose the distinction of which are required vs nice to have. That is substantive info. So we should keep distinction. Could have two subheadings inside Requirements? But we only allowed headings for sections; we could embed Required Experience: and Nice to Have: within the list items? That might be okay but not ideal. Better to have two subsections: maybe

  Required Experience

  and

  Nice to Have

  but the instruction only mentions using

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

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. Could we use

  inside? Not prohibited but might deviate. Safer to keep two separate sections: Requirements and Qualifications. Use Requirements for required experience, Qualifications for nice to have. That matches the headings list. Thus:

  Requirements

  (required experience items)

  Qualifications

  (nice to have items)
  Then Benefits, Pay, Schedule. Now Benefits: list: - Competitive compensation packages - 401k with company match - Medical, dental, vision plans - Generous vacation policy, plus holidays Pay: The estimated starting salary range for this role is $118,000 - $140,000 annually less applicable withholdings and deductions, paid on a bi-weekly basis. The actual salary offered may vary based on relevant factors as determined in the Company’s discretion, which may include experience, qualifications, tenure, skill set, availability of qualified candidates, geographic location, certifications held, and other criteria deemed pertinent to the particular role. We need to keep that as prose under Pay heading. Schedule: hybrid position based in downtown Columbia, SC office. The role has been posted in Charlotte and surrounding markets for visibility, as the hybrid schedule may make the commute workable for candidates living outside the immediate Columbia area. Candidates should be within commuting distance of Columbia or open to relocation. We can put that as prose under Schedule heading. Now ensure we removed boilerplate: EEO, Export Control, Recruiting Fraud Alert, etc. Also remove duplicated lines (maybe none). Also remove navigation etc. Now produce HTML fragment. Let's craft. Check for any leftover boilerplate: The posting includes "EEO Statement", "Export Control", "Recruiting Fraud Alert". We'll omit those. Also note: The posting includes "Note: This