SaaS (Zuora) Billing and Payments Implementation Manager

We need to output HTML fragment with sections: About the role? The posting includes description about Accenture Salesforce practice, role description, responsibilities, requirements, benefits, pay (salary ranges), schedule? Travel may be required, amount varies 0-100% depending on business need. That's schedule? Not exactly schedule but travel. Could include Travel section? The instruction: Use headings for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include a section only when posting has real, specific content. So we need to decide which sections have content. We have: - About the role: The initial paragraph about Accenture's Salesforce practice and role description: "We Are Accenture’s Salesforce practice..." and description of role: "You Are A person that loves to talk about subscriptions..." This is about the role. So we can have About the role section. - Responsibilities: The "The Work" bullet list: Lead discovery and solutioning sessions..., Software implementations..., Contribute..., Have the ability..., Author deliverables..., Be the SME..., Travel may be required... So we can list responsibilities. - Requirements: The "What You Need" bullet list: minimum one year experience..., minimum two years software implementation..., minimum three years experience as team lead..., Bachelor’s Degree or equivalent..., Bonus Points If Certifications..., Strong background in producing written deliverables... So we can list requirements. - Qualifications: Might overlap with requirements; but we could treat "Bonus Points If Certifications..." as qualifications? However we already have requirements. The instruction says prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications? But we have separate headings allowed. We need to decide if we have distinct content for Qualifications beyond requirements. The posting includes "Bonus Points If Certifications..." and "Strong background in producing written deliverables..." which could be considered qualifications. But we could put them under Requirements as well. To avoid thin sections, maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow headings list; we can omit Qualifications if not distinct. - Skills: Not explicitly listed; maybe we can infer skills like Zuora, Stripe, Salesforce Billing, etc. But they are mentioned in responsibilities. Could create Skills section listing those platforms. However we need to avoid filler. The posting does mention "One of many modern SaaS subscription/billing platforms are your tools and include Zuora, Stripe and Salesforce Billing." That's a skill/tool list. Could be Skills. - Benefits: Explicit Benefits section: "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." So we include Benefits. - Pay: There's compensation details: "Compensation at Accenture varies depending on a wide array of factors..." plus salary ranges per location. So we include Pay. - Schedule: Travel may be required, amount varies 0-100% depending on business need. That's not exactly schedule but could be considered schedule/travel. Could include Schedule section about travel. However the instruction says include Schedule only if posting actually states them. It does mention travel may be required, amount varies. That's schedule-related. So we can include Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. So we strip all that. We need to preserve all substantive information. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". The compensation text includes "Compensation at Accenture varies depending on a wide array of factors..." which is somewhat generic but it's actual content. We should keep it. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (prose)

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• Zuora
• Stripe
• Salesforce Billing
• Other SaaS subscription/billing platforms

Benefits

• Medical, dental, vision, life, and long-term disability coverage
• 401(k) plan
• Bonus opportunities
• Paid holidays
• Paid time off

Pay

Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. 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.

• California: $132,500 to $302,400
• Colorado: $132,500 to $261,300
• Connecticut: $132,500 to $261,300
• District of Columbia: $141,100 to $278,200
• Illinois: $122,700 to $261,300
• Maine: $112,900 to $222,500
• Maryland: $132,500 to $261,300
• Massachusetts: $132,500 to $278,200
• Minnesota: $132,500 to $261,300
• New York: $122,700 to $302,400
• New Jersey: $141,100 to $302,400
• Ohio: $122,700 to $241,900
• Virginia: $122,700 to $278,200
• Washington: $141,100 to $278,200

Schedule

Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements.

We need to ensure we didn't include any boilerplate like "Visit us here" link etc. The About the role section should include the description about Accenture Salesforce practice and role description. We need to preserve all substantive information; we can include the initial paragraph about Accenture's Salesforce practice and the role description. Let's extract that. Original 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." We need to keep that prose, but remove the link and its surrounding markup. So we should strip the tag and its content? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not boilerplate; it's a reference to "Visit us here". It's maybe considered navigation? It's a link to more info; could be considered navigation. Safer to remove the link and its text? The instruction says remove boilerplate, navigation, legal, EEO, etc. That link is navigation. So we should remove the entire element and its inner text "Visit us here to find out more about Accenture's Salesforce practice". However the sentence continues: after the link, there is "You Are A person that loves to talk about subscriptions." There's no space? Actually the original: "...practice You Are A person..." So after removing the link, we need to ensure proper spacing. We'll just produce a clean paragraph: "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). 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." We need to keep the capitalization? Not important. Now responsibilities: The "The Work" list: - 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