Business Analyst with FACS (Flexible Automated Collection System)

To be a Business Analyst (BA) working on FACS (Flexible Automated Collection System) which is often used for loan servicing, collections, and debt recovery there are several key skills and knowledge areas that will help someone succeed in that role.

Here s a breakdown of the most important skills:

Core BA Skills

• Requirements Gathering: Ability to work with stakeholders to elicit, clarify, and document business needs.
• Process Mapping & Analysis: Experience documenting current vs. future state processes using tools like Visio or Lucidchart.
• Gap Analysis: Identifying gaps between system capabilities and business needs.
• Testing Support: Writing test cases, supporting UAT, and validating that solutions meet business requirements.

FACS System-Specific Skills

• Understanding of Loan Servicing or Collections Workflows: Knowledge of how accounts are managed, from origination to charge-off.
• FACS Screen Navigation: Knowing how to use the FACS screens and navigate its UI (green screen or newer web-based interface).
• FACS Tables & Codes: Familiarity with key system tables, field codes, and how statuses, codes, and flags impact automation.
• Batch Job/Process Knowledge: Understanding nightly jobs, processing cycles, and common automation routines in FACS.
• Report Writing or Querying: Some ability to write queries (e.g., SQL or FACS-specific reporting tools like Sequel or Informatica) to extract data or validate changes.

Technical Knowledge (Nice to Have)

• Understanding of Interfaces: How FACS integrates with other systems (e.g., payment processors, credit bureaus, CRM tools).
• File Layouts & SFTP/File Delivery: Familiarity with how files are exchanged in batch environments.
• Change Management Tools: Tools like Jira, Azure DevOps, or HP ALM for tracking requirements, defects, and testing.

Soft Skills

• Strong Communication: Explaining complex system behavior to non-technical stakeholders.
• Problem Solving: Diagnosing issues in production or testing based on logs, data anomalies, or workflows.
• Documentation: Writing clear business requirements, use cases, and SOPs.
• Stakeholder Engagement: Working with both business and IT teams, and sometimes third-party vendors (especially if FACS is hosted by Dovenmuehle or another servicer).