MCA ISO Onboarding: A Practical Workflow for New Broker Relationships
A practical MCA ISO onboarding workflow for organizing partner details, submission rules, access, attribution, test deals, and ongoing reviews.
Create one partner record before the first submission
Start with the ISO’s legal business name, public-facing name, primary contacts, responsible internal owner, approved submission channel, and any identifiers your team uses to connect leads and deals to the relationship. Store the source documents and confirmed instructions with that record rather than spreading them across personal inboxes. If a detail is still pending, mark it as unresolved and assign an owner instead of filling the gap with an assumption.
Confirm roles and escalation paths
Document who handles new packages, missing items, status questions, approvals, stipulations, funding confirmation, and post-funding questions on each side. Include a backup path for time-sensitive issues and define when a matter should move beyond the day-to-day contact. The goal is not to create a long directory; it is to prevent every exception from being forwarded through the original salesperson until someone finds the right person.
Translate submission guidance into a working checklist
Record the products or deal types the relationship covers, the information expected at intake, required documents, naming or packaging instructions, and the channel used to submit. Keep confirmed requirements separate from preferences and internal notes. When guidance is conditional or case by case, preserve that language and route it for review rather than turning it into a hard rule that could reject a workable package.
Set access by job responsibility
Give each user only the portal, shared workspace, notification, or reporting access needed for their role, following the controls available in your systems. Record who approved the access, what was granted, and who owns future changes. Use named accounts where possible within your normal policies, and include a defined process for role changes or departures so old access does not remain simply because nobody owns the cleanup.
Protect attribution from the first lead
Decide how the ISO, individual rep, lead source, and responsible internal owner will be represented before live volume begins. Test that those fields carry from intake into the deal record and remain visible through submission and funding. If your operation uses separate rules for ownership, commissions, or protected accounts, link the applicable record or review step without assuming the software alone resolves a contractual question.
Run a controlled first package
Treat the first suitable deal as an end-to-end workflow check. Confirm the package reaches the correct queue, required files are readable, attribution is intact, notifications go to the intended people, and both teams can see the next action. Record any issue and correct the underlying instruction, mapping, or ownership field before volume increases. Do not use invented or altered applicant information just to force a test through a live process.
Move onboarding into an active-partner review
Onboarding should end with a visible status, an effective date, an internal owner, and a short list of any open exceptions. After launch, review inactive users, bounced notifications, packages sent through the wrong channel, missing attribution, outdated contacts, and unresolved guidance. A regular exception queue keeps the relationship current without making both teams repeat the full onboarding every time one detail changes.