NetLoan - Record Funding on a Servicer Loan
Overview
This article shows how to record cash that owners are funding into a Servicer loan using the Funding Request workflow. Use it when funding flows to the loan independent of borrower activity - for example, loans where the lender funds 100% upfront while the borrower draws against it incrementally, or LOC structures where funds are received for a percentage of the available credit. Funding Requests can also be auto-created from a Draw Request (see NetLoan - Process a Draw on a Servicer Loan); the steps below describe creating one directly. The bills and invoices created on processing differ by ownership type - 3rd Party Owners get a single invoice, Subsidiary Owners get an intercompany invoice/bill pair.
Prerequisites
- NetLoan - Create a Servicer Loan must be complete (loan record exists, schedule generated, loan commenced).
- NetLoan - Set Up Ownership on a Servicer Loan must be complete - at least one active ownership record must exist on the loan. Funding Requests can't generate transactions without ownership.
- The Loan Type the loan was created from must have the Funding Invoice Item and Funding Bill Item populated. For Subsidiary Owners, the Subsidiary Owner Principal Bill Item must also be configured (see NetLoan - Configure Global Settings and Loan Type for Servicer Loans).
- NetSuite role with permission to create and approve NetLoan Funding Requests, and run the Funding Request suitelet.
Step-by-Step
Navigation
- Create a Funding Request: type New NetLoan Funding Request into the NetSuite global search bar to open a new Funding Request record (no menu entry exists for this yet).
- Process an approved Funding Request: NetLoan > Process Monthly Transactions > Monthly Bills
Process steps:
- Open a new Funding Request via the NetSuite global search (type New NetLoan Funding Request).
- Populate the request:
- Loan: the Servicer loan being funded.
- Funding Amount: the cash being funded by owners.
- Date: the effective date of the funding event.
- Draw Request: leave blank for a standalone funding event. (When a funding request is auto-created from a draw, this links back to the originating Draw Request.)
- Save. The system applies an auto-generated name to the request. Status defaults to Pending Approval.
- Approve the request: change Status to Approved and save. The change requires the appropriate role.
- Navigate to NetLoan > Process Monthly Transactions > Monthly Bills and select the Funding Request Invoice transaction type filter. Select the period for which you would like to process funding bills, any other filters you would like to apply, select the approved Funding Requests you would like to process, and submit them for processing. On successful processing, the status updates to Processed and the corresponding bills/invoices are created.
What gets created per ownership type:
| Ownership Type | Transactions created |
|---|---|
| 3rd Party Owner | One invoice in the loan's subsidiary. Customer = customer on the ownership record. |
| Subsidiary Owner | An intercompany pair: one invoice in the loan's subsidiary (customer = customer on the ownership record) and one bill in the owner's subsidiary (vendor = the loan-sub's representing vendor; uses the Subsidiary Owner Principal Bill Item booked to Note Receivable rather than the clearing account). |
| Servicer Owner | Not supported: should not be selectable on the ownership record. |
Each invoice or bill is created in proportion to that owner's Principal Ownership Percentage × the funding amount, and the resulting transactions are linked back to the Funding Request via the Funding Invoices sublist.
Considerations
- Funding can stand alone or follow a draw. Use a standalone Funding Request when funding is independent of borrower activity (upfront funding on a Dutch loan, LOC commitment funds). When funding follows a draw, check Generate Fund Request on the Draw Request and the system will create the matching Funding Request automatically - see NetLoan - Process a Draw on a Servicer Loan.
- Ownership must exist before processing. A Funding Request can be created and approved with no ownership in place, but processing will fail because there are no owners to allocate the funding to. Set up ownership before submitting for processing.
- Ownership percentages drive the split. Each owner's invoice/bill amount is funding amount × Principal Ownership Percentage on that owner's ownership record. If percentages don't total 100% across owners, the request will not process - ownership records on the loan must already total 100% on principal (enforced when ownership is set up).
Related Articles
- NetLoan - Servicer Entity Type Loans Overview
- NetLoan - Configure Global Settings and Loan Type for Servicer Loans
- NetLoan - Set Up Ownership on a Servicer Loan
- NetLoan - Distribute Payments to Owners on a Servicer Loan
Record Structure
NetLoan Funding Request
| Field Name | Field Type | Description | Example | Field ID |
|---|---|---|---|---|
| Name | Text | Auto-generated identifier for the request. Set by the system on save. | FR-2026-0042 | name |
| Loan | List/Record | The Servicer loan being funded. Pre-populated when the request is opened from a loan record. | Servicer Loan #12345 | custrecord_da_funding_loan |
| Funding Amount | Currency | The total cash being funded by owners. Each owner's invoice/bill is calculated as this amount × Principal Ownership Percentage. | 100,000.00 | custrecord_da_funding_amount |
| Date | Date | The effective date of the funding event. Used as the transaction date on the resulting bills and invoices. | 04/15/2026 | custrecord_da_funding_date |
| Status | List/Record | Lifecycle status of the request. Pending Approval → Approved → Processed (or Rejected). | Approved | custrecord_da_funding_status |
| Draw Request | List/Record | The Draw Request that triggered this funding event, when applicable. Blank for standalone funding requests. | Draw Request #DR-1042 | custrecord_da_funding_draw_request |
Funding Invoices sublist: displays all invoices and bills generated when the request was processed, linked back to the request for traceability. The sublist is populated automatically by the processing job; users do not edit it directly.
