LendEasy/Docs
Get API keys
GuidesLoansReschedule installments

Reschedule installments

Request, approve, and apply a broader repayment modification—grace periods, extra terms, rate and due-date changes—through a workflow where the approver is never the requester.

Rescheduling is the governed modification workflow for changes that need a proposal and a separate reviewer. One request can express a due-date shift, principal or interest grace periods, extra terms, a product-permitted rate change, or a recurring moratorium—effective from a chosen date.

Re-age and re-amortize are direct schedule commands with narrow semantics. A reschedule request is appropriate when a lender must review a full modification package before it becomes effective.

Request lifecycle

The request does not change the schedule until it is approved—and the approver must be a different user from the requester. That request→approve pair is the second-person control for reschedules; they do not pass through the maker-checker inbox used by other governed commands.

Cedar modification package

Using the same August 20 snapshot, Cedar has $2,640 outstanding and three past-due installments. A hardship specialist proposes:

  • no payment due before September 15, 2027;
  • eight monthly $330 principal-only installments;
  • new maturity April 15, 2028; and
  • no waived principal, interest, or fees.

The request carries the terms; the review documents, affordability notes, and customer acceptance evidence live on the case named in the LendEasy-Case header.

Create the request

Reason codes come from the tenant catalog—read GET /v1/rescheduleloans/template for the current list.

curl -X POST "$BASE/v1/rescheduleloans" \
  -H "Authorization: Bearer $TOKEN" \
  -H "LendEasy-Tenant: demo-lender" \
  -H "LendEasy-Case: case_CEDAR_HARDSHIP_4" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: cedar-hardship-modification-v1" \
  -d '{
    "loanId": 7204,
    "rescheduleFromDate": "2027-09-01",
    "rescheduleReasonId": 61,
    "submittedOnDate": "2027-08-20",
    "adjustedDueDate": "2027-09-15",
    "extraTerms": 3,
    "recalculateInterest": true,
    "rescheduleReasonComment": "Temporary income reduction; resume Sep 15.",
    "dateFormat": "yyyy-MM-dd",
    "locale": "en"
  }'
{
  "resourceId": 5,
  "loanId": 7204
}

Other term fields include graceOnPrincipal, graceOnInterest, newInterestRate, and recurringMoratoriumOnPrincipalPeriods. GET /v1/rescheduleloans/{scheduleId} returns the pending request with its proposed changes and decision state; GET /v1/rescheduleloans lists requests and their approval status.

What reviewers compare

Dimension Original remaining terms Proposed terms
Outstanding principal $2,640.00 $2,640.00
Past-due amount $990.00 $0.00 after application
Remaining payments 8 8
Payment amount $330.00 $330.00
Next due date Already overdue Sep 15, 2027
Maturity Jan 8, 2028 Apr 15, 2028
Total remaining cost $2,640.00 $2,640.00

For Harbor or another interest-bearing loan, the reviewer also weighs interest already accrued, future interest under recalculateInterest, total remaining payments, effective rate changes, and any disclosure consequence. Build the comparison from the current schedule read and attach it to the case.

Approve or reject

curl -X POST "$BASE/v1/rescheduleloans/5?command=approve" \
  -H "Authorization: Bearer $TOKEN" \
  -H "LendEasy-Tenant: demo-lender" \
  -H "Content-Type: application/json" \
  -d '{
    "approvedOnDate": "2027-08-21",
    "dateFormat": "yyyy-MM-dd",
    "locale": "en"
  }'

Approval applies the schedule change in the same step; ?command=reject records the decision and leaves the schedule untouched. The decision retains the originating governance linkage and takes no new LendEasy-Case header. Both the request and the decision appear in the loan’s governance records.

If loan facts change between submission and review—a payment posts, a restriction lands—the reviewer rejects and the specialist submits a fresh request against current facts. An approval never silently applies terms computed from a stale balance.

After application

Read GET /v1/loans/7204?associations=repaymentSchedule,transactions for the authoritative new schedule. Future autopay targets and statements use it. Completed documents, prior delinquency snapshots, and the original request remain immutable.

Reverse or correct

There is no undo command for an applied reschedule. Correct with a new reschedule request against the current schedule, linked to the same case; the original request, its approval, and customer communications remain in evidence, and affected reporting recalculates from the corrected schedule.

Never use rescheduling to hide an unauthorized waiver or write-off. Any forgiven component must post through its own governed command—waive interest, waive a charge, or write off—with its own approval and accounting.
Unified search across guides, recipes & the API referenceEsc