Financial Systems Director - Close & Consolidation

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Envestnet", "The Team You’ll Join", "How You’ll Contribute", then sections like "Oracle EPM / FCCS Platform Ownership", "Close & Consolidation Process Ownership", "ASC 606 Revenue Recognition Governance", "Cross-Pillar Partnership", "Technical Depth Required", "Accounting Depth Required", "What You’ll Need to Bring", "Nice-to-Haves", "Why You’ll Enjoy Working at Envestnet", "Sponsorship", "Our Investment in You". Also location info at top: "Job Location The primary work location for this role is Berwyn, PA, Boston, MA, or Raleigh, NC with a hybrid work model. We must not repeat job title as heading. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use h3 for sections, but we can also use other headings? Probably we should stick to h3 for each section heading. Use

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

  for prose. 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. 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include. The posting has many sections; we can group them logically. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use those headings if appropriate. However the posting has specific sections like "Oracle EPM / FCCS Platform Ownership", "Close & Consolidation Process Ownership", etc. Those are substantive content; we should include them as sections with h3 headings. We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting does have "Our Investment in You" which includes salary range and benefits. So we can include a Benefits section (maybe combine salary and benefits). Pay section: we have salary range; we could include Pay section. Schedule: not mentioned (hybrid work model is location/hybrid). Could include Schedule? Not explicitly. The posting mentions hybrid work model but not schedule details. Might not create Schedule section unless specific. Better to avoid. We need to preserve all substantive information. So we need to include location/hybrid info somewhere, maybe as a short p at top. We must remove boilerplate: EEO, sponsorship (visa), recruitment fraud, etc. Also remove "Our Commitment to Inclusion & Belonging", "Sponsorship", "Recruitment Fraud". Also remove "Our Investment in You" maybe we keep benefits and pay but not the fluff? Actually "Our Investment in You" includes salary range, benefits description. That's substantive. We'll keep that but maybe rename to Benefits and Pay. We need to avoid duplication. Also need to avoid "Nice-to-Haves" maybe we can include as part of Requirements/Qualifications. We need to output only HTML fragment. Let's structure:

  Job Location: The primary work location for this role is Berwyn, PA, Boston, MA, or Raleigh, NC with a hybrid work model.

  Then sections:

  About Envestnet

  with paragraph.

  The Team You’ll Join

  with paragraph.

  How You’ll Contribute

  with paragraph (maybe long). Could break into
  for duties? The paragraph is long; we could keep as

  . But instruction: use

  • for any list of duties/requirements/benefits. The "How You’ll Contribute" is a list of responsibilities separated by periods. Could convert to
    • . Might be better to keep as

      but it's not a list. However it's a series of duties; we could split into list. The instruction says use

      • for any list of duties/requirements/benefits. So we should convert that to list. Similarly, the sections like "Oracle EPM / FCCS Platform Ownership" are a list of duties; we can make
        • . "Close & Consolidation Process Ownership" also list. "ASC 606 Revenue Recognition Governance" list. "Cross-Pillar Partnership" list. "Technical Depth Required" list. "Accounting Depth Required" list. "What You’ll Need to Bring" list. "Nice-to-Haves" list. "Why You’ll Enjoy Working at Envestnet" paragraph. "Our Investment in You" includes salary range and benefits; we can make a

          for salary and maybe a

          for benefits. We must not include sections like Sponsorship, Recruitment Fraud, EEO. Let's extract content. I'll copy relevant text. Job Location: "The primary work location for this role is Berwyn, PA, Boston, MA, or Raleigh, NC with a hybrid work model." About Envestnet: "Envestnet is an adaptive WealthTech company that is redefining the future of wealth management by helping advisors meet the moment with its comprehensive technology, actionable insights, and industry leading support. Backed by over 25 years of experience and approximately $7.0 trillion in platform assets, Envestnet is trusted by over one third of financial advisors across leading banks, wealth managers, brokerages, and RIAs. For a deeper look at how Envestnet is shaping the future of financial advice, visit www.envestnet.com." The Team You’ll Join: "The Financial Systems team at Envestnet plays a critical role in powering the technology behind the company’s finance operations, building and enhancing the systems that support reporting, reconciliation, and the close process. Partnering closely with Finance stakeholders, the team develops integrations, dashboards, and automation within Oracle Fusion to ensure accurate, scalable, and efficient financial data flow across the organization. By combining deep technical expertise with business insight, they drive continuous improvement in how financial processes are executed—making it an exciting space for those who enjoy solving complex problems at the intersection of finance and technology." How You’ll Contribute: list items: - Responsible for design, development, support and optimization of Envestnet’s critical software programs that power wealth management, data aggregation and operational workflows. - Ensures applications are highly available, secure and compliant with company and regulatory standards, while meeting the needs of advisors, clients and internal teams. - Manages integrations, monitors performance and ensures effective incident resolution. - Ensures applications are scalable, efficient and resilient. - Provides expertise and advice to influence decisions and priorities related to Enterprise Applications processes and service delivery. - Packages IT elements into repeatable deployments using automation techniques and technologies. - Reviews, proposes and recommends best practices related to application development, deployment and ongoing support. - Selects and conducts proof-of-concept exercises on tools needed to support application development, deployment and operation. - Evaluates and recommends strategies for using emerging operational technologies. - Works with colleagues and vendors to evaluate products and solutions that will improve or enhance application services. - Assesses usage and utilization trends, making design and implementation recommendations toward scaling an infrastructure’s architecture. Oracle EPM / FCCS Platform Ownership: - Own Oracle FCCS configuration: metadata hierarchies, consolidation rules, calculation sequences, and data forms - Write and maintain FCCS Groovy scripts for consolidation logic, currency translation, and close automation - Configure and govern FDMEE / Oracle Data Management workflows, data load rules, and source-system mappings - Drive FCCS refresh automation using EPM Cloud Automate to support accelerated close timelines - Administer Oracle ARCS (Account Reconciliation Cloud Service) or govern BlackLine operations; conduct future-state evaluation of Oracle ARCS migration - Develop and maintain Smart View templates for Finance and Accounting users Close & Consolidation Process Ownership: - Stabilize and govern Oracle FCCS consolidation process — eliminate recurring month-end failures related to account combo propagation and refresh timing - Design and implement intercompany transaction elimination strategy and controls, including new India-US flows - Manage entity and consolidation hierarchy across US and India operations, including new entity onboarding - Co-own India Tally-to-Oracle Fusion migration: FCCS extract design, INR functional currency setup, multi-currency translation validation, and intercompany elimination rules - Partner with EY on ledger architecture decisions affecting consolidation (currency conversion, SLA rate types, reporting currency configuration) - Establish close calendar, control testing framework, and audit coordination process - Drive month-end close cycle time from current state to sub-7-day (Year 1) and 3-5-day (Year 2+) targets ASC 606 Revenue Recognition Governance: - Own ASC 606 revenue recognition program across all lines of business: govern the existing automated engine (Tamarac, PC — automated, 300+ tests, penny-perfect) and extend to MoneyGuide and future LOBs - Serve as primary financial systems partner to the CAO on revenue recognition methodology, SSO arrangement accounting, and variable consideration - Ensure rev rec automation outputs are audit-ready and SOX-compliant Cross-Pillar Partnership: - Write functional specifications and consolidation data pipeline requirements for the Integration & Workato Platform team; review technical designs and validate outputs - Partner with Director, Data & Analytics to ensure close and consolidation data is available in the analytics platform (Snowflake/EFRE) for real-time reporting - Coordinate with Director, Revenue & Billing on billing-to-GL cutoff timing and reconciliation handoff Technical Depth Required: - Oracle FCCS: Hands-on configuration: metadata, data forms, consolidation and translation rules, Groovy script development and debugging - EPM Cloud Automate: Job scheduling, close automation sequences, and dependency management - FDMEE / Oracle Data Management: Workflow configuration, data load rules, location and mappings setup - Oracle ARCS / BlackLine: Reconciliation template configuration, matching rules, close governance - Smart View: Template development, connection management, and user administration - Oracle Fusion GL: Chart of accounts, consolidation sets, OTBI/BIP reporting - Integration literacy: Ability to review REST API payloads, validate data pipeline designs, and specify integration requirements for engineers — you will not write ETL code but you must be able to specify and validate it Accounting Depth Required: - ASC 606 revenue recognition (5-step model) — experience operating and governing automated rev rec processes in a SaaS/subscription business - ASC 830 foreign currency translation and remeasurement — understanding of functional vs. reporting currency, CTA, and multi-entity consolidation mechanics - Intercompany elimination methodology for complex multi-entity structures across jurisdictions - SOX compliance for financial close: ITGCs, automated controls, evidence collection, and audit coordination - Multi-ledger consolidation architecture — able to discuss design trade-offs with EY and the CAO What You’ll Need to Bring: - Hands