Payment
A payment represents funds remitted by the borrower toward a credit facility. When a borrower makes a payment, the system automatically breaks it down into individual allocations that settle specific obligations according to a defined priority order. Defaulted obligations receive payment first, with interest settled before principal within the defaulted and nondefaulted groups.
Payment Processing Flow
When a payment is recorded against a credit facility, the following sequence occurs:
-
Payment Recording: The payment amount is recorded and credited to a payment holding account in the ledger. This holding account acts as a temporary staging area before funds are distributed to individual obligations.
-
Allocation Job Triggered: The payment recording event triggers the allocation background job, which handles the distribution of funds across outstanding obligations.
-
Obligation Retrieval and Sorting: The system retrieves all outstanding obligations for the credit facility and sorts them according to the priority rules described below.
-
Sequential Allocation: The system works through the sorted list of obligations, allocating as much of the payment as possible to each one. For each allocation, a ledger transaction moves funds from the holding account to the appropriate receivable account.
-
Completion Check: After each allocation, the system checks whether the obligation is fully satisfied. If the outstanding balance reaches zero, the obligation is marked as Paid.
Allocation Priority
The allocation algorithm prioritizes defaulted obligations so payments reduce defaulted exposure before servicing nondefaulted obligations. Within each group, interest is settled before principal:
| Priority | Obligations |
|---|---|
| 1 | Defaulted interest |
| 2 | Defaulted principal (disbursal) |
| 3 | Nondefaulted interest |
| 4 | Nondefaulted principal (disbursal) |
Within each priority group, obligations with earlier effective dates receive payment first. Earliest creation time breaks ties when effective dates match.
For example, defaulted principal receives payment before overdue interest. Among nondefaulted obligations, Not Yet Due, Due, and Overdue statuses do not override interest-before-principal ordering. Obligations that are not yet due remain eligible for payment.
Only settled obligations participate in payment allocation. Interest accrued within the current, incomplete accrual cycle remains in the pending ledger layer and is not yet an interest obligation. Once that accrued interest is settled and an interest obligation is created, it participates in subsequent payment allocation according to the priority above.
Partial Payments
The system handles partial payments gracefully. If a payment is not large enough to cover all outstanding obligations:
- The payment is allocated to obligations in priority order until the payment amount is exhausted.
- Obligations that receive partial allocation have their outstanding balance reduced by the allocated amount but remain in their current status.
- The next payment received will continue the allocation from where the previous one left off, starting again from the highest-priority remaining obligation.
For example, if a borrower owes $1,000 across three obligations and makes a $400 payment, the system will fully pay the first obligation (if it is $400 or less) and partially pay the next one. The borrower's repayment plan will update to show the reduced balances.
Payment Allocation Records
Each allocation creates a PaymentAllocation record that permanently links a portion of a payment to a specific obligation. These records serve as an audit trail and provide transparency into how funds were distributed.
A PaymentAllocation contains:
| Field | Description |
|---|---|
| Payment ID | The payment from which funds are being allocated |
| Obligation ID | The obligation receiving the allocation |
| Amount | The dollar amount allocated from this payment to this obligation |
| Allocation Index | A sequential index tracking the order of allocations for a given obligation |
A single payment can generate multiple allocation records (one per obligation it touches), and a single obligation can receive allocations from multiple payments over time.
Accounting Impact
Each payment allocation generates a ledger transaction that:
- Debits the payment holding account (reducing the unallocated payment balance)
- Credits the appropriate receivable account for the obligation (reducing the amount owed)
The credited receivable account depends on the obligation's type (interest or principal) and current status (Not Yet Due, Due, Overdue, or Defaulted). Repayments of defaulted obligations credit the dedicated defaulted receivable, reducing the balance moved there when the obligation defaulted.
Obligation Completion
When the sum of all payment allocations against an obligation equals its initial amount, the obligation's outstanding balance reaches zero and it transitions to the Paid status. This transition is automatic and immediate. Once paid, an obligation requires no further action from the borrower or the operator.
When all obligations under a credit facility are paid, the facility itself is automatically marked as complete. See Credit Facilities for details on facility completion.
Overpayment Handling
If a borrower makes a payment larger than the total outstanding obligations, the system allocates funds to all obligations (including those not yet due) until either the payment is fully distributed or all obligations are satisfied.