Unlike traditional loans, MCAs use factor rates and remittances that may change with merchant sales. Your servicing software needs to handle those terms and keep every collection, balance, and adjustment accurate.
Many funders still use a CRM to track deals, spreadsheets to calculate balances, and an ACH portal to process payments. That might work when you're funding a handful of deals, but as your portfolio grows, every new advance adds more payments, returns, balance updates, and syndicator calculations for your team to manage.
Without automation, you'll eventually need more servicing staff just to keep up. When information is spread across different tools, missed updates can lead to incorrect balances, delayed collections, and payout errors.
MCA servicing software helps your existing team handle a larger portfolio while spending less time updating records and more time recovering payments, managing risk, and keeping capital available for new deals.
In this guide, we'll explain how MCA servicing works, what your software should handle, and how to choose a platform that fits your funding operation.
Every MCA deal goes through three main stages, from the moment an ISO submits a file to the day the merchant pays off the advance.
1. Origination and underwriting. You receive the submission, review bank statements, assess the merchant's risk, approve the deal, and prepare the agreement.
2. Funding. The merchant signs the agreement, you send the funds, and the advance becomes active.
3. Servicing. Your team collects remittances, manages the merchant's account, and works toward renewal or payoff.
Servicing is where the money you've advanced needs to come back. A deal may look profitable when you fund it, but your actual return depends on how much you collect and what it costs to collect it.
Missed payments, slow collections follow-up, and servicing errors can eat into your margins. If your team needs more people every time your portfolio grows, your operating costs rise along with deal volume.
That's why servicing has such a direct impact on your funding business: it affects how much you recover, how much you spend managing each advance, and how much capital you have available for the next deal.
Your servicing team handles nine connected tasks throughout the life of an advance:
These tasks all depend on accurate payment information. When a payment clears, returns, or gets adjusted, the records affected by that payment need to stay in sync.
To understand why, it helps to look at the difference between ACH processing, collections, and servicing.
Your ACH processor, collections team, and servicing system each handle a different part of managing an active advance.
| Function | What it does |
|---|---|
| ACH processing | Moves payments between bank accounts and reports whether they cleared or returned. |
| Collections | Follows up with merchants on missed payments, delinquent accounts, and recoveries. |
| MCA servicing | Keeps payment histories, outstanding balances, collections activity, and syndicator payouts accurate throughout the advance. |
For example, your ACH processor might report that a $1,000 debit returned. Your collections rep needs to contact the merchant, while the servicing system needs to correct the balance and account for any affected syndicator distribution.
If those systems don't share information, someone has to update each one manually. When updates are missed, your team can end up working from the wrong balance, delaying collections, or paying a syndicator on money you haven't collected.
For funders, the cost goes beyond extra admin work. Payment problems can take longer to resolve, your servicing staff spend more time fixing records, and incorrect balances can lead to costly payout mistakes.
Once an advance is funded, it enters a servicing process that continues until renewal or payoff. Here's how the process works.
Steps 3 through 8 repeat as payments and other servicing events occur.
This is where servicing becomes expensive when done manually. Across hundreds of active advances, your team may be checking ACH reports, updating balances, reviewing returns, and calculating payouts every day.
Automating those tasks lets your servicing staff focus on the accounts that actually need attention, so you can take on more deals without increasing your servicing workload at the same rate.
A failed ACH pull means expected cash hasn't arrived. The longer it takes your team to identify and work that payment issue, the longer those funds remain uncollected.
Not every return can be handled the same way. An insufficient-funds return may allow a retry, while an account-closed or unauthorized-payment return requires a different response.
Here are five common ACH return codes:
| Return code | What it means | What your team should do |
|---|---|---|
| R01 | Insufficient funds | Investigate and retry if permitted. |
| R02 | Account closed | Stop debiting the account and request new authorized payment instructions. |
| R03 | Account not found | Verify the merchant's bank details before another attempt. |
| R08 | Payment stopped | Investigate the stop-payment before taking further action. |
| R29 | Business account holder says the debit wasn't authorized | Suspend further attempts, investigate the authorization, and escalate. |
The return code matters because retrying payments incorrectly can create additional fees, disputes, and compliance problems. Unauthorized-payment returns, for example, generally can't simply be retried under the original authorization.
Your servicing software should recognize the return code, correct the payment record, and flag the account for the right follow-up.
The gain is faster action on missed payments. Your collections team can focus on contacting merchants and resolving payment issues instead of spending time identifying returns, checking balances, and deciding which accounts need attention.
Let's follow a $100,000 MCA to see how servicing works in practice and where payment issues can affect your returns.
| Deal terms | Amount |
|---|---|
| Advance amount | $100,000 |
| Factor rate | 1.40 |
| Total purchased amount (RTR) | $140,000 |
| Estimated daily remittance | $1,000 |
| Estimated collection period | 140 business days |
If every $1,000 payment clears as scheduled, you'd collect the full $140,000 in approximately 140 business days. But merchants don't always pay exactly as expected.
Day 0: The deal funds. You send $100,000 to the merchant, activate the advance, and schedule $1,000 daily ACH remittances.
Day 1: Collections begin. The first ACH debit is initiated. Once the payment clears, it counts toward the collected RTR.
Day 10: The merchant is paying as expected. Ten payments of $1,000 have cleared. You've collected $10,000, leaving $130,000 in outstanding RTR.
Day 20: An ACH payment returns. The processor reports insufficient funds. The returned payment needs to be recorded, any provisional credit reversed, and the account flagged for follow-up. If your team misses the return, the outstanding balance may be understated, and the merchant could continue falling behind before anyone contacts them.
Day 35: The merchant requests a true-up. The merchant's sales have declined, and the agreement calls for reconciliation. After reviewing the request, you adjust the daily remittance from $1,000 to $600. The remaining RTR stays the same, but collections will take longer, so your capital stays tied up in the advance for longer than originally expected.
Renewal review: The merchant becomes eligible for additional funding. Your underwriting team reviews the merchant's payment history and outstanding RTR before deciding whether to offer another advance. If those numbers are wrong, you risk making a new funding decision using inaccurate information about the existing deal.
Payoff: The purchased amount is fully collected. Collections stop, remaining syndicator distributions are settled, and the advance is closed.
Throughout this process, accurate servicing helps you understand what's been collected, what still needs to come back, and when capital may become available for new deals.
When comparing servicing platforms, focus on the work your team currently handles manually, the mistakes that cost you money, and which tasks the software can automate.
Every confirmed payment, return, and adjustment changes how much is left to collect from a merchant. If those changes aren't recorded correctly, your team may use the wrong balance when calculating a payoff, reviewing a renewal, or paying a syndicator.
For example, here's how a $140,000 RTR changes as transactions are recorded:
| Transaction | Remaining RTR |
|---|---|
| Advance funded | $140,000 |
| First $1,000 ACH clears | $139,000 |
| Second $1,000 ACH clears | $138,000 |
| Previous $1,000 payment returns | $139,000 |
| $500 manual remittance clears | $138,500 |
A reliable servicing ledger records each transaction and preserves its history. When a payment returns, the system records the reversal while keeping the original transaction visible. That means your team can see exactly why a balance changed without searching through ACH reports or reconstructing payment activity in Excel.
For funders, the gain is fewer hours investigating discrepancies, more accurate payoff and renewal figures, and less risk of collecting or distributing the wrong amount.
Beyond the ledger, look for the features that will reduce manual work and help protect your collections.
| Feature | What it helps your team accomplish | Priority |
|---|---|---|
| ACH integration | See payment status and returns without checking separate processor reports. | Critical |
| Payment reconciliation | Catch missing or mismatched payments before balances become inaccurate. | Critical |
| Receivables reconciliation | Process merchant true-ups and document adjustments without rebuilding payment schedules manually. | Critical |
| Collections management | Identify failed payments sooner and keep follow-up from getting delayed. | Critical |
| Portfolio reporting | Find underperforming deals and spot collection problems across the book. | Critical |
| Audit trails and permissions | Trace financial changes and reduce the risk of unauthorized adjustments. | Critical |
| Syndication management | Calculate partner allocations and reduce payout errors. | Critical if you syndicate |
| Renewal management | Review repeat funding opportunities using accurate payment histories and balances. | High |
| Accounting integrations | Reduce manual reconciliation between servicing and accounting. | High |
| Merchant and ISO portals | Reduce routine requests for payment histories, balances, and documents. | Useful |
The goal is to find software that handles the recurring tasks consuming your team's time and helps prevent the errors that can cost you money.
Syndication becomes harder to manage as you add more deals and capital partners. Let's use the same $100,000 advance with a $140,000 RTR. You fund 70%, and a syndicator funds 30%.
That calculation is easy for one advance. But across 200 active advances, 15 capital partners, and different fee arrangements, your team has to keep track of thousands of allocations. Every returned payment creates another adjustment.
If you distribute a syndicator's $300 share before the merchant's $1,000 ACH payment is confirmed, a later return can leave you trying to recover money that's already been paid out.
Your servicing software should calculate syndicator allocations using confirmed collections, while tracking participation, fees, pending distributions, and any necessary adjustments.
This reduces the time your team spends calculating payouts and investigating discrepancies. It also helps avoid overpayments and gives your capital partners more reliable information about how their money is performing. When syndicators trust your reporting and distributions, it's easier to maintain those relationships as you bring more outside capital into your deals.
Funding more deals doesn't automatically mean you're making more money. You might be collecting more in total while ACH returns, defaults, or servicing costs are eating into your margins. If you only look at total funding volume and collections, those problems can be easy to miss.
Your servicing software should help you understand how your portfolio is actually performing.
| KPI | What it tells you |
|---|---|
| Collection rate | How much of your expected remittances you're collecting. |
| ACH return rate | How often payments fail or return. |
| Outstanding RTR | How much of the purchased receivables remains to be collected. |
| Capital exposure | How much funded capital remains at risk. |
| Delinquency and default rates | Which deals are falling behind or entering default. |
| Vintage performance | How advances funded in different periods perform over time. |
| Realized returns | How much you're earning after relevant costs and losses. |
| Renewal rate | How many merchants receive additional funding. |
| ISO performance | Which brokers are submitting deals that perform well after funding. |
For example, if one ISO consistently brings merchants with higher default rates, that information can help you review the relationship or tighten underwriting for similar submissions. If collections are slowing across a particular group of advances, you can investigate before more capital becomes tied up in underperforming deals.
The gain is better control over where your money goes next. You can identify which deals are performing, where losses are increasing, and which types of merchants and brokers are delivering stronger returns.
One important distinction: RTR is different from profit. A $100,000 advance at a 1.40 factor has a $140,000 purchased amount and a $40,000 gross spread. But broker commissions, cost of capital, ACH fees, servicing expenses, and defaults all affect how much of that spread you actually keep. Your reporting needs to account for those costs so you can make funding decisions based on actual performance.
When a merchant disputes a payment, requests a reconciliation, or challenges an agreement, your team may need to show exactly what happened on the deal. If those records are scattered across emails, spreadsheets, and processor portals, gathering that information can take hours. Missing records or inconsistent servicing practices can also create legal and compliance exposure.
Your servicing software should preserve signed agreements, payment authorizations, ACH transaction histories, reconciliation requests, remittance adjustments, and records of who approved changes. Those records matter in two important areas.
Some MCA agreements allow merchants to request remittance adjustments when their sales change. How those provisions are written and followed can matter when determining whether an MCA is treated as a purchase of receivables or recharacterized as a loan.
Your servicing records should show when a merchant requested reconciliation, how the request was reviewed, and what adjustment was made. This helps your team demonstrate that the agreement was serviced according to its terms, rather than having to reconstruct decisions months later.
State commercial financing disclosure requirements, including those in California and New York, can create documentation and recordkeeping obligations depending on the transaction and applicable rules. Keeping agreements, disclosures, authorizations, and servicing records organized reduces the work involved when you need to produce documentation for a review, dispute, or audit.
For funders, the gain is less time gathering records and a clearer history of how each advance was managed.
Software supports that recordkeeping, but your contracts and servicing practices still need to comply with applicable requirements. Have qualified commercial-finance counsel review both.
There are three main ways to manage MCA servicing. Each comes with different costs, responsibilities, and trade-offs.
You purchase a platform and manage servicing with your own team. This gives you control over merchant relationships, collections, and portfolio data. It also lets you automate work that would otherwise require additional servicing staff as your book grows.
You'll generally find two types of platforms.
Point solutions handle specific tasks, such as ACH processing, reconciliation, or collections. They can work well when you only need to fill one gap in an existing system. But when those tools aren't properly connected, your team still has to move payment information and reconcile balances between them. As deal volume increases, the labor cost of managing those handoffs can offset the savings from using cheaper individual tools.
End-to-end lending platforms connect origination, underwriting, funding, servicing, collections, and syndication. On a platform like Onyx IQ, teams work from the same deal record throughout the funding lifecycle. That means fewer manual transfers, less duplicate work, and a smaller servicing workload per advance.
You hire a third-party company to handle some or all of your servicing operation. Depending on the provider, that may include ACH collections, merchant follow-up, reconciliation, and syndicator payouts.
This can reduce the number of internal staff you need, but servicing fees become an ongoing expense. You also give another company responsibility for important merchant interactions. If payment issues aren't resolved promptly or servicing performance falls short, the financial consequences can still affect your funding business.
Outsourcing can reduce your internal workload, but you need to weigh that saving against servicing fees, oversight costs, and the control you're giving up.
Building your own platform gives you control over the features, integrations, and workflows. But it also means paying developers to build and maintain the system, support ACH processors, manage security, and keep up with changing requirements. Those costs continue after launch.
Every new feature, processor update, or servicing issue becomes another development task. That can pull money and attention away from underwriting, funding, and growing your portfolio.
For most funders, the real comparison is what each approach costs to run as your portfolio grows. Factor in software fees, servicing staff, development, maintenance, reconciliation work, and the cost of correcting errors. The goal is to find an approach that lets you manage more advances without letting servicing costs consume more of your margin.
Every vendor can show you a feature list. What you need to see is how the platform handles the situations that create work and cost money in your servicing operation.
Ask vendors to run a real MCA deal through the software. Here's a test you can use:
Pay attention to what happens when the payment returns or the remittance changes. Does the system update the relevant records? Can you see why the balance changed? Does someone need to export a report, open Excel, or manually correct the numbers?
Every manual step adds work as your portfolio grows. A task that takes a few minutes on one advance can become hours of recurring work when you're servicing hundreds of deals.
When comparing prices, look beyond the monthly subscription. Consider how many people you need to service your portfolio today and how many you'd need if deal volume doubled. A platform with a higher subscription price may cost less overall if it eliminates enough manual work and helps prevent expensive servicing errors.
Onyx IQ brings origination, underwriting, funding, servicing, collections, and syndication into one platform. Here's how its servicing capabilities help funders reduce operating costs, manage collections, and grow their portfolios.
When origination and servicing run in separate systems, your team has to transfer deal terms, payment information, and balances between them. That adds work every time a new advance funds. When information doesn't match, someone has to investigate the discrepancy before the account can be serviced correctly.
With Onyx IQ, origination, underwriting, funding, servicing, collections, and syndication use the same deal record. The information captured during origination carries into servicing.
Your team can take on more active advances without spending more time moving information or reconciling balances between systems.
Manually calculating syndicator shares takes time, especially when deals have different participation percentages, management fees, and returned payments. A mistake can mean paying a partner too much, correcting distributions later, or spending hours explaining discrepancies.
Onyx IQ tracks syndicator participation and fees, then calculates payouts from confirmed collections. Partners can review their positions through an investor portal and use virtual wallets to hold or redeploy capital.
Your team spends less time preparing distributions and correcting payout errors, while syndicators get clearer information about their investments.
When ACH activity lives in a separate processor portal, your team has to check that system to find out what cleared, what returned, and what needs follow-up. That takes time, and if someone doesn't catch a returned payment promptly, the account can remain unresolved longer.
Onyx IQ integrates with major ACH processors and brings payment information into the deal record.
Your team can identify payment problems sooner, spend less time checking processor reports, and focus on recovering missed collections.
Every returned payment creates work for your collections team. Someone has to identify the return, review the account, contact the merchant, document the issue, and decide what happens next. When reps spend too much time gathering information, they have less time to work the merchants who owe you money.
Onyx IQ can move failed payments into a Payment Issues queue and trigger automated merchant follow-up by text and email. If an account needs legal collections, the platform can also package its payment history and supporting documents for the handoff.
Your collections reps can spend more time resolving payment problems and recovering funds instead of identifying issues and gathering paperwork.
MCA funders work with factor rates, purchased receivables, daily remittances, true-ups, renewals, and syndicator splits. When software is designed around amortizing loans, your team may need extra calculations or workarounds to handle those terms. Every workaround adds another step someone has to manage, check, or correct.
Onyx IQ is designed around MCA servicing requirements, with those terms and calculations built into the platform.
Your team can service advances with fewer manual adjustments, reducing the workload and errors that become more expensive as deal volume grows.
If portfolio data is spread across spreadsheets, ACH reports, and accounting tools, preparing financial reports can take hours before anyone can even start analyzing the numbers. That also makes it harder to spot rising defaults, weakening collections, or underperforming funding vintages early.
Onyx IQ provides reporting capabilities including vintage analysis, static pools, collection curves, and financial reporting outputs. The platform also has SOC 2 Type II certification, which can support security reviews by capital partners and other stakeholders.
Your team can spend less time preparing reports and more time understanding which deals are performing, where capital is at risk, and what needs attention before losses grow.
See how many more advances your team could manage with less manual servicing work. Bring your toughest servicing scenario, whether it's a returned ACH payment, a true-up, or a syndicated deal. We'll show you how Onyx IQ handles it using your numbers.
Book a demoACH processing moves payments between bank accounts and reports whether they clear or return. MCA servicing manages the full post-funding process, including payment histories, balances, collections, reconciliation, and syndication.
Payment reconciliation checks whether initiated ACH payments actually cleared and were recorded correctly. Receivables reconciliation, also called a true-up, adjusts the merchant's remittance based on actual sales when required by the MCA agreement.
You can use separate systems, but they'll need to exchange accurate deal terms, balances, and payment information. An integrated platform keeps origination and servicing on the same deal record, reducing manual transfers and the time your team spends checking information between systems.
Yes. Third-party servicing companies can manage ACH collections, payment reconciliation, merchant follow-up, and other tasks. Outsourcing can reduce your internal workload, but you'll need to account for servicing fees, oversight, and any legal or financial responsibilities your company retains.
No. RTR, or Right to Receive, is the total amount of purchased receivables to be collected under an MCA agreement. For example, a $100,000 advance with a $140,000 RTR has a $40,000 gross spread. Your actual profit depends on how much you collect and what you spend on commissions, capital, servicing, fees, and losses.
Onyx IQ runs the full lifecycle on one platform: origination, underwriting, funding, servicing, collections, and syndication, all on the same deal record. Servicing uses the terms captured at origination, so your team doesn't re-enter data or reconcile balances between systems.
Onyx IQ has native integrations with five ACH processors: ACHWorks, Actum, ACH.com, UZO, and Wells Fargo, plus an open API for others. You manage payment plans, pauses, and bank account changes inside the deal record without logging into a separate processor portal.
Yes. You add syndicators with their participation percentage and management fees, and Onyx IQ calculates and distributes payouts from confirmed collections. Syndicators review their positions in their own portal, hold and redeploy capital through virtual wallets, and the platform handles clawbacks when a deal goes bad.
Yes. When a payment fails, Onyx IQ moves the deal into a Payment Issues queue and sends the merchant an automated text and email. If an account goes to legal collections, the platform packages the payment history and supporting documents for the law-firm handoff in one step.
Yes. Onyx IQ holds SOC 2 Type II certification, which is the security standard most capital partners and bank sponsors ask for before extending a credit facility.
Yes. Onyx IQ produces static pool reports by vintage, collection curves by deal age, and GAAP-style outputs from the same data that ran the payments, without a separate reporting build. This is the reporting a bank sponsor or credit fund typically asks to see.
Onyx IQ's own setup takes a few days. Going fully live usually takes about 3-4 weeks, since most of that time is spent connecting ACH processors and other integrations.