The first time a capital partner asks for a static pool report, a borrowing base, or GAAP month-end numbers, you find out very quickly whether your reporting is ready for institutional money.
Banks, credit funds, and family offices want to see how your book performs over time, how much risk sits in it, and whether they can trust the numbers enough to put more capital behind you. If those reports take days to build from your CRM, servicing system, ACH portal, and spreadsheets, the raise slows down with them.
This guide breaks down the reports capital partners expect, and how to get your reporting ready before the request lands in your inbox.
Most MCA software is built to help you run the business day to day. It shows you what you funded, what you collected, which merchants are behind, and what's happening across the book right now.
But capital partners need a different view. A bank, credit fund, or family office wants to see how groups of deals perform over time. They want to know how much gets collected after three months, six months, or a year, how losses develop, and whether the performance is consistent enough for them to put more money behind you.
That's what institutional reporting is built to show. Even if your current dashboards are useful for running the shop, they may not answer the questions a capital partner is asking during diligence.
| What your day-to-day dashboard shows | What a capital partner wants to see |
|---|---|
| What you funded and collected this week | How a batch of deals performs over months |
| Which merchants are behind right now | How much is collected at 3, 6, and 12 months |
| The state of the book today | Whether performance is consistent enough to back |
Here are the reports they'll usually want to see:
When you raise capital, the same reports come up again and again. Here's what each one shows, why a partner cares about it, and why it matters if you can't produce it quickly.
| 1 | Static pool reports by vintage. A static pool groups the deals you funded in the same month or quarter and tracks how that exact group performs over time. Capital partners use it to judge the quality of your underwriting without newer deals hiding the performance of older ones. If you can't produce it, they have a much harder time deciding whether your book is strong enough to back. |
| 2 | Collection curves by deal age. A collection curve shows how much RTR has been collected at different points after funding, such as 3, 6, 12, or 18 months. Partners use it to understand how quickly and consistently your deals pay back. Without that view, it's harder for them to model what their own return could look like. |
| 3 | GAAP or accrual month-end reporting. Banks and institutional partners usually want month-end numbers in the accounting format their finance and audit teams already use. If your reporting is only cash-based, their team may have to rebuild the numbers before they can analyze the book, which slows down diligence. |
| 4 | Borrowing base reports. If you have a credit facility, the lender needs to know which receivables are eligible to borrow against and how much availability you have at any given time. The borrowing base report is what they use to calculate that. If it's late or inaccurate, your ability to draw on the facility can be delayed. |
| 5 | Covenant compliance reporting. Credit facilities usually come with rules you have to stay inside, such as delinquency limits, concentration limits, or minimum net worth. Your lender will expect regular reporting showing that you're still meeting those requirements. If that reporting is late or incomplete, you can create problems with the facility even when the underlying book is performing well. |
| 6 | Portfolio concentration and exposure. Partners want to see how much of the portfolio is concentrated in one industry, broker, geography, or risk band. They use that to understand whether too much of their capital depends on the same type of merchant or source. Too much concentration can affect how much they're willing to lend or the terms they offer. |
| 7 | Clean, current RTR numbers. Partners need a current view of Total RTR, Syndication RTR, and Active RTR so they can understand the size and health of the book. If those numbers are stale or have to be pieced together by hand, it becomes harder for them to trust the rest of the reporting. |
| 8 | Syndicator statements on demand. Syndicators want to see their position, payments, payouts, and returns by deal without waiting for someone on your team to build a report. Clear, current statements make it easier for partners to understand where their money is and how it's performing. |
| 9 | SOC 2 Type II and a clear audit trail. Institutional partners also care about the systems behind the numbers. They may ask whether your platform is SOC 2 Type II and whether changes to deal data, decisions, and records are tracked. That gives them more confidence that the data they're reviewing is secure and traceable. |
If you want to go deeper into the reporting side of running your portfolio, our guide to loan portfolio management software explains how these reports fit into day-to-day portfolio management. Knowing which reports partners want is the first step. The next is knowing how often they expect to receive them.
Capital partners usually want these reports on a set schedule, and the exact cadence will be written into your agreement. Here are the timelines you'll see most often.
| Report | Typical cadence |
|---|---|
| Borrowing base | Weekly or monthly |
| Static pool and vintage reports | Monthly or quarterly |
| Collection curves | Monthly or quarterly |
| Covenant compliance certificate | Monthly or quarterly |
| GAAP or accrual month-end package | Every month-end |
| Portfolio concentration | Monthly |
| RTR and payment status | Live, with a monthly review |
| Syndicator statements | Monthly, plus on request |
The timing matters almost as much as the report itself. A late borrowing base can delay a draw. A missed covenant report can create problems with the facility even if the book is performing well. If your team has to rebuild every report from scratch each time, staying on schedule becomes much harder.
That's where many funders run into the real reporting problem. Producing the reports is one thing, and producing them accurately, every time they're due, without losing days of work is another.
When your deal data lives across origination, servicing, ACH, and spreadsheets, every capital-partner report has to be assembled by hand. Each one has to be pulled together from those systems, reconciled until the numbers match, and rebuilt in the format the partner expects. That takes time every single month, and by the time the report is ready, the numbers may already be out of date.
The bigger problem is what that process tells the capital partner. If they ask for a static pool report or a borrowing base and your answer is, "we need a few days to pull that together," they can read that as a sign that your reporting isn't ready for institutional capital.
The cost is bigger than the hours your team spends rebuilding reports. Manual reporting can slow down diligence, delay decisions, and make it harder for a partner to feel confident putting more money behind your book. How quickly and cleanly you can produce the numbers is part of what they're evaluating.
If you plan to raise capital, do this work before a bank, credit fund, or family office starts asking for it:
| ✓ | Get the whole book onto one source of truth. Origination, servicing, syndication, and reporting should all pull from the same deal data. That makes it much easier to produce reports that actually tie out. |
| ✓ | Reconcile balances, RTR, and payment history. Find mismatches now and fix them before a partner's diligence team starts checking the numbers. |
| ✓ | Know the covenants you can realistically support. Understand your delinquency, concentration, and other key portfolio metrics before you agree to limits you may struggle to stay inside. |
| ✓ | Build the reports before anyone asks for them. Run a static pool, collection curve, borrowing base, and month-end package now. If something is hard to produce, you want to find that out before you're in the middle of a raise. |
| ✓ | Set a reporting calendar. Know which reports are due weekly, monthly, or quarterly so your team can produce them on time once the facility is live. |
| ✓ | Check your security requirements early. If a potential partner expects SOC 2 Type II or a clear audit trail, make sure your platform can support that before diligence starts. |
When a capital partner asks for a report, you should already know where the numbers come from, know that they match, and be able to send it without turning the request into a project.
Onyx IQ runs origination, servicing, collections, syndication, and reporting from the same deal data. That matters because the reports your capital partners ask for are built from the same records your team already uses to run the book. You don't have to export data from several systems, reconcile it in a spreadsheet, and rebuild the report every time someone asks for an update.
Here's how the main reporting requirements map to Onyx IQ:
| What your partner asks for | What it tells them | What Onyx IQ provides |
|---|---|---|
| Static pool by vintage | How a group of deals performs over time | Static pool reports |
| Collection curves | How quickly and fully deals pay back | Collection curve reports |
| GAAP or accrual month-end | Financial results in the format their finance team expects | Month-end and GAAP-accrual reporting |
| Borrowing base | How much eligible collateral is available to borrow against | Borrowing base reports |
| Covenant compliance | Whether the portfolio is staying inside agreed limits | Borrowing base, concentration, and delinquency reporting |
| Portfolio concentration | How much exposure sits in one industry, broker, or risk band | Concentration and exposure dashboards |
| RTR health | The current state of the book | Active RTR, Syndication RTR, and Total RTR |
| Syndicator statements | Each partner's positions, payments, and returns | Investor portal and partner statements |
| Security and audit trail | Whether the data is secure and traceable | SOC 2 Type II, audit history, and raw-data reporting |
Because the reports all come from the same live book, your team can pull them without rebuilding the numbers every time. You can also keep recurring reporting on a set schedule, so a borrowing base, month-end package, or partner statement doesn't turn into another manual project.
Your syndicators get the same benefit. They can log in and see their own positions and statements without waiting for your team to send them. That means less time spent building reports and a much faster answer when a capital partner asks for the numbers.
See how Onyx IQ handles your capital-partner reporting. Book a demo| Free guide Learn how to get off spreadsheets without breaking your book Our step-by-step guide shows MCA funders how to move onto one lending platform without losing control of the live book. | Read the guide |
When you raise capital, your reporting becomes part of the diligence. A capital partner wants to see how your book performs, how much risk is in it, what they can lend against, and whether the numbers are current and reliable.
If you can produce static pools, collection curves, borrowing base reports, clean RTR, and month-end numbers quickly, the conversation keeps moving. If every request turns into a manual reporting project, diligence slows down with it.
If you're preparing to raise, book a demo and we'll show you how Onyx IQ produces the reports your capital partners need from the same live data that runs your book.
The exact requirements depend on the partner and the facility, but common reports include static pool reports by vintage, collection curves, GAAP or accrual month-end reporting, borrowing base reports, covenant compliance reporting, portfolio concentration, Active RTR, Syndication RTR, Total RTR, and syndicator statements. Institutional partners may also ask about security controls, audit history, and certifications such as SOC 2 Type II.
Start by grouping all the deals funded during the same period, such as a month or quarter. Then track how that exact group performs over time, including collections and remaining RTR. You can build the report by hand, but that usually means pulling data from origination, servicing, and payment systems and reconciling it every time. If your platform runs the full book on one set of deal data, the static pool can be generated directly from those records. Onyx IQ includes native static pool reporting for this purpose.
Operational dashboards help you run the business today. They show things like what you funded, what you collected, which merchants are behind, and what's happening across the current book. Institutional reporting looks at performance over time. A bank, credit fund, or family office wants to see how groups of deals perform months after funding so they can understand risk, collections, and expected returns before putting capital behind you.
A collection curve shows how much RTR has been collected at different points after funding, such as 3, 6, 12, or 18 months. That lets a capital partner see how quickly and consistently deals pay back over time. They use that information to understand the performance of the book and model what their own capital could look like if they fund alongside you.
It depends on the capital partner. Many institutional partners will ask about the security controls of the system holding your deal and payment data, and SOC 2 Type II can be an important part of that diligence. If you plan to raise from banks, credit funds, or other institutional sources, it's worth confirming your platform's security certifications early in the process. Onyx IQ is SOC 2 Type II certified.
Cash reporting shows when money actually comes in or goes out. GAAP or accrual reporting gives finance and audit teams a broader view of when revenue, expenses, assets, and liabilities are recognized. Institutional partners often use that format because it fits more easily into their own financial models, diligence process, and audits. If your team can already provide the numbers in the format they expect, their analysts spend less time rebuilding your reporting before they can evaluate the book.