Jobs · Accounting · Ohio

Sr. Accountant

Associated Materials Innovations · Cuyahoga Falls, OH · 3 wk ago
AccountingFull-time
We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the job posting. First, "Who We Are" is not a heading we need; we can ignore or maybe treat as "About the role"? Actually "About the role" heading should contain description of role. The posting includes "Summary" and "Objectives" and "Day-to-day Responsibilities". So we can put summary/objectives under About the role? Or we could have separate sections: About the role (summary), Responsibilities (day-to-day), Requirements (Education And Experience), Qualifications (maybe same as Requirements?), Skills (technical skills), Benefits (maybe not present), Pay (not present), Schedule (not present). We must not create sections with placeholder text. So only include sections where we have real specific content. We have: - About the role: we have "Summary" and "Objectives". That's substantive. - Responsibilities: "Day-to-day Responsibilities" list. - Requirements: "Education And Experience" list. - Qualifications: maybe same as Requirements? Could combine? But we can treat "Education And Experience" as Requirements. Qualifications maybe not separate; we could omit Qualifications if no distinct content. - Skills: we have "Advanced Microsoft Excel skills...", "Experience with Oracle ERP...", "Experience or demonstrated interest in applying AI tools...", "Working knowledge of internal control concepts...", "Strong technical, interpersonal, and time management skills", "Ability to work both independently...". Those are skills. - Benefits: posting mentions "Click to learn more about benefits." No actual benefits listed. So we should not create Benefits section because no specific content. - Pay: not specific; only says wage based on factors. Not specific numbers. So we should not create Pay section. - Schedule: not mentioned. Thus we output sections: About the role, Responsibilities, Requirements, Skills. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from those sections. Let's extract content. About the role: includes Summary paragraph and Objectives bullet list? Actually Objectives are bullet points preceded by "Objectives". We'll need to format as prose or list? The instruction: Use

    • for any list of duties/requirements/benefits, and

      for prose. Objectives are a list of objectives; could be treated as list. But we could also put them in

      as sentences. Safer to treat as list because they are bullet points. However the instruction says use

      • for any list of duties/requirements/benefits. Objectives are not duties/requirements/benefits but still a list. Might be okay to use
        • for any list. We'll use
          • for Objectives. Similarly, Day-to-day Responsibilities is a list; use
            • . Education And Experience is a list; use
              • . Skills: we have multiple skill statements; could be list as well. We need to preserve all details. Let's capture each. Summary paragraph: "This position reports to the Assistant Controller and is responsible for supporting the close process and ensuring timely and accurate financial reporting within a modern, systems-driven finance organization. The Senior Accountant works hands-on in Oracle R12 and Oracle EPM and with the company's data analytics and AI-enabled tools to shorten the close, strengthen internal controls, and improve data quality at the source. In addition, the Senior Accountant will work closely with the commercial FP&A organization for special projects and analyses. The successful candidate should possess strong analytical and time management skills coupled with intellectual curiosity, technical aptitude, and a bias toward replacing manual effort with repeatable, well-controlled processes." That's prose. Objectives list: - Ensure timely reporting of financial results through involvement in monthly, quarterly, and annual close processes - Confirm accuracy of reported balances through completion and/or review of account reconciliations - Reduce manual effort and close cycle time by automating recurring accounting, consolidation, and reporting activities in Oracle EPM and related tools - Improve data quality and transparency by resolving issues in the source systems and building repeatable, auditable analyses of transaction-level data Day-to-day Responsibilities list (multiple bullet points): - Prepare and/or review journal entries, including standard entries, reclassifications / adjustments, accruals, allocations, and intercompany transactions, and complete and review account reconciliations and general ledger activity for both Balance Sheet and Income Statement accounts, using automated routines and exception reporting to focus effort on true variances - Record and validate various financial transactions including intercompany sales, accrued liabilities, and customer / vendor rebates, sourcing support directly from system data rather than manually maintained spreadsheets - Administer Oracle R12 General Ledger and Oracle EPM Financial Consolidation and Close - Analyze transaction-level detail from source subledgers using the company's data analytics platform, including subledger-to-general ledger tie-outs, aging and cut-off analysis, and exception reporting that replaces manual sampling and spreadsheet roll-ups - Own data quality for assigned areas, including chart of accounts and master data mapping between source subledgers and the general ledger, validation and exception rules, and root-cause correction at the source rather than downstream adjusting entries Education And Experience list: - Bachelor's Degree in Finance/Accounting or a related field - 3+ years of financial accounting experience, preferably in a multi-entity, multi-system environment - CPA designation preferred, but not required - Advanced Microsoft Excel skills, including pivot tables, and lookup and modeling functions; proficiency with Word - Experience with Oracle ERP (R12) and Oracle EPM / consolidation systems a plus, but not required - Experience or demonstrated interest in applying AI tools to financial analysis, with sound judgment regarding validation of outputs and appropriate handling of company data - Working knowledge of internal control concepts, including system access, data integrity, and documentation of control evidence - Strong technical, interpersonal, and time management skills - Ability to work both independently and collaboratively; learns new systems quickly and is willing to train and support others in using them Now Skills: Actually many of those are skills; but we already included them in Education And Experience. The instruction: Use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to separate Requirements (education/experience) and Skills (technical skills). The Education And Experience includes both education/experience and some skill statements (Excel, Oracle, AI, internal control, technical interpersonal, ability to work). We could split: Requirements: education and experience (Bachelor's degree, 3+ years, CPA preferred). Skills: the rest (Excel, Oracle, AI, internal control, technical interpersonal, ability to work). However the instruction says preserve ALL substantive information; we can just keep them in Requirements and not create Skills if we think it's overlapping. But better to follow the suggested headings: Requirements for education/experience, Skills for technical/competency statements. Let's parse: Education And Experience bullet list includes: 1. Bachelor's Degree in Finance/Accounting or a related field 2. 3+ years of financial accounting experience, preferably in a multi-entity, multi-system environment 3. CPA designation preferred, but not required 4. Advanced Microsoft Excel skills, including pivot tables, and lookup and modeling functions; proficiency with Word 5. Experience with Oracle ERP (R12) and Oracle EPM / consolidation systems a plus, but not required 6. Experience or demonstrated interest in applying AI tools to financial analysis, with sound judgment regarding validation of outputs and appropriate handling of company data 7. Working knowledge of internal control concepts, including system access, data integrity, and documentation of control evidence 8. Strong technical, interpersonal, and time management skills 9. Ability to work both independently and collaboratively; learns new systems quickly and is willing to train and support others in using them We can separate: Requirements (education/experience): items 1-3. Skills: items 4-9. Thus we will have sections: About the role, Responsibilities, Requirements, Skills. Now we need to output HTML fragment only. Structure:

                About the role

                Summary paragraph.

                Objectives

                ?? Wait we said we will put Objectives under About the role? Actually we have About the role heading; we could include summary paragraph and then a list for Objectives. But the heading "About the role" is specified; we should not add another heading like Objectives unless we want to keep it as a subheading? The instruction: use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow the pattern. Probably we should keep About the role as a section containing summary and objectives (maybe as a list). But we could also add a subheading

                but not allowed? Not specified. Safer to keep About the role with summary paragraph and then a
                  for Objectives directly under it (no extra heading). That's fine. Similarly Responsibilities heading with list. Requirements heading with list (education/experience). Skills heading with list (skill statements). Let's craft. We must not repeat the job title as a heading. The job title is Senior Accountant (implied). Not used. We must not put Job ID/requisition numbers as headings; none present. Now produce HTML. Check for any boilerplate: we removed "Who We Are", "About Us", "Additional Information", "Equal Opportunity Employer", etc. We must preserve all substantive information: we have included summary, objectives, responsibilities, requirements (education/experience), skills. Check we didn't miss any detail: The summary includes "The Senior Accountant works hands-on in Oracle R12 and Oracle EPM and with the company's data analytics and AI-enabled tools to shorten the close, strengthen internal controls, and improve data quality at the source." Included. Objectives list included all four. Responsibilities list included all five bullet points. Requirements list includes bachelor's degree, 3+ years experience, CPA preferred. Skills list includes Advanced Microsoft Excel skills..., Experience with Oracle ERP..., Experience or demonstrated interest in applying AI tools..., Working knowledge of internal control concepts..., Strong technical, interpersonal, and time management skills, Ability to work both independently and collaboratively... Check we didn't miss any: The bullet about "proficiency with Word" is included in the Excel bullet? Actually bullet 4: "Advanced Microsoft Excel skills, including pivot tables, and lookup and modeling functions; proficiency with Word". We'll keep that as part of that skill. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now output. We need to ensure proper HTML: open and close tags. Let's write:

                  About the role

                  This position reports to the Assistant Controller and is responsible for supporting the close process and ensuring timely and accurate financial reporting within a modern, systems-driven finance organization. The Senior Accountant works hands-on in Oracle R12 and Oracle EPM and with the company's data analytics and AI-enabled tools to shorten the close, strengthen internal controls, and improve data quality at the source. In addition, the Senior Accountant will work closely with the commercial FP&A organization for special projects and analyses. The successful candidate should possess strong analytical and time management skills coupled with intellectual curiosity, technical aptitude, and a bias toward replacing manual effort with repeatable, well-controlled processes.

                  • Ensure timely reporting of financial results through involvement in monthly, quarterly, and annual close processes
                  • Confirm accuracy of reported balances through completion and/or review of account reconciliations
                  • Reduce manual effort and close cycle time by automating recurring accounting, consolidation, and reporting activities in Oracle EPM and related tools

Similar jobs

Sr. Accountant

Robert HalfGreat Falls, MT· 3 wk ago
apply on roberthalf.com

Sr. Accountant

Robert HalfPrinceton, NJ· 1 mo ago
Accountingapply on roberthalf.com

Sr. Accountant

Robert HalfDeLand, FL· 1 mo ago
Financeapply on roberthalf.com

Sr. Accountant

Robert HalfSecaucus, NJ· 2 mo ago
Accountingapply on roberthalf.com

Sr. Accountant

Veritas Search GroupIrvine, CA· 2 mo ago
Accountingapply on careers.topechelon.com

Sr. Accountant

Airbus US Space & Defense, Inc.Mobile, AL· 2 mo ago
Accounting