Finance Lead, Systems Governance & Administration
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes Company Description (maybe not needed? It's not a heading we need; we can include as prose maybe under About the role? Actually "Company Description" is not one of the allowed headings; we can embed as prose maybe under a generic
but we should not create extra headings. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if content exists. We need to decide which sections to include. Content: There's a "Company Description" paragraph about AbbVie. Could be placed under "About the role"? But that heading is for role description. However we could treat the company description as part of "About the role" or just as a
before any heading. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid having a
before headings. So we can include a
for company description. Then "Job Description" paragraph: "The Finance Lead, Systems Governance & Administration is responsible for maintaining the SAC & BPC Administrative Guide and documentation related to user training and reference tools. This role serves as a key liaison between developers, support teams, and business stakeholders to ensure all SAC changes are fully documented. The role will also support continuous improvement of administrative documentation, standard operating procedures, training materials, and testing processes." This is role overview; could be placed under "About the role" heading. Then "Responsibilities" section with bullet points. So we will have
Responsibilities
with- ... etc.
Then "Qualifications" section: includes Bachelor's degree etc. Also "Preferred Qualifications". We could combine under Qualifications heading, listing both required and preferred. Or we could have separate headings? The allowed headings include Qualifications (maybe includes both). We'll put required qualifications under Qualifications, and preferred qualifications maybe as a sublist or note. We'll keep under Qualifications.
Then "Skills": The posting mentions skills like documentation, technical writing, Microsoft Office, organizational, analytical, communication, ability to manage multiple projects. Also preferred qualifications include SAP Analytics Cloud administration, SAP BPC planning, knowledge of SOX, audit controls, governance processes, experience developing training materials, familiarity with Finance planning processes. Those could be considered skills. We could create a Skills section. But we need to ensure we have real content. We have those.
Then "Benefits": The posting includes "We offer a comprehensive package of benefits including paid time off (vacation, holidays, sick), medical/dental/vision insurance and 401(k) to eligible employees. This job is eligible to participate in our short-term incentive programs." Also note about bonus etc. So we have benefits content.
Then "Pay": The posting includes compensation range description under Additional Information. It says: "Applicable only to applicants applying to a position in any location with pay disclosure requirements under state or local law: The compensation range described below is the range of possible base pay compensation that the Company believes in good faith it will pay for this role at the time of this posting based on the job grade for this position. Individual compensation paid within this range will depend on many factors including geographic location, and we may ultimately pay more or less than the posted range. This range may be modified in the future." However they didn't actually give numbers. They didn't provide a specific range. So we have no actual pay numbers. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD') and never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they didn't state actual numbers, we should not create a Pay section. However they did mention benefits, so we can include Benefits.
Schedule: Not mentioned. So no Schedule.
Thus sections: About the role (maybe combine company description and job description), Responsibilities, Qualifications, Skills, Benefits.
We need to ensure we don't repeat job title as heading. Not needed.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, preferred qualifications, skills, benefits.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes EEO statements at end: "AbbVie is an equal opportunity employer..." etc. Also links for accommodation. Those should be removed.
Also "Additional Information" includes pay range description and benefits note; we already captured benefits. The pay range description is filler (no actual range) so we should drop it (or maybe we could include as a
but not as a Pay heading). Since it's just describing that they may disclose range but not giving numbers, it's not substantive? It's somewhat substantive but it's basically saying they may disclose range but not giving numbers. The instruction says never create Pay section unless posting actually states them. It didn't state actual numbers, so we should not create Pay heading. But we could still include the paragraph as a
somewhere? It's not a heading; but it's part of Additional Information. However it's somewhat boilerplate legal. Might be considered boilerplate? It's about pay disclosure. Might be considered legal boilerplate. Safer to drop it. Thus we will output:
Company Description paragraph
About the role
Job Description paragraph
Responsibilities
- ... each responsibility as li
Qualifications
- ... required qualifications
Preferred Qualifications:
maybe we can embed as- under Qualifications with a note? But we need to preserve detail. Could do
- .
Now Qualifications (required):
- Bachelor's degree in Information Systems, Computer Science, Business, Finance, or related field.
- 3+ years of experience supporting enterprise planning solutions.
- Strong documentation and technical writing skills.
- Advanced Microsoft Office skills, including Excel, Word, PowerPoint, SharePoint, and Teams.
- Excellent organizational, analytical, and communication skills.
- Ability to manage multiple projects and priorities simultaneously.
Preferred Qualifications (list):
- SAP Analytics Cloud (SAC) administration or support experience.
- SAP BPC planning experience.
- Knowledge of SOX, audit controls, and governance processes.
- Experience developing training materials and conducting knowledge transfer sessions.
- Familiarity with Finance planning processes such as Forecast, LBE, Plan, and LRP cycles.
Now Skills: The posting includes many skill mentions; some overlap with qualifications. But we can create a Skills section that enumerates skills like documentation, technical writing, Microsoft Office, organizational, analytical, communication, project management, SAP SAC administration, SAP BPC planning, SOX knowledge, audit controls, governance processes, training material development, knowledge transfer, finance planning processes (Forecast, LBE, Plan, LRP). However we must avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in the original? But we should not invent. We can include skills as a separate section, but we need to ensure we are not missing any skill not already captured. The qualifications already list many skills; but we can still include a Skills section that maybe consolidates them. However we risk duplicating content; but it's not prohibited. The instruction says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid repeating content. However we should aim to preserve all substantive information; we can include skills as a separate section but we must ensure we don't leave out any skill mentioned. Since qualifications already cover many, we could still include Skills but we need to ensure we don't omit any. Safer to not create a Skills section if its content is already covered under Qualifications; but the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine qualifications and skills into one Qualifications section, and not create a separate Skills heading. However the allowed headings include Skills; we can omit if we think it's thin. The qualifications already cover skills; we could treat them as qualifications. So we might not need a separate Skills heading. But we have also benefits. So sections: About the role, Responsibilities, Qualifications, Benefits. We need to include both required and preferred qualifications under Qualifications. We can separate with a
"Preferred Qualifications:" then
Qualifications
then- for required, then another
- for preferred with a heading? But we cannot create extra headings not allowed? We could use
for "Preferred Qualifications:" then
- . That's okay.
Similarly Skills: we could list under Skills heading.
Benefits:
Benefits
- ...
. Job Description (under About the role): "The Finance Lead, Systems Governance & Administration is responsible for maintaining the SAC & BPC Administrative Guide and documentation related to user training and reference tools. This role serves as a key liaison between developers, support teams, and business stakeholders to ensure all SAC changes are fully documented. The role will also support continuous improvement of administrative documentation, standard operating procedures, training materials, and testing processes." Now Responsibilities bullet points from the posting: List: - Own and maintain the enterprise SAC Administration Guide and supporting documentation. - Coordinate knowledge transfer sessions with developers and functional SMEs. - Translate technical recordings and knowledge transfer sessions into structured administrative documentation. - Ensure all administration documentation remains current, complete, audit-ready, and aligned to production functionality. - Manage document version control, approvals, review cycles, and archival processes. - Maintain SharePoint repositories, documentation trackers, and supporting governance materials. - Establish and enforce documentation standards, templates, and quality controls. - Develop governance documentation, and operational procedures. - Ensure documentation supports operational continuity and knowledge management. - Partner with development teams to ensure technical documentation accurately reflects implemented functionality. - Leads and develops monthly, quarterly and annual Plan, LRP and LBEs as required, including P&L, headcount, balance sheet, expense and capital using planning system and incorporates review changes of both financial and operating management. - Operates independently to prepare relevant variance analysis for each planning cycle and develops meaningful management reporting schedules for direct areas supported. - Works directly with Accounting Shared Service contact on monthly close process and financial reporting to ensure complete, accurate and timely monthly actual results, including variance analysis and commentary for P&L, headcount and balance sheet. - Understands monthly results and communicates issues vs. benchmark to businesses supported to agree on resolution or action plan. - Provides management with clear insights into drivers of business and financial performance and risk; assesses business/market opportunities and informs/recommends prioritization decisions. - Leads financial reviews and approvals (purchase order requests and invoices). - Leads ad hoc analysis, projects and process improvements as needed. - May have supervisory responsibility for one or more direct reports. We need to keep each as