MCA Renewal Workflow: From Eligibility Review to a Fresh Package
A practical MCA renewal workflow for tracking eligibility, reviewing current performance, coordinating rep outreach, and collecting a fresh submission package.
Build the renewal record when the deal funds
Capture the funded amount, funder, product, term, payment frequency, estimated completion date, rep owner, and any renewal conditions while the details are current. Keep those fields on the same deal record as the original application and submission history. The goal is not to predict approval; it is to give the team a reliable date and context for deciding when a new conversation makes sense.
Separate eligibility review from sales outreach
A date-based reminder alone can create poorly timed calls. Before outreach, review the payment history available to your team, current position, recent business performance, open service issues, and the funder’s current renewal process. Use a short internal status such as not ready, review needed, ready for contact, or no longer pursuing so reps know whether to call and operations can see why a deal is waiting.
Give one person the next action
Renewals stall when a rep assumes processing requested documents while processing assumes the rep is still qualifying interest. Assign an owner, a due date, and one next step at every stage. Examples include confirm interest, request updated statements, review the current position, resolve missing documents, or prepare the package for a named partner.
Collect a fresh package instead of recycling the old one
The original file is useful context, but the renewal decision depends on current information. Confirm business and ownership details, obtain the statement periods and supporting documents required for the new review, and record what changed since funding. Keep prior documents available for comparison while clearly labeling the files that belong to the renewal so nobody submits stale information by mistake.
Track the renewal as its own opportunity
Link the renewal to the original deal, but give it its own package status, submission history, partner responses, offer details, and outcome. This preserves the merchant relationship without mixing two underwriting cycles. It also lets managers distinguish renewals waiting on timing, renewals waiting on the merchant, and complete files waiting on an internal or funder response.
Review exceptions every week
A practical renewal queue should surface records with no owner, overdue next actions, eligibility dates that passed without review, document requests with no response, and submitted packages with no recorded outcome. A short weekly exception review is more useful than asking every rep for a full pipeline recap because it focuses the team on the deals that have stopped moving.