C2C Role: Techno BA (Payments Domain) On-site

Role: Techno BA (Payments Domain)

On-site Location:  Alpharetta Ga

Need candidate from Payment domain.

 

TM Implementations-

(4-6)- Technical Specialists

Focus: Support timely commercial client readiness for CD1 by receiving, validating, and certifying converted payment files as clients move from CMA IP formats to Fifth Third bank file specifications, providing rapid and precise feedback to minimize rework and delays.

Why Needed: The volume and pace of client file conversions require dedicated execution capacity to scale testing and validation efforts. These specialists reduce risk to conversion timelines, allow the Lead Technical Specialist and client-facing teams to remain focused on coordination and solution design, and help ensure continuity of Treasury Payments services post‑conversion.

 

Responsibilities

• Receive and validate client‑generated payment files against FITB bank file specifications during the CMA IP conversion.
• Identify format, mapping, and data defects and provide clear, actionable feedback to clients for correction and resubmission.
• Participate in client and internal working sessions to understand how files are being created (ERP/TMS, vendor approach, logic).
• Execute iterative file testing cycles and track outcomes through certification readiness for CD1.
• Partner closely with the Lead Technical Specialist and broader project team to support timelines, issue escalation, and clean handoffs.

Skills & Experience

 

• Strong attention to detail with proven experience reviewing, validating, or troubleshooting file‑based payment data.
• Ability to manage multiple files and testing cycles while meeting aggressive, conversion‑driven deadlines.
• Clear verbal and written communication skills, especially when explaining technical defects and required adjustments.
• Familiarity with payment file types (EDI 820, ACH, wire, check print) and/or ERP/TMS‑generated files preferred but trainable.
• Exposure to payment processing platforms (e.g., PEP+ mainframe, MTS Wire, Vector Connexion) is a plus, not required.

Duration:

 

Immediate start preferred. Resources will undergo a ~30‑day onboarding and training period, followed by active participation in client file validation and testing through September 8. Select resources may be extended beyond CD1 to support post‑conversion hyper care and early production stabilization.

 

High‑Level 30‑Day Ramp Plan

 

Days 1–7: Orientation & Foundations

 

Objective: Establish baseline knowledge and context for effective participation.

 

• Complete onboarding, access provisioning, and required compliance training
• Overview of CMA → FITB conversion program, CD1 timeline, and success criteria
• Introduction to FITB bank file specifications, testing standards, and validation rules
• Review sample files, common defect types, and historical conversion issues
• Shadow Lead Technical Specialist and/or experienced team members on file reviews and client discussions

Outcome: Resource understands the program, tools, file standards, and team operating model.

 

Days 8–15: Guided File Validation & Testing

 

Objective: Begin hands‑on execution with oversight.

 

• Perform file intake and validation on test files with peer or lead review
• Practice documenting defects and drafting client‑ready feedback
• Participate in client calls to understand file creation approaches and testing outcomes
• Learn tracking tools, status reporting expectations, and escalation paths
• Build familiarity with recurring patterns across clients and file types

Outcome: Resource can independently review files with light oversight and produce quality feedback.

 

Days 16–30: Independent Execution & Throughput Scaling

 

Objective: Operate independently and contribute at expected capacity.

 

• Own file validation and re‑test cycles for assigned clients or workstreams
• Provide timely, accurate feedback to support rapid client corrections
• Actively manage testing queues, deadlines, and issue resolution
• Escalate complex or repeat issues with clear analysis and recommendations
• Contribute to documentation supporting certification and BAU handoff readiness

Outcome: Resource is fully productive, managing files independently and supporting conversion throughput ahead of CD1.

 

End‑of‑Ramp Readiness Check

By Day 30, resources should be able to:

 

• Independently validate client payment files against FITB specifications
• Confidently explain validation outcomes and required fixes
• Keep pace with conversion volume and testing timelines
• Support CD1 readiness with minimal oversight