Senior Accountant, Partnership

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse. Posting includes: - About The Role: paragraph description. - Key Responsibilities: list of duties. - Other Duties: note about job description not comprehensive; but that's boilerplate? It's generic; we should remove boilerplate. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Other Duties Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties, or responsibilities that are required of this employee for this job. Duties, responsibilities, and activities may change at any time with or without notice." This is generic boilerplate; likely should be removed. - TRAVEL: Minimal travel expected. That's a detail; could be part of responsibilities? Not a section. Could be included in responsibilities? Not needed. - Minimum Requirements: Experience, Education. - Additional Eligibility Requirements: CPA preferred, foreign currency translation, experience with systems, background check etc. Some of that is boilerplate (background check). We need to preserve substantive info: CPA preferred, foreign currency translation or multinational entity reporting preferred, experience with Yardi, OneStream, Blackline, or similar accounting and reporting systems preferred. Also maybe "Employment is contingent upon the successful completion of a background check, drug screening, and verification of employment, education, and other credentials relevant to the position." That's boilerplate; remove. - What We Offer: list of benefits: Competitive Base Salary + Annual Bonus, Generous Paid Time Off and Holidays, Employee Stock Purchase Program – purchase shares at a 15% discount, Employer-matching 401(k) Program + Profit Sharing Program, Student Debt Program – we’ll contribute up to $10,000 towards your student loans!, Tuition Assistance Program, Comprehensive and progressive Medical/Dental/Vision options, Professional Growth, And much more! - No explicit Pay or Schedule details. So we should not create Pay or Schedule sections because not stated. - Benefits: we have content. - Skills: maybe we can infer from responsibilities? But we should only create Skills section if posting has real specific content for it. The posting does not have a separate "Skills" heading. Could we extract skills from responsibilities? The instruction: "Prefer a few substantive sections over many thin ones." We could combine skills into Requirements or Qualifications. But we have separate headings allowed: Requirements, Qualifications, Skills. We need to decide what to put where. We have Minimum Requirements (Experience, Education). Additional Eligibility Requirements (CPA preferred, foreign currency translation, systems experience). Those could go under Requirements or Qualifications. Qualifications often include education, certifications, experience. Let's map: - About the role: we have paragraph. - Responsibilities: list from Key Responsibilities. - Requirements: maybe experience and education (minimum requirements). Could also include "Partnership, consolidation, or real estate accounting experience is preferred." That's a requirement/qualification. - Qualifications: maybe CPA preferred, foreign currency translation, systems experience. - Skills: maybe not explicitly listed; we could omit. - Benefits: list from What We Offer. - Pay: not present; omit. - Schedule: not present; omit. We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must preserve all substantive information; do not invent or summarize away detail. We need to output HTML fragment with

for each section heading,

• for lists,

  for prose. We need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract the About The Role paragraph: "About The Role The Senior Accountant, Partnership Accounting owns accounting and financial reporting for a portfolio of operator partnerships, including foreign operators and other complex structures, with emphasis on monthly intercompany consolidation, journal entries, account reconciliations, and billbacks under US GAAP, SOX requirements, and Company policy. The role also reviews staff accountants' work, trains and mentors new team members, and drives process improvements that make the close more efficient and repeatable. The successful candidate has firm command of accounting fundamentals, resolves consolidation and foreign currency translation issues independently, knows when to escalate, and is a trusted resource to operating partners and the accounting team." We need to keep that as prose in

  . Now Responsibilities: list items from Key Responsibilities. Let's extract each bullet (they are semicolon separated? Actually each sentence starts with a verb). We'll break into list items. List: - Serve as the primary accounting contact for an assigned portfolio of operators, including foreign operators and other complex structures, resolving inquiries independently, leading operator meetings, and escalating matters to management when appropriate. - Maintain accurate books and records for assigned partnership entities, including preparation of journal entries to support a complete and accurate monthly close. - Perform monthly account reconciliations and review reconciliations prepared by staff accountants, ensuring working papers fully support all balances and reconciling items are resolved timely. - Review the work of staff accountants across assigned operators, including journal entries, operator setup, consolidations, and key controls, providing specific and timely feedback with minimal errors or missed items. - Perform monthly consolidation and intercompany elimination procedures, independently identifying and resolving consolidation issues, including foreign currency translation errors. - Review monthly operator financial submissions and perform analytical review of financial and operating results, developing and pursuing questions with operators on variances and quarterly trends, including the impact on non-GAAP metrics such as NOI and FFO. - Apply the appropriate accounting treatment across RIDEA and non-RIDEA structures. - Support the accounting for acquisitions, dispositions, and other transaction activity affecting operator-accounted properties, partnering with the transactions team on complex deals. - Perform key internal controls for partnership accounting, prepare documentation supporting SOX requirements, and serve as a point of contact for external and internal audit requests. - Train, coach, and mentor staff accountants on partnership accounting fundamentals. - Initiate process improvement projects that build sustainable, repeatable processes, and document related procedures. - Perform ad-hoc analysis and other duties as required. We should keep all. Now Requirements: Minimum Requirements: Experience: 3-5 years of public or corporate accounting experience is required. Partnership, consolidation, or real estate accounting experience is preferred. Education: Bachelor’s degree in accounting is required. Knowledge of accounting theory, including GAAP and IFRS, is preferred. We could format as list. Now Qualifications: Additional Eligibility Requirements: CPA preferred. Experience with foreign currency translation or multinational entity reporting is preferred. Experience with Yardi, OneStream, Blackline, or similar accounting and reporting systems is preferred. Also maybe "Employment is contingent upon..." we drop. Now Benefits: list from What We Offer. Let's extract each: - Competitive Base Salary + Annual Bonus - Generous Paid Time Off and Holidays - Employee Stock Purchase Program – purchase shares at a 15% discount - Employer-matching 401(k) Program + Profit Sharing Program - Student Debt Program – we’ll contribute up to $10,000 towards your student loans! - Tuition Assistance Program - Comprehensive and progressive Medical/Dental/Vision options - Professional Growth - And much more! (maybe vague; but it's part of the list; we can keep as item.) We should keep all. Now we need to output HTML fragment only. Structure:

  About the Role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...
  We should not include Pay or Schedule. Check for any duplicated lines: none. Check for boilerplate: we removed Other Duties, TRAVEL line, background check etc. Check for any mention of "Minimal travel is expected for this position." That's a substantive detail; should we keep? It's not a section; maybe we could include it under Responsibilities as a note? But it's not a duty. Could be included as a separate paragraph under About the role? Not ideal. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that detail somewhere. Where to put? Could add a short paragraph under About the role or maybe a separate section like "Travel". But we only have allowed headings; we could add a

  after About the role before Responsibilities: "Minimal travel is expected for this position." That preserves info. Similarly, there is a line: "Other Duties Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties, or responsibilities that are required of this employee for this job. Duties, responsibilities, and activities may change at any time with or without notice." That's boilerplate; remove. Also there is a line: "Employment is contingent upon the successful completion of a background check, drug screening, and verification of employment, education, and other credentials relevant to the position." That's boilerplate; remove. Also there is a line: "About Welltower ..." and later "EOE/AA..." etc. That's boilerplate; remove. Also there is a link: "https://welltower.com/newsroom/careers/" - that's application instructions? Should remove. Also there is "Welltower® Inc. (NYSE: WELL) ..." etc. That's boilerplate about company; remove. Thus final HTML includes About the role paragraph, Responsibilities list, Requirements list, Qualifications list, Benefits list, plus a short paragraph for travel. We need to ensure we don't miss any substantive info from the posting. Let's double-check the original text for any other substantive bits: - "At Welltower, we’re transforming how the world thinks about senior living and wellness-focused real estate." (company description) - boilerplate? It's generic marketing; could be considered boilerplate but it's substantive about company mission. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories; but it's more like company overview. The instruction says "Prefer a few substantive sections over many thin ones." The company overview might be considered boilerplate but it's not explicitly listed to remove. However typical job postings include company description; but the instruction didn't say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we could keep the opening paragraph? But the instruction also says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It didn't say to remove company description. However the earlier part: "Reformat a job posting into clean, well-structured semantic HTML." Usually we keep the role description but not the fluff. The opening paragraph about Welltower's mission might be considered fluff but not prohibited. However to be safe, we might keep it as part of About the role? Actually the About the role section already includes role description; we could prepend a brief company overview as a paragraph before About the role? But the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The company overview is not a section heading we have; we could just include it as a

  before the About the role heading? That would be outside any section; but we only output HTML fragment; we could include a

  at start. However the instruction about sections: we could treat the opening paragraph as part of "