Regulatory Business Analyst II

Regulatory Business Analyst II – AxiomSL / FR 2052a & FR Y-15

Location: New York, NY
Job Type: Contract – Special Project
Department: Regulatory Projects
Industry: Banking / Financial Services

Position Overview

Our client is seeking an experienced Regulatory Business Analyst II with strong hands-on experience with AxiomSL (ControllerView) and Federal Reserve regulatory reporting, specifically FR 2052a and/or FR Y-15.

This is a key project role focused on conducting a comprehensive gap analysis of the organization's current data environment against regulatory reporting requirements. The successful candidate will identify data gaps, define sourcing requirements, develop data mapping specifications, and work closely with Finance, Data, Technology, and Regulatory stakeholders to ensure the necessary data is available and properly structured for reporting.

The ideal candidate will have 10+ years of Business Analysis experience within Corporate/Investment Banking (CIB) and a proven track record of implementing FR 2052a or FR Y-15 at a major banking institution.

Key Responsibilities

• Conduct "As-Is" vs. "To-Be" data analysis for FR 2052a and FR Y-15 reporting requirements.
• Identify missing data elements, data quality issues, granularity gaps, and other reporting deficiencies.
• Partner with Finance and business stakeholders to understand financial products, business processes, and reporting requirements.
• Translate complex Federal Reserve regulatory requirements into clear Business Requirements Documents (BRDs) and Functional Requirements Documents (FRDs).
• Define specific data sourcing requirements for transactional, counterparty, collateral, balance sheet, and other financial data.
• Develop detailed source-to-target data mapping specifications.
• Map source data into the AxiomSL Operational Data Store (ODS) and consolidated data model.
• Work closely with Data Architects, Data Engineers, ETL teams, and upstream system owners to resolve data sourcing and transformation issues.
• Analyze large datasets and perform data validation and reconciliation using SQL and other analytical tools.
• Identify and communicate risks, dependencies, and data quality concerns to senior stakeholders.
• Drive open issues and requirements through resolution while maintaining project timelines.
• Provide subject matter expertise and guidance to business, technology, and regulatory stakeholders.

Qualifications

• Bachelor's degree in Finance, Accounting, Computer Science, Information Technology, Business, or related field.
• 10+ years of Business Analysis experience within Corporate/Investment Banking (CIB).
• Hands-on experience working with AxiomSL / ControllerView.
• Required: Demonstrated experience implementing FR 2052a and/or FR Y-15 at a major banking institution.
• Strong understanding of Federal Reserve regulatory reporting requirements.
• Strong knowledge of financial products, including liquidity, lending, securities, derivatives, collateral, and balance sheet products.
• Experience with data mapping, data lineage, data sourcing, data modeling, and data quality analysis.
• Strong SQL skills and experience working with large datasets.
• Experience with Power BI or similar data visualization/analytics tools.
• Ability to develop detailed BRDs, FRDs, data mapping documents, and functional specifications.
• Excellent communication and stakeholder management skills, including the ability to work with senior Finance, Regulatory, Data, and Technology teams.
• Strong analytical, problem-solving, and organizational skills.
• Ability to work independently and drive complex regulatory initiatives through completion.

Ideal Candidate

The ideal candidate is someone who has actually implemented FR 2052a or FR Y-15 using AxiomSL at a major bank—not simply someone who has regulatory reporting experience. They should be comfortable getting into the data, understanding what the regulations require, identifying what is missing, and then working with Data and Technology teams to determine where the data needs to come from and how it needs to be mapped into Axiom.