SaaS (Zuora) Billing and Payments Implementation Manager

We need to output HTML fragment with sections: About the role? The posting includes "We Are:" description of Accenture's Salesforce practice. That's about the company, maybe "About the role"? Actually "We Are:" is about the practice, could be "About the role"? Usually "About the role" is description of role. But we have "You Are:" describing candidate profile. "The Work:" describing responsibilities. "What you need:" requirements. "Bonus Points If:" qualifications/skills. Compensation: they have salary ranges per location. Also benefits: they mention benefits. Also schedule? Not given. Travel may be required. So we need sections: About the role? Could combine "We Are:" as about the company but maybe better as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to pick headings that match content. We have: - About the role: could be the "We Are:" description? Actually that's about Accenture's Salesforce practice, not the role. But we could treat as "About the role" describing the team/practice. Might be acceptable. - Responsibilities: from "The Work:" bullet points. - Requirements: from "What you need:" bullet points. - Qualifications/Skills: from "Bonus Points If:" maybe skills. - Benefits: from benefits paragraph. - Pay: from salary ranges table. - Schedule: not given; travel may be required but not schedule. Could omit Schedule section. We must not create sections with placeholder text. So include only those with real content. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, accommodation, legal statements, etc. Also remove "Requesting an Accommodation", "Equal Employment Opportunity Statement", "Other Employment Statements", etc. Also remove "Visit us here to find out more about Accenture's Salesforce practice" maybe keep as part of About the role? It's a link but we can keep as prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details: e.g., "We Are: Accenture’s Salesforce practice, and we live to see what this platform can do. Since we were one of the first on the scene, we’re the largest global Salesforce practice, not to mention one of the best. In fact, we are the industry-leader for building Salesforce solutions, and we are Master Certified in all 12 industries and clouds. We use tech like Lightning, Einstein, and Bolt to build stronger, better relationships with customers. And we are always learning. We’re building the most resourceful team on the planet, and helping our people with new skills, training, and support to get over 4,200 certifications including Certified Technical Architect (CTA). Visit us here to find out more about Accenture's Salesforce practice" "You Are: A person that loves to talk about subscriptions..." etc. "The Work: Lead discovery and solutioning sessions focused on Order to Revenue with a focus on billing, payments, rev rec and collections. Software implementations that typically involve Zuora, Salesforce Billing, Stripe or other SaaS based, non-ERP solutions. Contribute to larger Lead to Cash programs though ownership of post-order processes Have the ability to speak to a broad range of client team members including finance and product owners. Author deliverables that can include detailed designs, process flows and user stories. Be the SME for all things subscription and payments. Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements." "What you need: A minimum of one year experience in SaaS Billing system such as Zuora, Salesforce Billing, Aria or other recognized leader in the SaaS billing space A minimum of two years software implementation experience A minimum of three years of experience working as a team lead or member of a multi-team program. Bachelor’s Degree or equivalent (12 years) work experience (If an, Associate’s Degree with 6 years of work experience) Bonus Points If: Certifications in SaaS software platforms such as Salesforce or Zuora Strong background in producing written deliverables including requirements, detailed designs and process flows" Note: The "Bonus Points If:" appears inside "What you need:"? Actually after the degree requirement they wrote "Bonus Points If:" then list. We'll treat as separate section maybe "Preferred Qualifications" or "Skills". We'll use "Skills" heading for those. Compensation: they have a paragraph: "Compensation at Accenture varies depending on a wide array of factors... As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below. We anticipate this job posting will be posted until 11/07/2026." Then they list salary ranges per location. Also they mention benefits: "Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture" Thus we need Pay section with the salary ranges table. Benefits section with benefits description. We should not include the posting end date? It's substantive? It's about posting duration; maybe we can include in a

under About the role? But it's not a standard heading. Could include as a note in About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that line somewhere. Could put in a

under About the role or maybe a separate "Posting Info" but not a standard heading. Better to include in About the role paragraph. We must not include boilerplate like EEO, accommodation, legal statements, etc. So we will strip those. Now produce HTML:

About the role

We Are: Accenture’s Salesforce practice, and we live to see what this platform can do. Since we were one of the first on the scene, we’re the largest global Salesforce practice, not to mention one of the best. In fact, we are the industry-leader for building Salesforce solutions, and we are Master Certified in all 12 industries and clouds. We use tech like Lightning, Einstein, and Bolt to build stronger, better relationships with customers. And we are always learning. We’re building the most resourceful team on the planet, and helping our people with new skills, training, and support to get over 4,200 certifications including Certified Technical Architect (CTA). Visit us here to find out more about Accenture's Salesforce practice. You Are: A person that loves to talk about subscriptions. As the economy shifts from buy to subscribe, you are excited to guide companies on their transformation journey. Since the heart of any subscription engine is billing and payments, you are in your element. In addition to understanding the details of invoicing, payment processing and collections, you can lead the discovery conversation with finance, product and IT teams on defining a scalable solution. Regardless of industry, your knowledge of core recurring, usage and one time products can be applied to any client. One of many modern SaaS subscription/billing platforms are your tools and include Zuora, Stripe and Salesforce Billing. With your experience and ability to lead, you can upskill the members of your team and the client.

But maybe we should split "You Are:" into a separate section? The instruction only lists certain headings; we could treat "You Are:" as part of About the role or maybe as "Qualifications"? Actually "You Are:" describes candidate profile, could be under "Requirements" or "Skills". But we already have Requirements and Skills sections. Might be better to keep "You Are:" as part of About the role? However the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings. It doesn't say we cannot add other headings, but better to stick to those. Thus we need to map content to those headings. About the role: could include the "We Are:" description (company/practice) and maybe also the "You Are:"? But "You Are:" is more about candidate traits; maybe that fits under Requirements or Skills. However we have separate Requirements (what you need) and Skills (bonus points). The "You Are:" is more about mindset/experience; could be part of Requirements? But we already have a "What you need:" section for hard requirements. The "You Are:" is more about attitude; could be placed under "About the role" as description of ideal candidate. Might be okay. Alternatively, we could treat "You Are:" as part of "Requirements" but it's not a requirement per se. Safer to put under About the role. Thus About the role paragraph will include both We Are and You Are. Responsibilities: from The Work. Requirements: from What you need (the mandatory requirements). We'll list as

• . Skills: from Bonus Points If. Benefits: from benefits paragraph. Pay: from salary ranges table. We should not include Schedule. Now we need to preserve all substantive information: include the sentence about travel may be required and travel 0-100% within Responsibilities. Include the line about posting until 11/07/2026 maybe under About the role as a note. We must not include boilerplate like EEO, accommodation, legal statements, etc. Now craft HTML. We need to ensure we don't duplicate lines. Let's extract exact text: We Are: Accenture’s Salesforce practice, and we live to see what this platform can do. Since we were one of the first on the scene, we’re the largest global Salesforce practice, not to mention one of the best. In fact, we are the industry-leader for building Salesforce solutions, and we are Master Certified in all 12 industries and clouds. We use tech like Lightning, Einstein, and Bolt to build stronger, better relationships with customers. And we are always learning. We’re building the most resourceful team on the planet, and helping our people with new skills, training, and support to get over 4,200 certifications including Certified Technical Architect (CTA). Visit us here to find out more about Accenture's Salesforce practice You Are: A person that loves to talk about subscriptions. As the economy shifts from buy to subscribe, you are excited to guide companies on their transformation journey. Since the heart of any subscription engine is billing and payments, you are in your element. In addition to understanding the details of invoicing, payment processing and collections, you can lead the discovery conversation with finance, product and IT teams on defining a scalable solution. Regardless of industry, your knowledge of core recurring, usage and one time products can be applied to any client. One of many modern SaaS subscription/billing platforms are your tools and include Zuora, Stripe and Salesforce Billing. With your experience and ability to lead, you can upskill the members of your team and the client. The Work: Lead discovery and solutioning sessions focused on Order to Revenue with a focus on billing, payments, rev rec and collections. Software implementations that typically involve Zuora, Salesforce Billing, Stripe or other SaaS based, non-ERP solutions. Contribute to larger Lead to Cash programs though ownership of post-order processes Have the ability to speak to a broad range of client team members including finance and product owners. Author deliverables that can include detailed designs, process flows and user stories. Be the SME for all things subscription and payments. Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements. What you need: A minimum of one year experience in SaaS Billing system such