Most MCA underwriting queues have two structural problems that compound each other as volume grows, and neither is visible until the damage shows up in the portfolio.
The first is operational: two underwriters working the same deal simultaneously, overwriting each other's work, wasting analysis hours, and creating a compliance trail with no clear decision owner.
The second is a credit policy problem: with no documented rules enforcing your approval criteria, every underwriter applies their own interpretation of what a fundable deal looks like, and at scale, those interpretations diverge.
Onyx IQ's underwriting queue is built to solve both. Here's how each problem occurs and what the queue structure does to prevent it.
In underwriting, this is called collision. It occurs when two analysts open and work the same deal simultaneously—and it happens for one specific structural reason: the queue operates as a shared pull list with no file locking.
An underwriter opens a deal from the queue, and because the system doesn't lock the file or update its status, the same deal remains visible and accessible to every other analyst. A second underwriter—seeing it still marked as available—opens it and starts reviewing. Both are now working the same file at the same time.
When Underwriter A saves their analysis and Underwriter B saves theirs, the second save overwrites the first. One analyst's work is gone. If they reached different conclusions before that point, the deal now has two conflicting decisions with no audit trail showing which one stands.
In operations running email-based workflows, the same collision happens when a deal is distributed to a group alias. Two analysts respond, both start reviewing, and neither knows the other has already begun.
The operational cost is two senior underwriters billing hours to the same deal. The compliance cost is a decision with no traceable owner and no documented rationale—exactly what an investor or regulator asks for first.
The collision problem is mechanical. The consistency problem is structural and harder to see.
When credit policy isn't encoded in the system, approval logic lives in your senior underwriter's judgment—which industries they're comfortable with, where they draw the line on FICO, how they weight deposit history. Every other underwriter interprets that policy through their own lens.
Two analysts can review the same deal and reach different approval amounts, different pricing, and different risk conclusions because there's no single rule they're both following.
At 100 deals a day, the issue is invisible until the portfolio reflects it: uneven risk distribution, approvals that can't be explained to an investor, and a senior underwriter who becomes a single point of failure because the credit policy only lives in their head.
In Onyx IQ, deals enter the underwriting queue in an unclaimed state. No underwriting tab appears on the file. Every analyst on the team can see the deal in the queue, but no one can work it yet.
When an underwriter claims the deal, the underwriting tab opens, the claim is logged with a timestamp, and the file is now exclusively owned by that analyst. No second underwriter can open the same deal in an active state. The queue updates immediately to reflect the claimed status.
For the operations manager, the queue view shows exactly who owns each deal, what stage it's in, and how long it has been waiting.
Collision is structurally impossible—not dependent on team communication, manual assignment, or anyone checking first.
Onyx IQ's rule-based scorecard engine moves credit policy out of your senior underwriter's head and into the automated platform.
Your head of credit configures approval criteria directly—FICO thresholds, time in business minimums, industry restrictions, average monthly deposit requirements—and the system runs those rules automatically on every deal before an underwriter opens the file.
A deal with a FICO score under your chosen threshold is auto-declined. The ISO receives an automated notification immediately without an analyst involved. A deal that clears every threshold is flagged as auto-approved. Edge cases route to the queue with a refer flag for manual review.
When criteria need to change—a tighter deposit minimum, a new industry exclusion—your head of credit updates the scorecard directly without an IT ticket. Scorecard versioning preserves every previous rule set, so every historical decision is traceable to the policy in place when it was made.
Default stipulations auto-attach to every approval—driver's license, voided check, merchant agreement. Up to six approval options can be sent to the ISO in a single notification.
Every approval, decline, and revision is logged in a full audit trail.
One of our clients described the gains:
"Onyx IQ helped us streamline credit, ACH, and contract workflows into one system and made underwriting faster and more focused using the Scorecard."
Faster and more focused is the structural outcome.
When auto-declines and auto-approvals are handled by the scorecard, the underwriting queue contains only deals that need human judgment—the edge cases, the refer flags, the files where an experienced analyst's read actually matters. Your senior underwriter stops spending hours on decisions the system makes consistently and focuses on the ones only they can make.
New underwriters work to the same credit standard as your most experienced analyst from their first deal in the queue. Credit policy is auditable and consistent—not assumed and variable.
Onyx IQ is a full-cycle, automated lending platform built specifically for MCA and alternative lenders.
The underwriting queue, claiming system, and scorecard engine above are one layer of a connected system running origination, funding, servicing, collections, syndication, and portfolio management in a single platform.
Every credit decision feeds the contract workflow, the funding module, and the servicing engine directly—there’s no need for re-entry, reconciliation, and there’s no version drift between what underwriting approved and what funding executes.
Your head of credit owns the rules, your underwriters execute against them, and the system enforces them at every deal, at any volume.
Every month your credit policy lives in your senior underwriter's head instead of your system, you're one departure away from losing it.
Book a walkthrough with the Onyx IQ team and we'll show you how the claiming system, scorecard configuration, and role-based queue work together—mapped to your team's current structure and deal volume.