District Credit Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: The Role (description), Key Responsibilities, What You Will Need (Requirements/Qualifications), What We Offer (Benefits). Also maybe "Why Join ASSA ABLOY Entrance Systems?" includes benefits etc. But we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - Intro about company (maybe "About the role"? Actually "About the role" is not present; we have "The Role:" description. Could treat as "About the role". Or we could have a section "About the role" with paragraph describing role. - Key Responsibilities: list. - What You Will Need: requirements/qualifications/skills. - What We Offer: benefits. Also there is "Why Join ASSA ABLOY Entrance Systems?" with bullet points: Comprehensive Benefits, Meaningful Impact, Career Growth & Development. That's more fluff but includes benefits etc. However we already have benefits in "What We Offer". We should not duplicate. We can combine benefits info. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

  About the role

  The District Credit Manager oversees credit and collection operations within an assigned territory, ensuring timely and effective credit decisions and account resolution. This role is responsible for conducting credit investigations, performing underwriting analysis, and interpreting financial data to establish credit limits and mitigate risk. The manager monitors aging accounts, supervises collection efforts, ensures compliance with lien and bond laws, and collaborates closely with sales and district management to resolve disputes and optimize receivables performance. Additionally, this role leads and motivates a credit team, facilitates agency placements, recommends write-offs or legal action as necessary, and contributes to continuous process improvement through reporting and analysis. This position reports to the Director Credit Collections, NA.

  Responsibilities

  • Conduct and supervise credit investigations on existing and potential customers
  • Perform underwriting analysis on GC’s/owners, sureties, and other pertinent parties for new jobs
  • Analyze and interpret information received from corporate financial statements, D&B, NACM and other credit services to establish unsecured and secured credit extension within assigned limits of authority
  • Prepare and submit necessary monthly reports to management regarding collection issues
  • Follow closely the course of aging accounts and determine action needed
  • Perform and supervise all collection call activity for accounts within the assigned territory with timely follow up
  • Review lien / bond filing dates to ensure compliance and protect collectability of AR
  • Apprise Director of Credit & Collections on collection activity and key issues as requested
  • Follow all required state/federal lien/bond laws for branches assigned
  • Follow up on disputes timely and work with District Managers, Salesmen, and appropriate personnel for timely resolution
  • Motivate, train, and monitor activities of assigned credit team
  • Facilitate placement of accounts with collection agencies
  • Recommend bad debt write offs, reserves, and legal action when necessary
  • Communicate regularly and partner with District Managers, Salesman, and appropriate personnel regarding collection and next steps
  • Recommend process improvements to enhance efficiency of team and department
  • Ad-hoc reporting as needed

  Requirements

  • 5+ years in the credit & collection field, construction industry preferred
  • Analytical financial skills
  • Excellent communication skills both oral and written
  • Organizational, Prioritization, and Time Management skills
  • Ability to handle stress successfully and multi-task
  • Ability to work independently on assigned tasks
  • Computer software skills (Windows, Office, Excel)
  • Interpersonal skills and conflict resolution
  • Understanding of KPI’s and performance metrics
  • Ability to work as a team

  Benefits

  • Comprehensive Benefits: competitive pay, robust health insurance options, retirement plans
  • PTO, holidays, tuition reimbursement and service awards
  • Health, dental, and vision plans
  • 401(k) with company matching
  • Short- and long-term disability, life, and accidental insurance
  • 15 PTO days and 11 paid holidays
  • Work-Life Balance: Flexible scheduling for when life happens
  • Ongoing Training & Recognition: structured onboarding, online courses, learning from experienced colleagues, Length of Service awards
  We need to ensure we didn't include Pay or Schedule sections unless explicitly stated. Benefits includes mention of competitive pay but not explicit pay amount; we can keep under Benefits. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated, so okay. We should avoid duplication: we listed "Comprehensive Benefits: competitive pay, robust health insurance options, retirement plans" and also separate health/dental/vision etc. Might be okay but could be considered duplication. However we need to preserve ALL substantive information; not invent or summarize away detail. The posting includes both "Comprehensive Benefits Enjoy competitive pay, robust health insurance options, and retirement plans. Your well-being matters to us, which is why we also offer PTO, holidays, and additional perks like tuition reimbursement and service awards." and later "What We Offer: Comprehensive Benefits Health, dental, and vision plans 401(k) with company matching Short- and long-term disability, life, and accidental insurance 15 PTO days and 11 paid holidays Work-Life Balance Flexible scheduling for when life happens. Ongoing Training & Recognition Get up to speed quickly with our structured onboarding process. Access to online courses to keep your skills sharp and up to date. Learn from experienced colleagues and industry experts. Length of Service awards to celebrate your milestones." Thus we need to include all those details. We can combine into a Benefits section with bullet points covering each distinct benefit. Let's list distinct benefits: - Competitive pay - Robust health insurance options - Retirement plans - PTO (paid time off) - Holidays - Tuition reimbursement - Service awards - Health, dental, and vision plans - 401(k) with company matching - Short- and long-term disability - Life insurance - Accidental insurance - 15 PTO days (maybe same as PTO) - 11 paid holidays - Work-Life Balance: Flexible scheduling - Ongoing Training & Recognition: structured onboarding, online courses, learning from experienced colleagues, Length of Service awards We may have overlapping items (PTO, holidays, tuition reimbursement, service awards appear twice). We should preserve all but can combine duplicates? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicates are okay but we could combine to avoid redundancy but not lose info. Safer to list each distinct benefit once, but ensure we don't lose any. Let's compile a set: - Competitive pay - Robust health insurance options - Retirement plans - PTO (paid time off) – 15 days - Holidays – 11 paid - Tuition reimbursement - Service awards (Length of Service awards) - Health, dental, and vision plans - 401(k) with company matching - Short-term disability - Long-term disability - Life insurance - Accidental insurance - Flexible scheduling (Work-Life Balance) - Structured onboarding - Access to online courses - Learning from experienced colleagues and industry experts - Length of Service awards (already covered) Maybe we can keep "Length of Service awards" as separate. We need to avoid filler like "commensurate with experience". Not present. Thus Benefits section bullet list. Now ensure we didn't include any boilerplate like "Our Commitment to Diversity & Inclusion". That's EEO/diversity boilerplate; we should remove it per instructions: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should omit the diversity section. Also remove "Why Join ASSA ABLOY Entrance Systems?" maybe we can keep some content but it's mostly fluff; but we already captured benefits etc. The "Meaningful Impact" and "Career Growth & Development" could be considered substantive? They are generic but maybe we should keep if they are specific? They are somewhat generic but still part of posting. However instructions: Prefer a few substantive sections over many thin ones. Could include a section "About the company" maybe but not required. The instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the company" or "Why join". So better to omit those sections to stay within allowed headings. However we must preserve ALL substantive information; if we omit the "Why Join" section, we lose some substantive info like "Meaningful Impact" and "Career Growth & Development". Are those considered substantive? They are somewhat generic but still part of posting. The instruction says "include a section ONLY when the posting has real, specific content for it". The "Why Join" section includes bullet points: Comprehensive Benefits, Meaningful Impact, Career Growth & Development. Those are somewhat generic but still content. However we already have Benefits covered; Meaningful Impact and Career Growth & Development are vague but still present. Could we incorporate them into About the role or elsewhere? Not really. But we could create a section "About the company" but not allowed heading. The allowed headings list does not include "About the company". So we should not create a heading not in the list. However the list is examples, not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples; we could use other headings if needed, but they gave examples. Safer to stick to those. Thus we can omit the "Why Join" section, but we would lose some info. However the instruction says "Preserve ALL substantive information". If we omit, we violate. But maybe those are considered boilerplate? "Meaningful Impact" and "Career Growth & Development" are generic fluff; maybe they are considered boilerplate? Not exactly EEO but could be considered filler. The instruction to remove duplicated lines and application instructions; not explicitly to remove fluff. However they say "never emit a heading followed by filler/placeholder text". Those bullet points are not filler/placeholder; they are specific statements. But they are vague. However we could incorporate them into a section like