Investor portals and integration

Once you have multiple capital providers or facilities over $100M, self-service access becomes valuable. An investor portal gives your lenders what they need without requiring your team to respond to every data request. Beyond portals, your systems need to integrate with payment processors, banks, credit bureaus, and facility counterparties. The quality of these integrations determines how much manual reconciliation your team does.

What capital providers expect

A functional investor portal provides three categories of access:

Document repository

Monthly servicer reports
Quarterly performance decks
Borrowing base certificates
Compliance certifications
Legal documents (facility agreement, amendments)

Organized by date and document type, searchable, with clear naming conventions. Lenders should be able to find any document without asking you.

Data access

Downloadable loan tape (current and historical)
Stratification tables
Performance charts
Custom data queries (advanced feature)

Most lenders want the raw data so they can run their own analysis. Don’t assume a dashboard is sufficient; provide download capability.

Notifications

Monthly report availability
Covenant compliance status
Material events (trigger breach, amendment, etc.)

Automated notifications reduce “where is the report” inquiries. Set clear delivery schedules and stick to them.

Portal platform options

Third-party fund administration platforms

Platform	Services	Typical Cost
Alter Domus	Full fund administration with investor portal	$30-75K annually
SS&C	Enterprise-scale administration	$50-100K+ annually
Citco	Strong in credit funds	$40-80K annually
CSC Global	Document and reporting services	$20-50K annually

Illustrative pricing. See pricing disclaimer.

These platforms bundle portal functionality with fund administration services. If you need NAV calculation, investor accounting, or regulatory reporting, the bundled approach makes sense. For pure document and data access, you’re paying for functionality you don’t use.

Custom build

If your needs are specific or you have strong internal technology capabilities, a custom portal is achievable. Expect:

$100-300K to build
6-12 months development time
Ongoing maintenance (1-2 engineers or contractor support)

Custom builds make sense when:

You have multiple products with different reporting needs
You want to differentiate on investor experience
Your data access patterns don’t fit standard platforms
You have the technical team to maintain it

Hybrid approach

Many originators use a simpler approach until scale demands more:

Document repository (SharePoint, Google Drive, Dropbox) with controlled sharing
Automated report distribution by email
Structured folder organization by investor and date

This works until you have 5+ capital relationships or lenders start expecting real-time access. The main downside is no unified view across investors and no self-service for historical data.

Report formats and frequency

What lenders actually want (vs. what you might assume):

Report	Frequency	Format	Notes
Loan tape	Monthly	CSV/Excel	Standardized format per facility
Servicer report	Monthly	PDF + Excel	Summary + detail
Borrowing base	Monthly/Weekly	Excel	Calculation with supporting schedules
Covenant certificate	Monthly/Quarterly	PDF	Officer certification
Performance deck	Quarterly	PDF/PowerPoint	Visual summary with commentary
Static pool data	Monthly	Excel	Cohort-level performance tracking

Note: Ask your capital providers what format they actually want before you build elaborate reporting. Many prefer a clean Excel file over a fancy dashboard they’ll never log into.

Report delivery timing

Set clear expectations and meet them consistently:

Monthly reports: Due within 15-20 business days of month-end
Borrowing base: Per draw frequency (weekly or monthly)
Quarterly decks: Within 30 days of quarter-end
Annual reviews: Align with facility anniversary

Late reports signal operational issues. If you’ll miss a deadline, communicate proactively with your lenders.

Integration requirements

Your systems need to talk to each other and to external parties. Plan these integrations as core infrastructure, not afterthoughts.

Payment processing

ACH/NACHA file generation and transmission: Your LMS generates NACHA files for ACH debits and credits. These go to your processor (bank or third party).

Payment posting from processor to LMS: When payments clear, your LMS needs to know. Automated posting eliminates manual entry errors.

Return handling: NSF returns, unauthorized transactions, and disputes need automated processing. Manual return handling becomes a bottleneck at volume.

Reconciliation: Daily reconciliation between payment processor and LMS. Every payment received should match a payment posted.

Bank accounts

Daily balance feeds: Your LMS should know current cash positions without manual lookup.

Transaction-level detail: For reconciliation, you need every transaction, not just end-of-day balances.

Automated cash positioning: When managing multiple accounts (collection, operating, reserve), automation prevents manual errors.

Credit bureaus

Metro 2 reporting: Monthly required for consumer loans. Fixed-width format with specific field requirements.

Dispute handling workflow: When consumers dispute information, you need a documented resolution process.

Credit pull integration: For collections, pulling updated credit helps prioritize accounts.

Custodian

Document status tracking: Know which loan files are certified, which have exceptions.

Exception notifications: Automated alerts when documents are missing or deficient.

Certification workflow: Streamlined process for getting new loans certified.

Trustee/calculation agent

Distribution files: Amounts and accounts for waterfall distributions.

Investor reports: Required format varies by trustee; automate generation where possible.

Reconciliation data: Your numbers should tie to theirs without manual intervention.

Data delivery standards

Different counterparties accept different formats and delivery methods:

Counterparty	Typical Format	Delivery Method
Lender/trustee	CSV, XML, Excel	SFTP, email, portal upload
Calculation agent	XML, CSV	SFTP, API
Credit bureaus	Metro 2 (fixed-width)	SFTP
Payment processor	NACHA (fixed-width)	Direct connection or SFTP
Custodian	CSV, XML	SFTP, portal

APIs are becoming more common but are still not universal. Plan on supporting SFTP and flat file delivery for at least some counterparties. File formats are usually prescribed; you adapt to their requirements.

Reconciliation procedures

You need documented reconciliation for each data interface:

Cash reconciliation

Bank account balances match expected cash position in LMS.

Frequency: Daily
Tolerance: $0 variance (investigate everything)
Owner: Operations team

Loan count reconciliation

Number of loans in LMS matches trustee/lender records.

Frequency: Monthly
Tolerance: Zero variance
Owner: Operations team

UPB reconciliation

Total principal balance matches across systems.

Frequency: Monthly
Tolerance: Less than 0.01% variance (investigate larger)
Owner: Finance team

Payment reconciliation

Payments posted match payments received.

Frequency: Daily
Tolerance: $0 variance
Owner: Operations team

Build these reconciliations into your monthly close process. When they break, fix the root cause, don’t just adjust the numbers.

Integration implementation priorities

Not all integrations are equally urgent. Prioritize in this order:

Phase 1: Critical operations

Payment processor (can’t service without this)
Bank accounts (cash visibility)
LMS reporting (loan tape generation)

Phase 2: Compliance and reporting 4. Credit bureaus (Metro 2 regulatory requirement) 5. Investor reports (lender relationship) 6. Custodian (document certification)

Phase 3: Efficiency 7. Trustee/calculation agent (waterfall automation) 8. Analytics platform (data warehouse feeds) 9. Investor portal (self-service access)

Common integration mistakes

Underestimating file format complexity. Metro 2 and NACHA formats have specific requirements that aren’t obvious. Budget time for testing and certification.

Skipping reconciliation. Just because data flows doesn’t mean it’s correct. Build reconciliation from day one.

Manual processes that don’t scale. Uploading files manually works at 1,000 loans. At 10,000 loans with daily processing, you need automation.

Ignoring error handling. What happens when a file fails? Integration design should include alerting, retry logic, and exception queues.

Assuming APIs exist. Many counterparties still require SFTP and flat files. Don’t architect for APIs without confirming availability.

Data and analytics infrastructure - the data that feeds your reports
Security and compliance - protecting data in transit and at rest
Technology and infrastructure - overview and implementation roadmap