What is MBL software? Member business lending, the cap, and what the software does about it

What the software actually does

Strip away the branding and member business lending software does five jobs. It takes the application and the borrower's documents. It converts those documents into a standardized spread. It builds a view of whether the borrower and the guarantors can service the debt. It records the decision, the exceptions and the covenants. And it watches the credit after booking, so a covenant breach or a missing statement surfaces before it becomes a finding.

Very few products do all five. Most credit unions end up with a division of labour: a consumer origination system that can take a business application, a commercial platform or analyst toolkit that does the credit work, and a spreadsheet somewhere handling the part nobody sold them. Working out which of the five jobs is actually slow at your credit union is the whole evaluation, and it is worth doing before the first demo rather than during the third.

• Intake: application, borrower and guarantor documents, entity structure
• Spreading: business and personal returns and interim statements into a standard template
• Analysis: debt service coverage across entities and guarantors, ratios, benchmarks
• Decision record: risk rating, exceptions, approvals, covenants, the credit memo
• Monitoring: periodic statements, covenant tests, concentration and cap reporting

The cap, in plain terms

Member business lending is capped. The limit is expressed two ways, as 1.75 times the credit union's net worth and as 12.25% of total assets, and it originates in the Credit Union Membership Access Act of 1998, the statute usually referred to by its bill number, H.R. 1151. Which formulation binds depends on the credit union's own numbers, and the operative rule text and your examiner are the authorities on how it applies to you. Nothing here is regulatory advice.

What matters for a software conversation is the consequence. A bank growing a commercial book worries about concentration policy. A credit union growing a member business book worries about concentration policy and about running out of headroom, which is a different problem with different tools. Two of them are ordinary: accurate categorisation of what counts toward the cap, and reporting that tells you how much room is left. One of them is structural: loan participations, where part of a loan is sold to another institution so the originating credit union keeps the relationship without consuming as much of its own capacity.

That is why participations are the single most useful thing to ask a vendor about, and why the answer across this entire category is currently the same. No vendor we reviewed publishes a cap calculation, and loan participation capability appears in none of their material. For a segment defined by a cap, that is a real gap, and it means the cap lives in your own reporting rather than in the lending system.

What Part 723 covers, and why it shows up in a software evaluation

NCUA Part 723 is the rule for member business loans. In practical terms it is where expectations about documentation, underwriting standards and portfolio concentration limits live, and it is the reason an examiner asks a credit union to show its work rather than describe its intentions. Read the rule itself for the mechanics; what follows is only how it lands on a technology decision.

It lands as an evidence requirement. An examiner reviewing a member business loan file wants to see how the numbers were derived, who reviewed them, which exceptions were identified and approved, and whether covenants have been tested since booking. Software either produces that as a by-product of the work or leaves your team assembling it after the fact, and the difference is a recurring internal cost that never appears in a licence comparison.

This is the criterion where the category divides most sharply, and not in the direction the market's recommendations suggest. Of the vendors in this segment, one states plainly that member business lending programs are regulated by the NCUA, which sets requirements for documentation, underwriting and portfolio concentration limits, and maps examination expectations to product features. One other explicitly scopes itself to smaller member business loans and treats auditor and examiner evidence as a named capability. The rest, including the largest and most frequently recommended platforms, address the regulator generically or not at all.

• Ask what the product produces without being asked, not what it can be configured to produce
• Look for a figure that traces back to the document and page it came from
• Look for an exception and covenant record that is a by-product of the credit work
• Ask who calculates the cap today, and confirm it is not assumed to be the software
• Treat an unverifiable claim about audit outcomes as worth nothing

How this differs from commercial lending software generally

Most of the products a credit union will be shown were built for banks and adapted. That is not disqualifying, and several of them are the strongest options available. But the adaptation shows in specific places, and knowing where saves time.

Pricing is the clearest. A licence priced on total assets treats a credit union with a large balance sheet and a modest member business book like a commercial bank of the same size, which is the wrong shape entirely. At least one vendor in this market prices on the business lending portfolio and the number of users instead, and for a typical credit union program the two bases produce very different numbers for identical work.

Reference evidence is the other. Ask for a US credit union running the specific product for member business lending, ideally with the lending executive on the call. Bank references answer a different question, and in at least one case a vendor's named credit union references include institutions outside the United States and therefore outside NCUA supervision, which cannot tell you anything about Part 723 readiness.