Lender error list

Error format Lender returns most errors as RFC 9457 problem details with the application/problem+json media type. A rate-limit refusal answers a flat {code, title, message} body on application/json.

{
  "title": "Unprocessable Entity",
  "status": 422,
  "detail": "validation failed",
  "errors": [
    {
      "location": "body.grossRequestedAmount",
      "message": "expected string",
      "value": 50000
    }
  ]
}

{
  "code": 429,
  "title": "rate_limit_exceeded",
  "message": "rate limit exceeded"
}

Field definitions

code – The stable, machine-readable domain code the refusal carries, in the form LENDER-NNNN. Absent when the refusal has not been given one. Branch on this first.
status – The HTTP status code.
title – The status name, such as Unprocessable Entity.
detail – What went wrong on this occurrence. Below 500, it describes the specific refusal. For 500, 502, and 503, it carries a fixed generic value instead of the underlying cause.
errors – Optional list of schema-validation details. Each entry carries a location, a message, and the value Lender received.
type – https://errors.lerian.studio/v1/LENDER-NNNN when code is present. The RFC 9457 default about:blank otherwise.

The flat rate-limit body carries code, title, and message instead. Its code repeats the numeric HTTP status. Its title names the refusal and its message explains it in one sentence. Neither string varies with the caller or names your remaining quota. Branch on code when the response carries one, and on the HTTP status and the content type when it does not. Read detail only as prose for a human. Authorization and idempotency middleware can answer in their own response formats.

Client errors

Lender answers a 4xx when the request is the problem, and detail names the specific refusal. Lender scopes a lookup to the caller’s tenant and to the parent named in the path. An identifier that resolves outside that scope answers the same way as an identifier that resolves to nothing. A command needs a subject on the caller identity, because Lender records that subject as the actor behind the change. Byte limits apply twice: the framework limits the request body, and each file-ingestion surface limits the file it accepts. Schema validation runs before the handler and fills errors with one entry per rejected location. A business rule runs inside the handler and answers with detail alone. Three examples: a currency assertion that disagrees with the loan, a set composition that mixes currencies, and a fund configured without a registry.

Status	What it means	What to do
`400`	The request arrives without a body, or the body is not the exact JSON shape the operation reads.	Send a body that matches the operation’s schema, then repeat the request.
`400`	The `X-Idempotency` header is longer than the operation accepts.	Send a shorter key, then repeat the request.
`401`	The request arrives without an authenticated identity.	Send a valid bearer token, then repeat the request.
`401`	The identity is authenticated, and its subject is empty.	Use a token whose subject identifies the caller.
`403`	The request lacks a validated tenant identity for the resource the operation works on.	Use a token scoped to the tenant that holds the resource, then repeat the request.
`404`	The identifier in the path names a resource this tenant does not hold.	Check the identifier, and check the tenant the token is scoped to.
`404`	The resource exists, and the parent named in the path does not hold it.	List the parent’s own resources, then use an identifier from that list.
`409`	Another request carrying the same `X-Idempotency` value is still running.	Wait the `Retry-After` interval, then read the resource. Do not send the command again.
`422`	The `X-Idempotency` value was already used for a request with a different body.	Do not send this command under a new key. Read the outcome of the original request first, then decide.
`409`	The `idempotencyKey` in the body names a term already recorded with different content.	Read the term on record. A new key records a second term for the same set.
`409`	The resource sits at a different lifecycle step, or it was already closed.	Read the resource, then act from the step it is at.
`409`	Another writer changed the resource during the request.	Read the resource again, then repeat the request.
`409`	An external registry already accepted this exact command.	Read the protocol on record instead of issuing the command again.
`413`	The request body is larger than the operation accepts.	Send a smaller body.
`413`	The uploaded file is larger than the ingestion surface accepts.	Send a smaller file.
`405`	The path exists, and it does not accept this HTTP method.	Use a method the operation declares in the API reference.
`415`	The `Content-Type` header names a format the operation does not read.	Send `application/json`.
`429`	The caller sent more requests than the deployment’s rate limit allows.	Read the `Retry-After` header, wait that many seconds, then repeat the request.
`422`	The request does not match the operation’s schema.	Correct each entry in `errors`, then repeat the request.
`422`	The request matches the schema, and a business rule refuses its content.	Read `detail`, correct the request, then send it again.
`409`	A command reached a resource that is already closed, and it is not the redelivery of the command that closed it.	Redelivering the original command under the same request identity answers `200` with the record that already stands. This status means a second, different command. Read the record, then decide; nothing was posted twice.
`409`	The refusal is reproducible: repeating the request reproduces the conflict.	Do not repeat it. The state the request was built against changed, so reconcile the record and issue the command the current state calls for.
`422`	The refusal is terminal by design: the request can never succeed as stated.	Do not resend it, with or without corrections. `detail` names the case. The operation refused rather than leaving the resource half-changed, and the resource is exactly as it was.
`422`	The refusal names deployment or operator configuration rather than a malformed request.	Correcting the body will not help. `detail` names the object and the state it is in. Fix the configuration, then send the original request again.

Server errors

Lender answers a 5xx when the request is sound and the call could not complete. For these statuses detail carries a fixed generic value, so the underlying cause stays inside the service. A 503 covers two conditions: a capability the deployment does not run, and a dependency Lender cannot reach at the moment of the call. A 502 covers a third party that refuses a command Lender forwards to it, such as the registry that records an assignment of receivables.

Status	What it means	What to do
`500`	Lender could not complete the request.	On a read, repeat the request. On a command that moves money, read the resource first, and repeat only if the command did not land. If the status repeats, contact support with the operation, the tenant, and the time of the call.
`502`	The registry Lender forwards to refused the command.	The response does not name the reason. Check the fund’s registry configuration and the command’s data, then issue the command again.
`503`	The deployment does not run the capability the operation needs.	Ask your platform team to enable the capability for your deployment.
`503`	A store or a downstream dependency was unreachable.	Retry with backoff.

Error codes

The tables below list the codes that Lender returns. title is the name of the HTTP status, and detail describes the specific case for a person, so branch on code, not on detail.

General

Code	Status	Refusal
`LENDER-0000`	`500` Internal Server Error	Lender could not classify the failure. Treat it as a server error.

Products

Code	Status	Refusal
`LENDER-0101`	`409` Conflict	The loan product is not active, so you cannot change its current version.
`LENDER-0102`	`422` Unprocessable Entity	The version you named is not a version of this loan product.
`LENDER-0103`	`400` Bad Request	`chargeEffectiveAt` or `accountCreatedAt` is a calendar date. Send an RFC 3339 instant.

Origination

Code	Status	Refusal
`LENDER-0201`	`409` Conflict	The application is already disbursed, and this disbursement declares no `trancheNumber`.
`LENDER-0202`	`422` Unprocessable Entity	The disbursement amount or its `trancheNumber` contradicts the approved amount.
`LENDER-0203`	`404` Not Found	No loan application in your tenant has this identifier.
`LENDER-0204`	`409` Conflict	Another request changed this application first. Nothing was written.
`LENDER-0205`	`409` Conflict	A different disbursement already uses this idempotency key.
`LENDER-0206`	`403` Forbidden	The authenticated subject cannot perform this action on this application.
`LENDER-0207`	`422` Unprocessable Entity	Lender cannot resolve the product-version profile that this disbursement needs.
`LENDER-0208`	`422` Unprocessable Entity	The net amount does not equal gross minus the withholdings, minus the origination fee.
`LENDER-0209`	`422` Unprocessable Entity	The origination fee is equal to or greater than the amount left after the withholdings.
`LENDER-0210`	`422` Unprocessable Entity	The product retains an origination fee that its accrual basis cannot amortize.
`LENDER-0211`	`409` Conflict	The loan account already has a loan application.
`LENDER-0212`	`422` Unprocessable Entity	A field of the request is malformed.
`LENDER-0213`	`409` Conflict	The action is not permitted from the application’s current status. `detail` names the status.
`LENDER-0214`	`422` Unprocessable Entity	A counterparty’s payment instant is further ahead of Lender’s clock than the permitted skew.
`LENDER-0215`	`422` Unprocessable Entity	The requested rate is outside the product version’s rate band.
`LENDER-0216`	`422` Unprocessable Entity	The product version declares no rate band.
`LENDER-0217`	`422` Unprocessable Entity	The currency in the disbursement request is not the application’s currency.
`LENDER-0218`	`422` Unprocessable Entity	The opening entry that the reschedule request cites does not match this contract.
`LENDER-0219`	`422` Unprocessable Entity	A schedule-preview money or rate field is not a decimal.
`LENDER-0220`	`422` Unprocessable Entity	A schedule-preview decimal string is longer than Lender accepts.
`LENDER-0221`	`422` Unprocessable Entity	A schedule-preview decimal has an exponent outside the accepted range.
`LENDER-0222`	`503` Service Unavailable	The deployment has no loan-application reader for this route.
`LENDER-0223`	`503` Service Unavailable	Schedule preview is not configured in this deployment.
`LENDER-0224`	`503` Service Unavailable	The deployment cannot run the release that a substantial renegotiation needs.
`LENDER-0225`	`422` Unprocessable Entity	The loan product behind this application is not active.
`LENDER-0226`	`422` Unprocessable Entity	The version you named is not the product’s current version.
`LENDER-0227`	`422` Unprocessable Entity	The disbursement’s `jurisdictionExtensions` carries no `disbursedAt`.
`LENDER-0228`	`422` Unprocessable Entity	The product version does not admit the application’s borrower kind.
`LENDER-0229`	`422` Unprocessable Entity	The first due date is on or before the disbursement date.
`LENDER-0230`	`422` Unprocessable Entity	The application declares no borrower kind, and the operation needs one.
`LENDER-0231`	`422` Unprocessable Entity	The first due date is so late that the first installment repays no principal.
`LENDER-0232`	`422` Unprocessable Entity	The request sets both a first due date and a grace period.
`LENDER-0233`	`422` Unprocessable Entity	The deployment prices no tax for the application’s borrower kind.
`LENDER-0234`	`422` Unprocessable Entity	The schedule produced a period of zero days or fewer under the jurisdiction’s calendar.
`LENDER-0235`	`422` Unprocessable Entity	The product version does not admit the chosen first due date.
`LENDER-0236`	`422` Unprocessable Entity	The application cites a schedule offer that is not on file.

Servicing

Code	Status	Refusal
`LENDER-0301`	`422` Unprocessable Entity	Lender cannot read the request as a payment: the amount is not positive or has sub-cent precision, the idempotency key is missing, or the instant is invalid.
`LENDER-0302`	`409` Conflict	The payment is dated before facts that the loan account already settled.
`LENDER-0303`	`409` Conflict	A different payment already uses this idempotency key.
`LENDER-0304`	`409` Conflict	The per-installment breakdown allocates more than the installment owes.
`LENDER-0305`	`404` Not Found	No active loan account has this identifier.
`LENDER-0306`	`409` Conflict	The loan account has more than one live application, so its chart of accounts is ambiguous.
`LENDER-0307`	`422` Unprocessable Entity	The loan product version has no accounting profile.
`LENDER-0308`	`422` Unprocessable Entity	The product’s chart of accounts cannot express this movement.
`LENDER-0309`	`422` Unprocessable Entity	The movement cannot be expressed as a ledger posting under the product’s accounting profile.
`LENDER-0310`	`503` Service Unavailable	A component that this movement needs is not configured in the deployment.
`LENDER-0311`	`404` Not Found	The payment to reverse is not on this loan account.
`LENDER-0312`	`409` Conflict	The payment already has a reversal.
`LENDER-0313`	`422` Unprocessable Entity	A payment dated after the one you reverse stands on the contract.
`LENDER-0314`	`422` Unprocessable Entity	The schedule changed after the payment you reverse.
`LENDER-0315`	`422` Unprocessable Entity	A later payment and a later schedule version both stand on the contract.
`LENDER-0316`	`409` Conflict	A different reversal already uses this idempotency key.
`LENDER-0317`	`422` Unprocessable Entity	The reversal request is missing the lineage facts it needs.
`LENDER-0318`	`403` Forbidden	No validated identity reached the read, so Lender cannot scope it.
`LENDER-0319`	`409` Conflict	The loan has no single live application, so the compensating entry has no chart of accounts.
`LENDER-0320`	`409` Conflict	Lender cannot establish whether the original payment reached the ledger.
`LENDER-0321`	`422` Unprocessable Entity	The requested page or filter is not valid.
`LENDER-0322`	`409` Conflict	An earlier settlement already used part or all of this rebate.
`LENDER-0323`	`422` Unprocessable Entity	The returned payment carried unapplied cash, so it cannot become a receivable.
`LENDER-0324`	`404` Not Found	No returned-payment receivable has this identifier.
`LENDER-0325`	`409` Conflict	The receivable is already collected.
`LENDER-0326`	`422` Unprocessable Entity	The collection cannot be applied as sent.
`LENDER-0327`	`422` Unprocessable Entity	The payment you reverse booked nothing.
`LENDER-0328`	`503` Service Unavailable	Settlement is not configured in this deployment.
`LENDER-0329`	`404` Not Found	The schedule version you named is not on this contract.
`LENDER-0330`	`422` Unprocessable Entity	A field of the settlement or reschedule request is malformed.
`LENDER-0331`	`422` Unprocessable Entity	This contract settles only against a prepayment quote, and the request has none.
`LENDER-0332`	`422` Unprocessable Entity	The settlement is for more principal than the contract owes.
`LENDER-0333`	`422` Unprocessable Entity	The schedule version carries interest and no rate.
`LENDER-0334`	`422` Unprocessable Entity	The accrual run cannot recognize the months that this schedule creates.
`LENDER-0335`	`422` Unprocessable Entity	The product has no rule for the gain or loss of a substantial renegotiation.
`LENDER-0336`	`422` Unprocessable Entity	The product has no derecognition or recognition rule.
`LENDER-0337`	`422` Unprocessable Entity	The replacement contract’s terms are incomplete.
`LENDER-0338`	`422` Unprocessable Entity	The modification is substantial (Res. CMN 4.966 art. 22), so it is not a successor schedule of this contract.
`LENDER-0339`	`422` Unprocessable Entity	The schedule cannot place the first installment on the requested date.
`LENDER-0340`	`422` Unprocessable Entity	The contract has no positive carrying amount to renegotiate.
`LENDER-0341`	`422` Unprocessable Entity	A payroll-deducted contract cannot be renegotiated substantially.
`LENDER-0342`	`409` Conflict	A different schedule-version request already uses this idempotency key.
`LENDER-0343`	`409` Conflict	The contract has already left the servicing book: it was settled, assigned, or ported.
`LENDER-0344`	`409` Conflict	A substantial renegotiation of this contract already exists.
`LENDER-0345`	`409` Conflict	The outbox quarantined a posting for this contract.
`LENDER-0346`	`409` Conflict	A posting for this contract was published, and the ledger did not confirm it.
`LENDER-0347`	`409` Conflict	A posting for this contract is in transit, and its acknowledgement has not arrived.
`LENDER-0348`	`400` Bad Request	The payment instant is a calendar date. Send an RFC 3339 instant.

Accounting

Code	Status	Refusal
`LENDER-0401`	`503` Service Unavailable	No chart balance-transfer sweep is configured, so a chart change cannot move balances.
`LENDER-0402`	`503` Service Unavailable	Lender could not read the ledger, so the sweep moved nothing.
`LENDER-0403`	`409` Conflict	The chart change is refused, because the deployment cannot move the balances it would leave behind.
`LENDER-0404`	`409` Conflict	A contract has no ledger asset, so Lender cannot read its balances.
`LENDER-0405`	`409` Conflict	The retry rebuilt a posting that differs from the one already queued for the same recognition.
`LENDER-0406`	`422` Unprocessable Entity	The chart can divert a returned final payment, and it lacks the rules to provision and write off that debt.
`LENDER-0407`	`422` Unprocessable Entity	Some item identifiers selected for the retry do not belong to the accrual run. `errors[].value` names up to ten of them.
`LENDER-0408`	`422` Unprocessable Entity	The product books this contract into accounts that it shares with other contracts, so the exit cannot be measured.
`LENDER-0409`	`409` Conflict	The ledger holds funds on this contract’s accounts.
`LENDER-0410`	`503` Service Unavailable	Lender could not read the ledger.
`LENDER-0411`	`422` Unprocessable Entity	The product books the deferred origination fee into a shared account.
`LENDER-0412`	`409` Conflict	The contract’s deferred-fee accounts carry a line that no reconciliation bucket covers.
`LENDER-0413`	`422` Unprocessable Entity	The deferred-fee reconciliation names no loan account.
`LENDER-0414`	`409` Conflict	The chart balance transfers on the deferred-fee accounts do not net to zero.
`LENDER-0415`	`404` Not Found	No disbursed contract in your tenant has this loan account.
`LENDER-0416`	`409` Conflict	More than one application claims this loan account.
`LENDER-0417`	`422` Unprocessable Entity	No chart of the product version was in force on the day that the first tranche was disbursed.
`LENDER-0418`	`422` Unprocessable Entity	A stored chart of the product fails accounting-profile validation.
`LENDER-0419`	`422` Unprocessable Entity	The product books the revenue tax (PIS/COFINS) into a per-contract account.

Assignment of receivables

Code	Status	Refusal
`LENDER-0501`	`422` Unprocessable Entity	The payoff amount agreed with the fund exceeds the face value of the installments that the fund still owns.
`LENDER-0502`	`422` Unprocessable Entity	The payoff amount agreed with the fund is zero or less.
`LENDER-0503`	`422` Unprocessable Entity	The sale sends a retention field with no value: `retainedFraction` is null or blank, or `sellerRetainsControl` is null.
`LENDER-0504`	`422` Unprocessable Entity	The retained fraction reaches the substantial-retention threshold. Lender assembles a sale only when the fraction is below it.
`LENDER-0505`	`422` Unprocessable Entity	The seller retains control of what it sold (Res. CMN 4.966 art. 26 III). Lender does not book this kind of sale.
`LENDER-0506`	`422` Unprocessable Entity	A retained fraction is not a decimal string from 0 to 1 with no more than 8 decimal places.

Audit

Code	Status	Refusal
`LENDER-0801`	`503` Service Unavailable	The loan audit history store has no database behind it.

Brazil

Code	Status	Refusal
`LENDER-0900`	`422` Unprocessable Entity	The deployment’s rate table has no IOF rate for the borrower kind.
`LENDER-0901`	`422` Unprocessable Entity	The problem-asset declaration names no norm article.
`LENDER-0902`	`422` Unprocessable Entity	The declaration names no source.
`LENDER-0903`	`422` Unprocessable Entity	The declaration cites no evidence.
`LENDER-0904`	`422` Unprocessable Entity	The declaration has no signer: no validated identity reached it, and it names no declaring subject.
`LENDER-0905`	`422` Unprocessable Entity	The declaration is not valid for another reason: an evaluation date in the future, no idempotency key, or a field over its length limit.
`LENDER-0906`	`404` Not Found	No loan account in your tenant has this identifier.
`LENDER-0907`	`409` Conflict	This idempotency key already recorded a declaration.
`LENDER-0908`	`403` Forbidden	No validated tenant identity reached the declaration route.
`LENDER-0909`	`503` Service Unavailable	The declaration store is unreachable.
`LENDER-0910`	`422` Unprocessable Entity	No completed re-assessment sweep covers that business date.
`LENDER-0911`	`422` Unprocessable Entity	`businessDate` is not a `YYYY-MM-DD` date.
`LENDER-0912`	`503` Service Unavailable	The deployment has no schedule generator for the Brazilian tax quote.

Brazil loan products

Consignado operations

Loan product lifecycle

Product versions

Product configuration

Floating-rate tables

Document templates

Loan Applications

Credit instruments

Regulatory disclosures and risk

Payoff and prepayment

Account overview and audit

Charges and schedule

Repayments

Transactions

Returned payment receivables

Assignment funds

Assignment sets

Assignment exceptions and registry

Accounting

Portfolio dashboards

Jurisdictions

Tax

Session

Streaming

Error handling

Events

Lender error list

Client errors

Server errors

Error codes

General

Products

Origination

Servicing

Accounting

Assignment of receivables

Audit

Brazil

​Client errors

​Server errors

​Error codes

​General

​Products

​Origination

​Servicing

​Accounting

​Assignment of receivables

​Audit

​Brazil

Client errors

Server errors

Error codes

General

Products

Origination

Servicing

Accounting

Assignment of receivables

Audit

Brazil