> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Declare a qualitative problem-asset assessment > Records an operator's declaration that a contract is, or is not, a problem asset for a qualitative reason under Res. CMN 4.966 art. 3 paragraphs 1 and 2 — the situations that characterise an asset as problematic with no arrears at all. The declaration carries a MANDATORY evidence reference and is immutable: a prior characterisation is withdrawn by declaring the same trigger again with characterizesProblemAsset false and its own evidence, never by deleting. The nightly stage sweep reads the live declarations. ## OpenAPI ````yaml /pt/openapi/v3-current/lender.yaml post /api/v1/br/loan-accounts/{id}/problem-asset-assessments openapi: 3.1.0 info: contact: email: contact@lerian.studio name: Lerian Studio url: https://lerian.studio description: >- Code-first OpenAPI 3.1 surface for the Lender service. Routes that move money are at-most-once per X-Idempotency: when one answers 5xx, the X-Idempotency-Fenced response header says whether that key is now refusing resends (true) or free to retry (false or absent). See docs/contracts/money-route-idempotency.md. license: name: Lerian Studio General License title: Lender API version: 1.0.0 servers: - url: https://lender.sandbox.lerian.net security: - BearerAuth: [] tags: - description: >- Caller session projection: validated subject and effective permissions for the presented token. name: Session - description: >- Ledger accounting operations: journal entries and accrual postings for loan accounts. name: Accounting - description: >- Loan application intake and lifecycle: submission, decisioning, and status. name: LoanApplications - description: >- Loan product catalog: definition, versioning, and activation of lending products. name: LoanProducts - description: >- Loan account servicing operations: balances, schedules, and account-level actions. name: Loan Accounts - description: >- Portfolio dashboard read operations: aggregated portfolio and performance views. name: Dashboard - description: >- Jurisdiction registry: supported jurisdiction profiles and their capabilities. name: Jurisdictions - description: >- Jurisdiction-specific loan application operations (Brazil origination surface). name: Loan Applications - description: >- Tax computation operations for jurisdiction-specific lending (e.g. Brazil IOF). name: Tax - description: >- Brazil consignado privado operations: contract lifecycle, exclusion repair, and compensating adjustments. name: Consignado - description: >- Credit-instrument document template registry: versioned drafting and publication of CCB clausulado. name: DocumentTemplates paths: /api/v1/br/loan-accounts/{id}/problem-asset-assessments: post: tags: - Problem Asset Assessments summary: Declare a qualitative problem-asset assessment description: >- Records an operator's declaration that a contract is, or is not, a problem asset for a qualitative reason under Res. CMN 4.966 art. 3 paragraphs 1 and 2 — the situations that characterise an asset as problematic with no arrears at all. The declaration carries a MANDATORY evidence reference and is immutable: a prior characterisation is withdrawn by declaring the same trigger again with characterizesProblemAsset false and its own evidence, never by deleting. The nightly stage sweep reads the live declarations. operationId: declareLoanAccountProblemAssetAssessment parameters: - description: Loan account (contract) identifier. in: path name: id required: true schema: description: Loan account (contract) identifier. format: uuid type: string - description: >- Canonical idempotency request ID. Required: a declaration changes what the contract is provisioned at, so without a key a retry cannot be told apart from a second characterisation. in: header name: X-Idempotency required: true schema: description: >- Canonical idempotency request ID. Required: a declaration changes what the contract is provisioned at, so without a key a retry cannot be told apart from a second characterisation. type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/DeclareProblemAssetAssessmentHumaBody' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/ProblemAssetAssessmentResponse' description: Created headers: X-Idempotency-Replayed: description: >- "true" when this response replays a request already executed under the same X-Idempotency, so nothing ran a second time and no money moved again. Absent on a first execution. schema: type: string '400': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- The at-most-once contract refused the request before any handler ran: no X-Idempotency header (IDEMPOTENCY_KEY_REQUIRED), a key under a spelling this service does not read (IDEMPOTENCY_KEY_HEADER_UNKNOWN), or a request that could not be scoped to a tenant (IDEMPOTENCY_TENANT_REQUIRED). The code is in the problem document's `code` member. '401': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unauthorized '403': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Forbidden '404': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Not Found '409': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Conflict '422': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Unprocessable Entity '500': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Internal Server Error '503': content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: Service Unavailable default: content: application/problem+json: schema: $ref: '#/components/schemas/Detail' description: >- Any other status this operation may carry, rendered as a problem document — including a refusal produced ahead of the service, such as a gateway or ingress answering on its behalf. components: schemas: DeclareProblemAssetAssessmentHumaBody: additionalProperties: false properties: characterizesProblemAsset: description: >- The verdict. False records that the trigger was evaluated and did NOT characterise the asset — which is how a prior characterisation is withdrawn, and is not the same as never having looked. type: boolean declaredBy: description: >- Declaring subject, used ONLY on a deployment with authentication disabled. When the request carries a validated identity, that subject is recorded and this field is ignored. maxLength: 256 type: string evaluatedOn: description: >- The business day the assessment was made (YYYY-MM-DD). A day and not an instant: it is compared against a competencia, which is a civil day. examples: - '2026-09-30' type: string evidenceNotes: description: >- The assessor's own notes. Optional: the reference is what makes the declaration checkable, the prose is what makes it readable. maxLength: 4096 type: string evidenceReference: description: >- Mandatory pointer to the evidence: a document id, a case number, a URL. Required because this declaration suspends the contract's income recognition and raises its provision, and one that cites nothing cannot be reviewed. examples: - proc-0801234-56.2026.8.26.0100 maxLength: 512 type: string source: description: >- Where the characterisation came from: the credit committee, the bureau feed, the court notice. examples: - Comite de credito 2026-09-30 maxLength: 256 type: string trigger: description: >- The norm article the assessment invokes. Free text because art. 3 par. 2 is an open list ("entre outros"): the console offers the incisos as presets and accepts any other article an assessor names. Stored trimmed and lower-cased, because the article is the identity a later withdrawal has to match: sent as ART_3_P2_III it is stored, returned and withdrawn as art_3_p2_iii. Examples: art_3_p1, art_3_p2_i, art_3_p2_iii, art_3_p2_iv, art_3_p2_vi. examples: - art_3_p2_iii maxLength: 128 type: string required: - trigger - source - evidenceReference - evaluatedOn - characterizesProblemAsset type: object ProblemAssetAssessmentResponse: additionalProperties: false properties: assessmentId: description: Identity of this declaration. type: string characterizesProblemAsset: description: The verdict recorded. type: boolean createdAt: description: When the declaration was recorded (RFC 3339, UTC). type: string declaredBy: description: Authenticated subject that declared it, as free text. type: string evaluatedOn: description: Business day the assessment was made (YYYY-MM-DD). type: string evidenceNotes: description: The assessor's own notes, empty when none were written. type: string evidenceReference: description: Pointer to the evidence behind the declaration. type: string loanAccountId: description: Contract the declaration is about. type: string source: description: Where the characterisation came from. type: string trigger: description: >- The norm article invoked, trimmed and lower-cased. This is the form a withdrawal of this declaration must use. type: string required: - assessmentId - loanAccountId - trigger - source - evidenceReference - evidenceNotes - evaluatedOn - characterizesProblemAsset - declaredBy - createdAt type: object Detail: additionalProperties: true properties: code: description: >- Stable, machine-readable domain error code scoped to the emitting service (format: -NNNN). type: string detail: description: >- A human-readable explanation specific to this occurrence of the problem. examples: - Property foo is required but is missing. type: string errors: description: Optional list of individual error details items: $ref: '#/components/schemas/ErrorDetail' type: - array - 'null' instance: description: >- A URI reference that identifies the specific occurrence of the problem. examples: - https://example.com/error-log/abc123 format: uri type: string status: description: HTTP status code examples: - 400 format: int64 type: integer title: description: >- A short, human-readable summary of the problem type. This value should not change between occurrences of the error. examples: - Bad Request type: string type: default: about:blank description: A URI reference to human-readable documentation for the error. examples: - https://example.com/errors/example format: uri type: string upstream: $ref: '#/components/schemas/Upstream' description: >- RFC 9457 extension member: the error a proxied third-party provider reported. Absent unless the emitting service explicitly surfaced one. type: object ErrorDetail: additionalProperties: false properties: location: description: >- Where the error occurred, e.g. 'body.items[3].tags' or 'path.thing-id' type: string message: description: Error message text type: string value: description: The value at the given location type: object Upstream: additionalProperties: false properties: code: description: The upstream provider's own error code, verbatim. examples: - E4001 type: string message: description: >- The upstream provider's own error message, verbatim (bounded, never its raw response body). examples: - account not found at provider type: string type: object securitySchemes: BearerAuth: bearerFormat: JWT description: JWT bearer token issued by the identity provider. scheme: bearer type: http ````