Big Tuna Blog
MCA Funder Operations7 min read

MCA Payment Account Changes: A Controlled Servicing Workflow

By Johnny Accardo · Founder & CEO, Big Tuna Solutions

A practical MCA payment account change workflow for verifying requests, coordinating processor updates, protecting schedule history, and confirming the first payment.

Open a servicing request without changing the active setup

Create a request linked to the active account and capture who submitted it, when it arrived, the stated reason, the requested effective date, the source channel, and the documents or account details supplied. Keep the current payment account and schedule active while the request is being reviewed. A pending request should not silently replace the setup that still governs transactions. Give the request its own owner and status so the merchant conversation, internal review, and external update can move without operators editing the live record too early.

Confirm the requester and the account being serviced

Match the request to the correct merchant, agreement, location, and active servicing account before reviewing the new information. Follow the organization's established process for confirming that the requester is permitted to make the request, using contact information and channels already maintained by the team when applicable. Record the confirmation source, time, operator, and any discrepancy. A familiar name or a reply inside an old email thread is context, not a substitute for the review steps the organization requires.

Review the replacement account as a new version

Store the proposed account details and supporting materials as a new payment-account version rather than overwriting the prior version. Record the account holder information, financial institution details used by the process, document dates, source, and review status. Compare the new information with the merchant and agreement records, then route mismatches or incomplete items to a named reviewer. Keep display and access controls appropriate to sensitive account data, and avoid copying full details into general notes or tasks.

Map pending activity before choosing an effective date

Review payments already initiated, returns still being resolved, holidays or processing cutoffs relevant to the team, and any open remittance change or account adjustment. Identify which expected payment is intended to be the last on the prior account and which is intended to be the first on the replacement account. If timing is uncertain, keep the change in an exception state rather than creating two competing instructions for the same payment period. The effective-date record should explain the transition without rewriting the historical schedule.

Track the processor or bank update as a separate handoff

When the internal decision is complete, create the required external update task with its owner, submission time, reference, intended effective date, and the exact servicing account it affects. Keep requested, submitted, acknowledged, completed, and rejected states distinct. An internal approval does not prove that a processor or other party has applied the change. Link responses and confirmation evidence to the request so another operator can see what was sent, what came back, and whether follow-up is still open.

Activate the new version without erasing the old one

Activate the replacement account only after the team's required decision and external setup steps are supported. Close the prior version with its own end date and retain the period during which it was effective. Keep the expected-payment schedule separate unless an approved remittance decision also changes the amount, percentage, or frequency; moving the payment account alone should not silently become a schedule change. Notify the owners of reconciliation, returns, merchant communication, and other affected queues of the effective transition.

Confirm the first payment and close the transition

Review the first expected payment after the effective date against the processor event, bank evidence available to the team, active account version, and servicing schedule. Confirm that no duplicate or unexpected transaction remained tied to the prior setup, and route any difference through the normal payment or return exception workflow rather than repeatedly editing the change request. Record the reviewer, review time, result, and continuing work. Ongoing queues should surface approved changes that were never completed, completed updates without a first-payment check, and later activity against a retired account version.