Coordinator, Student Business Processes

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc. We need to parse the posting. Title: Coordinator, Student Business Processes Employee Classification: PE - Professional/Technical Exempt Pay Grade: PT 08 Division: Business and Finance Subdivision: Controller Department: Business and Finance Campus Location: Main Campus General Summary: Plan and supervise administrative, operational, and technical activities with moderate authority to make commitments on behalf of Student Business Services. This may include tracking and monitoring student refunds, billing, student concerns, and processing in various vendor/partner computer applications. Principal Duties And Responsibilities: list of duties. Other duties as assigned. Minimum Qualifications: Knowledge of business administration principles and report writing tools with strong skills in written and interpersonal communication. Bachelors Degree in Accounting or related Business field is required. Bachelors degree in Accounting Information Systems is desirable. Previous Experience In Customer Service Is Required. Three years of systems administration experience working with Blackboard, TouchNet Cashiering, BankMobile, or a comparable 3rd party application, is required. Experience within the last 3 years with systems integration is required. Preferred Qualifications: Previous experience managing system upgrades is required. Ability to define and develop solutions to business needs is necessary. Ability to communicate effectively both written and oral is necessary. Demonstrated ability to work effectively in a team-oriented design/development process is necessary. Special Instructions: N/A Appointment Percentage: 100% We need sections: About the role (maybe General Summary), Responsibilities (Principal Duties), Requirements (Minimum Qualifications?), Qualifications (Preferred Qualifications?), Skills (maybe communication etc), Benefits (none), Pay (Pay Grade maybe?), Schedule (maybe appointment percentage? but schedule is about work hours; not given). We must only include sections if posting has real specific content. We have Pay Grade: PT 08. That's pay info. So we can include Pay section with that. Schedule: Not given. No mention of schedule besides "Work some nights and weekends during the opening of semesters and off-site events." That's schedule info. So we can include Schedule section with that. Benefits: Not mentioned. So omit Benefits. Skills: Could extract from qualifications: strong written and interpersonal communication, ability to define/develop solutions, ability to communicate effectively both written and oral, demonstrated ability to work effectively in a team-oriented design/development process. Also knowledge of business administration principles and report writing tools. So we can include Skills section. About the role: General Summary. Responsibilities: Principal Duties. Requirements: Minimum Qualifications. Qualifications: Preferred Qualifications. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate like EEO etc (none present). Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

Plan and supervise administrative, operational, and technical activities with moderate authority to make commitments on behalf of Student Business Services. This may include tracking and monitoring student refunds, billing, student concerns, and processing in various vendor/partner computer applications.

Responsibilities

• Coordinate system software upgrades and modifications as they relate to Eagle Card, Touchnet, Blackboard, Ellucian Banner, and all other Student Business Services partner computer applications.
• Serve as liaison between Eastern Michigan and all 3rd party software vendor partners.
• Identify, document and troubleshoot application related issues and assist users and technical staff accordingly.
• Responsible for leading process improvements integrating 3rd party software with Ellucian Banner where possible.
• Act as liaison with various business offices in the Controller Department regarding all Finance integrations.
• Monitor and track equipment needs, such as hardware and software for vendor partner systems.
• Participate in the development of departmental policies and procedures, with general responsibility for the implementation, monitoring, and interpretation of policy directives concerning any system changes.
• Represent the department to other administrators and to outside agencies, with authority to make commitments on administrative policies and procedures within specified parameters.
• Present for Fast Track and other related programs.
• Ensure quality customer service, handle complaints, and problem cases.
• Utilize Banner to complete job responsibilities such as research student refunds, non-refundable aid, and time out disbursements.
• Analyze, prepare, review and process all student refund requests while adhering to university policy and federal regulations.
• Maintain current knowledge of processing financial aid and managing FSA funds, including methods of disbursement, credit balances, condition of disbursement, and student and parent loans.
• Provide oral and written communication to students and other business units to help resolve refund and billing issues that students may encounter.
• Answer and/or resolve customer disputes, complex problems, and questions concerning refunds.
• Update websites, WIKI, and procedure manuals.
• Work some nights and weekends during the opening of semesters and off-site events.
• Perform related duties, as required.

Requirements

• Knowledge of business administration principles and report writing tools with strong skills in written and interpersonal communication.
• Bachelor's Degree in Accounting or related Business field is required.
• Bachelor's degree in Accounting Information Systems is desirable.
• Previous experience in customer service is required.
• Three years of systems administration experience working with Blackboard, TouchNet Cashiering, BankMobile, or a comparable 3rd party application is required.
• Experience within the last 3 years with systems integration is required.

Qualifications

• Previous experience managing system upgrades is required.
• Ability to define and develop solutions to business needs is necessary.
• Ability to communicate effectively both written and oral is necessary.
• Demonstrated ability to work effectively in a team-oriented design/development process is necessary.

Skills

• Strong written and interpersonal communication.
• Knowledge of business administration principles and report writing tools.
• Ability to define and develop solutions to business needs.
• Ability to communicate effectively both written and oral.
• Demonstrated ability to work effectively in a team-oriented design/development process.

Pay

Pay Grade: PT 08

Schedule

Work some nights and weekends during the opening of semesters and off‑site events.

We need to ensure we didn't repeat content unnecessarily. The Skills section duplicates some from Requirements/Qualifications but that's okay as long as we preserve all substantive info. However we might be duplicating too much; but instructions: Preserve ALL substantive information; do NOT invent or summarize away detail. It's okay to have overlapping content if it's present in multiple places. However we might be repeating same bullet points from Requirements and Qualifications into Skills; but those are also present elsewhere. It's not prohibited. However we might want to avoid duplication but not required. The instruction: "Prefer a few substantive sections over many thin ones." Having Skills separate may be thin but it's okay if we have substantive content. Could combine Skills into Requirements or Qualifications but we already have those sections. Might be better to omit Skills if it's just repeating. But we need to include all substantive info; if we omit Skills, we still have that info in Requirements and Qualifications. So we can drop Skills to avoid thin section. Let's see: The Skills we listed are basically same as some points in Requirements and Qualifications. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Check if any other info: Employee Classification, Division, Subdivision, Department, Campus Location, Appointment Percentage. Those are metadata; we could fold into a short

under About the role or maybe a separate "Details" section but not required headings. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph after About the role maybe containing classification, division, subdivision, department, location, appointment percentage. Or we could add a

with that info. We need to preserve ALL substantive information. So we must include Employee Classification, Division, Subdivision, Department, Campus Location, Appointment Percentage somewhere. Not as headings. So we can add a

after About the role that includes those. Let's craft:

About the role

Plan and supervise administrative, operational, and technical activities with moderate authority to make commitments on behalf of Student Business Services. This may include tracking and monitoring student refunds, billing, student concerns, and processing in various vendor/partner computer applications. Employee Classification: PE - Professional/Technical Exempt; Pay Grade: PT 08; Division: Business and Finance; Subdivision: Controller; Department: Business and Finance; Campus Location: Main Campus; Appointment Percentage: 100%.

But we already have Pay and Schedule sections; we might duplicate Pay Grade. Better to keep Pay Grade in Pay section and not duplicate. However we need to include Pay Grade somewhere; we have Pay section. So we can omit Pay Grade from the About paragraph. Similarly we might include Schedule info in Schedule section; we can omit from About paragraph. Thus About paragraph includes Employee Classification, Division, Subdivision, Department, Campus Location, Appointment Percentage. Let's write:

Employee Classification: PE - Professional/Technical Exempt; Division: Business and Finance; Subdivision: Controller; Department: Business and Finance; Campus Location: Main Campus; Appointment Percentage: 100%.

Now Pay section:

Pay

Pay Grade: PT 08

Schedule section:

Schedule

Work some nights and weekends during the opening of semesters and off‑site events.

Now ensure we didn't include any boilerplate like "Other duties as assigned." Already included in Responsibilities list as a bullet. Good. Check for any duplicated lines: We have bullet "Work some nights and weekends during the opening of semesters and off-site events." That's also in Schedule section; we have it both as a bullet and schedule paragraph. That's duplication. We should avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but maybe we should avoid repeating same detail in two places. Better to keep it only in Schedule section and remove from Responsibilities bullet. However the bullet is part of Principal Duties; it's a duty. If we remove it, we lose that duty from Responsibilities. But we could keep it in Responsibilities and not duplicate in Schedule; but then Schedule section would be empty or just mention that schedule info is covered elsewhere. However we need a Schedule section only if posting has real specific content for it. The posting does have that sentence; we could keep it in Responsibilities and not create a separate Schedule section (since we could fold schedule info into Responsibilities). But the instruction says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having schedule info also elsewhere. But we prefer few substantive sections over many thin ones. Having a Schedule section with just that sentence may be thin; maybe better to incorporate schedule info