Financial Operations Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Department" and "Job Summary". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. 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. IMPORTANT: include a section ONLY when the 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - About The Department (description of Globus). Could be "About the role"? Actually "About The Department" is about the department, not role. But we can treat as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: "About the role" could contain the Job Summary and maybe department description. But we must not repeat job title. We can include a short paragraph about the role and department. - Responsibilities: we have a long list. - Requirements/Education/Work Experience/Certifications: we have Education Minimum Qualifications, Work Experience Minimum requirements, Certifications Preferred Qualifications, Experience (Preferred Qualifications), Technical Skills Or Knowledge, Preferred Competencies. These could be grouped under "Requirements" or "Qualifications" and "Skills". The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide which to include based on content. We have: Education: Minimum Qualifications: college degree in related field. Work Experience: Minimum requirements include knowledge and skills developed through 2-5 years of work experience in a related job discipline. Certifications: Preferred Qualifications (actually heading says Certifications Preferred Qualifications but then it's a list of experience). Actually the text: "Certifications Preferred Qualifications Experience 2–4 years of experience in financial operations, accounting, or a related role, preferably in a higher education, nonprofit, research, or SaaS environment." So it's mixing. Then "Experience" bullet list: Experience with accounts receivable, etc. Then "Technical Skills Or Knowledge": proficiency in Oracle, advanced Excel, etc. Then "Preferred Competencies": strong analytical, etc. Thus we have multiple categories: Education, Experience, Technical Skills, Competencies. We could create sections: "Qualifications" (education + experience), "Skills" (technical skills + competencies). Or we could have "Requirements" (education + experience) and "Skills". The instruction says prefer a few substantive sections over many thin ones. So maybe two sections: "Qualifications" and "Skills". But we also have Responsibilities separate. We also have Pay and Benefits and Schedule: we have Pay Range $75,000 - $90,000, Benefits Eligible Yes, Working Conditions: remote position with occasional attendance at in-person meetings required. Also Scheduled Weekly Hours 37.5. So we have Pay, Benefits, Schedule (hours). So we should include those sections as they have real content. Thus sections: About the role (maybe combine department description and job summary), Responsibilities, Qualifications (education + experience), Skills (technical + competencies), Pay, Benefits, Schedule. We must not include headings with filler. Ensure each heading has substantive content. We need to strip boilerplate: remove EEO, equal opportunity, scam warning, application instructions, etc. Also remove "Application Documents", "Reference checks", etc. Also remove "Job Family", "Role Impact", "FLSA Status", "Pay Rate Type", etc? Those are minor metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can drop those lines. We need to preserve all substantive information: that includes pay range, benefits eligible, weekly hours, working conditions (remote). Also the department description, job summary, responsibilities, qualifications, skills, etc. We must not invent or summarize away detail. So we need to keep the details as given, but we can format into

and

• . Must not add extra info. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  Department Globus Finance, HR & Business Operations About The Department Globus (www.globus.org) is a mission-driven organization dedicated to enabling discovery by delivering advanced data management and computation capabilities to researchers worldwide. As a unit within The University of Chicago, Globus develops and operates commercial-quality, software-as-a-service used by thousands of institutions, including research universities, national laboratories, federal agencies, and commercial research organizations. Core features are free for non-profit researchers, and the Globus service is sustained through institutional subscriptions that unlock advanced features for organizations needing greater control, compliance support, and deeper integration with their research computing environment. This model reflects the organization’s core commitment: making secure, reliable cyberinfrastructure services accessible to the broadest possible research community. The Globus team comprises professional software developers and business operations staff, as well Globus Labs, a dedicated research group pioneering novel methods and technologies. Team members are geographically distributed—a structure that reflects the global nature of the research communities we serve—while maintaining a collaborative culture focused on making an impact in disciplines ranging from the life sciences and astronomy to materials science and public policy.

  Job Summary We are seeking a Financial Operations Analyst to join the Globus business operations team. The financial operations that sustain Globus's mission sit at the heart of this role — from the full cycle of accounts receivable, invoicing, collections, and cash receipting, to deferred revenue management, variance reporting, and financial statement preparation for senior leadership. This role is well-suited to someone who sees the numbers behind a growing, mission-driven organization and immediately wants to understand them. You will thrive here if you are energized by variety and complexity; if you take pride in doing the detail work well, and you want to be part of a small, collaborative team where accurate, well-run financial operations genuinely matter. Curiosity, rigor, and a willingness to learn by doing are what will make you successful here. If that sounds like the environment where you do your best work, we would love to hear from you!

  But note we should not repeat the job title; we didn't. The "Job Summary" phrase is part of the content; we can keep it. But we might want to avoid duplication: The first paragraph already includes "Department Globus Finance, HR & Business Operations About The Department". That's okay. Now Responsibilities: we need to convert the bullet list into
  • . The responsibilities paragraph is a long sentence with many items separated by periods and semicolons. We need to split into list items. The instruction: Use
    • for any list of duties/requirements/benefits. So we should parse each duty as a separate
    • . The original responsibilities text: "Manage the end-to-end accounts receivable process in collaboration with the central AR team and Sales Operations team, including recording deposits in Oracle, monitoring University funds for misdirected payments, investigating discrepancies, and supporting improvements to the accuracy and efficiency of the function. Serve as the primary point of contact for customer-facing payment communications, handling inquiries and collections correspondence with professionalism and clarity. Monitor AR and deferred revenue subledgers and perform regular reconciliations and error corrections. Perform monthly bank account reconciliations across accounting, revenue, and bank records, and conduct daily general ledger downloads and reconciliations to maintain the integrity of receivable balances. Assists with tracking state sales tax obligations arising from Globus subscription activity, and support state filings on schedule; work with the customer team on KYC processes to collect required tax documentation (e.g., exemption certificates, entity information). Assist with budget management and monthly forecasting using the department's budgeting and planning system (UCPLAN); contribute to variance analyses. Support preparation of financial statements and ad hoc analyses for senior leadership. Monitor the general ledger for spending activity and budget-to-actual variances; proactively submit journal entries and cost corrections as needed to maintain accuracy and ensure expenses are recorded to the correct accounts. Support procurement activities across the department including submitting operational and high-value procurement requests in Oracle; assist staff with transactions in Oracle, Concur, and Workday. Support special projects spanning procurement, financial analysis, budgeting, and other areas as directed. Performs a variety of operating or cost accounting activities which require moderate knowledge of accounting theories and principles. Interprets accounting records for the purpose of determining gains and losses, receipts and disbursements, and inventory. Performs other related work as needed." We need to make each line a
    • . Ensure we keep the content exactly. Now Qualifications: we have Education Minimum Qualifications, Work Experience Minimum requirements, Certifications Preferred Qualifications (though it's actually experience). We'll combine into a
      • list. Education: "Minimum requirements include a college or university degree in related field." Work Experience: "Minimum requirements include knowledge and skills developed through 2-5 years of work experience in a related job discipline." Certifications Preferred Qualifications: Actually the heading "Certifications Preferred Qualifications Experience 2–4 years of experience in financial operations, accounting, or a related role, preferably in a higher education, nonprofit, research, or SaaS environment." That seems like a mislabel; but we can treat as "Preferred experience: 2–4 years of experience in financial operations, accounting, or a related role, preferably in a higher education, nonprofit, research, or SaaS environment." Then there is a list of experience items: "Experience with accounts receivable, general ledger maintenance, and month-end close processes. Experience working within a large ERP system (Oracle FST, Workday, or SAP strongly preferred). Experience supporting research finance for federal and non-federal grant funds. Experience supporting budget preparation and variance analysis. Experience in a small team or unit finance role contributing to multiple functions often with competing priorities and deadlines (AR, procurement, reporting)." We could combine these into a list under Qualifications. Technical Skills Or Knowledge: list: "Proficiency in Oracle Financial Systems strongly preferred; experience with Concur and Workday is a plus. Advanced Excel skills (pivot tables, VLOOKUP/XLOOKUP, data validation); experience with financial reporting tools or BI tools (Power BI, Tableau, or similar) a plus. Familiarity with GAAP and general accounting principles. Experience with or interest in data visualization and financial dashboard development. Familiarity with principles of post-award financial management." Preferred Competencies: list: "Strong analytical and problem solving skills. Excellent organizational skills and constant attention to detail. Ability to work discreetly with sensitive and confidential data. Ability to manage competing priorities and meet recurring deadlines in a high-volume transactional environment. Effective written and verbal communication skills, including ability to present financial information clearly to non-financial colleagues. Proactive problem-solving orientation; comfort identifying errors and discrepancies and pursuing resolution independently. Collaborative working style with ability to partner across functions (engineering, sales, research administration) and across institutions. Comfort operating in ambiguity and a growth-oriented, evolving environment." We could combine Technical Skills and Preferred Competencies into a "Skills" section. Now Pay: we have "Pay Range $75,000.00 - $90,000.00". Also "Pay Rate Type Salary", "FLSA Status Exempt". Those are minor metadata; we could include them in a short

        under Pay section, or drop them. The