Senior Accounts Receivable Billing Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if appropriate. Not required to use all. We should include sections only when posting has real specific content. Values could be considered part of "About the role" or maybe we could create a section "Values" but not in allowed list; better to incorporate into "About the role" prose.
We also have schedule info: hybrid schedule with Tuesdays and Wednesdays required in-office. That's schedule content. So we can create a Schedule section.
Benefits: we have list of benefits.
Pay: not provided, so omit.
Qualifications/Skills: we have requirements that could be split into Qualifications and Skills but we can just use Requirements section covering both. The instruction says we can use Qualifications, Skills headings if we have content. But we have requirements that include education, experience, proficiency, skills. Could split but not required. Safer to keep a single Requirements section.
Thus sections: About the role (intro paragraph), Responsibilities (list), Requirements (list), Benefits (list), Schedule (maybe short paragraph). Ensure we don't include filler like "commensurate with experience". Not present.
We must not include boilerplate: EEO, compensation disclaimer, etc. Also remove "Other duties as assigned" maybe considered boilerplate? It's part of responsibilities list; it's substantive? It's generic but it's in the posting. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "Other duties as assigned" is generic but it's in the posting; we should keep it as it's part of responsibilities. It's not boilerplate like EEO. So keep.
Now produce HTML:
About the role
Vector Solutions is a leading, AI-enabled, performance platform powering safe, compliant, and efficient operations for the public, educational, and commercial sectors. We bring training, safety, and workforce operations together to boost readiness, reduce risk, and drive high-performance results for the everyday heroes who count on us. We are seeking an experienced and detail-oriented Senior Biller to join our dynamic finance team. The Senior Biller will oversee billing processes, ensuring timely and accurate invoicing, while managing complex billing operations. This role requires strong analytical skills, meticulous attention to detail, and expertise in billing practices within Salesforce and NetSuite. You will collaborate closely with sales, customer service, and finance teams to ensure smooth billing processes and enhance overall customer satisfaction.
Responsibilities
- Oversee the end-to-end billing cycle, ensuring accurate and timely processing of invoices and payments.
- Manage and resolve complex billing inquiries and disputes from clients, working closely with the collections and customer service teams.
- Review and verify billing data to ensure accuracy and compliance with contracts, policies, and procedures.
- Generate monthly, quarterly, and annual billing reports and assist with internal audits.
- Analyze billing discrepancies and work with relevant departments to resolve issues.
- Maintain and update billing records, ensuring proper documentation for each client.
- Implement process improvements to increase efficiency and accuracy in billing operations.
- Assist in the development and enforcement of billing procedures and policies.
- Coordinate with finance and accounting teams to ensure proper reconciliation of payments and accounts.
- Other duties as assigned.
Requirements
- Accounting Certificate or Associate Degree in Finance / Accounting required; Bachelor's degree in Accounting, or related field (preferred).
- 5+ years of experience billing, invoicing, and other accounts receivable-related functions.
- In-depth knowledge of billing systems, invoice practices, and financial reconciliation.
- Strong proficiency in accounting software (e.g., QuickBooks, SAP, Oracle - NetSuite).
- Excellent communication and interpersonal skills to work with cross-functional teams and clients.
- High level of attention to detail and accuracy in billing and financial reporting.
- Ability to manage multiple tasks, prioritize workloads, and meet deadlines.
- Strong problem-solving skills and ability to work independently.
- Proficient in Microsoft Office Suite (Excel, Word, PowerPoint).
- Proficient in Salesforce.
- Ability to work a hybrid schedule out of our Tampa office, with Tuesdays and Wednesdays as required in-office days.
Benefits
- Friendly, open, and casual work environment
- Comprehensive benefits package effective the first of the month after hire
- Matching 401(k) retirement plan
- Healthy work-life balance with flexible work arrangements and generous time off
- Generous referral incentive program
- Tuition Reimbursement Program
- Pet Insurance
- OnePass Gym/Wellness Discount Program
- Calm Health-Employee Membership
- Company social events
- Employee Resource Groups
- Philanthropic opportunities
Schedule
Ability to work a hybrid schedule out of our Tampa office, with Tuesdays and Wednesdays as required in-office days.
But note schedule already included in requirements; we might duplicate. Better to not duplicate. The schedule info is already in requirements; we could keep it only there and not create schedule section. However the instruction: include a section ONLY when posting has real specific content for it. The schedule content exists; we could put it in Schedule section and remove from requirements to avoid duplication. But we might lose that detail if we remove from requirements. Better to keep schedule in requirements and not create separate schedule section to avoid duplication. The instruction says preserve ALL substantive information; duplication is not prohibited but we should avoid redundant sections. It says "Prefer a few substantive sections over many thin ones." So we can keep schedule within requirements and not create schedule section. Thus we will not have Schedule section. Check that we didn't include Pay section. Now ensure we removed all boilerplate: EEO, compensation disclaimer, etc. Also removed "What We Value" section (not in allowed headings). Could we incorporate values into About the role? Might be okay to add a short paragraph about values after intro? But that would be adding content not originally separate; but we could incorporate as part of About the role prose. However the values list is substantive; we should preserve it. The instruction: preserve ALL substantive information. So we need to include the values somewhere. We could add a section "Values" but not in allowed headings list; but the list says e.g., not exhaustive? It says "Use