Senior Financial Analyst, Tech Finance Operations

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's examine posting. Content: - Intro: "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for an Analyst, Finance to join our ever-evolving Technology Procurement FP&A team and help us unleash the potential of every business. Global Payments serves more than 6,000,000 customers, processing nearly $4 trillion in annual volume across 94 billion transactions in more than 175 countries." - "About The Team This Technology Procurement FP&A team is part of Global Payment’s Technology & Product FP&A group. The wider group covers all Technology spend across the Company, as well as strategic investments in our Products and Services. The Technology Procurement FP&A team ensures Technology, Procurement and Finance stakeholders have the right information to deliver large and/or complex deals with our vendors. The team ensures deals are modelled correctly, provides options and manages stakeholders to ensure value is delivered for Global Payments." - "What You’ll Own Relationships with, and coordination of, multi-functional teams including Procurement, Finance, Technology, Controllership and Technical Accounting, Treasury and Project Workstreams Preparation of Procurement Process Review (“PPR”) analysis and allocation schedules Maintain PPR Pipeline, build Cash Flow forecasts and prepare presentations Ad-hoc trackers, approvals, and PRs/POs Support of financial modelling of vendor agreements included in Business Cases Support for Procure-to-Pay finance and accounting teams Support of Procurement and Finance Integration, Separation and Transformation initiatives" - "What You’ll Bring Knowledge of FP&A and Accounting principles, practices and processes in an international matrix organisation Understanding Procure-to-Pay finance processes Effective communication style Strong critical thinking skills, using logic and reasoning to identify alternative solutions to problems Ability to plan and accomplish work to ensure critical deadlines are met Proficient in MS Office suite, including Excel and PowerPoint It’s a bonus if you have Oracle EPBCS experience SAP Ariba and/or Zip experience Prior experience with vendor contracts and procurement discussions Experience working with global stakeholders in North America, Europe and Asia" - "About The Team Our inclusive and global teams win together every day. We’re proud to have the best minds in the industry, who you can learn from as you grow your career. The people, the energy, the connections – it’s unmatched. Come and be part of an ever-evolving company and get dynamic opportunities that go beyond borders. What makes a Globalpayer? Globalpayers think like a client, act like an owner and win as one team. We’re curious and innovative – always finding better ways to deliver impact. We empower each other to make decisions, and it’s our passion that drives excellence in everything we set out to do. Does this sound like you? Then you sound like a Globalpayer. Apply now to take your career global." - Then link: https://jobs.globalpayments.com/en/why-global-payments/benefits/ (application instruction? maybe benefits link). Must remove application instructions. - Then: "Applicant must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; We will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)." This is a requirement (visa). Should we keep? It's substantive info about eligibility. It's not boilerplate? It's a requirement. We can include under Requirements or Qualifications. - Then: "Diversity and EEO Statements Global Payments is an organization that stands against racism, intolerance and injustice in all its forms — one that respects, honors and celebrates the diversity of our team members and the differences among us. Our commitment to fostering a company culture that values and respects Inclusion and Diversity is steadfast. Standing together as one company, we will continue to work to drive positive change for the communities in which we live and work and stamp out injustice." This is EEO boilerplate; must remove. - Then: "linkedin.com/in/shonali-r-66744622 -SB" maybe a reference; remove. Thus we need to extract sections. Potential sections: - About the role: maybe the intro paragraph describing role and company. Could be "About the role". We have intro: "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for an Analyst, Finance to join our ever-evolving Technology Procurement FP&A team and help us unleash the potential of every business. Global Payments serves more than 6,000,000 customers, processing nearly $4 trillion in annual volume across 94 billion transactions in more than 175 countries." That's about role/company. - About The Team: appears twice; we can combine into one "About the Team" section. Content: description of team purpose etc. Also later inclusive team description. Could combine. - Responsibilities: "What You’ll Own" list. - Requirements/Qualifications/Skills: "What You’ll Bring" list plus visa requirement. We need to decide which headings to use. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose among these. We should not create sections without real content. Benefits, Pay, Schedule: not present (except link to benefits but that's just a URL; not substantive). So we omit those. We need to avoid duplication. We'll produce sections: About the role, About the Team, Responsibilities, Requirements (or Qualifications/Skills). Could combine Requirements and Skills into one? But we have separate headings possible. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section titled "Requirements". Or we could have "Qualifications" and "Skills" separate if we have distinct content. The "What You’ll Bring" includes knowledge, skills, bonus experience. That's both qualifications and skills. Could split: Qualifications: knowledge of FP&A, understanding Procure-to-Pay, ability to plan, etc. Skills: MS Office proficiency, Oracle EPBCS, SAP Ariba, Zip, vendor contracts, global stakeholders. But that's splitting thinly. Better to have one "Requirements" section covering all. Thus sections: About the role, About the Team, Responsibilities, Requirements. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities and Requirements we need lists. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point as is, not paraphrase. Let's extract bullet points from "What You’ll Own": - Relationships with, and coordination of, multi-functional teams including Procurement, Finance, Technology, Controllership and Technical Accounting, Treasury and Project Workstreams - Preparation of Procurement Process Review (“PPR”) analysis and allocation schedules - Maintain PPR Pipeline, build Cash Flow forecasts and prepare presentations - Ad-hoc trackers, approvals, and PRs/POs - Support of financial modelling of vendor agreements included in Business Cases - Support for Procure-to-Pay finance and accounting teams - Support of Procurement and Finance Integration, Separation and Transformation initiatives Note: some are sentences; we can keep as list items. Now "What You’ll Bring": - Knowledge of FP&A and Accounting principles, practices and processes in an international matrix organisation - Understanding Procure-to-Pay finance processes - Effective communication style - Strong critical thinking skills, using logic and reasoning to identify alternative solutions to problems - Ability to plan and accomplish work to ensure critical deadlines are met - Proficient in MS Office suite, including Excel and PowerPoint - It’s a bonus if you have Oracle EPBCS experience - SAP Ariba and/or Zip experience - Prior experience with vendor contracts and procurement discussions - Experience working with global stakeholders in North America, Europe and Asia Also visa requirement: "Applicant must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; We will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)." This is a requirement; we can include as a list item. Now About the Team: we have two paragraphs. Let's combine: First paragraph: "This Technology Procurement FP&A team is part of Global Payment’s Technology & Product FP&A group. The wider group covers all Technology spend across the Company, as well as strategic investments in our Products and Services. The Technology Procurement FP&A team ensures Technology, Procurement and Finance stakeholders have the right information to deliver large and/or complex deals with our vendors. The team ensures deals are modelled correctly, provides options and manages stakeholders to ensure value is delivered for Global Payments." Second paragraph: "Our inclusive and global teams win together every day. We’re proud to have the best minds in the industry, who you can learn from as you grow your career. The people, the energy, the connections – it’s unmatched. Come and be part of an ever-evolving company and get dynamic opportunities that go beyond borders. What makes a Globalpayer? Globalpayers think like a client, act like an owner and win as one team. We’re curious and innovative – always finding better ways to deliver impact. We empower each other to make decisions, and it’s our passion that drives excellence in everything we set out to do. Does this sound like you? Then you sound like a Globalpayer. Apply now to take your career global." We should remove the "Apply now to take your career global." as it's application instruction? It's a call to action; maybe considered boilerplate? The instruction says remove application instructions. So we should remove that sentence. Also remove the link to benefits. Also remove the "Does this sound like you? Then you sound like a Globalpayer." maybe okay as it's part of culture description; but it's somewhat promotional. It's not boilerplate; it's part of team description. We'll keep it but remove the apply call. Thus About the Team content: combine both paragraphs minus the apply sentence. Now About the role: intro paragraph: "Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for an Analyst, Finance to join our ever-evolving Technology Procurement FP&A team and help us unleash the potential of every business. Global Payments serves more than 6,000,000 customers, processing nearly $4 trillion in annual volume across 94 billion transactions in more than 175 countries." We should not repeat job title as heading; we already have heading About the role. Now we need to output HTML fragment only, no /, no markdown fences. Thus:

  About the role

  Ready to take your career global? Make your mark at one of the biggest names in payments. We’re looking for an Analyst, Finance to join our ever-evolving Technology Procurement FP&A team and help us unleash the potential of every business. Global Payments serves more than 6,000,000 customers,