Financial System Analyst

We need to output HTML fragment with sections: location and schedule maybe not headings? The instructions: 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. We have location: Cleveland or Chicago. Schedule: Hybrid. Should we include a Schedule section? Yes, schedule is given: Hybrid. So we can have

Schedule

with

Hybrid

maybe also location? Could combine location and schedule in a short paragraph. But location is also given. Could include location in same paragraph or separate? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Schedule heading. Location could be part of Overview or maybe a short paragraph. There's no explicit heading for location; we can include location in a

under Overview or separate. The posting includes "Location: Cleveland or Chicago". We'll preserve that. We also have Position Overview paragraph. We'll put that under maybe

About the role

or just a

after heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading for overview. Then Responsibilities heading for key responsibilities. Then Qualifications heading for qualifications. Then Benefits heading for benefits. Then Pay heading for compensation. Then Schedule heading for schedule/hybrid. Possibly also Skills? Not needed. We must not create sections with filler. Ensure we have real content. We need to remove boilerplate: EEO statement, Non-Solicitation Statement, etc. We need to preserve all substantive information: location, schedule, overview, responsibilities list, essential capabilities (maybe part of qualifications or skills?), qualifications, compensation, benefits. Essential capabilities could be considered Skills or Requirements. We could put them under Requirements or Skills. Since we have Qualifications heading for education/experience, we could put essential capabilities under Skills heading. But we need to decide. We have "Qualifications" section includes Bachelor's degree etc. Then "Essential Capabilities" list of soft skills. Could be under Skills heading. We'll create a Skills heading for those. We also have "Compensation Target compensation for this role starts is $90,000 to $125,000/year." That's pay. Benefits: list of Day 1 Benefits etc. We need to output only HTML fragment, no markdown fences. Let's craft:

About the role

Location: Cleveland or Chicago

Schedule: Hybrid

This position is responsible for the day-to-day administration of the support, analysis and continuous improvement efforts for the suite of financial systems used by the Finance Department including but not limited to Aderant, iTimekeep, BigHand Iridium BI/Intellistat, Oddr, etc. Ensures the day-to-day administration of the system is handled efficiently and effectively by taking timely action to resolve service desk requests; manage routine systems configuration and maintenance; respond to business questions and perform root cause analysis of any issues.

Responsibilities

• Manage financial systems, related user support functions, user training, and work balancing efforts for the systems including:
• Employee management tasks/user access administration
• Mass updates in Aderant via SQL
• Monthly & annual rate changes for all standard, exception & variable rates
• Update bill images when document modifications are made
• Provide support to external vendors
• Actioning service desk problems, issues, and service requests
• Understanding and maintenance of system and data interdependencies
• Initial point of contact for Aderant and other finance system users’ support concerns
• Write SQL queries for Management Studio users (weekly time reports, compliance reports for FP&A, Client Value reports, billing, etc.)
• Develop and/or enhance financial system business administration and support policies, procedures, and support documentation.
• Act as a data steward for the firm’s financial and operational data, aiding in the development of efficient reporting solutions.
• First point of contact with Information Technology to identify and coordinate IT/Finance business solutions and objectives, including:
• Validating business functions after installations, patches, etc. are completed by the vendor or IT team
• Drive continuous improvement efforts over Aderant system capabilities, identifying best practices and system enhancements.
• Performs other Finance department analytical projects as assigned.

But nesting

inside
• is okay but we need proper HTML. Could flatten: main responsibilities as list items, with sub-items maybe as separate
  . Simpler: just list each responsibility as
  • . We'll keep it simple. Let's list each bullet from the posting: - Manage financial systems, related user support functions, user training, and work balancing efforts for the systems including: - Employee management tasks/user access administration - Mass updates in Aderant via SQL - Monthly & annual rate changes for all standard, exception & variable rates - Update bill images when document modifications are made - Provide support to external vendors - Actioning service desk problems, issues, and service requests - Understanding and maintenance of system and data interdependencies - Initial point of contact for Aderant and other finance system users’ support concerns - Write SQL queries for Management Studio users (weekly time reports, compliance reports for FP&A, Client Value reports, billing, etc.) - Develop and/or enhance financial system business administration and support policies, procedures, and support documentation. - Act as a data steward for the firm’s financial and operational data, aiding in the development of efficient reporting solutions. - First point of contact with Information Technology to identify and coordinate IT/Finance business solutions and objectives, including: - Validating business functions after installations, patches, etc. are completed by the vendor or IT team - Drive continuous improvement efforts over Aderant system capabilities, identifying best practices and system enhancements. - Performs other Finance department analytical projects as assigned. We can flatten: each top-level bullet as
  • . For sub-bullets we can either include them within the same
  • using commas or separate
    . Simpler: include them as part of the same
    • text. But we need to preserve all substantive information; we can include sub-bullets as separate
    • under a nested
      . That's fine. Let's construct:

      Responsibilities

      • Manage financial systems, related user support functions, user training, and work balancing efforts for the systems including:
      • Employee management tasks/user access administration
      • Mass updates in Aderant via SQL
      • Monthly & annual rate changes for all standard, exception & variable rates
      • Update bill images when document modifications are made
      • Provide support to external vendors
      • Actioning service desk problems, issues, and service requests
      • Understanding and maintenance of system and data interdependencies
      • Initial point of contact for Aderant and other finance system users’ support concerns
      • Write SQL queries for Management Studio users (weekly time reports, compliance reports for FP&A, Client Value reports, billing, etc.)
      • Develop and/or enhance financial system business administration and support policies, procedures, and support documentation.
      • Act as a data steward for the firm’s financial and operational data, aiding in the development of efficient reporting solutions.
      • First point of contact with Information Technology to identify and coordinate IT/Finance business solutions and objectives, including:
      • Validating business functions after installations, patches, etc. are completed by the vendor or IT team
      • Drive continuous improvement efforts over Aderant system capabilities, identifying best practices and system enhancements.
      • Performs other Finance department analytical projects as assigned.
      But we have mismatched tags: we opened
      for responsibilities, then inside we have
      • then another
        without closing the outer
        • . Actually we need proper nesting: each
        • can contain a
          . So structure:
          • Manage financial systems, related user support functions, user training, and work balancing efforts for the systems including:
            • Employee management tasks/user access administration
            ...
          • Performs other Finance department analytical projects as assigned.
          But we also have the first point of contact item with its own sublist. Let's craft properly. We'll produce:

          Responsibilities

          • Manage financial systems, related user support functions, user training, and work balancing efforts for the systems including:
            • Employee management tasks/user access administration
            • Mass updates in Aderant via SQL
            • Monthly & annual rate changes for all standard, exception & variable rates
            • Update bill images when document modifications are made
            • Provide support to external vendors
            • Actioning service desk problems, issues, and service requests
            • Understanding and maintenance of system and data interdependencies
            • Initial point of contact for Aderant and other finance system users’ support concerns
            • Write SQL queries for Management Studio users (weekly time reports, compliance reports for FP&A, Client Value reports, billing, etc.)
            • Develop and/or enhance financial system business administration and support policies, procedures, and support documentation.
            • Act as a data steward for the firm’s financial and operational data, aiding in the development of efficient reporting solutions.
            • First point of contact with Information Technology to identify and coordinate IT/Finance business solutions and objectives, including:
              • Validating business functions after installations, patches, etc. are completed by the vendor or IT team
              • Drive continuous improvement efforts over Aderant system capabilities, identifying best practices and system enhancements.
          • Performs other Finance department analytical projects as assigned.
          That seems okay. Now Qualifications:

          Qualifications

          • Bachelor’s degree in Information Technology, Business Administration or Accounting with Information Systems focus.
          • Experience in relational databases and database administration.
          • Minimum two (2) to three (3) years’ experience with accounting or ERP systems and relational databases.
          • Strong computer skills are essential including advanced Excel, SQL, SSRS, preferred.
          • Understanding of project management and change management