Same Day Funding (SDF) – Standard Operating Procedure (SOP)

Purpose

This SOP standardizes how Same Day Funding (SDF) is enabled, managed, and canceled for merchants under the CBCAL 7524 BIN. It ensures consistency, compliance, and proper coordination between ISO/Sales reps, Risk/Underwriting, Back Office Support, and other stakeholders.

Scope

• All internal teams responsible for onboarding, ticketing, risk review, pricing updates, and cancellation of SDF.
• ISO/Sales reps requesting SDF enablement or cancellation via ticket.
• Merchants must be under BIN CBCAL 7524 to be eligible for SDF.

Eligibility & Prerequisites

1. Processor & BIN: Merchant must be onboarded on TSYS with BIN CBCAL 7524.
2. Credit Score Requirement:Merchant must have a minimum credit score of 580 to qualify for SDF.
   • If credit score ≥ 580: Merchant may be enabled for SDF subject to Risk/Underwriting approval; the monthly SDF fee applies.
   • If credit score < 580: Merchant is not eligible for SDF; no enrollment allowed.
3. Authorization Agreement: The SDF addendum must be signed and attached to the merchant’s CRM Documents section.
4. Document Verification: Required documentation must be complete before Risk/Underwriting review.
5. Batch/Cutoff Times: Merchants must batch by Cycle 5 (8:00 AM EST) to be included in the 10:00 AM EST Same Day ACH window. Batches after this cutoff will fund the next business day.
6. Ticket Submission: For existing merchants, an SDF ticket must be submitted by the ISO/Sales rep using the ticket fields defined in the ISO/Sales Rep – Submitting Same Day Funding (SDF) Tickets & Cancellations procedure.

Roles & Responsibilities

Process Overview

1. New Merchant Flow (During Boarding)

1. Boarding Associate: Collects and verifies required merchant documents, ensures processor = TSYS and BIN = CBCAL 7524, confirms credit score ≥ 580, sets Funding Type = Same Day in CRM.
2. Underwriting: Reviews documentation and verifies eligibility; approves or denies SDF enrollment.
3. Risk/Underwriting: Performs final eligibility check; approves enrollment and notifies Back Office Support for pricing setup.
4. Back Office Support: Completes CRM configuration, ensures SDF is enabled, confirms merchant batches by Cycle 5 (8:00 AM EST) for 10:00 AM ACH window, prepares for funding.

Note: If CRM changes fail to feed to CBOS/Express, follow the manual backup procedure for SDF setup.

2. Existing Merchant Flow (ISO/Sales Rep Ticket Submission)

Follow the procedure documented here: ISO/Sales Rep – Submitting Same Day Funding (SDF) Tickets & Cancellations

• Verify merchant eligibility (processor, BIN, credit score ≥ 580).
• Send SDF addendum via EDOCUSIGN; confirm it appears in Documents.
• Complete ticket fields (RFC = Risk/Underwriting, Actual Problem = Funding Type Update, Funding Type = Same Day, Group = NY Risk).
• Submit ticket.
• Merchants must batch by Cycle 5 (8:00 AM EST) for the 10:00 AM EST Same Day ACH window.

3. Internal SDF Ticket Workflow (After ISO/Sales Rep Submission)

Internal teams follow this procedure: Internal Workflow – Same Day Funding (SDF) Tickets

• Review ticket and verify merchant eligibility, credit score, and signed addendum.
• Risk/Underwriting approves or denies request.
• Approved tickets are transferred to Back Office Support (Pricing Issues queue).
• Back Office updates pricing in CRM.
• Log all updates for audit purposes in SharePoint.

4. Cancellation Process

For cancellation requests submitted by ISO/Sales reps: Same Day Funding (SDF) Cancellation Process

• Open cancellation ticket and verify merchant account is active and SDF-enabled.
• Risk/Underwriting disables SDF if approved and documents action in ticket.
• Transfer ticket to Back Office Support to remove SDF fee.
• Verify CRM reflects disabled SDF and fee removal.
• Log action in SharePoint Activity Log.
• Escalate any discrepancies immediately.

Quality Control & Documentation

• CRM must reflect correct SDF status.
• Pricing must match executed agreements.
• Action must be logged in SharePoint Same Day Funding (SDF) Activity Log with: DBA Name, MID, Date approved by Risk, Date pricing updated, and team member performing the update.
• Escalate any discrepancies immediately.

Review & Audit

• Internal teams must periodically audit SDF records for compliance.
• Escalate tickets not processed within SLA to Risk management.
• Escalate pricing or batch issues to Back Office management.

Document Control

• Review annually or upon policy changes.