PeopleSoft Finance Senior Business Analyst
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must use - for any list of duties/requirements/benefits, and
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Job ID / requisition numbers as headings". Also remove "Advertised Salary Range Part/Full Time: Full Time" maybe not needed unless it's pay. It says "Advertised Salary Range Part/Full Time: Full Time". No actual salary range given, just part/full time. Since no salary amount, we should not create Pay section unless posting actually states them. It does not state salary amount, so we should not create Pay section. Schedule: not given. Benefits: they list benefits in "Exceptional Benefits That Invest in You:" and later repeated. So we can create Benefits section with list.
Responsibilities: we have "Key Responsibilities" list. Use
Responsibilities
with - .
Requirements/Qualifications: we have "What You'll Bring" (experience), "Preferred Qualifications", "Minimum Qualifications", "Knowledge/Skills/Abilities". We need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So we could combine qualifications into a single "Qualifications" section with lists. But we must preserve all substantive information; we can't omit details. We can combine but need to keep all details. Could create
Qualifications
and then have sub-lists? But we must use - for any list. Could have multiple
inside section. That's okay.
We also have "About UofSC" description; could be "About the role"? Actually "About UofSC" is about the institution, not role. Could be placed as a before sections. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have heading "About the role" for the role description (the "About The Role" paragraph). The "About UofSC" could be a general description maybe not needed as heading; could be a
before sections.
We also have "Advertised Job Summary" which is a paragraph summarizing role. Could be included under About the role or as its own paragraph.
We need to avoid duplication: there is repeated benefits text later; we should include only once.
We need to remove EEO statement, special instructions to applicant, job close date, etc.
We must not include application instructions (the link to apply). Also remove "Click https://..." etc.
We must not include "EEO Statement". Also remove "Preferred Qualifications Minimum Qualifications (Classified and Unclassified positions)" heading as we will incorporate into Qualifications.
We must not include "Knowledge/Skills/Abilities" as separate heading if we merge into Qualifications.
We must not include "Job Close Date", "Special Instructions to Applicant".
We must not include "Advertised Salary Range Part/Full Time: Full Time" as heading; we can maybe note full-time in a
but not as Pay section.
We must not include "About UofSC" as heading unless we treat as "About the role"? Actually "About UofSC" is about the university; we could just include as a
before sections without heading.
Thus final HTML:
About UofSC: ...
About the role
... (Advertised Job Summary + About The Role paragraph)
Responsibilities
- ... each responsibility
Qualifications
What You'll Bring:
- ... each bullet
Preferred Qualifications:
- ... each bullet
Minimum Qualifications:
- ... each bullet
Knowledge/Skills/Abilities:
- ... each bullet
Benefits
- ... each benefit
We need to ensure we preserve all substantive information from those sections.
Let's extract content.
About UofSC paragraph:
"From the Upstate to the Lowcountry, the University of South Carolina system is transforming the lives of South Carolinians through the impact of our eight institutions and 20 locations throughout the state. More than 50,000 students are enrolled at one of eight institutions, including the research campus in Columbia and comprehensive four-year universities in Aiken, Upstate and Beaufort. In addition, our Palmetto College campuses in Salkehatchie, Union, Lancaster and Sumter enable students to earn associate or bachelor's degrees through a combination of in-person, online or blended learning. All of our system institutions place strong emphasis on service — helping to build healthier, more educated communities in South Carolina and beyond."
We can keep as .
Advertised Job Summary:
"PeopleSoft Finance Senior Business Analyst Spend your days supporting the enterprise financial systems that help power South Carolina's flagship university while working in the heart of Columbia, one of the Southeast's most vibrant and growing capital cities. Join a dynamic team within the Division of Information Technology as we continue to enhance and modernize our PeopleSoft Financials environment to better serve faculty, staff, and students across the university. As a Senior PeopleSoft Finance Business Analyst, you will lead impactful projects, drive process improvements, collaborate with stakeholders across campus, and serve as a trusted expert in delivering innovative, customer-focused technology solutions. This is an opportunity to make a meaningful difference, expand your professional expertise, and contribute to the operational excellence that supports USC's mission of education, research, and service."
Note: The job title appears at start; we should not repeat job title as heading, but it's okay inside paragraph.
About The Role paragraph:
"In this role, you'll be a strategic partner helping shape how USC's financial systems serve the university community. We're seeking someone with strong PeopleSoft Financials experience with a background in post-award Grants Management, Receivables, and Billing who enjoys balancing production support, business analysis, process improvement, and project leadership. You'll have the opportunity to work with a talented team, contribute to major initiatives, and make a visible impact on the efficiency and effectiveness of our financial operations."
We can combine both paragraphs under About the role.
Key Responsibilities list:
- Support PeopleSoft Financials Users by leading incident triage, troubleshooting production issues, performing root cause analysis, and developing ad hoc PeopleSoft queries to support business users and operational needs.
- Lead business process analysis, system enhancements, and project delivery by evaluating current processes, identifying opportunities for improvement, defining requirements, creating functional specifications, and supporting and testing complex application modifications and upgrades.
- Serve as the functional subject matter expert for assigned PeopleSoft modules, providing guidance and support to business stakeholders, business analyst peers, and technical teams on processes, system functionality, and best practices.
- Lead and support strategic PeopleSoft initiatives by serving as the business analyst on mid-size to large projects, partnering with vendors and stakeholders, facilitating cross-functional collaboration, supporting release and change management activities, mentoring team members, and providing project estimates, status updates, and recommendations to leadership.
What You'll Bring (experience):
- PeopleSoft Financials Expertise: 5 or more years' experience supporting PeopleSoft Financials (FSCM) 9.x or higher, with demonstrable knowledge of application configurations, transaction processing, and underlying data relationships.
- Experience with Post-Award Grants Management and Accounts Receivable is highly desired.
- Additional experience in one or more of the following areas is also preferred: Billing, Accounting, Finance, Accounts Payable, Travel & Expenses, Purchasing, or related business operations.
- Strong Reporting and Analytical Skills: Proficiency with SQL, PeopleSoft Query Manager, and nVision reports, with the ability to leverage data to support business decisions, process improvements, and issue resolution.
- Collaborative Problem Solver: Proven ability to work effectively with business stakeholders, technical teams, and vendors to deliver customer-focused solutions; experience with Phire release management is a plus.
Why Join Us? (we could treat as Benefits? Actually it's more about motivations; but we have Benefits section separate. The "Why Join Us?" includes bullet points: Drive Enterprise-Wide Impact, Lead Meaningful Work, Be a Trusted Expert, Grow with a High-Performing Team, Perks of the University of South Carolina Downtown Location, Energetic Leadership, Exceptional Benefits That Invest in You. Some of those are benefits-like. However we already have Benefits section from later. To avoid duplication, we could incorporate the "Why Join Us?" points into Benefits or keep as separate section like "Why Join Us?" but instruction only lists certain headings; but we can still use other headings? It says use
for section headings (e.g. 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)." Likely they expect only those headings. So we should map content to those headings. "Why Join Us?" content can go under Benefits or maybe under Qualifications? Better to incorporate into Benefits as they are benefits/perks. However some points like "Drive Enterprise-Wide Impact" etc are more about role impact; could be under About the role? But we already have About the role. To keep sections few, we could incorporate those points into Benefits as additional bullet points.
But we must preserve all substantive information; we can add them to Benefits list.
Now Preferred Qualifications:
- Minimum Qualifications (Classified and Unclassified positions) Preferred related areas include, but are not limited to Accounting, Finance, Accounts Receivable and Billing, Accounts Payable, Purchasing, or Information Technology.
- PeopleSoft Financials 9.x or higher application support experience.
- Experience creating PeopleSoft Queries and nVision reports.
- Phire release management application support experience
Knowledge/Skills/Abilities list (many bullets). We need to preserve all.
Let's extract each bullet:
- Extensive knowledge of capabilities, techniques, and intricacies of enterprise resource planning (ERP) information systems – including deep knowledge of at least one of the following area: General Ledger, Purchasing, Accounts Payable, Accounts Receivable, Contracts, Grants Management, Projects, or Banking.
- Ability to understand and carry out complex technical analysis, instructions and requests.
- Ability to communicate in a clear and concise manner – including creating and giving presentations.
- Ability to work effectively with users, vendors, and IT personnel.
- Ability to identify and resolve problems.
- Ability to plan, direct, instruct, and review the work of technical personnel.
- Ability to lead complex technical projects.
- Extensive knowledge of technical documentation.
- Working knowledge of information system software, internet software, spreadsheet software and word processing software as well as basic PC applications and operations – including Word, Excel and other MS Office products.
- Project management skills.
- Occasional work at other than normal times may be required based on production support responsibilities and other duties as assigned from time-to
for prose. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Job ID / requisition numbers as headings". Also remove "Advertised Salary Range Part/Full Time: Full Time" maybe not needed unless it's pay. It says "Advertised Salary Range Part/Full Time: Full Time". No actual salary range given, just part/full time. Since no salary amount, we should not create Pay section unless posting actually states them. It does not state salary amount, so we should not create Pay section. Schedule: not given. Benefits: they list benefits in "Exceptional Benefits That Invest in You:" and later repeated. So we can create Benefits section with list. Responsibilities: we have "Key Responsibilities" list. Use
Responsibilities
with- .
Requirements/Qualifications: we have "What You'll Bring" (experience), "Preferred Qualifications", "Minimum Qualifications", "Knowledge/Skills/Abilities". We need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So we could combine qualifications into a single "Qualifications" section with lists. But we must preserve all substantive information; we can't omit details. We can combine but need to keep all details. Could create
Qualifications
and then have sub-lists? But we must use- for any list. Could have multiple
- inside section. That's okay.
We also have "About UofSC" description; could be "About the role"? Actually "About UofSC" is about the institution, not role. Could be placed as a
- ... each responsibility
- ... each bullet
- ... each bullet
- ... each bullet
- ... each bullet
- ... each benefit
before sections. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have heading "About the role" for the role description (the "About The Role" paragraph). The "About UofSC" could be a general description maybe not needed as heading; could be a
before sections. We also have "Advertised Job Summary" which is a paragraph summarizing role. Could be included under About the role or as its own paragraph. We need to avoid duplication: there is repeated benefits text later; we should include only once. We need to remove EEO statement, special instructions to applicant, job close date, etc. We must not include application instructions (the link to apply). Also remove "Click https://..." etc. We must not include "EEO Statement". Also remove "Preferred Qualifications Minimum Qualifications (Classified and Unclassified positions)" heading as we will incorporate into Qualifications. We must not include "Knowledge/Skills/Abilities" as separate heading if we merge into Qualifications. We must not include "Job Close Date", "Special Instructions to Applicant". We must not include "Advertised Salary Range Part/Full Time: Full Time" as heading; we can maybe note full-time in a
but not as Pay section. We must not include "About UofSC" as heading unless we treat as "About the role"? Actually "About UofSC" is about the university; we could just include as a
before sections without heading. Thus final HTML:
About UofSC: ...
About the role
... (Advertised Job Summary + About The Role paragraph)
Responsibilities
Qualifications
What You'll Bring:
Preferred Qualifications:
Minimum Qualifications:
Knowledge/Skills/Abilities:
Benefits
. Advertised Job Summary: "PeopleSoft Finance Senior Business Analyst Spend your days supporting the enterprise financial systems that help power South Carolina's flagship university while working in the heart of Columbia, one of the Southeast's most vibrant and growing capital cities. Join a dynamic team within the Division of Information Technology as we continue to enhance and modernize our PeopleSoft Financials environment to better serve faculty, staff, and students across the university. As a Senior PeopleSoft Finance Business Analyst, you will lead impactful projects, drive process improvements, collaborate with stakeholders across campus, and serve as a trusted expert in delivering innovative, customer-focused technology solutions. This is an opportunity to make a meaningful difference, expand your professional expertise, and contribute to the operational excellence that supports USC's mission of education, research, and service." Note: The job title appears at start; we should not repeat job title as heading, but it's okay inside paragraph. About The Role paragraph: "In this role, you'll be a strategic partner helping shape how USC's financial systems serve the university community. We're seeking someone with strong PeopleSoft Financials experience with a background in post-award Grants Management, Receivables, and Billing who enjoys balancing production support, business analysis, process improvement, and project leadership. You'll have the opportunity to work with a talented team, contribute to major initiatives, and make a visible impact on the efficiency and effectiveness of our financial operations." We can combine both paragraphs under About the role. Key Responsibilities list: - Support PeopleSoft Financials Users by leading incident triage, troubleshooting production issues, performing root cause analysis, and developing ad hoc PeopleSoft queries to support business users and operational needs. - Lead business process analysis, system enhancements, and project delivery by evaluating current processes, identifying opportunities for improvement, defining requirements, creating functional specifications, and supporting and testing complex application modifications and upgrades. - Serve as the functional subject matter expert for assigned PeopleSoft modules, providing guidance and support to business stakeholders, business analyst peers, and technical teams on processes, system functionality, and best practices. - Lead and support strategic PeopleSoft initiatives by serving as the business analyst on mid-size to large projects, partnering with vendors and stakeholders, facilitating cross-functional collaboration, supporting release and change management activities, mentoring team members, and providing project estimates, status updates, and recommendations to leadership. What You'll Bring (experience): - PeopleSoft Financials Expertise: 5 or more years' experience supporting PeopleSoft Financials (FSCM) 9.x or higher, with demonstrable knowledge of application configurations, transaction processing, and underlying data relationships. - Experience with Post-Award Grants Management and Accounts Receivable is highly desired. - Additional experience in one or more of the following areas is also preferred: Billing, Accounting, Finance, Accounts Payable, Travel & Expenses, Purchasing, or related business operations. - Strong Reporting and Analytical Skills: Proficiency with SQL, PeopleSoft Query Manager, and nVision reports, with the ability to leverage data to support business decisions, process improvements, and issue resolution. - Collaborative Problem Solver: Proven ability to work effectively with business stakeholders, technical teams, and vendors to deliver customer-focused solutions; experience with Phire release management is a plus. Why Join Us? (we could treat as Benefits? Actually it's more about motivations; but we have Benefits section separate. The "Why Join Us?" includes bullet points: Drive Enterprise-Wide Impact, Lead Meaningful Work, Be a Trusted Expert, Grow with a High-Performing Team, Perks of the University of South Carolina Downtown Location, Energetic Leadership, Exceptional Benefits That Invest in You. Some of those are benefits-like. However we already have Benefits section from later. To avoid duplication, we could incorporate the "Why Join Us?" points into Benefits or keep as separate section like "Why Join Us?" but instruction only lists certain headings; but we can still use other headings? It says use
for section headings (e.g. 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)." Likely they expect only those headings. So we should map content to those headings. "Why Join Us?" content can go under Benefits or maybe under Qualifications? Better to incorporate into Benefits as they are benefits/perks. However some points like "Drive Enterprise-Wide Impact" etc are more about role impact; could be under About the role? But we already have About the role. To keep sections few, we could incorporate those points into Benefits as additional bullet points. But we must preserve all substantive information; we can add them to Benefits list. Now Preferred Qualifications: - Minimum Qualifications (Classified and Unclassified positions) Preferred related areas include, but are not limited to Accounting, Finance, Accounts Receivable and Billing, Accounts Payable, Purchasing, or Information Technology. - PeopleSoft Financials 9.x or higher application support experience. - Experience creating PeopleSoft Queries and nVision reports. - Phire release management application support experience Knowledge/Skills/Abilities list (many bullets). We need to preserve all. Let's extract each bullet: - Extensive knowledge of capabilities, techniques, and intricacies of enterprise resource planning (ERP) information systems – including deep knowledge of at least one of the following area: General Ledger, Purchasing, Accounts Payable, Accounts Receivable, Contracts, Grants Management, Projects, or Banking. - Ability to understand and carry out complex technical analysis, instructions and requests. - Ability to communicate in a clear and concise manner – including creating and giving presentations. - Ability to work effectively with users, vendors, and IT personnel. - Ability to identify and resolve problems. - Ability to plan, direct, instruct, and review the work of technical personnel. - Ability to lead complex technical projects. - Extensive knowledge of technical documentation. - Working knowledge of information system software, internet software, spreadsheet software and word processing software as well as basic PC applications and operations – including Word, Excel and other MS Office products. - Project management skills. - Occasional work at other than normal times may be required based on production support responsibilities and other duties as assigned from time-to
- for any list. Could have multiple