MCA Bank Account Changes: A Controlled Pre-Funding Workflow
A practical workflow for handling merchant bank account changes without letting outdated details follow the deal into closing or funding.
Open a change record before editing the deal
Capture who requested the change, when it arrived, which account is being replaced, the proposed new account, and where the deal currently sits. Keep the request separate from the approved deal data until the team has reviewed it. That gives processors and closers one visible place to work instead of relying on an email thread or a note that can be missed.
Confirm the request through an established channel
Use the verification process your organization and funding partner already require. A processor should not treat a reply from an unfamiliar address or a forwarded attachment as sufficient on its own. Record the channel used, the person contacted, and the outcome so the next reviewer can see how the request was confirmed without guessing.
Review the supporting account documents as a set
Check that the account holder, business identity, routing information, and account details agree across the documents provided for the new account. Also note whether the change affects statements already used during review. The goal is not to silently swap one field; it is to understand which parts of the current package still describe the same business and which need another look.
Map every place the old account is still in use
Review the application, CRM record, analysis, partner submissions, approval conditions, closing documents, and any funding or payment instructions already prepared. Mark each affected item as pending, updated, or not applicable. This impact check prevents an internal record from showing the new account while a partner or signed document still carries the old one.
Version the change instead of overwriting history
Preserve the prior details, supporting files, review notes, and effective time, then create the updated version. Label superseded documents clearly so nobody pulls them into a closing package by mistake. A clean version trail also makes it easier to explain why the package changed and which information was active at each handoff.
Route the updated package to the right reviewers
Send the change only to the internal owners and external partners whose work is affected, following their current review requirements. Give the request an owner and keep the deal from advancing until every required response is recorded. If a partner asks for a refreshed document or another review, track that as an open dependency rather than burying it in notes.
Reconcile the final account before funding
Before the deal is marked ready, compare the approved account details with the latest closing documents, partner confirmation, and destination information in the funding workflow. Close the change record only when those sources agree and any superseded instructions are clearly retired. Review unresolved or unusually late changes in an exception queue so urgency does not bypass the process.