Why it matters
Lender matching in Ferrylend never guesses. Before it checks a single rule, the CRM builds a deal profile: a snapshot of every fact a lender rule can ask about. A fact that is missing is unknown, not zero, and a hard rule on an unknown fact puts that lender in Needs data. So the quality of your matches is exactly the quality of the profile. Ten minutes spent here saves a day of submitting to lenders that were never going to fund the file.
The profile is saved with every match run, so you can always see what the deal looked like when a lender was ranked.
What the profile reads, and where you set it
| Fact | Comes from | Where you set it |
|---|---|---|
| Requested amount, deal type | The deal | The deal header (Requested, Deal type) |
| State, industry, NAICS, entity type | The merchant | Merchant profile: State, Industry, Entity type |
| Time in business | The merchant's start date | Date established (months are counted from it) |
| Owner FICO (highest), ownership % (highest) | Owners and guarantors | Merchant Owners tab: FICO, Ownership, Role |
| True revenue, deposits, average daily balance, deposit count, NSFs, negative days, revenue trend | The current statement analysis | Deal Bank statements tab |
| Monthly revenue when there is no analysis yet | The merchant's stated figure | Stated monthly revenue |
| Existing positions and their monthly payments | Active existing positions | Existing positions on the deal Overview or merchant Positions tab |
| Bank statements on file, documents present | Documents marked received or verified | Deal Documents & stips tab |
| Open position with this lender | Active positions linked to that lender | The position's Funder |
- True revenueTrue revenue is a merchant's real monthly sales on the bank statements: total deposits minus transfers, loan and MCA proceeds, refunds, reversals and owner money.
- Average daily balance (ADB)Average daily balance (ADB) is the mean of a bank account's end-of-day balances over a month. Funders use it to judge whether a merchant can carry daily payments.
- Negative daysNegative days are the days in a month when a merchant's bank account ends below zero. Funders cap them because each one risks a returned debit.
- PositionsA position is one open cash advance on a merchant's account, numbered in the order taken: first position, second position and so on.
- Time in business (TIB)Time in business (TIB) is how long a business has operated, usually counted in months from formation or start date. Funders set minimums by product.
Four rules worth knowing
- The deal's analysis wins. The CRM uses the current statement analysis on this deal; if there is none it falls back to the merchant's latest current analysis. Only when neither exists does it use Stated monthly revenue, and the matches card then says revenue is merchant-stated until a statement analysis is added.
- Owners and guarantors only. FICO and ownership come from contacts whose role is owner or guarantor, and the matcher takes the highest score on file.
- Payoffs do not count. A position switched to Pay off with the new advance is left out of the position count and the existing monthly payments, because the new funding retires it. Mark consolidations this way or every lender with a position limit will look stricter than it is.
- Positions entered beat the analysis. If you have entered active positions, they decide the count and payments. If you have not, the statement analysis figures are used. If the merchant truly has no advances, enter 0 positions in the analysis so the count is known.
Revenue-type rules can set a lookback (for example, the last 3 months), so the matcher averages or takes the worst month over that window from the analysis months. More months in the analysis means rules can be read the way the lender wrote them.
Step by step
Before you read the matches
0 of 7Common mistakes
- Leaving Date established blank. Every time-in-business rule then reads No data, and most lenders have one.
- Entering the owner's score on a contact with a role other than owner or guarantor. The matcher does not read it.
- Counting a position you are consolidating. Switch on Pay off with the new advance instead of deleting it, so the history stays.
- Relying on stated revenue for a real submission. Lenders underwrite to the statements; so should the matches.
- Expecting a home-based rule to pass. The merchant form has no home-based field yet, so a lender marked Home-based OK off reads No data on that rule.
Try it in the app
Signed in? Open the screen this lesson covers.
Finished this lesson?
0 of 7 lessons in Underwriting and analysis
Progress is saved in this browser. Sign in to keep it across devices.
Related lessons
- Underwriting and analysisReading the match matrixHow to read the deal's lender matches: eligibility groups, cell colors, the score, near misses, the recommended amount, and when submitting anyway makes sense.
- Processor playbookEntering the bank statement analysisType each month's deposits, true revenue, balances, NSFs, negative days and MCA debits into the deal's statement grid, and read the summary lenders match on.
- Processor playbookRecording existing positionsAdd every advance the merchant is already paying, mark the ones the new deal pays off, and see how positions drive holdback and lender matching.
- Reading bank statementsTrue revenue vs deposits: a worked exampleTotal deposits overstate what a merchant earns. A worked month showing which credits to strip (transfers, advances, refunds, owner money) and the arithmetic.
- Help centerHow lender matching worksEvery deal is checked against the criteria of every active lender program of its product, with a pass, fail or unknown result per rule, a reason you can read, and whether the file is ready for that lender.