Adjust a charge

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.

Before choosing adjustment

Situation	Correct action
Original $25 fee should legally have been $15	Adjust the assessed charge down by $10.
Original $25 fee was valid, lender grants courtesy relief	Waive $10.
Borrower already paid a fee that must be returned	Refund the charge.
Charge was applied but has no payments or waivers yet	Update or remove it directly.

This distinction controls accounting, customer explanation, and fee-performance reporting.

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

Adjustment is a governed charge command. A human call carries LendEasy-Case when case management is enabled.

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
  }
}

The adjustment posts as a dated transaction linked to the charge. No existing payment transaction is edited; allocation replay creates linked changes while each payment preserves its original amount and value date.

Update before financial dependencies

Before any payment, waiver, or other dependency exists, the applied charge can be corrected 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"
  }'

Once financial dependencies exist, PUT is rejected and the dated adjustment command is the correction path.

Governance and idempotency

Both routes write governance records readable at GET /v1/loans/7204/governance-records, and maker-checker can park either command for a second approver based on adjustment size, charge class, or whether the change produces a credit. Retrying with the same Idempotency-Key returns the original result. A second correction creates a second linked adjustment; it does not mutate the first.

Undo

There is no undo command for a charge adjustment. A wrong adjustment is corrected by a new adjustment against the current amount, linked through the same case.