Credit Facility Management — User Guide

Your complete guide to using dv01's Credit Facility Management (CFM) platform.

This guide walks you through each part of the CFM tool and how to use it — from uploading loan data to generating borrowing base and monthly servicer reports, to running loan allocation optimizations across your facilities.

Platform URL: https://credit-facility.dv01app.com/

Table of Contents

1. Overview & Getting Started
2. Managing Your Loan Data
3. File Upload Portal
4. Configuring a Facility
5. Generating Borrowing Base (BB) Reports
6. Generating Monthly Servicer Reports (MSR)
7. Loan Allocation with the Leverage Optimizer
8. Facility Analytics & Monitoring
9. Troubleshooting Common Issues
10. Getting Help

1. Overview & Getting Started

What is Credit Facility Management?

CFM is dv01's platform for managing warehouse credit facilities. It gives you a single place to:

• Manage loan-level data across your facilities
• Configure facility rules, eligibility criteria, and covenants
• Generate borrowing base (BB) reports to deliver to your warehouse lenders
• Generate monthly servicer reports (MSR) for compliance
• Optimize loan allocation across multiple facilities to maximize advance dollars
• Monitor facility performance, covenant compliance, and concentration trends over time

Who This Guide Is For

• Credit facility analysts — day-to-day users preparing BBs and MSRs, evaluating transactions
• Capital markets / treasury teams — planning loan allocation and monitoring facility headroom
• Operations — monitoring covenant compliance and delivering reports to lenders

Logging In

1. Navigate to https://credit-facility.dv01app.com/
2. Sign in with the credentials provided by dv01 during onboarding
3. You'll land on the facilities dashboard — only facilities belonging to your organization are visible

Main Navigation

2. Managing Your Loan Data

Before you can generate reports, CFM needs access to your loan-level data. There are two ways to get data into the platform.

2.1 Option A: dv01-Managed Datasets

If dv01 manages your data pipeline (for example, you're already a Portfolio Surveillance or Data Direct client), your loan data automatically flows into CFM.

• Data is normalized to dv01's standard schema
• Enriched fields (loan age, delinquency status, etc.) are pre-calculated
• Reports can be generated near-instantaneously
• No manual upload required

2.2 Option B: Self-Service Tape Upload

You can also upload loan tapes directly. This is especially useful for ad-hoc scenarios or if you're not yet fully integrated with dv01's data pipeline.

How to upload a tape

1. Drop your loan tape file to the SFTP folder provided during onboarding, or
2. Upload directly through the webapp in the data management section
3. The tape is automatically normalized into dv01's standard schema
4. Enriched tables are created and become available for BB, MSR, and optimizer runs

Supported file formats

CSV files are the standard format. dv01 will confirm the expected schema and required fields during onboarding.

2.3 Reviewing Your Available Data

From the facility details page, you can see:

• The most recent as of date available for your data
• Historical data dates available for retrospective reports
• Which dataset is currently selected for report generation

2.4 Multi-File Facilities

Some facilities require data from multiple source files — for example, the MSR might come from one file while covenant data lives in a supplemental document. CFM supports this by decoupling individual data points so they can be parsed from different sources and reassembled into a unified model.

If your facility uses multiple source files, make sure all expected files are delivered before generating reports. Missing files will result in incomplete outputs.

3. File Upload Portal

The File Upload Portal enables you to upload position and purchase tapes directly into CFM, without needing a full pipeline integration. This is ideal for:

• Quickly onboarding a new facility
• Uploading ad-hoc reporting data (e.g., a one-off file for a specific report)
• Identifying and resolving data discrepancies in your source file before ingestion

Once uploaded and normalized, files appear as datasets in CFM and can be used to generate BBs, MSRs, and optimizer runs.

3.1 Creating a Data Recipe

A Recipe defines how your raw file maps to a clean, validated table in the platform. You can reuse Recipes across uploads or build new ones for different file formats. Setup has two parts:

Part 1: Configuration

Part 2: Field Editor

• Columns — set data type, nullability, date format, and mark required fields
• Aliases — assign multiple source column names to the same output field (useful when different clients use different headers for the same data)
• Final Output Tab — preview how the data will appear after mapping, before you upload
• Import from File — bootstrap a Recipe by pointing at a sample file instead of building columns one by one

3.2 Importing Uploaded Data into a Facility

Once data is uploaded via a Recipe, import it into your facility configuration:

1. From the facility setup, click Add Datasets → Select Uploaded Files
2. Browse all datasets uploaded through your Recipes — you'll see schema, dataset, and table info at a glance
3. Check the Status column to confirm uploads completed successfully — failed uploads are flagged and cannot be imported
4. Select one or more datasets and click Import Selected

Imported datasets are then available as data sources when generating BB, MSR, or optimizer runs.

4. Configuring a Facility

A facility configuration defines the rules for how your warehouse operates — which loans are eligible, what the advance rates are, what concentration limits apply, and which triggers/covenants are monitored.

4.1 Facility Configuration Components

4.2 Creating a Facility

New facilities are created via the Create a Facility button in the upper right of the Facilities page. A facility configuration includes:

• Eligibility criteria — create, clone, reorder, and set up dependency chains between rules
• Concentration limits — with configurable thresholds (see Section 4.7)
• Advance rates — configurable per facility, with loan-level granularity
• Triggers — monthly, rolling average, and vintage-based triggers
• Waivers and amendments — temporarily exempt specific loans or rules from a BB run; waivers are reusable across reporting periods
• Manual distribution entry — record cash distributions tied to a BB run (full waterfall engine on roadmap)
• Facility balance tracking — record draws, paydowns, and manual adjustments; the balance can be reconstructed on any date from the delta stream

4.3 Initial Facility Setup (Onboarding)

Initial facility setup is typically done by dv01 during onboarding:

1. dv01 reviews your credit agreement and term sheet
2. dv01 comes back with clarifying questions on how to interpret specific terms
3. The facility is configured with all eligibility rules, advance rates, and concentration tests
4. BB and MSR templates are prepared
5. A first report is generated and validated against your expectations

Timeline: Typically 1 week for integration + onboarding. Complex facilities may take longer.

4.4 Editing & Recycling Facility Configurations

Once onboarded, you can modify facility configs through the webapp:

1. Navigate to the facility details page
2. Open the Configurations section
3. Edit eligibility criteria, advance rates, concentration tests, triggers, or covenants as needed
4. Save your changes — the system creates a new version while keeping the previous version intact

Recycling a configuration: If many of an existing facility's characteristics apply to a new one, you can recycle it from the Configurations section. This clones the full configuration as a starting point, saving setup time.

4.5 Configuration Versioning

Every change to a facility config creates a new version. This means:

• You can run "what-if" analysis by editing a config without losing the prior setup
• Historical reports remain tied to the config version used when they were generated
• You can roll back to a prior config version if needed

4.6 Config Drift Detection

When you execute a report (BB or MSR), CFM checks whether the facility config has changed since the last run. If drift is detected, you'll see a warning and be required to acknowledge the change before the report is posted to the facility ledger. This prevents accidental config changes from silently affecting your financial calculations.

4.7 Concentration Limits & Reporting Aggregates

Concentration limits and reporting aggregates are configured per facility to control risk exposure and generate summary analytics.

Excess Concentrations

• Highlight limits as minimum or maximum
• Create aggregations based on sum, count, weighted average, or non-weighted average
• Create non-binding excess concentrations using Tag Only — these are tracked but do not reduce the borrowing base
• Filter the denominator to scope the concentration test to a subset of the pool

Reporting Aggregates

• Create aggregations based on sum, count, weighted average, or non-weighted average
• Filter the denominator to scope the aggregate to a specific subset
• Reporting aggregates appear in the report output alongside concentration test results

4.8 Triggers vs. Covenants

In short: Triggers are "check engine" lights. Covenants are "rules of the road."

5. Generating Borrowing Base (BB) Reports

A borrowing base report calculates how much you can draw against the collateral in your facility, based on eligibility criteria, advance rates, and concentration tests.

5.1 When to Generate a BB

BB reports are typically generated:

• Weekly (most facilities)
• When new loans are added to the facility
• Before the MSR (monthly) — the MSR often references the most recent BB
• As part of an optimization run (see Section 7)

5.2 How to Generate a BB Report

1. Navigate to /borrowing-base/generation and click Generate, then select a facility configuration
2. Enter a report name, select an as-of date, and optionally choose a report template for the Excel output
3. Choose your data source:
   • dv01-managed dataset — select a portfolio or enriched dataset
   • Uploaded loan tape — select your uploaded file for the determination date
4. Dataset overrides (optional): apply WHERE filters or optimization filters to scope the data — useful when the facility pool includes multiple periods
5. Tape columns (optional): configure which columns appear and their ordering in the loan tape tab of the report
6. Manual inputs (optional): define calculations and values to be referenced in the report template
7. View the Date Profile to confirm the report as-of date fits the pool/facility date range
8. Click Generate

5.3 BB Report Output

After a BB report runs, you can:

• Review the Borrowing Base overview — advance amount & rate, collateral balance, loan count
• Review the configuration data mapping used for the run
• Download the report in multiple formats: Excel report, JSON request, or SQL query
• The Excel download includes a data tape and formulas for facility-specific rules, including custom expressions for complex calculations
• Execute the run to post it to the Transaction Log, and/or Duplicate the run to re-run with edits

5.4 How Long Does It Take?

• dv01-managed data: Near-instantaneous
• Uploaded tape: Under 10 minutes from upload to completed report

5.5 Reviewing BB Results

After a BB report runs, you'll see:

• The total borrowing base amount
• Advance rate summary (effective rate after concentration adjustments)
• Eligibility breakdown (eligible / ineligible balances)
• Concentration test results (which tests were breached and by how much)
• Balance context: beginning / ending balances, commitment amount, true-up amount

5.6 Exporting a BB Report

BB reports are generated as Excel files using the template configured for your facility. To export:

1. Open the report from the report detail page
2. Click Download Excel
3. The file is ready to send to your warehouse lender

5.7 Historical BB Reports

All executed BB reports are stored and viewable:

• One executed BB per transaction_date per facility
• View historical reports from the facility details page
• Download any past BB report at any time

5.8 Editing and Re-Running a Report

If a report errored or you need to adjust inputs, use the Edit & Run button on the report detail page. This lets you modify inputs and re-execute without starting from scratch.

6. Generating Monthly Servicer Reports (MSR)

The Monthly Servicer Report is the monthly compliance report you submit to your warehouse lender. It documents facility performance, trigger calculations, covenant compliance, waterfall/collections, and balance history.

6.1 What's in an MSR

• Beginning and ending balance for the period
• Trigger calculations (default ratio, delinquency, excess spread, CNL, etc.)
• Covenant compliance checks (pass/fail against contractual thresholds)
• Waterfall and collections calculations
• Loan-level detail (via linked or embedded tape)

6.2 Before You Generate an MSR

Make sure you have:

1. The most recent weekly BB (the MSR often references BB values)
2. End-of-period loan data loaded (either via dv01-managed dataset or uploaded tape)
3. Any required manual inputs (e.g., current SOFR reference rate)
4. The MSR Excel template uploaded for your facility

6.3 How to Generate an MSR

1. Navigate to /monthly-servicing/generation and click Generate, then select a facility configuration
2. Enter a report name, select an as-of date, and optionally choose a report template for the Excel output
3. Set the reporting period — beginning of period (bop_date) and end of period (eop_date)
4. Select the data source (dv01-managed or uploaded tape)
5. Dataset overrides (optional): apply WHERE filters or optimization filters to scope the data
6. Tape columns (optional): configure which columns appear and their ordering in the loan tape tab
7. Manual inputs: define calculations and values to be referenced in the report template (e.g., SOFR reference rate)
8. View the Date Profile to confirm the report dates fit the pool/facility
9. Click Generate
10. Review the balance summary — beginning balance should chain from the previous period's ending balance
11. Confirm and execute

Note: Triggers can be monthly, rolling average, or vintage-based, and can reference platform-wide data (i.e., outside the facility pool). After execution, you can Execute to the Transaction Log, Duplicate the run to re-run with edits, or download the Excel report, JSON request, or SQL query.

6.4 Configurable Triggers

The MSR calculates performance triggers configured for your facility:

Trigger thresholds and which triggers apply are configured in your facility settings.

6.5 Covenant Compliance

When generating the MSR, the system checks your facility's performance against all configured covenants. The report clearly shows pass/fail status for each covenant, along with the calculated value vs. the threshold.

6.6 Waterfall and Collections

The MSR includes automatic waterfall and collections calculations based on your facility's payment priority structure. These use either Excel formulas in the template or backend logic, depending on your facility setup.

6.7 Reviewing & Exporting the MSR

1. Review the generated report in the detail view
2. Verify trigger values, covenant status, and balance roll-forward
3. Download the Excel file
4. Submit to your lender

6.8 Historical MSR Tracking

All executed MSRs are stored and accessible:

• One executed MSR per eop_date per facility
• View performance trends over time
• Download past reports at any time

7. Loan Allocation with the Leverage Optimizer

The Leverage Optimizer helps you decide how to allocate loans across multiple warehouse facilities to maximize your total advance dollars while respecting each facility's eligibility criteria, concentration limits, and advance rate caps.

7.1 When to Use the Optimizer

Use the optimizer when you need to:

• Allocate new loan originations across multiple facilities
• Rebalance existing allocations to improve leverage
• Model "what-if" scenarios before committing to a facility placement
• Identify which facilities have available capacity for specific loan types
• Maximize excess concentration headroom before a BB submission

7.2 Data Configuration

Before running an optimization, define the dataset in Data Configuration. Multiple datasets can be chosen to aggregate across pools or asset types. The following fields need to be mapped:

7.3 How to Run an Optimization

1. Navigate to /optimizer
2. Click New Optimization Run (or Edit & Run on an existing run)
3. Select the consolidated pool of loans to optimize (from uploaded tape or dv01-managed dataset)
4. Select the facilities to include in the optimization
5. Review and edit facility configurations as needed (see "what-if" below)
6. Optionally freeze existing allocations (see Section 7.5)
7. Click Run Optimization
8. Wait for the run to complete — typically around 2 minutes for large pools

Note: Optimization runs are currently synchronous — you'll need to wait for the run to finish. You may need to refresh the page to see updated status.

7.4 Editing Facility Configs for Optimization

Before running an optimization, you can edit any facility's configuration. This is useful for modeling scenarios:

• Changing advance rates to see how total leverage shifts
• Tightening or loosening concentration tests to test different risk profiles
• Adjusting eligibility criteria to see which loans fall in/out

Your original facility config is preserved — these edits only apply to the optimization run.

7.5 Freezing Allocations

When optimizing additional loans only (keeping existing allocations fixed):

1. Enable "optimize additional loans only" mode
2. Existing loans stay in their current facility
3. The optimizer only places new originations
4. This matches the reality that existing facility allocations are typically locked in

7.6 Reviewing Optimization Results

After a run completes, you'll see:

• Total advance dollars across all facilities
• Per-facility summary: eligible balance, advance rate, borrowing base amount
• Loan-level facility assignments (including "unassigned" for loans the optimizer chose not to place)
• Concentration test status per facility
• Comparison to the prior allocation (if applicable)

7.7 Exporting Optimization Results

You can export:

• Consolidated loan tape — includes the facility assignment for every loan
• Summary report — facility-level advance amounts and utilization
• Borrowing base reports — one per facility, based on the optimized allocation

The loan tape export can be used to submit your new allocation to your warehouse lenders.

7.8 Historical Optimization Runs

All optimization runs are saved. You can:

• View results from previous runs
• Compare different runs side-by-side
• Load a prior run as the starting point for a new optimization
• Re-export summaries and BBs from any prior run

8. Facility Analytics & Monitoring

Beyond report generation, CFM provides analytics to help you monitor facility health and performance over time.

8.1 Time-Series Warehouse Analytics

Track how your facility evolves:

• Eligibility trends — how much of your portfolio qualifies over time
• Performance metrics — default ratios, delinquency, losses by period
• Concentration drift — how your portfolio's concentration profile shifts
• Advance rate evolution — effective rate after all adjustments

8.2 Excess Concentration Trends

View how concentration test results change over time. This helps identify:

• Which tests are trending toward breach
• Which tests consistently constrain your facility
• Impact of new originations on concentration headroom

8.3 Transaction Log & Facility Ledger

The Transaction Log is a persistent, chained, auditable facility balance record — designed to replace error-prone manual roll-forwards. Every report execution and manual adjustment creates a new entry.

What's tracked per entry

• Commitment amount
• Current loan amount
• True-up amount
• Beginning & ending balances per period
• Draws, paydowns, and manual adjustments

How it works

• Each executed BB and MSR posts to the Transaction Log automatically
• Balances chain across periods — each MSR's beginning balance links to the previous period's ending balance
• Only executed reports write to the log (drafts do not)
• Balance can be reconstructed on any date from the delta stream

Config Drift Detection

The system identifies when a facility configuration has changed since the last run, preventing silent changes from affecting financial calculations. When drift is detected, you must acknowledge the change before posting new results to the ledger.

Prior vs. Current View

The Transaction Log supports side-by-side comparison of BB/MSR reports across runs, with highlighted differences. This provides a full audit trail for compliance and review — you can see exactly what changed between any two report executions.

8.4 Covenant Compliance Monitoring

Track covenant compliance across periods:

• Historical pass/fail status for each covenant
• Values vs. thresholds over time
• Early identification of covenants approaching breach

9. Troubleshooting Common Issues

9.1 My BB numbers don't match what I expect

Common causes, in order of likelihood:

1. Date mismatch: Verify you're looking at the correct transaction_date. BB reports are date-specific.
2. Config change: Did someone recently edit the facility configuration? If so, the config drift warning should have flagged this at execution time.
3. Different data source: Check whether the report used a dv01-managed dataset vs. an uploaded tape.
4. Concentration breach: A concentration test may have reduced the effective advance rate. Review the test results in the report.
5. Data freshness: If using dv01-managed data, verify the data has been updated for the reporting period.

9.2 My MSR beginning balance doesn't match the previous period's ending balance

1. Verify the previous MSR was executed (not just drafted). Only executed reports write to the ledger.
2. Check for config drift between periods. If the facility config changed, you'll need to acknowledge the change before the new report posts.
3. Review the facility ledger to confirm ending balances for the prior period.
4. If this is your first MSR in the new ledger system, initial balances may need to be manually seeded by dv01.

9.3 My MSR triggers show unexpected values

1. Verify the reporting period dates (bop_date and eop_date) are correct.
2. Check that manual inputs (e.g., SOFR reference rate) were entered correctly.
3. For vintage-based triggers, confirm the correct vintage cohorts are being included.
4. Verify the loan data for the period is complete.

9.4 Report generation failed or errored

1. Click the Edit & Run button on the report detail page to modify inputs and retry.
2. Verify your loan tape is complete for the selected date range.
3. Check that the facility has a valid configuration (all required fields set).
4. If the error persists, contact support with the report ID.

9.5 Template upload fails

1. Ensure the Excel file doesn't use reserved table names (e.g., Tape, ExtendedTape).
2. Verify the template structure matches the expected format.
3. Check that the file size is within limits.
4. If issues persist, contact support and attach the template.

9.6 Optimization is taking too long

• For large pools (250K+ loans across multiple facilities), expect around 2 minutes.
• If significantly longer, try reducing the loan pool size or number of facilities to isolate the issue.
• Refresh the page to check status — the optimizer doesn't currently auto-update.

9.7 I can't see a facility or the application is down/unresponsive

• If a facility is missing, contact dv01 support.

9.8 The platform is down or unresponsive

• Verify credit-facility.dv01app.com is the correct URL.
• Try a different browser, clear your cache, contact support.

10. Getting Help

Contact Support: support@dv01.co

 Contacting Support, Include:

• The facility name and ID
• The report ID (if applicable)
• A screenshot or error message
• The steps you took leading up to the issue

Onboarding & Training

Your account manager can schedule additional training sessions for new users on your team. Reach out through your usual dv01 contact.

Feature Requests

We actively develop CFM based on client feedback. Share feature requests through your account manager or directly with the support team.