Adjust a charge · LendEasy Docs

Correct the assessed amount of a specific charge while preserving its original assessment, payment history, and a linked adjustment trail.

A charge adjustment corrects the amount that should have been assessed. It is not the same as forgiving a valid amount and not the same as returning money already paid.

Correcting what was assessed

CommandPOST /v1/loans/{loanId}/charges/{loanChargeId}?command=adjustment

Case contextRequired on human calls

ApprovalMaker-checker, keyed to size, class, or a credit result

Ledger effectA dated transaction linked to the charge

UndoNone — a second adjustment against the current amount

Correcting an assessment without editing history

Charge readassessed, paid, waived, outstandingautomatic
Dependencies checkedPUT before them, adjustment afterautomatic
Adjustment postsdated, linked to the chargeautomatic
Allocation replayedeach payment keeps its original amountautomatic

No existing payment transaction is edited. The correction is a new record standing beside the old one, which is why a charge's history still reads as what it was.

Adjust corrects, waive forgives, refund returns

the assessment was wrong

Adjust

Original $25 fee should legally have been $15
Adjust the assessed charge down by $10

the assessment was right

Waive

Original $25 fee was valid, lender grants courtesy relief
Waive $10

the money already moved

Refund

Borrower already paid a fee that must be returned
Refund the charge

This distinction controls accounting, customer explanation, and fee-performance reporting. A charge applied with no payments or waivers yet is updated or removed directly instead.

Read the charge first

GET /v1/loans/7204/charges/44 returns the assessed, paid, waived, and outstanding amounts. An adjustment cannot reduce the assessment below what the charge’s history already requires—if $20 has been paid, correcting the assessment to $15 creates a $5 credit consequence that must be handled deliberately, not discovered later.

Adjust an assessed charge

curl -X POST "$BASE/v1/loans/7204/charges/44?command=adjustment" \
  -H "Authorization: Bearer $TOKEN" \
  -H "LendEasy-Tenant: demo-lender" \
  -H "LendEasy-Case: case_HBR_FEE_REVIEW_2" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: hbr-fee-adjust-2027-04-15" \
  -d '{
    "amount": 10.0,
    "transactionDate": "2027-04-15",
    "dateFormat": "yyyy-MM-dd",
    "locale": "en"
  }'

{
  "officeId": 1,
  "clientId": 412,
  "loanId": 7204,
  "resourceId": 44,
  "changes": {
    "amount": 10.0
  }
}

Update before financial dependencies

Before any payment, waiver, or other dependency exists, correct the applied charge in place instead:

curl -X PUT "$BASE/v1/loans/7204/charges/44" \
  -H "Authorization: Bearer $TOKEN" \
  -H "LendEasy-Tenant: demo-lender" \
  -H "LendEasy-Case: case_HBR_FEE_REVIEW_2" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 15.0,
    "dueDate": "2027-04-11",
    "dateFormat": "yyyy-MM-dd",
    "locale": "en"
  }'

Governance and idempotency

Both routes write governance records readable at GET /v1/loans/7204/governance-records. Retrying with the same Idempotency-Key returns the original result.

A wrong adjustment is corrected by another adjustment

The correction is a new adjustment against the current amount, linked through the same case. It does not mutate the first.