Big Tuna Blog
MCA Funder Operations7 min read

MCA Servicing Boarding: A Clean Handoff From Funding to Active Accounts

By Johnny Accardo · Founder & CEO, Big Tuna Solutions

A practical MCA servicing boarding workflow for turning final funding records into accurate schedules, account ownership, payment instructions, and reviewable exceptions.

Start boarding from a confirmed funding event

Open the boarding record from the final funding confirmation used by the organization, not from an approval or a message that funds were expected. Link the deal identifier, funding date, movement reference, confirmed amount, final recipient account, and supporting evidence. If the transaction funded in more than one movement, keep those events separate and show which ones make up the boarded total. The servicing record should begin with what actually closed, while any unmatched or incomplete movement remains visible as an exception.

Freeze the final deal baseline without flattening its history

Identify the executed agreement and closing-document version that governs the account, then capture the final purchase amount, purchased amount, remittance terms, effective dates, and other fields the servicing process requires. Preserve links to the offer, approval, stipulation, and closing history rather than copying disconnected values into a new screen. When a final term differs from an earlier approval, show both the superseded value and the source of the change so the servicing team can understand the baseline without reopening the entire deal file.

Build the first expected-payment schedule from the effective terms

Create the expected schedule from the final effective agreement data and the organization's established servicing method. Record the calculation inputs, start date, frequency, expected amount or percentage, applicable calendar treatment, and schedule version. Review the first expected date against the actual funding date and any payment activity already in flight. A schedule should be reproducible from its inputs; entering only a next-payment amount makes later reconciliation difficult when timing or terms change.

Connect payment instructions to the boarded account

Attach the payment or processor setup record that applies to the account, including the source, effective date, external reference, current status, and evidence required by the team's process. Keep submitted, accepted, active, rejected, and corrected states distinct. Do not mark payment setup complete merely because instructions were sent. If bank-account information changed during closing, confirm that the boarded setup matches the final reviewed version and route any conflict back to the appropriate exception owner.

Assign servicing ownership and carry forward open work

Name the account owner, servicing queue, communication contacts, escalation path, and next scheduled review before the deal leaves closing operations. Carry forward every relevant open item with its source, owner, due date, and effect on servicing. Examples may include missing movement evidence, an unresolved schedule question, a pending processor confirmation, or incomplete participation records. A funded status should not erase work that still matters; it should make the receiving team responsible for a clearly defined list.

Reconcile syndication and internal records where applicable

For a syndicated transaction, compare the final participation version with the funded baseline and the account values being boarded. Link participant commitments, confirmed movements, allocation amounts, and any servicing or reporting fields the organization maintains. Keep unresolved participation differences separate from the merchant payment schedule so one does not silently change the other. Even when different teams own these records, the boarded account should identify the current participation version and the exceptions still awaiting reconciliation.

Release the account through a boarding review

Use a final review to compare the funding evidence, executed documents, boarded terms, first expected schedule, payment setup, ownership, and open exceptions. Record who completed the review, when it occurred, which sources were checked, and the resulting status. Keep separate outcomes for ready for active servicing, active with named exceptions, or returned for correction according to the team's process. After release, review queues should surface funded deals that were never boarded, accounts without active payment setup, first expected dates that have passed without a source event, and boarding records closed with unresolved ownership.